Fractal Architecture

Apply heuristics from Mark Seemann's "Code That Fits in Your Head" (2021) — fractal architecture, working-memory limits, cyclomatic complexity ceilings, vertical slices, encapsulation through invariants, functional core / imperative shell, checklists, and sustainable software engineering. Use when designing, decomposing, sizing methods/classes, deciding what fits in working memory, or evaluating whether code is sustainable over the long term.

5 stars 2 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill fractal-architecture
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/fractal-architecture ~/.claude/skills/fractal-architecture

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Code That Fits in Your Head (Mark Seemann)

Apply these heuristics when writing or reviewing code, sizing methods and classes, deciding how to decompose a problem, designing APIs, or assessing whether a codebase can be maintained sustainably. The central question is: **"Does this code fit in my head?"** If you can't hold a unit's behavior in working memory, you can't reason about it confidently.

## Core Philosophy

**Software engineering is a craft constrained by human cognition.** The limits of working memory — not language features, not paradigms — are the binding constraint on code quality.

**Code is read far more than written, and reasoning about it is the most expensive activity.** Optimize the reading experience first; the writing will follow.

**Sustainable code preserves the team's ability to keep changing it.** Speed today that destroys speed tomorrow is not engineering, it is borrowing.

**Heuristics over rules.** Seemann offers numeric thresholds (7±2, ≤ 80 chars, CC ≤ 7), but they are starting points — defaults to deviate from with reason, not laws to obey blindly.

---

## Working Memory: The Binding Constraint

Miller's law (1956): humans hold roughly **7 ± 2 chunks** in working memory at once. Cowan (2001) refined this to about **4 ± 1** for unrelated items.

Implications for code:
Read the full skill on GitHub

Details

Skill name
fractal-architecture
Path
plugins/engineering-practices/skills/fractal-architecture/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Fractal Architecture skill do?

Apply heuristics from Mark Seemann's "Code That Fits in Your Head" (2021) — fractal architecture, working-memory limits, cyclomatic complexity ceilings, vertical slices, encapsulation through invariants, functional core / imperative shell, checklists, and sustainable software engineering. Use when designing, decomposing, sizing methods/classes, deciding what fits in working memory, or evaluating whether code is sustainable over the long term.

How do I install the Fractal Architecture skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Fractal Architecture popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Grok

5

bolasblack/claude-skills

xAI Grok second opinion via the grok CLI — three modes. Review: independent diff review with a pass/fail gate. Challenge: adversarial pass that tries to break the code. Consult: ask Grok anything, with session continuity for follow-ups. Use when the user says "grok review", "grok challenge", "ask grok", or wants a second opinion from Grok.

Software Development

Flow Efficiency

5

vnovakovits/claude-skills

Apply Niklas Modig & Pär Åhlström's flow-efficiency framework from "This is Lean — Resolving the Efficiency Paradox" (2012). Covers the central paradox (resource efficiency vs flow efficiency), the efficiency matrix, Kingman's formula and why high utilization destroys flow, the three laws of process dynamics (Little's Law, the law of bottlenecks, the law of variation), the "variation × utilization" killer combination, lean as an operational strategy not a tool, and the diagnostic vocabulary for explaining why "keeping everyone busy" actively harms delivery. Use when a team is busy but not ship

Software Development

Guardrails

5

bolasblack/claude-skills

Rendered guardrail framework: keep a repo's hard rules in one-rule-per-file GRL sources behind a compact router, and render only the rules a task needs. Use when gathering guardrail context before implementing or reviewing code, when creating, editing, retiring, or reviewing GRL rule files or .agents/guardrails/index.md, when running the guardrails CLI (validate, render, review-metadata, next-id), or when setting up, adopting, or bootstrapping a guardrail framework in a repo that does not have one yet. Do NOT use for ordinary lint rule authoring unless the lint rule backs a guardrail, for runt

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.