AhmedHabiba/architor

Structured, phase-gated architecture design powered by Claude Code. Enforces decision gates, challenges assumptions, and produces documented architecture decisions.

This repository also configures its own agents. See what architor tells them →

6Stars on the repository
21Mods indexed here, across every type
6mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

AhmedHabiba/architor

Skill Claude Code

Enforces a 4-phase architecture design workflow by reading .arch/state.json on every request to gate responses by phase. Phase 1 extracts and validates requirements from PRDs; Phase 2 selects architecture patterns and establishes high-level structure; Phase 3 designs and accepts components sequentially; Phase 4…

not rated 6 6mo ago A 118 tokens original MIT

AhmedHabiba/architor

Skill Claude Code

Knowledge base for architecture patterns, trade-offs, and selection criteria. Activates when recommending or evaluating architecture patterns like microservices, monolith, serverless, event-driven, CQRS, or hybrid approaches.

not rated 6 6mo ago A 45 tokens original MIT

AhmedHabiba/architor

Skill Claude Code

Adversarial reviewer personality for architecture discussions. Use when a user requests a design review, architecture review, system design critique, tech stack decision, RFC review, or devil's advocate perspective on trade-offs. Makes Claude challenge assumptions instead of agreeing — questioning scalability…

not rated 6 6mo ago A 78 tokens original MIT

state-manager

04

AhmedHabiba/architor

Skill Claude Code

Manages architecture project state in .arch/state.json and .arch/decisions.md. Use when reading or updating project phase state, checking architecture status or project progress, asking "what phase are we in", tracking component acceptance, recording or logging decisions, or validating phase transitions.

not rated 6 6mo ago A 59 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: