🧺 Inherited Backlog

Every item on this page is inherited-not-committed. The archive estimated 47 PIMP implementation tasks plus a future-feature list. They are preserved for triage, not promised as current scope.

PIMP checklist summary

  • total imported tasks:
    • 47
  • archive estimate:
    • 60 to 80 hours
  • claimed grade movement:
    • A minus to A plus
  • priority groups:
    • critical: crash prevention and data integrity
    • major: UX smoothness and maintainability
    • minor: code quality, developer experience, future-proofing

Critical foundation items

  • error boundary system:
    • create ErrorBoundary component
    • wrap app in ErrorBoundary
    • add async error handling
    • add contextual boundaries around risky async surfaces
  • image resilience:
    • retry image loading
    • fallback for user and external images
    • generic image fallback wrapper
  • localStorage race fixes:
    • storage event listeners
    • safe storage wrapper
    • quota handling
    • key migration

Major architecture items

  • context refactor:
    • create focused app context
    • create notification context
    • reduce prop drilling
  • code splitting:
    • lazy load heavy overlays
    • lazy load editor and docs surfaces
    • add lightweight loading fallbacks
  • admin prompt confirm flow:
    • remember session trust
    • approve-all option
    • visible prompt diff for customized prompts
  • memoization:
    • blueprint filtering
    • project library normalization
    • stable handlers for expensive child trees

Quality and developer experience items

  • CSS consolidation:
    • audit CSS files
    • split global and component structure
    • remove duplicates only after visual proof
  • TypeScript migration:
    • add TypeScript config
    • create core types
    • migrate utilities first
    • migrate hooks and components gradually
  • testing infrastructure:
    • add Vitest and Testing Library
    • create test helpers
    • cover generation, wizard state, and error boundaries
  • accessibility:
    • Lighthouse audit
    • ARIA labels
    • modal focus traps
    • keyboard shortcut guide
    • contrast fixes
  • naming consistency:
    • hooks
    • components
    • boolean variables

Polish and validation items

  • performance:
    • debounced searches
    • virtualize only if measured need appears
    • lazy image loading and dimensions
  • UX:
    • loading states
    • actionable empty states
    • subtle success animation only if it does not slow flows
  • documentation:
    • JSDoc for critical functions
    • concise README update
    • contributing guide if project is opened to contributors
  • manual validation:
    • generate projects
    • edit and enhance prompts
    • save and reload
    • publish blueprint
    • test desktop and mobile
  • failure validation:
    • generation failure
    • invalid JSON
    • failed uploads
    • error boundary display
  • release discipline:
    • code review
    • changelog
    • version tag only if release process exists
    • post-deploy monitoring

Future features from 2DO

  • core functionality:
    • prompt template library
    • AI prompt analysis and improvement suggestions
    • prompt effectiveness rating based on target platform outcomes
    • prompt version history and comparison
    • prompt testing simulator
  • UI and UX:
    • drag-and-drop step reordering
    • collapsible workspace sections
    • customizable card themes
    • guided creation mode for beginners
    • keyboard shortcuts
    • touch-optimized mobile improvements
  • integration and sharing:
    • embeddable prompt cards
    • direct target-platform project creation when deliberately implemented
    • rich social sharing
    • collaborative real-time editing
    • import and export formats such as JSON and CSV
  • advanced features:
    • analytics dashboard
    • prompt variables with substitution
    • prompt chain visualization
    • localization and translation
    • contextual help system
    • conditional prompt paths based on target-platform responses

Triage rule

Before any item moves from inherited backlog to committed work:

  • confirm it still applies after the self-hosted cutover
  • remove WebSim-only assumptions unless target-platform specific
  • define observable acceptance checks
  • add it to current project planning outside this history page