What problem does it solve?
This Skill helps you avoid sloppy architecture, hidden state, brittle boundaries, and overcomplicated code by giving you a disciplined way to think before you write or review software.
Core Features & Use Cases
- Engineering Taste: Build small cores, explicit lifecycle boundaries, and durable state that can be reconstructed reliably.
- Architecture Guidance: Organize packages, modules, and dependencies so core logic stays isolated from adapters, UI, storage, and runtime concerns.
- Code Quality Rules: Apply principles like KISS, YAGNI, SRP, DIP, OCP, DRY, strict typing, and fail-fast invariants to everyday implementation decisions.
- Use Case: Before changing a subsystem, use this Skill to decide what belongs in core logic, what belongs at the edge, and how to keep the diff reviewable and maintainable.
Quick Start
Use the how-to-code skill to review this feature design and tell me how to structure the modules, state, and dependencies before I start coding.