Agenten stärken
Installation vom Herausgeber. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Noch kein paketiertes Release in der Registry. Folgen Sie der README des Repositorys.
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
A markdown-based framework for implementing rigorous software architecture practices in any project, with specialized AI assistant integration.
This framework provides a structured approach to:
AI-powered architecture documentation framework with ADRs, reviews, and pragmatic mode. Now available as Claude Code Plugin for easiest installation.
For detailed usage instructions, see USAGE.md. For troubleshooting and advanced usage, see TROUBLESHOOTING.md.
Choose the installation method for your AI assistant:
Claude Code supports three installation methods:
Option 1: Claude Code Plugin (Recommended) 🆕
Install via the Claude Code plugin system with automatic updates:
# In Claude Code, run these commands:
/plugin marketplace add codenamev/ai-software-architect
/plugin install ai-software-architect@ai-software-architect
That's it! The framework is now available in all your projects — including the seven skills, MCP server, and generated subagents as a single unit.
See USAGE-WITH-CLAUDE-PLUGIN.md for detailed installation guide, troubleshooting, and comparison with other methods.
Benefits: Simplest installation, automatic updates, works across all projects, no manual file management, ships skills + MCP + hooks as a unit
When to use: You use Claude Code and want the most streamlined experience with automatic updates.
Option 2: MCP Server
npm install -g ai-software-architect
Then register it with Claude Code (claude mcp add ai-software-architect -- mcp), or add it to ~/.claude.json (user scope) or your project's .mcp.json:
{
"mcpServers": {
"ai-software-architect": {
"command": "mcp",
"args": []
}
}
}
The npm package carries the server, not the framework tree: setup_architecture installs from the Claude Code plugin if present, otherwise from a clone named by CLAUDE_PLUGIN_ROOT in the server's env (see mcp/README.md). The other five tools read the project's own .architecture/ and need no framework tree.
Benefits: Programmatic automation, external tool integration, advanced project analysis
When to use: You need programmatic access or integration with other MCP-compatible tools.
Option 3: Traditional Setup
Setup architecture using: https://github.com/codenamev/ai-software-architect
See USAGE-WITH-CLAUDE.md for detailed instructions.
Benefits: No installation required, works immediately, maximum flexibility
When to use: Quick experiments, no installation permissions, or maximum customization needs.
If you're using Cursor, you have two options:
Option 1: MCP Server (Recommended)
npm install -g ai-software-architect
Then configure in Cursor settings (settings.json), pointing CLAUDE_PLUGIN_ROOT at a clone so setup_architecture has a framework tree to install from (Cursor has no Claude Code plugin to fall back on; the other five tools read the project's own .architecture/ once it exists and need no framework tree):
{
"mcp.servers": {
"ai-software-architect": {
"command": "mcp",
"args": [],
"env": { "CLAUDE_PLUGIN_ROOT": "/path/to/ai-software-architect" }
}
}
}
Option 2: Traditional Setup
Setup architecture using @https://github.com/codenamev/ai-software-architect
See USAGE-WITH-CURSOR.md for detailed traditional setup instructions.
MCP Support: GitHub Copilot and Codex currently have limited MCP support. Use the traditional setup method:
Setup architecture using: https://github.com/codenamev/ai-software-architect
See USAGE-WITH-CODEX.md for detailed setup instructions. The framework will be configured with context files that GitHub Copilot and Codex can automatically understand.
Choose the right installation method for your workflow:
Choose Plugin if (Recommended for most Claude Code users):
/plugin update)Choose MCP Server if:
Choose Traditional if:
Legend: ✅ Fully supported, ⚠️ Partially supported, ❌ Not supported, N/A Not applicable
Note: The Plugin bundles the same npm package as the MCP Server option, plus the seven skills, generated subagents, and ADR-validation hook as a single install unit.
Two-tier capability model (see ADR-015): Tier-1 operations are deterministic file/config tasks available on every channel, including the MCP server. Tier-2 capabilities — orchestrated architecture reviews, specialist reviews, and pragmatic enforcement — require LLM reasoning and are delivered only through the plugin/Skills (architecture-review, specialist-review, and the pragmatic-enforcer subagent), not as MCP tools. The Plugin gets Tier 2 via its bundled Skills; an MCP-only install does not.
See Feature Parity Analysis for detailed comparison.
Do you use Claude Code?
├─ Yes → ✅ Choose Plugin (simplest, ships skills + MCP + hooks together)
│
└─ No → Do you use Cursor?
├─ Yes → ✅ Choose MCP Server (Cursor compatible)
└─ No → Choose Traditional (universal — Copilot, Codex, etc.)
Still unsure? Start with Plugin if you use Claude Code. It's the easiest to set up and you can always switch later. All methods provide identical core functionality.
After installation, start using the framework with these standardized commands:
Setup:
Setup ai-software-architect
Create ADR:
Create ADR for [decision topic]
Example: "Create ADR for PostgreSQL database choice"
Architecture Review:
Start architecture review for [version/feature]
Examples: "Start architecture review for version 2.0.0" or "Start architecture review for authentication feature"
Specialist Review:
Ask [Specialist Name] to review [target]
Example: "Ask Security Specialist to review API authentication"
List Members:
List architecture members
Check Status:
What's our architecture status?
Enable Pragmatic Mode (Optional):
Enable pragmatic mode
Example: "Enable pragmatic mode with balanced intensity"
Implement with Methodology:
Implement [feature] as the architects
Examples: "Implement authentication as the architects" or "Implement user registration as the architects"
Recalibration (Traditional method):
Start architecture recalibration for [target]
See USAGE.md for detailed workflow instructions and platform-specific variations.
Already have AI Software Architect installed? Update to get the latest features and improvements.
For any AI assistant, simply ask:
Update the software architect framework from https://github.com/codenamev/ai-software-architect
Your AI assistant will fetch the latest framework files from the main branch while preserving your project's architecture artifacts (ADRs, reviews, recalibration plans).
If using the Claude Code Plugin:
# In Claude Code:
/plugin update ai-software-architect@ai-software-architect
This updates the plugin wrapper and everything it bundles (skills, MCP server, generated subagents, ADR-validation hook) as one unit. The standalone ~/.claude/skills/ copy was retired in 1.4.0 (ADR-012); if you still have one, remove it and install the plugin.
If using MCP Server:
# Update to latest version
npm update -g ai-software-architect
# Or reinstall
npm install -g ai-software-architect
If using Traditional Setup: follow UPGRADE.md. Do not run git fetch / git reset --hard inside .architecture/ — setup removes that directory's .git, so those commands resolve to your own project repository and reset --hard discards your uncommitted work.
Note: Updates preserve your project's custom architecture artifacts (ADRs, reviews, member customizations) while updating framework files (templates, base configuration, scripts).
✅ Updated Files:
.architecture/templates/ - Templates for ADRs, reviews, AGENTS.md.architecture/principles.md - Core architectural principles (if not customized)✅ Preserved Files:
.architecture/decisions/adrs/ - Your architectural decision records.architecture/reviews/ - Your architecture review documents.architecture/recalibration/ - Your recalibration plans.architecture/members.yml - Your customized team members.architecture/config.yml - Your configuration settingsSee UPGRADE.md for detailed upgrade instructions and troubleshooting.
.architecture/
├── decisions/
│ ├── adrs/ # Architectural Decision Records
│ └── principles.md # Architectural principles document
├── reviews/ # Architecture review documents
├── recalibration/ # Recalibration plans and tracking
├── comparisons/ # Version-to-version comparisons
├── docs/ # General architecture documentation
├── agent_docs/ # Detailed AI assistant guidance (progressive disclosure)
├── templates/ # Templates for various documents
└── members.yml # Architecture review team members
This framework is designed to work seamlessly with AI assistants. Each assistant has specialized instructions in the .coding-assistants directory.
For general usage instructions, see USAGE.md.
For Claude Code users, see USAGE-WITH-CLAUDE-PLUGIN.md (recommended plugin-based install) or USAGE-WITH-CLAUDE.md (traditional clone-based path) for detailed instructions.
Available Skills (installed with the Claude Code plugin):
Standard Commands:
Alternative Phrases:
Adding new specialists: edit .architecture/members.yml directly and run node tools/cli.js generate-subagents to refresh the corresponding agents/<id>.md subagent. Auto-creation during specialist-review was removed in 1.5.0 (see ADR-013) — the trade-off keeps the generated subagents and members.yml in sync at all times.
For Cursor users, see USAGE-WITH-CURSOR.md for detailed instructions.
Standard Commands:
Natural Alternatives (Cursor also understands):
Cursor uses .mdc rule files in the .coding-assistants/cursor/ directory to understand the framework.
For GitHub Copilot and OpenAI Codex users, see USAGE-WITH-CODEX.md for detailed instructions.
Natural Language Commands (context-based recognition):
Key Features:
Example Commands:
Support for additional AI assistants can be added by creating appropriate configuration files in the .coding-assistants directory following the established patterns.
The framework incorporates wisdom from influential software architects including Martin Fowler, Sandi Metz, Robert C. Martin, Eric Evans, Sarah Mei, Obie Fernandez, and others. These principles are embedded in the architectural documentation.
Externalizing Senior Thinking: The framework systematically captures "senior engineering thinking"—the invisible architectural reasoning about blast radius, reversibility, timing, and social cost that typically stays undocumented. By forcing explicit documentation of these considerations, we're creating the corpus of senior architectural thinking that the industry lacks.
Architecture reviews consider multiple specialized perspectives:
Pragmatic Mode helps prevent over-engineering by adding a "Pragmatic Enforcer" who:
When to use:
Configurable intensity:
Exemptions for Critical Areas: Pragmatic Mode maintains rigorous standards for:
Enable with:
Enable pragmatic mode
See ADR-002 and Pragmatic Mode Summary for details.
Using with Implementation Guidance: When using both Pragmatic Mode and Implementation Guidance together, pragmatic mode respects your configured security practices and methodological choices while challenging unnecessary complexity in other areas. The pragmatic enforcer ensures implementations remain simple while still following your team's documented standards for security, testing, and code quality.
Configuration-driven implementation that applies your team's methodology and best practices automatically:
Configure once:
implementation:
enabled: true
methodology: "TDD"
influences:
- "Kent Beck - TDD by Example"
- "Sandi Metz - POODR"
- "Martin Fowler - Refactoring"
Then simply say:
Implement authentication as the architects
Benefits:
Supports:
Use with:
Implement [feature] as the architects
¹ Measurement methodology documented in ADR-004 § Validation
See ADR-004 for details.
The framework now supports:
MIT
AI-powered architecture documentation framework with ADRs, reviews, and pragmatic mode. Now available as Claude Code Plugin for easiest installation.
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Ai Software Architect läuft lokal über stdio.
Zuletzt geprüft: 2026-11-10. AI-powered architecture documentation framework with ADRs, reviews, and pragmatic mode. Now available as Claude Code Plugin for easiest installation.
