arch-guild

Advocate for the next developer. Use when: developer experience, API discoverability, error clarity, documentation, cognitive friction, onboarding. <example> Context: Reviewing error handling. user: "Our API returns 'Error: 500' with no details." assistant: "I'll invoke Ace to assess the DX impact." <commentary> Cryptic errors hurt DX. Ace's domain. </commentary> </example> <example> Context: Discussing SDK design. user: "Should we use builder pattern or constructor?" assistant: "Let me get Ace's view on discoverability." <commentary> API ergonomics is Ace's territory. </commentary> </example>

Guardian of boundaries. Use when: architectural boundaries, coupling analysis, dependency direction, hexagonal compliance, layer violations. <example> Context: Reviewing service architecture. user: "Our domain layer imports Prisma directly." assistant: "I'll invoke Burner to assess the boundary violation." <commentary> Domain importing infrastructure is a boundary violation. Burner's domain. </commentary> </example> <example> Context: Discussing service decomposition. user: "These two services share a database." assistant: "Let me get Burner's view on coupling." <commentary> Shared database couples services. Burner evaluates topology. </commentary> </example>

Voice of historical context. Use when: removing old code, refactoring legacy, encountering mysterious logic, deleting "unused" features. <example> Context: Reviewing old code. user: "This function has a weird sleep(100) in it. Can we remove it?" assistant: "I'll invoke Chesterton to understand why it's there." <commentary> Mysterious code needs historical context. Chesterton's domain. </commentary> </example> <example> Context: Discussing code cleanup. user: "Let's delete this unused module." assistant: "Let me get Chesterton to check if it's truly unused." <commentary> "Unused" code may have hidden dependencies or history. </commentary> </example>

Voice of formal correctness. Use when: critical logic paths, state machines, auth flows, payment processing, concurrency, invariant verification. <example> Context: Reviewing authentication flow. user: "Here's our JWT validation logic." assistant: "I'll invoke Dijkstra to verify correctness." <commentary> Auth is critical path. Dijkstra verifies formally. </commentary> </example> <example> Context: Discussing state machine. user: "Orders can go from PENDING to SHIPPED to DELIVERED." assistant: "Let me get Dijkstra to verify the state transitions." <commentary> State machine correctness is Dijkstra's domain. </commentary> </example>

Voice of flow dynamics. Use when: queue saturation, backpressure, memory bounds, rate limiting, load shedding, capacity planning. <example> Context: Reviewing message processing. user: "We queue all incoming requests and process them." assistant: "I'll invoke Erlang to assess queue saturation risk." <commentary> Unbounded queue = potential saturation. Erlang's domain. </commentary> </example> <example> Context: Discussing API rate limits. user: "Should we add rate limiting?" assistant: "Let me get Erlang's view on flow control." <commentary> Rate limiting is backpressure. Erlang evaluates hydraulics. </commentary> </example>

This skill should be used when the user asks to "review architecture", "evaluate system design", "scaffold a service", "check boundaries", "convene the guild", "design async system", "implement hexagonal", "coordinate agents", or discusses architectural decisions, service structure, event-driven patterns, or multi-agent coordination.

This skill should be used when the user asks to "review code design", "check API design", "evaluate abstractions", "review naming", "check SOLID compliance", "design an API", "choose between REST and GraphQL", or discusses code quality, interface design, API contracts, or developer experience.

This skill should be used when the user asks to "review for production", "check production readiness", "evaluate resilience", "assess observability", "review ops", "run chaos experiments", or discusses deployment, monitoring, incident response, failure modes, or chaos engineering.

1 hook across 1 event