code-style
49Cursor rule Cursor
Code style conventions (formatting, in-code naming, structure) — loaded on demand for code work, not every chat.
Cursor rule Cursor
Code style conventions (formatting, in-code naming, structure) — loaded on demand for code work, not every chat.
Cursor rule Cursor
Error handling patterns — no silent catches, typed errors, errors at the edges — loaded on demand for code work.
Cursor rule Cursor
Performance requirements — budgets, measurement, avoid premature optimization — loaded on demand when performance matters.
Cursor rule Cursor
Testing requirements — what must be tested, coverage floors, unit vs integration vs E2e — loaded on demand for code work.
Cursor rule Cursor
GitHub repo hygiene — security policy, CI, rulesets, Releases vs a releases/ folder — load when changing .github/ or community files.
Cursor rule Cursor
Explain AI git co-authorship (Cursor/etc.), prevent it, and remove it safely.
Cursor rule Cursor
Ask when unclear; never guess requirements or product truth.
Cursor rule Cursor
Terse responses with full technical substance (default full intensity).
Cursor rule Cursor
Always enhance user prompts internally before acting (auto/self mode) -- install only with enhance-prompt-auto setup.
Cursor rule Cursor needs its repo
Folder and file naming, layout, grouping; fix legacy paths only with permission.
Cursor rule Cursor
Git setup, Conventional Commits, backups, and commit/push only with user permission.
Cursor rule Cursor
Safe refactors—moves, renames, and splitting code; update all references before removing the old.
Cursor rule Cursor
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
Cursor rule Cursor
Read and update project context after every task when context exists.
Cursor rule Cursor
Observability requirements — structured logs, spans, metrics on new endpoints — loaded on demand for ops-sensitive work.
Cursor rule Cursor
Prompt quality rules - clarity, precision, scope, output format, measurability, must-nots - loaded on demand for prompt engineering or when building new agent instructions.
Cursor rule Cursor
Security requirements — input validation at trust boundaries, secret handling, auth — loaded on demand for security-sensitive work.
Skill Claude CodeCodex
Run an accessibility audit — keyboard nav, ARIA, contrast, focus, labels, landmarks — and report gaps against WCAG 2.2 AA. Reports, does not auto-fix. Automation-first; asks only for the target surface. Use whenever the user wants an accessibility audit, a WCAG check, or runs /a11y, or after building any UI component.
Skill Claude CodeCodex
Think through what you are about to build like a senior engineer before writing any code. Surfaces decisions, aligns on language, and produces a clear implementation plan written to context/plan.md. Automation-first — answers its own questions from the context system and only surfaces genuinely blocking decisions. Use…
Skill Claude CodeCodex
Run a focused tech-debt cleanup pass — dead code, duplicate helpers, stale deps, unused exports, drift from conventions — and produce a safe, ordered removal plan. Automation-first; asks only before destructive removals. Use whenever the user wants a cleanup pass, to reduce tech debt, or runs /cleanup. Distinct from…
Skill Claude CodeCodex
Scaffold and continuously improve a project's shared context system — a context/ folder plus AGENTS.md, CLAUDE.md, and README.md — so AI agents build within a defined, accurate, modern structure instead of improvising. Self-improving; every run and every use makes the context more detailed and more true.…
Skill Claude CodeCodex
After building any UI component, extract the visual patterns that matter for consistency and save them to context/memory/ui-registry.md, so every component built afterward matches what came before. Uses context/design-system.md (tokens, rules) as the standard and context/design/ as the reference. Runs automatically…
Skill Claude CodeCodex
Write a postmortem from an incident timeline and contributing factors — timeline, impact, root cause, contributing factors, action items with owners. Automation-first; asks only when the timeline is unclear. Use whenever the user wants to write a postmortem, an incident report, or runs /postmortem, after /recover has…
Skill Claude CodeCodex
When something goes wrong during a build, diagnose what type of failure it is before deciding how to respond — targeted fix, hard reset, or full rethink. Uses the context system to tell a local bug apart from a polluted session or a wrong foundation, and routes a rethink back through /architect. Automation-first …
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: