crud-with-spec-kit
Build Spec-Driven CRUD Features
Teams often lose alignment when CRUD code is built separately from feature specifications. This skill helps Claude, Codex, and Claude Code convert Spec-Kit requirements into consistent APIs, clients, tests, and validation checks.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "crud-with-spec-kit". A Spec-Kit file defines a Project entity with title, owner, status, and required create, list, update, and delete actions.
Expected outcome:
- Entity summary with fields, constraints, and relationships.
- Backend route checklist for each required CRUD action.
- Validation and error-handling expectations.
- Test plan mapped to the specification success criteria.
Using "crud-with-spec-kit". A team has implemented CRUD routes and wants to verify coverage against the feature specification.
Expected outcome:
- Coverage summary for implemented and missing operations.
- Response format mismatches and validation gaps.
- Frontend client updates needed to match backend behavior.
- Prioritized fixes before release.
Security Audit
SafeThe five high-severity static weak-cryptography alerts are false positives caused by normal prose in SKILL.md, including words such as description, describing, desired, and codes. No evidence found of cryptographic code, command execution, network access, data exfiltration, or prompt-injection attempts.
Low Risk Issues (1)
Quality Score
What You Can Build
Create CRUD APIs from Specs
Convert a Spec-Kit feature description into backend route plans, validation rules, and test expectations.
Align Frontend Clients with APIs
Use entity definitions and endpoint requirements to design client services, forms, lists, and state flows.
Check Implementation Coverage
Compare completed CRUD behavior against success criteria and list missing routes, validations, or tests.
Try These Prompts
Use the crud-with-spec-kit skill to read my Spec-Kit feature file. Identify the entities, attributes, relationships, required CRUD operations, validation rules, and missing specification details.
Use the crud-with-spec-kit skill to create a backend implementation plan for this feature. Include routes, request and response models, validation behavior, error handling, and tests.
Use the crud-with-spec-kit skill to design frontend clients and CRUD screens for this specification. Include service methods, UI states, forms, list views, and validation feedback.
Use the crud-with-spec-kit skill to compare this implementation with the Spec-Kit requirements. Report implemented behavior, missing criteria, mismatched responses, weak validation, and recommended fixes.
Best Practices
- Start with complete entity definitions, constraints, relationships, and success criteria.
- Review generated routes and clients against your framework conventions before merging.
- Add tests for validation failures, permission boundaries, and response formats.
Avoid
- Using the skill with vague specifications that omit required operations or constraints.
- Accepting generated CRUD code without framework-specific review and test execution.
- Applying basic CRUD scaffolding to workflows with complex domain rules or unusual data access.