Menu
Deep reflection on the skill learning system itself. Analyzes what's working, what's stale, and proposes structural improvements. The meta-skill.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Scaffold a new dashboard chart component with registry, types, and proper theme integration.
Create a new customizable dashboard with its own chart registry, provider, and page. Use when adding dashboards like DRep or SPO dashboard.
Context window conservation rules. Invoke when approaching context limits or before large tasks.
End-of-session automation. Creates a journey and evolves skills based on session learnings.
Run the build and intelligently fix TypeScript errors with guardrails. Stops if fixes introduce more errors or the same error persists after 3 attempts.
Security and quality review of uncommitted changes. Checks for vulnerabilities, code smells, and best practice violations. Use before committing.
| name | reflect |
| updated | "2026-02-04T00:00:00.000Z" |
| description | Deep reflection on the skill learning system itself. Analyzes what's working, what's stale, and proposes structural improvements. The meta-skill. |
| argument-hint | [focus area] |
| user-invocable | true |
| allowed-tools | Read, Edit, Write, Glob, Grep, Bash, AskUserQuestion |
A periodic deep-thinking session about the skill learning system itself. Like a craftsperson stepping back to look at their workshop — not the work, but the tools and how they're organized.
Run this when things feel off, when the system feels heavy, or just periodically to keep skills sharp and lean.
/reflect # Full reflection across everything
/reflect theming # Focus on a specific area
$0 (optional) - Focus area: a skill name, "patterns", "journeys", or "system"Read everything that makes up the learning system:
.claude/skills/*/SKILL.md — All skill definitions
.claude/skills/_patterns.md — Shared cross-cutting knowledge
.claude/skills/wrap-up/SKILL.md — The learning engine
.claude/journeys/*.md — Recent session learnings (last 5-10)
Also check:
updated dates.versions/ history (indicates they've been actively evolved)For each skill, consider:
Every skill loaded into a session consumes tokens. A 500-line skill that's rarely used is expensive. Ask:
_patterns.md? (duplicate = remove from skill)_patterns.md pulling its weight?Compare skill instructions against the actual codebase:
# Check if key files referenced in skills still exist
# Check if import patterns match reality
# Check if component names are current
Look for:
Reflect on whether the system structure is working:
Look at recent journeys and see if the same mistakes keep recurring. If so, the learning loop has a gap — knowledge isn't reaching the right skill.
Use AskUserQuestion to present findings organized by priority:
_patterns.mdFor each finding, propose a specific action:
Apply the changes the user approves. This might include:
_patterns.mdUpdate updated dates on any modified skills.
This is NOT a frequent tool. It's the periodic "sharpen the saw" moment.
This skill exists because learning systems need to learn too.
A carpenter's workshop evolves — tools get reorganized, broken jigs get replaced, the workbench gets adjusted. But the carpenter doesn't reorganize every day. They do it when things feel wrong, or when they step back and see the clutter.
/reflect is that step back.