docs: add auto-claude spec and tracking files
- Add spec.md and requirements.json for task definition - Add qa_report.md with QA findings - Add task_logs.json and task_metadata.json for tracking
This commit is contained in:
17
.auto-claude/specs/001-conceptual-explanations/spec.md
Normal file
17
.auto-claude/specs/001-conceptual-explanations/spec.md
Normal file
@@ -0,0 +1,17 @@
|
||||
# Conceptual Explanations
|
||||
|
||||
Add brief 'Why This Works' explanations to each lesson that explain the concept behind the CSS property, not just the syntax. Include visual diagrams where helpful.
|
||||
|
||||
## Rationale
|
||||
The #1 criticism of Flexbox Froggy and similar tools is they teach syntax without explaining WHY. Codecademy and freeCodeCamp also criticized for 'just type this without understanding'. This is a major market gap we can fill.
|
||||
|
||||
## User Stories
|
||||
- As a beginner, I want to understand WHY CSS properties work so that I can apply knowledge to new situations
|
||||
- As a self-taught developer, I want conceptual understanding so that I can build from scratch, not just follow tutorials
|
||||
|
||||
## Acceptance Criteria
|
||||
- [ ] Each lesson includes a 'Concept' section explaining WHY the CSS property works
|
||||
- [ ] Explanations are concise (2-4 sentences) and beginner-friendly
|
||||
- [ ] Visual diagrams or illustrations included where helpful
|
||||
- [ ] Concept section is collapsible so advanced users can skip
|
||||
- [ ] Flexbox lessons explicitly explain container vs item distinction
|
||||
Reference in New Issue
Block a user