Principle Foundational Thinking
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
Install
npx skills add Dimon94/skills --skill principle-foundational-thinkinggit clone --depth 1 https://github.com/Dimon94/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/principle-foundational-thinking ~/.claude/skills/principle-foundational-thinkingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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.
Details
- Skill name
principle-foundational-thinking- Repository
- Dimon94/skills
- Path
skills/principle-foundational-thinking/SKILL.md- Repo updated
- 18 November 2026
- Copies
- Found in 3 GitHub repos
FAQ
What does the Principle Foundational Thinking skill do?
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
How do I install the Principle Foundational Thinking skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dimon94/skills --skill principle-foundational-thinking. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Principle Foundational Thinking popular?
It lives in Dimon94/skills, which has 107 GitHub stars and 21 forks, and is included in 2 curated skill lists.
Related skills
Maintain Verification Skill
107Dimon94/skills
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
Create Verification Skill
107Dimon94/skills
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
How
107Dimon94/skills
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
Principle Separate Before Serializing Shared State
107Dimon94/skills
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
Principle Encode Lessons in Structure
107Dimon94/skills
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
Content Tone Adjuster
260cafe3310/public-agent-skills
调整内容风格,提供「cafe3310 的移除 AI 常用滥用表达风格」「移除大词风格」「hexiecs 的极简直白风」「学术研究风(去公司战役感)」四种方向
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.