Alternatives
phoenix-contract-architect alternatives for AI agents.
Compare similar skills by workflow fit, trust score, quality, GitHub adoption, maintenance, and install readiness.
Current skill
phoenix-contract-architect
Role 07 of the Phoenix Security spec pipeline. Turns Phoenix Security requirements into precise implementable contracts: REST API endpoints with Phoenix auth patterns, tenant isolation invariants, cursor-based pagination (for 100K+ vuln record volumes), standard response envelopes, event schemas with idempotency keys, shared types, and a full error taxonomy using Phoenix's numeric error code ranges (4001–4099 auth, 4100–4199 tenant isolation, 4300–4399 integration errors, 5100–5199 AI/LLM errors). Use this skill when requirements are finalised and need to be turned into API specs, event schemas, or error taxonomies, or when someone says "design the API", "spec the contracts", "what does the API look like", "define the schemas", or "error handling design". Always run after phoenix-security-engineer and before phoenix-verification-matrix.