⚠️ Test Project: This is an experimental project testing Kiro IDE's spec-driven development approach. Currently work-in-progress and may be incomplete.
A hands-on exploration of Kiro IDE's three-layer spec-driven development methodology:
- Requirements using EARS syntax
- Technical design blueprints
- Implementation tasks for AI agents
This project accompanies my review and analysis of Kiro IDE. For the full context, methodology explanation, and lessons learned, read the blog post:
📖 Kiro IDE Review: Spec-Driven AI Development vs Traditional Coding Assistants
- Choose difficulty category (Easy, Medium, Hard) on start screen
- Strict category filtering for questions
- Accessible UI: ARIA roles, keyboard navigation, high contrast mode
- Animated feedback and results
- Offline support (service worker)
- Modern, mobile-friendly design
- Keyboard navigation for answer choices (Arrow Up/Down)
- Radiogroup and radio roles for answer buttons
- High contrast mode toggle for visually impaired users
- Clear focus indicators on all interactive elements
- Install dependencies:
npm install
- Start the development server:
npm start
- Run tests:
npm test
src/components/QuizContainer.tsx
: Main quiz logic and UIsrc/components/QuizContainer.test.tsx
: Accessibility and interaction testssrc/state/QuizContext.tsx
: State managementsrc/service-worker.js
: Offline support