What problem does it solve?
Engineers often jump into writing logic before settling core data structures, leading to premature abstractions, late-stage rewrites, and concurrency bugs. This Skill provides a decision framework for making foundational choices early, when they are cheap to change.
Core Features & Use Cases
- Data Structures First: Prompts you to define core types, trace access patterns, and choose structures matching dominant code paths before writing logic.
- Scaffold Sequencing: Orders work so CI, linting, test infrastructure, and shared types land before features, keeping commits small and single-purpose.
- Concurrency Check: Asks what happens when another actor modifies shared state, and isolates state when the answer is not "nothing".
- Use Case: Before starting a new service, apply this Skill to decide the core data model, sequence scaffolding work, and identify shared-state risks so downstream code becomes obvious.
Quick Start
Apply the foundational thinking principles to review my planned data structures and work sequencing before I start implementing this feature.