All skills
Each entry is a standalone playbook. Open one for full Markdown—principles, workflows, and checklists you can paste into agent rules or Cursor skills.
Showing 6 of 6
domain-modularization
Organizes code into domain modules (capabilities) instead of only technical layers; splits large files, keeps public vs internal boundaries, and reduces scattered domain logic. Use when restructuring a codebase, planning module layout, refactoring for maintainability, or when navigation and ownership by business capability are unclear.
Read skill →
housekeeping-docs
Keeps repositories tidy and documentation aligned with the real implementation—structure, naming, dead code and temp artifacts, and root docs (README, SPEC, TODO, ARCHITECTURE). Use when the user asks for housekeeping, repo cleanup, doc sync, documentation alignment, hygiene, or maintaining spec-driven project files.
Read skill →
lean-implementation
Guides lean, direct implementations by removing redundancy and dead code, avoiding unnecessary abstraction, and favoring readability over cleverness. Use when implementing features, refactoring, simplifying code, removing unused code, or when the user asks for minimal, maintainable, or proportionate solutions.
Read skill →
round-trip-testing
Verifies processing, migration, and conversion through realistic end-to-end round-trip cases—fixture input, run pipeline, compare to explicit expected output, iterate until stable. Use when validating transforms preserve meaning/structure, when adding migration or format conversion confidence, or when the user mentions round-trip tests, golden files, E2E data processing, or compatibility regressions.
Read skill →
test-to-completion
Verifies implemented work with sufficient tests, runs the relevant suites after changes and fixes, and blocks completion until tests pass. Use when implementing features, fixing bugs, refactoring, or when the user asks to finish, ship, or mark work complete; also when tests are missing, failing, or need regression coverage.
Read skill →
ui-backend-integration
Wires UI to real application logic and exposes domain capabilities through clear interfaces; handles loading, success, and error states. Use when building or reviewing end-to-end features, removing placeholder UI, surfacing backend capabilities in the UI, connecting forms and APIs, or verifying integrated user flows.
Read skill →