core template

State Tracking

Tracks current progress, what works, what doesnt, and the last prompt used. Critical for context restoration.

0 downloads
1 views
STATE.md
Template Preview

STATE.md Template

# STATE.md

## Current Phase
**Phase:** [1, 2, 3, 4, or 5]
**Phase Name:** [Foundation / Core Features / Responsive / Edge Cases / Launch]
**Status:** [Not Started / In Progress / Complete]

## What's Working
- [Feature/component that's complete and tested]
- [Another working feature]
- [Everything you've verified works]

## What's Not Working Yet
- [Bug or issue you've found]
- [Feature that's broken or incomplete]
- [Known problem to fix]

## What's Next
**Immediate Next Task:**
[The ONE thing you're about to work on right now]

**After That:**
1. [Next task after current one]
2. [Task after that]
3. [And so on...]

## Last AI Prompt (Copy-paste your last successful prompt)

[Your exact prompt here]


**Result:** [What happened - success/partial/failed]
**Git Commit:** [The commit message if you saved this]

## Issues to Discuss
- [ ] [Question or decision you need help with]
- [ ] [Technical challenge you're stuck on]
- [ ] [Design choice you're unsure about]

Example: Portfolio in Progress

# STATE.md

## Current Phase
**Phase:** 2 - Core Features
**Status:** In Progress (60% complete)

## What's Working
- ✅ Hero section displays name, title, and CTA button
- ✅ Projects array with 3 sample projects
- ✅ ProjectCard component renders correctly
- ✅ Routing between pages (Home, Projects, About)
- ✅ Tailwind styling applied throughout
- ✅ Header navigation with links

## What's Not Working Yet
- ❌ Project detail pages don't exist yet
- ❌ Contact form not connected to Formspree
- ❌ About page is just placeholder text
- ❌ Mobile responsive not tested (waiting for Phase 3)
- ⚠️ Warning in console: "Each child in list should have unique key prop"

## What's Next
**Immediate Next Task:**
Create individual project detail pages with full case studies

**After That:**
1. Hook up contact form to Formspree
2. Write actual about page content
3. Fix the key prop warning in ProjectCard
4. Add project images to public folder

## Last AI Prompt

Create a ProjectCard component that displays:

  • Project thumbnail image
  • Project title
  • Short description (2 lines max)
  • "View Project" link

Use Tailwind for styling. Make it a clean card with subtle shadow on hover. The card should be reusable and take props for: image, title, description, and link.


**Result:** Success - Component created and working
**Git Commit:** "Add ProjectCard component with hover effect"

## Issues to Discuss
- [ ] Should project detail pages be separate routes or modals?
- [ ] Do we need filtering/categories for projects, or keep it simple?
- [ ] Best way to handle project images - hardcode paths or use a data file?

Example: Dashboard Near Complete

# STATE.md

## Current Phase
**Phase:** 4 - Edge Cases & Polish
**Status:** In Progress (80% complete)

## What's Working
- ✅ All metric cards display real data
- ✅ Charts render with Chart.js
- ✅ User table with search and filter
- ✅ Pagination works correctly
- ✅ Mobile, tablet, desktop layouts all functional
- ✅ Loading states for all async operations
- ✅ Empty states with helpful messages
- ✅ Date picker updates metrics

## What's Not Working Yet
- ❌ Error handling for failed API calls not graceful
- ❌ Images don't have fallback when they fail to load
- ❌ No retry button on error state
- ⚠️ Chart sometimes renders before container is ready (visual glitch)
- ⚠️ Table search is laggy on slow connections

## What's Next
**Immediate Next Task:**
Add error boundaries and retry logic for API failures

**After That:**
1. Add image fallback placeholders
2. Fix chart rendering race condition
3. Add debounce to table search (300ms)
4. Full UAT (test everything)
5. Deploy to Vercel

## Last AI Prompt

The user table search is running on every keystroke and it's laggy. Add debounce so it only searches after user stops typing for 300ms. Use the existing handleSearch function but wrap it in a debounced version.


**Result:** Partial success - Debounce works but TypeScript error on debounce type
**Git Commit:** Not committed yet, waiting to fix TypeScript issue

## Issues to Discuss
- [ ] TypeScript complaining about debounce function type - need help with proper typing
- [ ] Should we add offline mode with cached data, or just show error?
- [ ] Performance: bundle size is 600KB - worth code splitting Chart.js?

Related Templates

Cohort 01 has limited seats.
Designers who code. Builders who ship.

ZEROFLUFF