By dylan
Codebase architecture generator. Creates docs/codebase-architecture.md and .claude/CLAUDE.md by exploring source and asking targeted questions.
A Claude Code plugin marketplace by Dylan.
/plugin marketplace add dylan/claude
Generates codebase architecture docs and enforces architecture-doc-first development.
/plugin install map@dylan
/map skill — Explores your codebase and generates two files:
docs/codebase-architecture.md — File inventory, data flow, state shape, event/API surface, and common task recipes, all with file:line references to actual source.claude/CLAUDE.md — Scaffold with project context and empty wisdom sections that fill in as you workPrompt hook — On any code-change prompt (add, fix, refactor, etc.), reminds Claude to consult and update the architecture doc. If no doc exists, suggests running /map first.
/map does| Section | When included |
|---|---|
| Header | Always — one-sentence description + key tech |
| Commands | Always — build, test, lint, format |
| File Inventory | Always — tables grouped by domain concern |
| Data Flow | Layered processing (web apps, pipelines, event systems) |
| State Shape | Non-trivial state (game servers, real-time, complex frontend) |
| Event/API Surface | External-to-internal mapping (endpoints, events, CLI) |
| Module Relationships | Composition roots, dependency graphs |
| Common Task Guide | Repeatable extension patterns with step-by-step recipes |
file:line pointers over inline codeGPU & Metal expert consultant — researches topics, reviews shader code, and maintains a NotebookLM knowledge base.
/plugin install gpu-expert@dylan
Combines Apple documentation (via sosumi MCP), a persistent NotebookLM knowledge base, and codebase analysis to answer GPU/Metal questions, review Metal code, and research GPU topics — all through the lens of Apple Silicon.
Requirements: sosumi MCP server, notebooklm CLI (authenticated), and the notebooklm-skill Claude Code skill. The skill degrades gracefully if sosumi or NotebookLM is unavailable.
Swift API Design Guidelines enforcer — active whenever you're writing, reviewing, or designing Swift code.
/plugin install swift-api-design@dylan
Enforces the Swift API Design Guidelines at every scope level — public APIs, internal helpers, local functions, closures, tuple members. Calls out violations with the specific guideline broken and a concrete rewrite. No hedging.
What it covers:
Any or unconstrained genericsWhat it doesn't cover: Protocol-oriented design choices, generics architecture, performance, memory management. Guidelines scope only.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub dylan/claude --plugin mapSwift API design reviewer. Enforces Swift API Design Guidelines — naming, argument labels, fluency, documentation, and conventions — across any Swift code at any scope level.
GPU and Metal expert consultant. Researches topics, reviews shader and Metal code, and maintains a NotebookLM knowledge base — all through the lens of Apple Silicon.
Expert Swift API design guidance for naming, argument labels, documentation comments, terminology, and conventions.
Code documentation with automated doc generation, code explanation, and tutorial engineering
Maps and documents codebases of any size using parallel AI subagents
Use this agent when you need to analyze a service or codebase component and create comprehensive documentation in CLAUDE.md files. This agent should be invoked after implementing new services, major refactoring, or when documentation needs updating to reflect the current codebase structure. Examples: <example>Context: The user has just implemented a new authentication service and wants to document it properly. user: 'I just finished implementing the auth service, can you document how it works?' assistant: 'I'll use the codebase-documenter agent to analyze the authentication service and create detailed documentation in CLAUDE.md' <commentary>Since the user has completed a service implementation and needs documentation, use the Task tool to launch the codebase-documenter agent to create comprehensive CLAUDE.md documentation.</commentary></example> <example>Context: The user wants to ensure a newly added API module is properly documented for the team. user: 'We need documentation for the new payment processing API I just added' assistant: 'Let me use the codebase-documenter agent to analyze the payment processing API and create proper documentation' <commentary>The user needs documentation for a new API module, so use the codebase-documenter agent to create CLAUDE.md files with setup instructions and architectural notes.</commentary></example>
Make your AI agent code with your project's architecture, rules, and decisions.
Turn complex codebases into clear, navigable architecture diagrams