principle-foundational-thinking

What problem does it solve? Engineers often jump into writing logic before settling core data structures, leading to premature abstractions, late-stage rewrites, and unsafe shared state. This Skill provides a decision framework to apply before coding so foundational choices keep options open. ## Core Features & Use Cases - Data-Structure-First Reasoning: Define core types early, trace access patterns, and match structures to dominant code paths. - Scaffold Sequencing: Order work so CI, linting, test infrastructure, and shared types land before features, keeping commits small and single-purpose. - Concurrency Check: Ask what happens when another actor modifies shared state, and isolate when the answer is not "nothing". - Use Case: Before implementing a new service module, use this Skill to decide the core data model, sequence test infrastructure ahead of features, and verify no shared mutable state crosses actor boundaries. ## Quick Start Apply the foundational thinking principles to review my planned data structures and work sequencing before I start implementing this feature.