aico-frontend-implement
Execute frontend implementation with TDD. Read all constraint files before coding, write failing test first, verify after each step. Use this skill when: - User asks to "implement this", "implement the plan", "start implementation", "execute plan" - Have an implementation plan ready and need to execute it - Executing steps from /frontend.plan output - User says "start coding", "write the code", "begin implementation" - User asks to "use TDD", "write test first", "test-driven" for frontend code - User asks to "write tests", "add tests", "create tests" - Fixing UI bugs (write failing test that reproduces bug first) TDD Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST TDD Cycle: RED (write failing test) → Verify fails → GREEN (minimal code) → Verify passes → REFACTOR Prerequisites: - MUST have task file in docs/reference/frontend/tasks/ (use /frontend.tasks first if not exists) - MUST read design-system.md, constraints.md, and design spec before writing any code. Flow: Check Task File → Read Constrai
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Features and purpose
Execute frontend implementation with TDD. Read all constraint files before coding, write failing test first, verify after each step. Use this skill when: - User asks to "implement this", "implement the plan", "start implementation", "execute plan" - Have an implementation plan ready and need to execute it - Executing steps from /frontend.plan output - User says "start coding", "write the code", "begin implementation" - User asks to "use TDD", "write test first", "test-driven" for frontend code - User asks to "write tests", "add tests", "create tests" - Fixing UI bugs (write failing test that reproduces bug first) TDD Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST TDD Cycle: RED (write failing test) → Verify fails → GREEN (minimal code) → Verify passes → REFACTOR Prerequisites: - MUST have task file in docs/reference/frontend/tasks/ (use /frontend.tasks first if not exists) - MUST read design-system.md, constraints.md, and design spec before writing any code. Flow: Check Task File → Read Constrai
Quick start
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
Guides ↗Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-21
- Index updated
- 2026-02-28
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!