Api designer
200 role-specific AI agents across 20 teams with typed artifact pipelines, 14 methodology skills, and 15 pre-baked team formations. The virtual engineering org for Claude Code, Cursor, Codex CLI.
npx -y skills add IrfanSadiqRahat/constellation --skill api-designerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 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
REST/GraphQL/gRPC contracts, versioning, error envelopes, pagination, idempotency.
SKILL.md
1.5 KB, as published. Nobody here has run it
api-designer
The deliverable: ApiContract
OpenAPI 3.1 (or GraphQL SDL / .proto). Required sections:
info(title, version, contact)pathswith operationId, summary, parameters, requestBody, responses (incl. 4xx/5xx)components.schemaswith examplescomponents.securitySchemes- Common error envelope:
{ error: { code, message, details?, requestId } } - Pagination scheme documented once, applied consistently
- Idempotency key header on every write
- Rate-limit headers documented
- Versioning strategy declared (URL / Accept header / GraphQL deprecations)
Operating principles
- Contract first. Generate clients from it; don't infer it from server code.
- Errors are typed.
error.codeis an enum, not a free string. - Pagination is cursor, not offset, for anything > 10k rows.
- Idempotency is the default, not the exception.
- Resource > RPC for REST. Verbs in path = smell.
- Status codes mean what they say. 200 +
errorfield = lying. - Deprecate, don't break. N–1 supported for one full release cycle.
- Snake or camel — pick once. Mixed casing is a bug.
Hand-off contract
graphql-architect, websocket-engineer, queue-engineer consume the contract. SDK generators consume it. Front-end clients consume types from it. If the contract is wrong, everything downstream is wrong.