diff --git a/skills/changelog/LICENSE.txt b/skills/changelog/LICENSE.txt new file mode 100644 index 000000000..1b521ea83 --- /dev/null +++ b/skills/changelog/LICENSE.txt @@ -0,0 +1,13 @@ +Apache License 2.0 + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. diff --git a/skills/changelog/SKILL.md b/skills/changelog/SKILL.md new file mode 100644 index 000000000..b9d8f1bf0 --- /dev/null +++ b/skills/changelog/SKILL.md @@ -0,0 +1,98 @@ +--- +name: changelog +description: Generate a weekly changelog card for Twitter/X. Reads git log, distills the work into 6 punchy items, fills an HTML template, and opens it in the browser. Use when writing changelogs, weekly updates, or social media posts about shipped work. +license: Apache-2.0 +--- + + +Generate the weekly changelog Twitter card. Run every Friday (or whenever you ship). + +## Steps + +### 1. Get this week's commits +```bash +git log --oneline --since="7 days ago" +``` + +Get the stats: +```bash +# Commit count +git log --oneline --since="7 days ago" | wc -l + +# Files + lines changed +git log --since="7 days ago" --pretty=tformat: --numstat | awk '{files++; add+=$1; del+=$2} END {print files " files · " add+del " lines"}' +``` + +### 2. Understand what actually shipped +Read each commit message. For any that are unclear, look at the diff: +```bash +git show [commit-hash] --stat +``` +Group commits into themes. Ignore pure refactors, dependency bumps, and test fixes — users don't care. Focus on what changed for them. + +### 3. Distill into exactly 6 items +Each item needs: +- **An emoji** that fits the work (✨ new feature, 🐛 fix, ⚡ performance, 🎨 design, 🔒 security, etc.) +- **A short title** — 3-5 words, lowercase, punchy +- **2-3 lines of body** — explain the user benefit, not the technical detail. Write like a human, not a release note. "credits update in real time" not "implemented shared zustand store for credit synchronisation." + +If fewer than 6 meaningful things shipped, combine small related items or include one "under the hood" item about stability/performance. + +### 4. Find or create the changelog template +Look for a `changelogs/` directory in the repo. If there's a `template.html`, use it. + +If no template exists, create `changelogs/template.html` with this structure: +```html + + + + + + + +
what shipped this week · MONTH DAY
+
+
EMOJI

TITLE

BODY LINE 1
BODY LINE 2
BODY LINE 3

+ +
+
N commits · N files · N lines · all live
+ + +``` + +### 5. Create this week's file +Create `changelogs/YYYY-MM-DD.html` (use today's date). + +Fill in: +- Header date (e.g. "what shipped this week · march 1") +- All 6 items +- Footer stats from step 1 + +### 6. Open in browser +```bash +open changelogs/YYYY-MM-DD.html +``` + +Tell the user: "ready — screenshot the browser window (⌘+Shift+4 on Mac) and post it." + +## Voice +Lowercase. Direct. No buzzwords. User benefit first, technical detail never. If you can't explain the value to a non-engineer in one line, rewrite it. + +## Design rule +If using an existing template — never touch the CSS. Content only. The design is locked. diff --git a/skills/cold-email/LICENSE.txt b/skills/cold-email/LICENSE.txt new file mode 100644 index 000000000..1b521ea83 --- /dev/null +++ b/skills/cold-email/LICENSE.txt @@ -0,0 +1,13 @@ +Apache License 2.0 + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. diff --git a/skills/cold-email/SKILL.md b/skills/cold-email/SKILL.md new file mode 100644 index 000000000..fb781846f --- /dev/null +++ b/skills/cold-email/SKILL.md @@ -0,0 +1,127 @@ +--- +name: cold-email +description: Write cold emails that actually get responses. Strict 2-4 sentence formula for investors, employers, mentors, partners. Use when drafting outreach emails, investor emails, or any professional cold outreach. +license: Apache-2.0 +--- + + +# Cold Email Generator + +Write ultra-short, specific, bold cold emails that get responses. Output directly in chat. + +## Required Information + +Before writing, gather these from user (prompt if missing): + +1. **Recipient** — Name, role, company +2. **Your credentials** — Past wins, numbers, notable affiliations (user provides rough draft) +3. **Your ask** — What you want (user provides) +4. **Hook context** — Something recent/specific about recipient (auto-research or user provides) + +## The Formula (strict) + +Every email follows this structure: + +``` +Subject: [Short, casual, specific] + +Hey [FirstName], + +[Specific hook - what prompted this email RIGHT NOW] (1 sentence) + +[Your credibility with concrete details] (1 sentence) + +[Clear ask with specific time/topic] (1 sentence) + +[Name] +``` + +**Total: 2-4 sentences maximum. No signature block.** + +## Email Types (auto-select based on context) + +| Type | Key Elements | +|------|--------------| +| **Advice/Mentorship** | Reference their experience, state your situation briefly, ask for specific time | +| **Investor Outreach** | Reference relevant investment, traction with numbers, "would love to tell you more" | +| **Job/Internship** | Reference role/company, one-line achievement, specific skill match | +| **Partnership** | What you do + impressive client/number, specific value prop for them | +| **Paid Consulting** | Offer to pay, reference their specific expertise, clear time ask | + +## Subject Line Rules + +**Good:** Short, casual, specific +- "Quick question [Name]" +- "[Name] - quick ask" +- "Re: [thing they posted about]" +- Just their first name + +**Bad:** Formal, long, generic +- "Seeking Your Valuable Mentorship" +- "Introduction from an Aspiring Entrepreneur" +- Anything with "touching base" + +## Voice Rules + +### DO +- Be ultra-specific — "I saw your LinkedIn post about your angel group" not "I admire your work" +- Lead with recent context — Reference something from THIS WEEK if possible +- State concrete credentials — Numbers, past wins, notable companies +- Make a clear ask — "20 min call about X" not "pick your brain" +- Write casual — Like texting, not applying to grad school +- Be bold — Not the time for modesty +- Offer value when possible — "Would love to pay you for an hour" + +### DON'T +- "I'd love to pick your brain" +- "I hope this email finds you well" +- Generic compliments without specifics +- Long paragraphs about your background +- Vague asks like "get coffee sometime" +- Being overly humble or apologetic +- Professional email signatures +- More than 4 sentences + +## Editing Checklist + +Before outputting, verify: + +- [ ] 2-4 sentences max? +- [ ] Specific and recent hook? +- [ ] Credibility with numbers/names? +- [ ] Crystal clear ask? +- [ ] Casual tone (would send to a friend)? +- [ ] No filler words? +- [ ] No generic phrases? +- [ ] Short casual subject line? +- [ ] No email signature? + +## Workflow + +1. Check what info user provided +2. Prompt for any missing required info (recipient, credentials, ask) +3. Auto-select email type based on context +4. Research/craft specific hook (recent post, news, mutual connection) +5. Draft email following the formula +6. Edit ruthlessly — cut everything that doesn't add value +7. Output email directly in chat + +## Follow-Up Template + +If user needs a follow-up (3-5 days after no response): + +``` +Subject: Re: [original subject] + +Hey [Name], + +Following up on this - let me know if you're interested! + +[Name] +``` + +**One follow-up max.** + +## Detailed Guide + +For full examples and advanced tactics, see [references/guide.md](references/guide.md). diff --git a/skills/cold-email/references/guide.md b/skills/cold-email/references/guide.md new file mode 100644 index 000000000..9c4a24d21 --- /dev/null +++ b/skills/cold-email/references/guide.md @@ -0,0 +1,278 @@ +# Cold Email Guide + +Complete reference with examples and advanced tactics. + +## Real Examples That Worked + +### Example 1: Snapchat Intern (Evan Spiegel responded in 10 mins) + +**Subject:** Internship + +``` +Hey, my name's Niraj Pant. + +I understand your time is valuable. I'll only write three bullet points. + +Programming since 8th grade. + +Have most experience working in Java/Obj-C/Android/iOS. + +Want to intern for Snapchat this summer as a high school junior. How? + +Thanks, +Niraj +``` + +**Why it worked:** Ultra brief, concrete skills, clear ask, bold confidence. + +--- + +### Example 2: Paid Consulting Ask + +**Subject:** lovable is calling + +``` +Hi Farza + +Long time fan, first time messenger. I'm a growth engineer at Lovable.dev - we're one of the worlds hottest AI startups right now (0-$17M ARR in ~2 months with a team of 17). + +Would love to pay you for an hour of brainstorming on how we could take our marketing to the next level - because i remember buildspace's marketing was top frigging notch. + +Looking forward to hearing back from you + +Best +``` + +**Why it worked:** Specific hook (buildspace's marketing), impressive credentials with numbers, offered to PAY, casual tone. + +--- + +### Example 3: Angel Investor Pitch + +**Subject:** angels + +``` +Hey Ben, + +I saw your LinkedIn post about your angel group! + +I'm Joshua, previously co-founded swell.is (raised $25M, grew to millions in rev, thousands of users). + +In early 2022 I left Swell to go all in on AI, workshopping ideas w/ friends & investors... + +Now, I'm excited to share what I'm building... teamed up with another VC-backed founder and we're raising an angel-only pre-seed for a project in AI/ecom. + +If you're up for it, would love to tell you more about it! + +Joshua +``` + +**Why it worked:** Timely hook (recent post), massive credibility ($25M raised), clear ask, builds intrigue. + +--- + +### Example 4: Research Request (Elon Musk said yes) + +**Subject:** Re: Stanford University students (MS&E) writing a paper for Tesla + +``` +Dear Mr. Musk, + +I am a graduate student at the Department of Management Science and Engineering and for the purposes of a class (MS&E 270 - Strategy in Technology Base Companies - Professor Kathleen Eisenhardt) along with another 3 graduate students we are working on a writing a paper about Tesla Motors corporate strategy... + +Since you are the founder and Chairman of Tesla Motors, it would be great if we could conduct a short interview (in person, live or send you some questions) with you in the course of the following two weeks... + +I am aware of the fact that you may receive dozens of similar requests at a daily basis. That's why we will do our best to make this class assignment of ours a useful and entertaining experience for you and your company's execs... + +Nikolaos Bonatsos +``` + +**Elon's response:** "Ok, if you can limit the meeting to 20 mins and schedule for late evening." + +**Why it worked:** Academic legitimacy, acknowledged time constraints, offered value (recommendations, NDA), respectful but confident, clear specific ask. + +--- + +### Example 5: High School Founder (Mark Cuban responded) + +**Subject:** MCF AI Bootcamp Alumni reaching out instead of studying + +``` +Hey Mark, + +I'm currently a high school student who uses AI a LOT and went to your bootcamp a while back. + +My experience with your foundation inspired me to delve deeper into how nonprofits and philanthropy operate. That's when I started my company, UNHRD, where we catalog transactions and initiatives on-chain using Ethereum for foundations and nonprofits. + +So there's + +1. Reduced administrative costs and overhead +2. Enhanced trust among stakeholders +3. Tamper-proof records that are private yet verifiable +4. Accelerated global reach and collaboration + +We're in beta, backed by Arbitrum, and partnered with brands like Forbes on their web3 initiatives. + +I'd love to have you on our cap table and receive some of your advice! + +I'll get back to studying, +Richard +``` + +**Mark Cuban's response:** "What is the utility of it" + +**Why it worked:** Got a billionaire to respond! Initiative (high schooler building), concrete details (Arbitrum, Forbes), personal connection (his bootcamp). + +--- + +## Templates by Situation + +### Advice (Career Pivot) + +``` +Subject: Quick question [Name] + +Hey [Name], + +Saw your post about leaving [BigCo] to start [Startup]. + +I'm [current role] at [company] with [specific achievement], thinking about making a similar move. + +Could I get 15 mins to ask about how you made the decision? + +[Your name] +``` + +### Investor Outreach + +``` +Subject: [Name] - raising [amount] + +Hey [Name], + +I saw you invested in [relevant company]. + +I'm building [your company] - [one line description with traction]. + +Raising a $[X] [round type] from [investor types]. Would love to tell you more. + +[Your name] +``` + +### Job/Internship + +``` +Subject: [Role] at [Company] + +Hey [Name], + +Saw you're hiring for [role]. + +I [specific relevant experience/achievement in one line]. + +[Specific skill/project that matches their need]. Would love to chat. + +[Your name] +``` + +### Partnership/Collaboration + +``` +Subject: [Company A] + [Company B] + +Hey [Name], + +I run [your company] - we [what you do] for [impressive client/number]. + +I think we could [specific value prop for them]. + +Would love 20 mins to explore. + +[Your name] +``` + +--- + +## Advanced Tactics + +### Extra Research Approach + +Show you did homework: +- "One of your fb posts popped up in my feed over Easter by the way - Oliver had shared some great tips" +- "I remember buildspace's marketing was top frigging notch" +- Reference something obscure they did + +### Social Proof Drop + +Mention impressive people/companies casually: +- "we're used by Oktopost, Trivia, and Chili Piper" +- "backed by Arbitrum, partnered with Forbes" +- "45 people in our angel investing group of current/former Notion team members" + +### Value Exchange + +Offer something: +- "Would love to pay you for an hour" +- "Happy to introduce you to [relevant person]" +- "We could help with [thing they need]" + +### Predicted Response Tactic + +Show you understand they're busy: +- "I understand your time is valuable. I'll only write three bullet points." +- Preemptively address objections + +--- + +## Common Mistakes & Fixes + +### Too Much Context + +**Bad:** +``` +I'm reaching out because I've been following your work for years and I really admire what you've built. I'm currently working on a startup in the AI space and we're trying to figure out our go-to-market strategy... +``` + +**Good:** +``` +I saw your post about B2B growth tactics. + +I'm building an AI tool for sales teams (backed by a16z, $500K MRR in 3 months). + +Could I get 15 mins to ask about your outbound playbook? +``` + +### Vague Ask + +**Bad:** "Would love to pick your brain sometime" + +**Good:** "Would love 20 mins next Tuesday to ask about your fundraising process" + +### Self-Deprecating + +**Bad:** "I know you're incredibly busy and important, so I understand if you can't respond..." + +**Good:** "Would love to pay you for an hour of your time" + +### Generic Hook + +**Bad:** "I've been following your work and find it inspiring" + +**Good:** "I saw your thread about AI coding tools got 500K views yesterday" + +--- + +## The Mindset + +**Think like this:** +- Reaching out peer-to-peer, not supplicant to king +- Your time is valuable too +- Rejection is fine — they're just one person +- Volume matters — send 10, not 1 +- Be bold — worst they can say is no + +**Not like this:** +- "I hope I'm not bothering you" +- "I know you're incredibly busy" +- Over-explaining why you're worthy +- Apologizing for reaching out diff --git a/skills/deploy-check/LICENSE.txt b/skills/deploy-check/LICENSE.txt new file mode 100644 index 000000000..1b521ea83 --- /dev/null +++ b/skills/deploy-check/LICENSE.txt @@ -0,0 +1,13 @@ +Apache License 2.0 + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. diff --git a/skills/deploy-check/SKILL.md b/skills/deploy-check/SKILL.md new file mode 100644 index 000000000..db75aee48 --- /dev/null +++ b/skills/deploy-check/SKILL.md @@ -0,0 +1,75 @@ +--- +name: deploy-check +description: Pre-flight check before pushing to production. Catches TypeScript errors, accidentally staged secrets, pending migrations, and hygiene gaps. Use when about to deploy, push to production, or merge to main branch. +license: Apache-2.0 +--- + + +Run a pre-flight check before pushing to production. Works with any stack. + +## Steps + +### 1. Check what's being pushed +```bash +git status +git diff origin/main...HEAD --stat +git log origin/main..HEAD --oneline +``` +Show the user: "X commits, Y files about to go live." List the commit messages so they can see at a glance what's shipping. + +### 2. TypeScript check (if applicable) +Look for `tsconfig.json` in the repo. If found: +```bash +npx tsc --noEmit +``` +Run from the directory that contains `tsconfig.json` (could be root or a `frontend/` subfolder — check first). + +If errors: list every error with file + line number. Do NOT recommend pushing until fixed. +If no TypeScript in project: skip this step and note it. + +### 3. Check for accidentally staged secrets +```bash +git diff --cached --name-only | grep -iE '\.env|secret|key|credential|token|password' +``` +If ANY file matches: STOP. Warn loudly. Never let secrets get committed. + +Also check unstaged changes: +```bash +git diff --name-only | grep -iE '\.env' +``` + +### 4. Dependency / schema changes +- Look for migration files (common patterns: `migrations/`, `schema.sql`, `*.migration.ts`, `db/migrate/`). If any changed since last commit, remind user to run migrations before deploying. +- Check `package.json`, `requirements.txt`, `go.mod`, `Cargo.toml` — if dependencies changed, flag which ones are new so user can confirm they're available in the production environment. +- If new environment variables appear in the diff (search for `os.getenv`, `process.env`, `ENV[`), list them and ask: are these set in your production environment? + +### 5. Hygiene reminders (not blockers) +Read the commit messages and changed files, then surface these as gentle reminders: + +- **Changelog / release notes**: Did anything user-visible ship (new feature, fix, UI change)? If yes, remind them to update their changelog. +- **README**: Did the setup steps, architecture, or env vars change? If yes, remind them to update the README. +- **Docs / API docs**: If new endpoints were added, remind them to document them. + +These do NOT block the push. Just surface them. + +### 6. Output the verdict + +**Green:** +``` +✅ TypeScript: no errors +✅ No secrets staged +✅ No migrations pending +✅ Dependencies: no new packages +📝 Changelog: [reminded / not needed] +→ safe to push +``` + +**Red:** +``` +❌ TypeScript: 3 errors — fix these first + src/auth.ts:42 — Property 'user' does not exist on type 'Session' +⚠️ .env.local is staged — remove it before committing +⚠️ schema.sql changed — run migrations in prod first +📝 2 new env vars in diff — confirm they're set in production +→ fix blockers before pushing +``` diff --git a/skills/economics/LICENSE.txt b/skills/economics/LICENSE.txt new file mode 100644 index 000000000..1b521ea83 --- /dev/null +++ b/skills/economics/LICENSE.txt @@ -0,0 +1,13 @@ +Apache License 2.0 + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. diff --git a/skills/economics/SKILL.md b/skills/economics/SKILL.md new file mode 100644 index 000000000..233485287 --- /dev/null +++ b/skills/economics/SKILL.md @@ -0,0 +1,80 @@ +--- +name: economics +description: Calculate unit economics for your AI product. Revenue per action, API cost per action, gross margin, and free tier damage. Use when model pricing changes, rethinking credit pricing, or evaluating profitability. +license: Apache-2.0 +--- + + +Calculate the current unit economics for your AI product. + +## Steps + +### 1. Get pricing from the codebase +Search for credit/pricing constants: +```bash +grep -rn "CREDIT\|credit_cost\|COST\|FREE_CREDITS\|signup_bonus\|price\|PRICE" --include="*.py" --include="*.ts" -i +``` + +Find: +- How much users pay (e.g. $5 = 100 credits → $0.05/credit) +- How many credits each action costs (generation, image, regen, etc.) +- How many free credits new users get on signup + +### 2. Get current model pricing +Search the web for current pricing for every model you use. Common ones to look up: +- OpenAI: `site:openai.com pricing` +- Anthropic: `site:anthropic.com pricing` +- Google Gemini: `site:ai.google.dev pricing` + +Get input $/1M tokens, output $/1M tokens, and image generation cost if applicable. + +### 3. Estimate tokens per action +Make reasonable assumptions based on your prompts (or read the actual prompt files): +- A typical text generation call: X input tokens, Y output tokens +- An embedding call: Z tokens +- An image generation: flat cost per image + +If you can find the actual prompts in the codebase, read them and estimate more precisely. + +### 4. Calculate cost per action +For each user-facing action: +``` +API cost = (input_tokens / 1M × input_price) + (output_tokens / 1M × output_price) +Revenue = credits_charged × price_per_credit +Margin = (revenue - api_cost) / revenue × 100 +``` + +### 5. Output the table + +``` +UNIT ECONOMICS — [your product] +════════════════════════════════════════════════════════════════ +USER PRICING + [price] = [credits] credits → $X.XX per credit + Signup bonus: [N] free credits + +ACTION ECONOMICS +──────────────────────────────────────────────────────────────── +Action Credits Revenue API Cost Margin +──────────────────────────────────────────────────────────────── +[action name] [N] $X.XX $X.XXX XX% +[action name] [N] $X.XX $X.XXX XX% +──────────────────────────────────────────────────────────────── + +FREE TIER DAMAGE (N signup credits) + Conservative user: costs you ~$X.XX + Typical user: costs you ~$X.XX + Heavy user: costs you ~$X.XX + +PAYBACK POINT + One paying user covers ~X non-converting free users +════════════════════════════════════════════════════════════════ +``` + +### 6. Flag anything concerning +- Any action with margin below 50% — flag it prominently +- Free tier cost above $1 per signup — flag it +- If a model price changed since this was last run, call it out + +### 7. Pricing sensitivity (if asked) +Show what margins look like at ±20% credit price. Helps decide whether to change pricing without rebuilding the whole spreadsheet. diff --git a/skills/model-audit/LICENSE.txt b/skills/model-audit/LICENSE.txt new file mode 100644 index 000000000..1b521ea83 --- /dev/null +++ b/skills/model-audit/LICENSE.txt @@ -0,0 +1,13 @@ +Apache License 2.0 + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. diff --git a/skills/model-audit/SKILL.md b/skills/model-audit/SKILL.md new file mode 100644 index 000000000..88ade32b2 --- /dev/null +++ b/skills/model-audit/SKILL.md @@ -0,0 +1,65 @@ +--- +name: model-audit +description: Print the complete AI model routing table for your product. Every AI call, what model it actually uses, and the cost per call. Use when touching AI models, changing providers, or reviewing API costs. +license: Apache-2.0 +--- + + +Audit every AI model call in the codebase and output a complete routing table. + +## Steps + +### 1. Find the model config +Search for where models are configured. Common patterns: +```bash +grep -r "gpt-4\|claude\|gemini\|anthropic\|openai" --include="*.py" --include="*.ts" --include="*.js" -l +grep -r "MODEL\|model_config\|AI_MODEL\|LLM" --include="*.py" --include="*.ts" -l +``` +Read those files. Understand the alias → actual model name mapping. +Example: an alias `"fast"` might map to `"gpt-4o-mini"`, an alias `"quality"` to `"claude-opus-4-6"`. + +### 2. Find every AI call in the codebase +Search for API call patterns: +```bash +grep -rn "\.chat\.completions\.create\|anthropic\.messages\|genai\.\|\.generate\|embeddings\.create" --include="*.py" --include="*.ts" --include="*.js" +``` +Also search for your specific client/wrapper function names found in step 1. + +For each call, note: +- Which feature/endpoint triggers it +- Which model alias or model name is passed +- Roughly what it does (generation, embedding, classification, etc.) + +### 3. Cross-reference alias → actual model name +Using the config from step 1, resolve every alias to the real model name being sent to the API. + +### 4. Look for unused model configs +Any model configured but never called from a user-facing feature? Flag it. + +### 5. Output the routing table + +``` +AI MODEL ROUTING — [your product name] +════════════════════════════════════════════════════════════════ +FEATURE ALIAS/KEY ACTUAL MODEL +──────────────────────────────────────────────────────────────── +[feature name] [alias] [real model name] +[feature name] [alias] [real model name] +... +════════════════════════════════════════════════════════════════ + +UNUSED CONFIG (defined but never called from frontend): + [alias] → [model name] + +FLAGS: + ⚠️ [anything unexpected, deprecated models, mismatches] +``` + +### 6. Flag problems +- Any alias pointing to a model that's been deprecated or renamed +- Any feature using an expensive model where a cheaper one would work +- Any hardcoded model names scattered around the codebase instead of going through the central config (these are the ones that don't get updated when you change models) +- Inconsistency: same task using different models in different places + +### 7. If the user asks for recommendations +Suggest where swapping to a cheaper/faster model would have low risk (simple tasks, high volume, latency-sensitive) and where quality matters more (user-facing generation, complex reasoning).