- Add .shared/prompts/ with tool-neutral prompts - Add .opencode/config/project.md, rules/, skills/ from opencode-kit - Add .codex/config/project.md from codex-kit - Copy .shared/prompts/ to both .opencode/prompts/ and .codex/prompts/ - Add features/INDEX.md and features/README.md - Update README with unified structure The two original starter kits are now redundant.
1.4 KiB
1.4 KiB
name, description, category
| name | description | category |
|---|---|---|
| backend | Builds APIs, database schemas, and RLS policies with Supabase | development |
Backend Developer
Builds API endpoints, database schemas, and RLS policies for a feature.
When to Use
/backend features/PROJ-X-feature-name.md
Skill Steps
-
Read context
- Read feature spec Tech Design section
- Check existing APIs:
ls src/app/api/ - Check Supabase client:
cat src/lib/supabase.ts
-
Implement backend
- Create API routes in
src/app/api/[entity]/ - Create database migrations if needed
- Add RLS policies for new tables
- Use Supabase client from
src/lib/supabase.ts
- Create API routes in
-
Write tests
- Unit tests for all endpoints
- Integration tests for API routes
-
Verify
- Run
npm testto ensure tests pass
- Run
-
Update tracking
- Mark feature as "Backend Done" in
features/INDEX.md
- Mark feature as "Backend Done" in
-
Suggest next step
- Recommend
/qanext
- Recommend
API Route Pattern
src/app/api/[entity]/
├── route.ts # GET, POST
├── [id]/route.ts # GET, PUT, DELETE
Rules
- Use Supabase client from
src/lib/supabase.ts - Follow existing route patterns
- Add RLS policies for all new tables
- Write tests for all endpoints
- Run
npm testafter implementation
Context Recovery
If context is compacted:
- Re-read feature spec Tech Design
- Check
git difffor uncommitted changes - Continue from next endpoint