merge: pull design system updates from annie/setup-design-system

Brings in DS component polish (Avatar, Button, Cards, DateBadge, Logo,
SearchBar/Panel, SideBar, Tags, Toggle), new components (Bookmark,
Dropdown, OrgHoverCard), token updates, shared fallbackColors util,
prettier config, and README/CI tweaks.

Conflict resolutions:
- Kept HEAD monorepo layout: all DS code lives under shared/ui,
  apps/dashboard imports via @app/ui barrel.
- Moved annie's root src/components/* + src/utils/* under shared/ui/src/.
- Dropped stray pre-monorepo root files (src/App.tsx, src/main.tsx,
  vite.config.ts) — replaced long ago by apps/dashboard equivalents.
- Rewrote DesignSystem.tsx imports to use @app/ui and @app/ui/assets/*
  subpath; added ./assets/* to shared/ui package exports.
- Extended shared/ui/src/index.ts to re-export Bookmark, Dropdown,
  OrgHoverCard.
- Added lucide-react as peer dep (shared/ui) and dep (apps/dashboard) —
  multiple DS components rely on it.
- Root package.json keeps workspace-dispatch scripts; added prettier
  format / format:check scripts + dev deps.
- Kept Manrope font link addition from previous commit.
- Dropped annie's committed .env (contained a rotated Gemini API key —
  pre-existing leak on source branch, addressed separately). Added
  .env / .env.local to .gitignore.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: megany128

.cursor/rules/frontend/figma.md

@@ -1,7 +1,9 @@
 ## Figma MCP Integration Rules
+
 These rules define how to translate Figma inputs into code for this project and must be followed for every Figma-driven change.
 
 ### Required flow (do not skip)
+
 1. Run get_design_context first to fetch the structured representation for the exact node(s).
 2. If the response is too large or truncated, run get_metadata to get the high‑level node map and then re‑fetch only the required node(s) with get_design_context.
 3. Run get_screenshot for a visual reference of the node variant being implemented.
@@ -10,6 +12,7 @@ These rules define how to translate Figma inputs into code for this project and
 6. Validate against Figma for 1:1 look and behavior before marking complete.
 
 ### Implementation rules
+
 - Treat the Figma MCP output (React + Tailwind) as a representation of design and behavior, not as final code style.
 - Replace Tailwind utility classes with the project’s preferred utilities/design‑system tokens when applicable.
 - Reuse existing components (e.g., buttons, inputs, typography, icon wrappers) instead of duplicating functionality.
@@ -19,7 +22,8 @@ These rules define how to translate Figma inputs into code for this project and
 - Validate the final UI against the Figma screenshot for both look and behavior.
 
 ### Figma MCP server rules
+
   - The Figma MCP server provides an assets endpoint which can serve image and SVG assets
   - IMPORTANT: If the Figma MCP server returns a localhost source for an image or an SVG, use that image or SVG source directly
   - IMPORTANT: DO NOT import/add new icon packages, all the assets should be in the Figma payload
-  - IMPORTANT: do NOT use or create placeholders if a localhost source is provided
+  - IMPORTANT: do NOT use or create placeholders if a localhost source is provided

.github/workflows/ci.yml

@@ -16,3 +16,5 @@ jobs:
         run: bun run type-check
       - name: Lint check
         run: bun run lint
+      - name: Format check
+        run: bun run format:check

.gitignore

@@ -25,3 +25,7 @@ dist-ssr
 
 # AI
 CLAUDE.md
+
+# Env
+.env
+.env.local

.prettierignore

@@ -0,0 +1,4 @@
+node_modules
+dist
+pnpm-lock.yaml
+convex/_generated

.prettierrc

@@ -0,0 +1,8 @@
+{
+  "semi": true,
+  "singleQuote": false,
+  "trailingComma": "all",
+  "printWidth": 80,
+  "tabWidth": 2,
+  "plugins": ["prettier-plugin-tailwindcss"]
+}

README.md

@@ -17,9 +17,9 @@ If you are developing a production application, we recommend updating the config
 
 ```js
 export default defineConfig([
-  globalIgnores(['dist']),
+  globalIgnores(["dist"]),
   {
-    files: ['**/*.{ts,tsx}'],
+    files: ["**/*.{ts,tsx}"],
     extends: [
       // Other configs...
 
@@ -34,40 +34,40 @@ export default defineConfig([
     ],
     languageOptions: {
       parserOptions: {
-        project: ['./tsconfig.node.json', './tsconfig.app.json'],
+        project: ["./tsconfig.node.json", "./tsconfig.app.json"],
         tsconfigRootDir: import.meta.dirname,
       },
       // other options...
     },
   },
-])
+]);
 ```
 
 You can also install [eslint-plugin-react-x](https://github.com/Rel1cx/eslint-react/tree/main/packages/plugins/eslint-plugin-react-x) and [eslint-plugin-react-dom](https://github.com/Rel1cx/eslint-react/tree/main/packages/plugins/eslint-plugin-react-dom) for React-specific lint rules:
 
 ```js
 // eslint.config.js
-import reactX from 'eslint-plugin-react-x'
-import reactDom from 'eslint-plugin-react-dom'
+import reactX from "eslint-plugin-react-x";
+import reactDom from "eslint-plugin-react-dom";
 
 export default defineConfig([
-  globalIgnores(['dist']),
+  globalIgnores(["dist"]),
   {
-    files: ['**/*.{ts,tsx}'],
+    files: ["**/*.{ts,tsx}"],
     extends: [
       // Other configs...
       // Enable lint rules for React
-      reactX.configs['recommended-typescript'],
+      reactX.configs["recommended-typescript"],
       // Enable lint rules for React DOM
       reactDom.configs.recommended,
     ],
     languageOptions: {
       parserOptions: {
-        project: ['./tsconfig.node.json', './tsconfig.app.json'],
+        project: ["./tsconfig.node.json", "./tsconfig.app.json"],
         tsconfigRootDir: import.meta.dirname,
       },
       // other options...
     },
   },
-])
+]);
 ```

ai/data/dummy_data.json

@@ -0,0 +1,92 @@
+[
+  {
+    "listserv": "ACSU",
+    "host": "ACSU",
+    "club": "ACSU",
+    "title": "ACSU Student Faculty Luncheon",
+    "description": "Connect with CS professors and students over lunch with other CS students.",
+    "date": "2026-03-13",
+    "location": "CIS 250 (Young Conference Room)",
+    "tags": ["networking", "cs", "faculty"]
+  },
+  {
+    "listserv": "ACSU",
+    "host": "ACSU",
+    "club": "ACSU",
+    "title": "1:1 Faculty Coffee Chat Week",
+    "description": "Sign up for informal 1:1 chats with professors about research opportunities, careers, and advice.",
+    "date": "2026-03-09",
+    "location": "Various campus locations",
+    "tags": ["research", "mentorship", "coffee"]
+  },
+  {
+    "listserv": "ACSU",
+    "host": "Cornell AppDev & Ramp",
+    "club": "Cornell AppDev",
+    "title": "AppDev x Ramp - HACK→HIRED",
+    "description": "One-day AI-focused hackathon with workshops, prizes, and a chance to interview for a Fall SWE internship at Ramp.",
+    "date": "2026-03-14",
+    "location": "eHub",
+    "tags": ["hackathon", "career", "recruiting", "ai"]
+  },
+  {
+    "listserv": "ACSU",
+    "host": "Citadel GQS",
+    "club": "",
+    "title": "Citadel Global Quantitative Strategies Tech Talk",
+    "description": "Tech talk on quantitative trading careers and how your research skills translate to GQS at Citadel.",
+    "date": "2026-03-17",
+    "location": "Upson 142",
+    "tags": ["finance", "tech-talk", "recruiting"]
+  },
+  {
+    "listserv": "WICC",
+    "host": "WICC",
+    "club": "WICC",
+    "title": "Cracking Your Career (CYC)",
+    "description": "Four-part series on pathways in computing, interviewing, resumes, and standing out in tech roles.",
+    "date": "2026-03-03",
+    "location": "Gates 114",
+    "tags": ["career", "workshop"]
+  },
+  {
+    "listserv": "WICC",
+    "host": "WICC & MathWorks",
+    "club": "WICC",
+    "title": "WICC x MathWorks MATLAB Challenge",
+    "description": "Hands-on MATLAB challenge using MATLAB Copilot with prizes, swag, and info on careers at MathWorks.",
+    "date": "2026-03-16",
+    "location": "Gates G01",
+    "tags": ["workshop", "mathworks", "ai", "swag"]
+  },
+  {
+    "listserv": "WICC",
+    "host": "WICC & Jane Street",
+    "club": "WICC",
+    "title": "WICC x Jane Street Tech Talks",
+    "description": "Talk on predictable communication at scale and Aria, Jane Street's low-latency messaging system, with food and swag.",
+    "date": "2026-03-18",
+    "location": "Phillips 101",
+    "tags": ["talk", "jane-street", "systems"]
+  },
+  {
+    "listserv": "WICC",
+    "host": "External",
+    "club": "",
+    "title": "HackDartmouth XI",
+    "description": "24-hour hackathon at Dartmouth with workshops, prizes, and a Lost In Space theme.",
+    "date": "2026-04-11",
+    "location": "Dartmouth",
+    "tags": ["hackathon", "travel"]
+  },
+  {
+    "listserv": "WICC",
+    "host": "Jane Street",
+    "club": "",
+    "title": "Jane Street FOCUS Program",
+    "description": "Multi-day NYC program for first-year students to explore trading, software development, and strategy at Jane Street.",
+    "date": "2026-05-19",
+    "location": "New York City",
+    "tags": ["program", "first-year", "professional-track"]
+  }
+]

ai/prompts/clubSummary.ts

@@ -0,0 +1,26 @@
+/* eslint-disable @typescript-eslint/no-explicit-any */
+export function clubSummaryPrompt(events: any[]) {
+  return `
+You are writing a very short description of what a student club does, based only on their recent events.
+
+You are given a JSON array called "events". All events belong to the **same club**, with a "club" field that contains its name.
+
+### Your task
+- Write **2–3 concise sentences** (max **70 words total**) describing:
+  - What the club focuses on (e.g. hackathons, career prep, mentorship, theory, community building).
+  - The typical kinds of events they run (talks, workshops, study groups, socials, conferences, etc.).
+  - The community/audience they serve (e.g. CS undergrads, women in computing, international students, etc.).
+- **Start the first sentence with the club name**, taken from the "club" field (e.g. "ACSU is...", "WICC is...").
+- Do **not** mention specific dates, rooms, or one‑off logistics; speak in general patterns.
+- Keep the tone clear and informative; no emojis.
+
+### Style constraints
+- Output **plain text only** (no markdown headings or bullets).
+- Use 2–3 sentences in a single short paragraph.
+
+Here are the events for this club (JSON):
+\`\`\`json
+${JSON.stringify(events, null, 2)}
+\`\`\`
+`;
+}

ai/prompts/weeklySummary.ts

@@ -0,0 +1,48 @@
+/* eslint-disable @typescript-eslint/no-explicit-any */
+export function weeklySummaryPrompt(events: any[]) {
+  return `
+You are generating a concise weekly opportunities digest for a single student.
+
+You are given a JSON array called "events". Each event may look like:
+{
+  "listserv": "ACSU",          // listserv or source that advertised the event
+  "host": "Cornell AppDev",    // primary hosting org or company (may differ from listserv)
+  "title": "AppDev x Ramp - HACK→HIRED",
+  "description": "One‑day hackathon with prizes and recruiting",
+  "date": "2026-03-14",
+  "location": "eHub",
+  "tags": ["hackathon", "career", "recruiting"]
+}
+
+Important:
+- \`listserv\` = who sent/advertised the opportunity (ACSU, WICC, etc.).
+- \`host\` = who is actually running the event (AppDev, Ramp, a company, a conference, etc.).
+Many events are cross‑posted; do not assume the listserv owns the event.
+
+### Your task
+- Write a **compact markdown digest** for this week, **no intro or outro sentences**.
+- **Group events by listserv** using markdown headings based on the \`listserv\` field:
+  - Use a level-3 heading for each listserv that appears, like:
+    - \`### ACSU\`
+    - \`### WICC\`
+    - \`### Cornell\`
+    - \`### Opportunities\`
+- Under each heading, list at most **3 high‑value events** that were advertised on that listserv, chosen for impact (recruiting, hackathons, major talks, strong mentorship/community events).
+- For each event, use **one clean bullet point** in this exact format:
+  - \`- **Title (Mar 14)** – 1‑sentence description that clearly names the **host** or event type, the key value prop, and location if available.\`
+    - Keep each description **under 25 words**.
+- Prefer **hackathons, recruiting, mentorship, and flagship events** over minor or redundant ones.
+- If a listserv has more than 3 events, summarize only the top 3 and ignore the rest.
+
+### Style constraints
+- Output **markdown only** (no code fences).
+- Use only \`###\` headings and \`- \` bullets, nothing else.
+- **No emojis, no unsubscribe text, no calendar links, no greetings or sign‑offs.**
+- **Total digest <= 220 words** across all sections.
+
+Now write the digest based on this JSON:
+\`\`\`json
+${JSON.stringify(events, null, 2)}
+\`\`\`
+`;
+}

ai/summarize.ts

@@ -0,0 +1,14 @@
+import { GoogleGenAI } from "@google/genai";
+
+const ai = new GoogleGenAI({
+  apiKey: process.env.GEMINI_API_KEY,
+});
+
+export async function generateSummary(prompt: string) {
+  const res = await ai.models.generateContent({
+    model: "gemini-2.5-flash",
+    contents: prompt,
+  });
+
+  return res.text;
+}