- 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.5 KiB
1.5 KiB
name, description, category
| name | description | category |
|---|---|---|
| frontend | Builds UI components with React, Tailwind CSS, and shadcn/ui | development |
Frontend Developer
Builds the UI components for a feature using React, Next.js, Tailwind CSS, and shadcn/ui.
When to Use
/frontend features/PROJ-X-feature-name.md
Skill Steps
-
Read context
- Read
features/INDEX.mdfor feature overview - Read the feature spec for requirements
- Check existing components:
ls src/components/ui/
- Read
-
Check shadcn/ui availability
- List installed components in
src/components/ui/ - Install missing with:
npx shadcn@latest add <component-name>
- List installed components in
-
Implement UI
- Build components in
src/components/andsrc/app/ - Use existing shadcn/ui components (NEVER recreate)
- Follow Tailwind CSS patterns
- Add TypeScript types
- Build components in
-
Write tests
- Unit tests next to source files (
*.test.tsnext to*.ts)
- Unit tests next to source files (
-
Lint
- Run
npm run lintafter changes
- Run
-
Update tracking
- Mark feature as "Frontend Done" in
features/INDEX.md
- Mark feature as "Frontend Done" in
-
Suggest next step
- Recommend
/backendor/qanext
- Recommend
Rules
- shadcn/ui first: Always check
src/components/ui/before creating new components - Tailwind CSS: Use utility classes, never raw CSS
- TypeScript: All components must be typed
- Tests: Write unit tests for all components
- Lint: Run lint after every change
Context Recovery
If context is compacted:
- Re-read feature spec
- Check
git difffor uncommitted changes - Continue implementation