entity-invariants-documentation
Use when writing or updating entity invariant documentation limited to core accounting, bookkeeping, and data-reliability principles. Includes entity descriptions, invariant tables, and optional standards references; excludes catalogues of validations, product policies, and implementation mechanics.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- entity-invariants-documentation
- description
- Use when writing or updating entity invariant documentation limited to core accounting, bookkeeping, and data-reliability principles. Includes entity descriptions, invariant tables, and optional standards references; excludes catalogues of validations, product policies, and implementation mechanics.
03 SKILL.md 正文
Entity Invariants Documentation
Load
Work
- Read the domain's existing documentation and entity definitions to establish terminology, relationships, and scope. Inspect related behavior as needed; existing validators alone do not establish the intended contract.
- Apply the writing rules' principle gate to every candidate invariant. Include only core accounting, bookkeeping, or data-reliability guarantees, expressed for the entity. Do not inventory field validations or reproduce its API.
- Follow the table format, using the accounting invariants only as a layout example. Existing rows must also pass the principle gate; their presence in a document does not establish eligibility.
- Verify applicable primary references, preserve IDs for retained invariants, and check document links and entity coverage within the requested scope.
- Link a new document from the domain's existing documentation index when one exists. Keep unresolved policy decisions and enforcement findings outside the entity document; documentation work does not authorize implementation fixes.
04 同仓库更多 Skills
testing
Use when adding, changing, or reviewing tests in this repository.
reporting-usecase-creation
Use when creating, changing, or reorganizing reporting use cases and their DTOs, read queries, tests, wiring, or HTTP endpoints. Does not cover accounting reporting-period or reporting-context management.
pr-reviewer
Use when reviewing code changes, pull requests, or branch diffs.
planner
Use whenever the user asks for a plan, implementation plan, approach, roadmap, or planning, and whenever the agent decides to create or present a plan before doing work.
pair-programmer
Use when implementing code changes in this repository.
migration
Use when creating, running, or reviewing database migrations.