principle-foundational-thinking

What problem does it solve? Codebases often accumulate premature abstractions, poorly chosen data structures, and unsafe shared state because structural decisions are made after logic is already written. This Skill provides a decision framework to apply before coding so downstream implementation 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 starting a new feature, apply this Skill to decide the core data model, sequence setup work ahead of feature work, and remove dead code before adding scaffolding. ## Quick Start Apply the foundational thinking principles to review my planned data model and work sequence before I start implementing this feature.