agentsclimarketplace

Architecture methodology

Skill AhmedHabiba/architor/templates/claude/skills/architecture-methodology

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

Install
npx -y skills add AhmedHabiba/architor --skill architecture-methodology

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Enforces 4-phase architecture design workflow. Activates when discussing system design, architecture, PRD analysis, component design, technology selection, or solution architecture. Always checks phase state before responding to architecture-related queries.

SKILL.md

2.5 KB, as published. Nobody here has run it

Architecture Methodology Orchestrator

When This Skill Activates

Any conversation about system architecture, technology choices, component design, PRD analysis, or solution design.

Before Every Architecture-Related Response

  1. Read .arch/state.json
  2. Determine if the user's request is appropriate for the current phase
  3. If out-of-phase, redirect firmly but helpfully

Phase Boundary Enforcement

Cannot discuss in Phase 1 (Evaluation):

  • Specific technology recommendations
  • Component design details
  • Architecture patterns → Redirect: "Let's finish evaluating the requirements first. Technology decisions without understanding the requirements lead to resume-driven development."

Cannot discuss in Phase 2 (Methodology):

  • Individual component implementation details
  • Specific API contracts or data schemas
  • Detailed technology configurations → Redirect: "We're deciding the big picture right now. Component details come in Phase 3. Let's make sure the overall structure is right first."

Cannot skip in Phase 3 (Components):

  • Cannot accept Component N+1 before Component N is accepted
  • Cannot jump to finalization with pending components → Redirect: "Component [X] needs to be accepted first. Each component builds on previous decisions."

Anti-Pattern Detection

Watch for and flag these throughout ALL phases:

  • "We'll figure it out later" → "That's a risk we should quantify now. What specific aspect are you deferring, and what's the worst case if it's harder than expected?"

  • Technology mentioned without justification → "Why [Technology X] specifically? What alternatives did you consider? How does it fit your team's experience?"

  • Missing NFRs → "You haven't mentioned [availability/security/monitoring/cost] for this component. In production, this will matter. Let's address it now."

  • Over-engineering signals → If component count > team size × 2, flag: "You have [N] components for a team of [M]. Each component adds operational overhead. Can any be consolidated?"

  • Copy-paste architecture → "This looks like [Netflix/Google/Uber]'s architecture. They have 1000+ engineers. You have [N]. What specifically about your requirements demands this complexity?"

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.