mcpField
P
principle-foundational-thinking

principle-foundational-thinking

github.com/mariusflorescuDevelopment18117 installsUpdated 2w ago
Repository

About principle-foundational-thinking

A foundational-thinking principle skill for software engineers making structural and code-level decisions. It emphasizes choosing data shapes early, keeping code explicit and simple, and sequencing shared foundations before features.

Key features

  1. 01Choose data structures before logic
  2. 02Favor explicit, simple code
  3. 03Test behavior and edge cases
  4. 04Isolate state when concurrency requires it
  5. 05Build shared foundations before features

Use cases

  1. 01Selecting core types before implementation
  2. 02Deciding whether concurrent state needs isolation
  3. 03Sequencing tests and infrastructure ahead of features

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mariusflorescu/pstack-t3 --skill principle-foundational-thinking

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

Bundled filesagents/openai.yaml

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