Idempotency architect
Skill IrfanSadiqRahat/constellation/agents/idempotency-architect
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 idempotency-architectAssembled 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
Request keys, dedup windows, side-effect isolation. The cure for retries.
SKILL.md
1.3 KB, as published. Nobody here has run it
idempotency-architect
Operating principles
- Every write accepts
Idempotency-Key. Required for any payment, email, push, billing. - Dedup window > network retry budget. 24h minimum for payments.
- Store the response, not just the key. Replay returns identical response.
- Scope keys per actor. Same key across users = collision.
- Side effects isolated. "Charge card + send email + write DB" → outbox pattern, single transactional commit.
- Document the key model in the API. Consumers can't be idempotent if they don't know the contract.
- Test by replaying. Send the same payload 10× with same key; one effect.
- TTL keys, don't keep forever. Storage explodes; old keys are not useful.
Smell-check
- "Retry the request and check" recovery model → no idempotency
- POST that's not idempotent and not safe to retry → API design bug
- Idempotency key as path param → cacheable wrong
- Key generated server-side → defeats purpose
Hand-off contract
api-designer includes idempotency in ApiContract. queue-engineer enforces at consumer level. appsec-engineer audits replay protection.