architecture
v0.10.0Uses Ousterhout's deep-module lens to scan an existing codebase for module-level architecture friction: shallow modules, seam leaks, and locality gaps. Presents candidates as a self-contained HTML report, then runs an interview loop on the selected candidate before handing off for planning. Also charts a repository and the systems it references as a C4 system landscape plus an application-portfolio table, committing the result as a record that later runs check for drift, and records an architecture decision into the repository's existing ADR convention.
By Melodic SoftwareLicense: MIT18 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 24, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install architecture for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install architecture-4@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/melodic-software/claude-code-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/architecture/.
Plugin files
├── .claude-plugin/plugin.json├── skills/map-landscape/SKILL.md├── skills/record-decision/SKILL.md└── skills/setup/SKILL.md
Included Skills3
Chart a repository and the systems it references as a C4 System Landscape plus an application-portfolio table: extract typed reference edges and portfolio facts from tested scripts, commit the result as a landscape record, report drift against it, and render both artifacts into the declared architecture home. Use when: 'map our landscape', 'system landscape', 'what systems do we have', 'what does this repo depend on', 'application portfolio', 'who owns which repo', 'what runtimes are we on', 'chart our repositories', 'C4 context across repos', 'inventory our systems', 'has our landscape drifted'. Skip when: the question is module-level structure inside one codebase (shallow modules, seam placement) which is /architecture:improve, fleet cleanup (stale branches, orphaned worktrees) which is /repo-fleet-hygiene:audit, org settings which is /github:audit, or doc-versus-code drift inside one repository which is /codebase-health:audit.
Record an architecture decision into the repository's existing ADR convention: discovers the ADR directory, numbering scheme, and record shape in use and writes one record that follows them; when no convention exists it names what it searched, offers common shapes, and writes nothing until the human chooses. Use when: 'record this decision', 'write an ADR', 'architecture decision record', 'capture this decision', 'document why we chose X', or after a design handoff or interview resolves a decision worth keeping. Skip when: the decision is easily reversed and unsurprising (no ADR earned), or the ask is supersession, an index, or status lifecycle beyond what the convention already defines.
Verify and converge the architecture plugin's consumer configuration: the convention-home binding, and the architecture topic doc declaring where landscape and portfolio artifacts land (architecture_dir) and which landscape dialect to emit (landscape_dialect). Use when: 'set up architecture', 'where should the landscape go', 'declare our architecture directory', 'map-landscape says there is no architecture home', 'switch the landscape dialect to structurizr', before a first /architecture:map-landscape run in a repository, or after changing the convention home. Actions: check (read-only), apply (writes the pointer region and topic doc, on explicit request).
Plugin manifests1
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "architecture",
"version": "0.10.0",
"description": "Uses Ousterhout's deep-module lens to scan an existing codebase for module-level architecture friction: shallow modules, seam leaks, and locality gaps. Presents candidates as a self-contained HTML report, then runs an interview loop on the selected candidate before handing off for planning. Also charts a repository and the systems it references as a C4 system landscape plus an application-portfolio table, committing the result as a record that later runs check for drift, and records an architecture decision into the repository's existing ADR convention.",
"author": {
"name": "Melodic Software",
"email": "[email protected]"
},
"license": "MIT",
"keywords": [
"architecture",
"refactoring",
"deep-modules",
"ousterhout",
"module-design",
"testability",
"c4",
"landscape",
"portfolio",
"adr",
"decision-record",
"skill"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[architecture on Agent Plugins Marketplace](https://pluginsmp.com/plugins/architecture-4)