armckinney/dev-essentials
Core personal development workflow, visual explanations, documentation standards, and engineering guardrails
Guides validation-driven personal development workflows: clarifying material ambiguities, defining validations before implementation, keeping diffs minimal, and verifying results with direct evidence. Use when starting a feature, bugfix, refactor, or pre-commit check.
Enforces concise, accurate code comments, docstrings, and repository documentation while keeping architectural SDLC docs cleanly separated when Gyrus is active. Use when writing or updating docs, comments, or READMEs.
Structures technical explanations using Mermaid diagrams, Markdown tables, and concise bullet points instead of walls of prose. Use when explaining a codebase, architecture, multi-step flow, debugging root cause, or PR/diff.