Layered Reasoning
Structures thinking across multiple abstraction levels (30,000 ft strategic, 3,000 ft tactical, 300 ft operational) while maintaining consistency between layers. Guides through top-down decomposition, bottom-up aggregation, cross-layer translation, and constraint propagation. Use when reasoning across multiple abstraction levels, designing systems with hierarchical layers, explaining concepts at different depths, maintaining consistency between principles and implementation, or when users mention 30,000-foot view, layered thinking, abstraction levels, top-down design, or strategy-to-execution
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill layered-reasoninggit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/layered-reasoning ~/.claude/skills/layered-reasoningPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Layered Reasoning --- ## Common Patterns ### Pattern 1: 30K → 3K → 300 ft Decomposition (Top-Down) **When**: Starting from vision/principles, deriving concrete actions **Structure**: - **30,000 ft (Strategic)**: Why? Core principles, invariants, constraints (e.g., "Customer privacy is non-negotiable") - **3,000 ft (Tactical)**: What? Approaches, architectures, policies (e.g., "Zero-trust security model, end-to-end encryption") - **300 ft (Operational)**: How? Specific actions, procedures, code (e.g., "Implement AES-256 encryption for data at rest") **Example**: Product strategy - **30K**: "Become the most trusted platform" (principle) - **3K**: "Achieve SOC 2 compliance, publish security reports, 24/7 support" (tactics) - **300 ft**: "Implement MFA, conduct quarterly audits, hire 5 support engineers" (actions) **Process**: (1) Define strategic layer invariants, (2) Derive tactical options that satisfy invariants, (3) Select tactics, (4) Design operational procedures implementing tactics, (5) Validate operational layer doesn't violate strategic constraints ### Pattern 2: Bottom-Up Aggregation **When**: Starting from observations/data, building up to principles **Structure**: - **300 ft**: Specific observations, measurements, incidents (e.g., "User A clicked 5 times, User B abandoned") - **3,000 ft**: Patterns, trends, categories (e.g., "40% abandon at checkout, slow load times correlate with abandonment")
Details
- Skill name
layered-reasoning- Repository
- lyndonkl/claude
- Path
skills/layered-reasoning/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Layered Reasoning skill do?
Structures thinking across multiple abstraction levels (30,000 ft strategic, 3,000 ft tactical, 300 ft operational) while maintaining consistency between layers. Guides through top-down decomposition, bottom-up aggregation, cross-layer translation, and constraint propagation. Use when reasoning across multiple abstraction levels, designing systems with hierarchical layers, explaining concepts at different depths, maintaining consistency between principles and implementation, or when users mention 30,000-foot view, layered thinking, abstraction levels, top-down design, or strategy-to-execution
How do I install the Layered Reasoning skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Layered Reasoning popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Linkedin Post Rewrite
200lyndonkl/claude
Rewrites a published substacker essay as a LinkedIn post with a hook fitting the 210-char fold, practitioner framing (less confessional than Substack), short 2-3 line paragraphs, and 0-2 niche hashtags. 900-2500 characters. Emits linkedin-post.md. Use as the LinkedIn-native arm of the Distribution Translator. Trigger keywords — LinkedIn post, LinkedIn rewrite, practitioner, professional network, niche hashtags.
Identify Kill List
200lyndonkl/claude
Names what the substacker writer should stop doing — habits with no evidence of use, goals that became theatre, sections with 2 consecutive dormant quarters, and agents in the team whose output the writer ignores. Produces a bulleted list, each item with one sentence of why. Max 4 items. Ordered by ease (easiest first). Used once per Growth Strategist review. Trigger keywords — kill list, stop doing, what to cut, dead habits, dormant, ignored output.
Market Mechanics Betting
200lyndonkl/claude
Translates beliefs (probabilities) into optimal actions (bet/pass/hedge) using quantitative frameworks including edge calculation, Kelly Criterion bet sizing, forecast extremizing, and Brier score optimization. Use when converting probabilities into decisions, calculating edge against market odds, sizing bets optimally, extremizing aggregated forecasts, improving Brier scores, or when user mentions betting strategy, Kelly Criterion, edge calculation, Brier score, extremizing, or translating belief into action.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.