Stats
Actions
Tags
From psenger-skills
Explores a codebase for architectural friction through the lens of Ousterhout's deep-module principle (small interface, large implementation). Seven-step interactive workflow: an Explore sub-agent navigates the codebase organically — the friction it experiences IS the signal. Surfaces candidate clusters with coupling reasons, call patterns, shared types, dependency categories, and existing tests that a boundary test would replace. User picks what to explore, frames the problem, then 3–4 parallel sub-agents design competing deep-module interfaces. Chosen design becomes a structured RFC action file readable by GitHub MCP or ROVO (Jira) MCP. Use when the user says "arch review", "find shallow modules", "module depth", "deep module", "Ousterhout", "testability audit", "surface coupling", "design interfaces", "RFC issues", or "architectural friction".
How this skill is triggered — by the user, by Claude, or both
Slash command
/psenger-skills:arch-lens [path/to/scope][path/to/scope]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Seven-step interactive architectural review. An Explore sub-agent navigates the
Seven-step interactive architectural review. An Explore sub-agent navigates the codebase the way a developer would — the confusion, file-bouncing, and untestable seams it encounters are the findings. No checklists, no rigid heuristics.
Deep module: small interface surface hiding a large, self-contained implementation. Lets callers test at the boundary. Lets AI agents reason without reading internals.
${CLAUDE_SKILL_DIR}/references/WORKFLOW.md — full step-by-step instructions${CLAUDE_SKILL_DIR}/references/DETECTION-PATTERNS.md${CLAUDE_SKILL_DIR}/references/INTERFACE-DESIGN.md${CLAUDE_SKILL_DIR}/references/RFC-FILE-FORMAT.md| Step | What happens | Requires user input |
|---|---|---|
| 1. Explore | Spawn Explore sub-agent; navigate organically; record friction | — |
| 2. Candidates | Synthesise friction into clusters; present max 8 with full context | — |
| 3. Pick | User selects a cluster and directs the angle | wait |
| 4. Frame | Problem statement, dependency category, blast radius, test boundary today | — |
| 5. Design | Spawn 3–4 parallel sub-agents with competing interface designs | — |
| 6. Choose | User picks interface or accepts recommendation | wait |
| 7. RFC file | Write arch-rfcs-YYYY-MM-DD.md to project root | — |
Full prompt text, cluster format, and step detail: see WORKFLOW.md.
file:line references and a before/after illustration${CLAUDE_SKILL_DIR}/references/WORKFLOW.md${CLAUDE_SKILL_DIR}/references/DETECTION-PATTERNS.md${CLAUDE_SKILL_DIR}/references/INTERFACE-DESIGN.md${CLAUDE_SKILL_DIR}/references/RFC-FILE-FORMAT.mdnpx claudepluginhub psenger/ai-agent-skills --plugin export-vault-noteCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.