Cursor rule Cursor
Guidelines for using hello world artifacts. This rule establishes standards that the hello-world skill and command follow. Demonstrates how rules provide persistent guidance that skills and commands reference.
Cursor rule Cursor
Decision framework for creating artifacts. Use when analyzing patterns to determine whether to create a rule, skill, command, or subagent, and how to organize it.
Cursor rule Cursor
When creating automations (workflows that combine multiple steps), decompose into discrete skills (the 'how') then package them into commands (the 'when' and order). Do not implement multi-step automations as a single bespoke command or skill.
Cursor rule Cursor
When git commit times out because the pre-commit or git hook is still running (e.g. full test suite), retry with an extended timeout; never use --no-verify.
Cursor rule Cursor
Rules for maintaining cross-references between artifacts and documentation. Use when creating artifacts, updating documentation, or maintaining reference integrity.
Cursor rule Cursor
When working on data modeling, fixtures, seeds, migrations, or test data, default to one canonical database path that both runtime and tests use.
Cursor rule Cursor
Rules for documentation standards and keeping documentation in sync with artifacts. Use when creating or updating documentation.
Cursor rule Cursor
Prefer a demonstrable slice before adding infrastructure. Use when planning features, phases, or tasks so the first deliverable is something that can be shown, not only 'the platform is in place'.
Cursor rule Cursor
Rules for maintaining clean, organized repository structure. Use when organizing artifacts, creating categories, or maintaining directory structure.
Cursor rule Cursor
When fixing a CI or reported failure, reproduce the failure locally with the same command as CI before applying the fix; then verify the fix. Do not fix from logs alone.
Cursor rule Cursor
Do not declare work complete until you have run the stated verification (e.g. tests, smoke test, plan step) and reported the result. Use when implementing plans, completing tasks, or summarizing deliverables.
Cursor rule Cursor
You Aren't Gonna Need It. Don't add abstraction, schema, or generic infrastructure until at least two concrete use cases need it. Use when designing or reviewing plans and code.
Cursor rule Cursor
Self-improvement guidelines for learning from mistakes, adapting to feedback, and continuously improving code quality and responses.
Cursor rule Cursor
This repository is a standalone project. All Cursor rules, skills, and commands live in .cursor/. Optional: symlink for global share, or run scripts/install-self-improvement.sh to copy the self-improvement bundle into another project.