principle-foundational-thinking

What problem does it solve? Developers often write logic before settling core data structures, leading to late-stage rewrites, premature abstractions, and unsafe shared state between concurrent actors. This Skill provides a decision framework to apply before coding so foundational choices keep options open. ## 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: Orders work so CI, linting, test infrastructure, and shared types land before features, with small single-purpose commits. - Concurrency Corollary: Requires asking what happens if another actor modifies shared state concurrently, and isolating state when the answer is not nothing. - Use Case: Before implementing a new feature module, apply this principle to choose the core data model, subtract dead code, and lay test scaffolding so downstream implementation becomes obvious. ## Quick Start Apply the foundational thinking principle to review my planned data structures and work sequencing before I start implementing this feature.