principle-foundational-thinking
Originally fromcursor/plugins
Installation
SKILL.md
Foundational Thinking
Get the data shape right before writing logic. Define core types early, trace every access pattern, and choose structures that match the dominant paths. DRY the structure, not every line.
Before sharing state between actors, ask what happens if another actor modifies it concurrently. If the answer is not "nothing", isolate.
Scaffold first. Whatever helps every later phase (CI, tests, shared types) goes first, after removing dead code. Keep commits small and single-purpose.
For module/interface reasoning invoke /codebase-design; for accepted project terminology, relationships, or ownership changes invoke /domain-modeling and reconcile the canonical project artifacts.