Cognitive Kernel — Development skill for Claude Code
6-layer intervention framework for cognitive bases — structural enforcement over procedural rules.
How to install Cognitive Kernel
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open d-wwei/cognitive-kernel and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Cognitive Kernel does
6-layer intervention framework for cognitive bases — structural enforcement over procedural rules.
Alternatives in Development
- Cs2 Knife — Create a high-fidelity procedural Three.js 3D reconstruction of 14.1k ★
- Claudes C Compiler — Claude Opus 4.6 wrote a dependency-free C compiler in Rust, with backends targeting x86 (64- and 32-bit), ARM 2.6k ★
- Haft — Engineering decisions engine that know when they're stale 1.4k ★
README
[English](README.md) | [中文](README.zh.md)
Cognitive Kernel
**Rules don't enforce themselves.**
One cognitive base, 30 lines of rules, injected into `CLAUDE.md` — it works. The agent's thinking changes. You can see it in the output.
Now install 19 bases. That's 720+ lines of rules, 100+ individual instructions, all competing for the agent's attention in the same context window. What happens? The same thing that happens when you tape 100 checklists to a wall — nobody reads any of them. The agent's attention gets diluted. Critical rules get skipped. The cognitive bases you installed are technically "active" but functionally invisible.
Why Text Rules Fail
Writing "you must do X" in a config file is the weakest possible intervention. It depends entirely on the agent noticing the rule, at the right moment, under cognitive load. That's like depending on a factory worker reading a safety poster while operating heavy machinery.
The 6-layer model replaces hope with structure. Instead of one mechanism (text in a file), each rule is enforced through the strongest viable channel:
| Layer | Mechanism | Strength | How It Works |
|---|---|---|---|
| L1 | Output templates | Strongest | Agent's response must include specific fields — structurally incomplete without them |
| L2 | Hooks | Strong | Platform hooks auto-inject reminders before key actions — agent gets intercepted |
| L3 | If-Then triggers | Medium | Pattern-matched rules fire automatically — no willpower needed |
| L4 | External verification | Strong | A separate sub-agent reviews the work adversarially — self-checking doesn't work |
| L5 | Core rules | Weak | A few critical rules stay in context — always visible, but still voluntary |
| L6 | Skill reference | Weakest | Full framework loaded on demand — agent has to choose to read it |
**The key insight:** L1 and L2 are structural — the agent cannot produce valid output without complying. L5 and L6 are vol
Related Skills
Run Evals
Replay the regression corpus inside THIS interactive session — no headless, no API key (ADR 0003). Required be
Claude Code System 3 Thinking
Implementation of System 3 (meta-cognitive layer) from the Sophia paper as a Claude Code extension for persist
Claude Dev Framework
Universal development discipline enforcement framework for Claude Code — hooks, rules, profiles, cross-project
Forge Install Rules
Install ValidationForge rules to .claude/rules/ for cross-session enforcement
Enforcement Contradiction Rules
Always-on. When the enforcement system itself produces contradictions — gates blocking their own prerequisites
Glass Atrium Ops Orchestrator
Orchestrator-specific rules — delegation enforcement · team composition · delegation communication · Wave Exec
Related Agents
Team Surfacer
Materials/surfacing builder in a directing-agent-teams project: physically based materials (PBR), wear, grime,
Lateral Thinker
Subconscious subagent that surfaces cross-disciplinary structural parallels from the Vestige memory graph. Inv
Polymathic Davinci
Reasons through Leonardo da Vinci's cognitive architecture — saper vedere (knowing how to see), mechanism-hunt