45ck crud-surface-reviewer
Purpose
Review whether the system exposes the right create, read, update, and delete operations without overexposing internals or missing key workflows.
Expected inputs
- current backend or persistence context
- data model or schema details
- constraints or stack context
- known risks or unresolved decisions
Deliverables
- structured recommendation
- design notes
- risks or gaps
- recommended next artifact
Trigger this skill when
- You are designing or reviewing backend behavior, persistence, or API structure rather than only UI flow.
- Data modeling, transactions, migration, or access-layer choices materially affect correctness or maintainability.
- A team needs sharper boundaries between domain logic, persistence logic, and API contracts.
Operating procedure
- Clarify the domain, data lifecycle, and current or intended persistence approach.
- Separate facts, assumptions, constraints, and unresolved backend-specific risks.
- Prefer concrete operational behavior over abstract framework enthusiasm.
- Explicitly handle invalid, missing, conflict, and rollback cases where relevant.
- Recommend the next most useful backend, persistence, or testing skill.
Quality gates
- The recommendation respects real data lifecycle and consistency needs.
- Failure and conflict cases are not ignored.
- Assumptions and unresolved decisions are visible.
- Output is specific enough to influence implementation, schema, or testing.
Output style
- Be concrete and structured.
- Separate findings, assumptions, and recommendations.
- Prefer explicit tradeoffs over single-answer absolutism.
- Use severity or priority where useful.
Failure modes to avoid
- Do not blur domain logic, persistence logic, and transport concerns.
- Do not describe happy-path behavior only.
- Do not hide uncertainty behind ORM or framework jargon.
- Do not recommend migrations or transactions without discussing rollback and compatibility.
Minimum output skeleton
## Summary
## Findings or proposal
## Evidence vs assumptions
## Risks or tradeoffs
## Recommended next skill
Handoff targets
- api-contract-writer
- repository-layer-designer
- transaction-boundary-checker