The full pipeline from idea to production. Every step exists because skipping it caused a bug.
Research β Plan β Test β Code β Review β Push
Not Code β Maybe Test β Push β Fix in Prod.
Before writing ANY code:
- Search for existing solutions β GitHub, npm, PyPI, crates.io
- Read the docs β don't guess at API behavior
- Check for prior art β someone probably solved this already
- Prefer battle-tested libraries over hand-rolled solutions
- If you find an 80% match, fork/wrap it β don't rewrite from scratch
For any task that takes more than 30 minutes:
- Write down what you're building (1-3 sentences)
- List the files you'll change
- Identify dependencies and risks
- Break into phases if complex
See testing.md for the full TDD workflow.
- Follow coding-style.md
- Follow security.md
- Small commits, each one compiles and passes tests
After writing code, review it yourself:
- Read every line of the diff
- Check for security issues
- Check for performance issues
- Check for edge cases
- Would a new team member understand this code?
See git-workflow.md for commit/PR conventions. The security hooks in this repo automate the pre-push checks.