codebase-fit-skills
Maps the repo using docs/ADVANCED_BUSINESS.md and docs/ADVANCED_TECHNICAL.md first, then code, to propose and author project-scoped skills and rules under .cursor/. Use when bootstrapping skills, refr
SKILL.md.cursor/skills/codebase-fit-skills/SKILL.md
GitHubCodebase-fit project skills (Wengz)
Goal
Turn what is documented and true in the repo into small, discoverable skills under .cursor/skills/<name>/SKILL.md and keep .cursor/rules/*.mdc as short distillations. Agents should default to Wengz conventions (credits, roles, locales, tRPC) instead of generic patterns.
Canon: docs/ADVANCED_BUSINESS.md → docs/ADVANCED_TECHNICAL.md → src/lib/error-handler.ts / notifications/ / roles.ts. See also .cursor/README.md.
Current skill inventory
| Skill | Trigger |
|---|---|
wengz-domain-workflows |
Request lifecycle, multi-role dashboards, SLA, contact leaks |
wengz-credits-payments |
Packages, subscriptions, proofs, wallet, withdrawals |
wengz-notifications-locale |
Email / in-app / SSE locale |
codebase-fit-skills |
This meta skill — refresh config from docs |
When to use
- User asks to study the codebase and create/refresh project skills or rules.
- Large refactor of
src/app/,src/server/, orprisma/. - Workflows diverge from
docs/*.md.
Storage rule
- Project skills:
.cursor/skills/<skill-name>/SKILL.md(committed). - Do not put project-specific skills in
~/.cursor/skills-cursor/.
Phase 1 — Map (read-only)
docs/ADVANCED_BUSINESS.mddocs/ADVANCED_TECHNICAL.md- Messaging:
error-handler,notifications/,messages/ - Code:
package.json,prisma/schema.prisma, routers, dashboards - Existing
.cursor/rules/**and.cursor/skills/**
Phase 2 — Choose candidates
Prefer one skill per fragile workflow. Skip mega-skills that paste ADVANCED docs — link instead.
Phase 3 — Author
- Name: lowercase hyphens, max 64 chars.
- Description: third person, WHAT + WHEN, trigger terms.
- Body: steps + real paths + doc links; keep under ~500 lines.
- Update
.cursor/README.mdinventory when adding/removing skills. - Keep always-apply rules short; put depth in skills.
Phase 4 — Verify
- Descriptions have clear triggers
- Paths and doc filenames real
- No duplicate skills; cross-link related ones
- Rules do not contradict ADVANCED docs
Output when analysis-only
- Short inventory grounded in ADVANCED docs
- Proposed skill/rule list
- Highest-leverage next file
Implement files when the user confirms or explicitly asks to create/update config.