crud
The crud skill auto-generates production-ready CRUD functionality for database entities, including API endpoints, validation schemas with Zod, row-level security authorization, pagination, search filters, and test cases across supported frameworks like Next.js with Prisma or Drizzle, Express, and Hono. Use it when scaffolding complete CRUD operations for new database tables, but avoid invoking it for UI component design, form layouts, database schema discussions, or general implementation guidance.
git clone --depth 1 https://github.com/Chachamaru127/claude-code-harness /tmp/crud && cp -r /tmp/crud/opencode/skills/crud ~/.claude/skills/crudSKILL.md
# CRUD Skill
Auto-generates CRUD functionality for specified entities (tables) at **production-ready level**.
## Quick Reference
- "**Create CRUD for task management**" → `/crud tasks`
- "**Want search and pagination too**" → Includes all together
- "**Include permissions (who can view/edit)**" → Sets up authorization/rules together
## Deliverables
- CRUD + validation + authorization + tests, **complete production-safe set**
- Minimize diff to match existing DB/code
**Features**:
- Validation (Zod) auto-add
- Auth/authorization (Row Level Security) auto-config
- Relations (one-to-many, many-to-many) support
- Pagination, search, filters
- Auto-generated test cases
---
## Auto-invoke Skills
**This skill must explicitly invoke the following skills with the Skill tool**:
| Skill | Purpose | When to Call |
|-------|---------|--------------|
| `impl` | Implementation (parent skill) | CRUD feature implementation |
| `verify` | Verification (parent skill) | Post-implementation verification |
---
## Execution Flow
Detailed steps are described in the phases below.
### Phase 1: Entity Analysis
1. Parse entity name from $ARGUMENTS
2. Detect existing schema (Prisma, Drizzle, raw SQL)
3. Infer field types and relations
### Phase 2: CRUD Generation
1. Generate model/schema if needed
2. Create API endpoints (REST or tRPC)
3. Add validation schemas (Zod)
4. Configure authorization rules
### Phase 3: Test Generation
1. Create unit tests for each endpoint
2. Add integration tests
3. Generate test fixtures
### Phase 4: Verification
1. Run type check
2. Run tests
3. Verify build
---
## Supported Frameworks
| Framework | Detection | Generated Files |
|-----------|-----------|-----------------|
| **Next.js + Prisma** | `prisma/schema.prisma` | API routes, Prisma client |
| **Next.js + Drizzle** | `drizzle.config.ts` | API routes, Drizzle queries |
| **Express** | `express` in package.json | Controllers, routes |
| **Hono** | `hono` in package.json | Route handlers |
---
## Output Structure
```
src/
├── lib/
│ └── validations/
│ └── {entity}.ts # Zod schemas
├── app/api/{entity}/
│ ├── route.ts # GET (list), POST (create)
│ └── [id]/
│ └── route.ts # GET, PUT, DELETE
└── tests/
└── {entity}.test.ts # Test cases
```
---
## Related Skills
- `impl` - Feature implementation
- `verify` - Build verification
- `auth` - Authentication/authorizationexecutor が返した advisor-request.v1 に対して方針だけ返す非実行 advisor
sprint-contract と review artifact を基準に verdict を返す read-only reviewer
実装、preflight 自己点検、検証、commit 準備を 1 タスク単位で進める統合ワーカー
Browser automation through the repo agent-browser CLI. Explicit helper for navigation, forms, screenshots, scraping, and web-app checks. Prefer Browser Use or Playwright when available. Do NOT load for: sharing URLs, embedding links, or editing screenshot files.
Explicit helper for authentication and payment implementation with Clerk, Supabase Auth, or Stripe. Do NOT load for: general UI work, database design, or non-auth features.
Team execution mode — backward-compatible alias for harness-work with team orchestration. Composer/composer 2.5 maps to the cursor backend.
Validates brainstormed ideas with Cursor PM, updates Plans.md, then handoff back. Cursor ↔ Claude Code 2-Agent workflow support. Use when user mentions Cursor PM handoff, 2-agent plan validation, CC-Cursor round trip, or brainstorm review. Do NOT load for: implementation work, single-agent tasks, or direct coding.
Quality guardrail for Claude/Codex update integration. Detects doc-only Feature Table additions and requires implementation or explicit planning. Internal use only.