principle-foundational-thinking
From the author
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 backnotprop/pstack --skill principle-foundational-thinking -a claude-code
Installs to .claude/skills/principle-foundational-thinking/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 90
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- fpf-problem-solvingCodeAlive-AI/ai-driven-developmentUse First Principles Framework (FPF) to decompose problems, architect systems, evaluate alternatives, define quality, qualify and develop methods, initiate inquiry from ordinary work, disambiguate agent-relative instructions, steer or resume work, surface applicable methods, coordinate development states, bridge domain terms, screen mandatory steps, compare configurations, probe capability, decide under uncertainty, reconsider decisions after their basis changes, establish causality, control-loop reasoning, reason about time, synthesize ontologies, govern ontic admission, publish views, revalidate sources, select representations, use checklists, and appraise advice. Triggers: FPF, bounded contexts, SoTA packs, assurance calculus, decision theory, operational parsimony, causal/temporal reasoning, architecture, modularity, transformation flows, structural adequacy, cultural evolution, lexical discipline, Parts A-I. Not for simple task planning, general philosophy, or Agile unrelated to FPF.Planning★ 167
- think-before-codingDevelopersGlobal/ai-agent-skillsForces explicit reasoning before writing any code. Surfaces assumptions, manages confusion, and prevents hallucination by demanding clarity upfront.Engineering★ 216
- design-firstrohitg00/skillkitGuides the creation of technical design documents before writing code, producing architecture diagrams, data models, API interface definitions, implementation plans, and multi-option trade-off analyses. Use when the user asks to plan a feature, architect a system, design an API, explore implementation approaches, or requests a technical design or spec before coding — especially for complex features involving multiple components, ambiguous requirements, or significant architectural changes.Design★ 1.6K
- brainstormingforyourhealth111-pixel/Vibe-SkillsYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.Planning★ 3.8K
- architecture-foundationmajiayu000/spellbookDesign architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.Planning★ 288
- architecture-feature-firstevanca/flutter-ai-rulesUse when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.Planning★ 663
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in