psenger/arch-lens
skills/arch-lens/SKILL.md
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".
tools
Updated Apr 18, 2026
$ install --global
skillsauthnpx skillsauth add psenger/ai-agent-skills arch-lensInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 5:00 AM47.4s5 files scanned
SKILL.md
- name:
- arch-lens
- description:
- >
- workflow:
- an Explore sub-agent navigates the codebase organically — the friction it
- allowed-tools:
- Read Grep Glob Write Bash(git *)
- argument-hint:
- [path/to/scope]
- compatibility:
- Requires git for churn analysis. No other external tools required.
Arch Lens
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.
Quick start
- If a path argument is given, scope to that directory; otherwise whole repo
- Load
${CLAUDE_SKILL_DIR}/references/WORKFLOW.md— full step-by-step instructions - Load
${CLAUDE_SKILL_DIR}/references/DETECTION-PATTERNS.md - Load
${CLAUDE_SKILL_DIR}/references/INTERFACE-DESIGN.md - Load
${CLAUDE_SKILL_DIR}/references/RFC-FILE-FORMAT.md - Execute the seven steps in WORKFLOW.md
Workflows
| 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.
Behavioural rules
- Explore agent friction observations are primary evidence — never override with static analysis
- Never propose interface designs before Step 5
- Never advance past Steps 3 or 6 without a user response
- Every RFC must include exact
file:linereferences and a before/after illustration - Name every dependency category explicitly — it determines the testing strategy
- Rank clusters: testability impact first, then cognitive load, then interface stability
Advanced features
- Full workflow detail and Explore agent prompt:
${CLAUDE_SKILL_DIR}/references/WORKFLOW.md - Friction vocabulary and dependency categories:
${CLAUDE_SKILL_DIR}/references/DETECTION-PATTERNS.md - Sub-agent brief template and design constraints:
${CLAUDE_SKILL_DIR}/references/INTERFACE-DESIGN.md - RFC action file format and complete example:
${CLAUDE_SKILL_DIR}/references/RFC-FILE-FORMAT.md
Related Skills
psenger/export-vault-note
testing
VerifiedTrustedCommunity
Exports a single Obsidian vault note and all its linked images into a portable zip or tar.gz archive, preserving vault-root-relative paths so the archive unpacks correctly anywhere. Use only when the user explicitly invokes /export-vault-note.
3SKILL.mdUpdated May 24, 2026
psenger/agent-os-profile-critique
development
VerifiedTrustedCommunity
Provides the audit checklists, severity criteria (blocking/warning/suggestion), and artifact patterns needed to properly review Agent OS profiles and standards. Always invoke this skill before auditing - without it you can only give generic feedback, not structured severity-tagged findings. Invoke when the user pastes a standard and asks if it is good or what is wrong with it; when the user asks to review, audit, validate, or critique an agent-os profile or standard; or when the user mentions "agent-os profile", "agent-os standard", or "my agent-os setup" in a review or validation context.
3SKILL.mdUpdated May 11, 2026
psenger/vault-scribe
development
VerifiedTrustedCommunity
Converts transcripts, video summaries, meeting notes, brainstorming sessions, strategy documents, and rough notes into polished Obsidian-flavored Markdown. Activates when creating or editing notes in an Obsidian vault, generating front matter, applying callout blocks, structuring knowledge base articles, or producing developer-facing guides. Also triggers on mentions of Obsidian, front matter, callout blocks, vault organisation, or requests for GitHub-compatible Markdown documents.
3SKILL.mdUpdated Apr 18, 2026
psenger/git-commit-pr-message
documentation
VerifiedTrustedCommunity
Generate git commit messages, PR titles/descriptions, and changelog entries. Analyzes staged changes, enforces Conventional Commits, scans for sensitive content, links tickets (GitHub Issues / Jira), and updates CHANGELOG.md. Triggers on: "commit", "create a PR", "push", "changelog", "release", or when the user is ready to commit or open a pull request.
3SKILL.mdUpdated Apr 18, 2026