mcpField
P
principle-foundational-thinking

principle-foundational-thinking

github.com/michael-denyerDevelopment3.7k881 installsUpdated 1d ago
Repository

About principle-foundational-thinking

A development skill for making structural and code-level decisions, with emphasis on data modeling, concurrency, scaffolding, and small increments. It is for developers planning and implementing software changes.

Key features

  1. 01Choose data structures before logic
  2. 02Prefer explicit, simple code
  3. 03Isolate unsafe shared state
  4. 04Build shared scaffolding early
  5. 05Make small, coherent increments

Use cases

  1. 01Model core data before implementing behavior
  2. 02Review whether concurrent state needs isolation
  3. 03Set up CI, linting, tests, and shared types
  4. 04Plan incremental changes with small commits

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/michael-denyer/pstack-claude --skill principle-foundational-thinking

After installing, type/principle-foundational-thinkingin Claude Code to confirm it loaded.

Details

From the project README

Foundational Thinking

Structural decisions protect option value. Code-level decisions protect simplicity.

Data structures first. Get the data shape right before writing logic. Define core types early, trace every access pattern, and choose structures that match the dominant paths.

At code level, DRY the structure, not every line. Types and data models should converge. Three similar statements still beat a premature abstraction. Prefer explicit over clever. Test behavior and edge cases, not line counts.

Concurrency corollary. Before sharing state between actors, ask "what happens if another actor modifies this concurrently?" If not "nothing", isolate.

Scaffold first. If something helps every later phase, do it first. Ask "does every subsequent phase benefit from this existing?" CI, linting, test infrastructure, and shared types are scaffold. Sequence for option value: setup before features, tests before fixes. Keep commits small and single-purpose.

Each increment should land a coherent abstraction or deepen one that exists. Do not spread a new capability across callers as special-case coordination.

Subtraction comes before scaffolding. Remove dead code first, then lay foundations.

Comments

Markdown supported