القائمة
Use when ledgerlite invoice/payment persistence, idempotency, account scoping, mutation, replay behavior, or audit recording changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when ledgerlite HTTP handlers, status codes, request headers, JSON serialization, OpenAPI, or the generated client change or should change.
Use when ledgerlite OpenAPI, schemas, generated client code, or generator behavior changes or a generated artifact may be stale.
Use for ledgerlite implementation and review work that changes Go code, tests, validation, CLI behavior, or cross-package behavior. Run the smallest focused test first and the aggregate offline validation before handoff.
| name | storage-invariants |
| description | Use when ledgerlite invoice/payment persistence, idempotency, account scoping, mutation, replay behavior, or audit recording changes. |
Check operations atomically from the caller's perspective. Account-owned keys must include the account in their storage identity. A replay that returns an existing result must not repeat mutations or audit events. A dry run performs no persistence and records no audit entry.
