principle-foundational-thinking

What problem does it solve? Codebases often accumulate fragile abstractions and premature complexity because structural decisions are made reactively. This Skill provides a decision framework to apply before writing logic, so core types, data structures, and work sequencing are chosen deliberately and downstream code becomes obvious. ## Core Features & Use Cases - Data Structures First: Prompts you to define core types early, trace access patterns, and match structures to dominant code paths. - Scaffold Sequencing: Directs you to build CI, linting, test infrastructure, and shared types before features, keeping commits small and single-purpose. - Concurrency Corollary: Requires asking what happens when another actor modifies shared state, and isolating state when the answer is not "nothing". - Use Case: Before implementing a new service module, apply this Skill to decide the core data model, confirm test scaffolding exists, and verify no shared mutable state crosses actor boundaries. ## Quick Start Apply the foundational thinking principles to review my planned data model and work sequence before I start implementing this feature.