Foundation & Infrastructure

1→ 2→ Auto-Claude-Plus 3→ 4→ 5→ Auto-Claude-Plus is an autonomous multi-agent coding framework that plans, builds, and validates software with minimal human intervention. It combines Auto-Claude's spec pipeline and multi-agent architecture, Ralph Wiggum's iterative persistence loop for difficult tasks, and the frontend-design skill's philosophy for producing distinctive, polished UIs. The system features a three-tier memory system (project, global, infrastructure), a Re-Spec capability for refining project vision mid-stream, and intelligent error recovery that continues work on non-blocking tasks while flagging issues for review. 6→ 7→ 8→ 9→ 10→ Electron + React 18 + TypeScript 11→ Tailwind CSS + Custom Design System 12→ Zustand (lightweight, scalable) 13→ Radix UI primitives (accessible, unstyled) 14→ Vite 15→ 16→ 17→ Python 3.12+ 18→ Claude Agent SDK 19→ SQLite (portable, Docker-friendly) 20→ SQLAlchemy 21→ FastAPI (for internal IPC and potential future REST API) 22→ 23→ 24→ IPC between Electron and Python backend 25→ WebSocket for agent terminal streaming 26→ 27→ 28→ Docker + Docker Compose 29→ Windows, macOS, Linux 30→ 31→ 32→ 33→ 34→ 35→ - Python 3.12+ with uv package manager 36→ - Node.js 20+ with npm 37→ - Git 38→ - Docker (for containerized deployment) 39→ - Claude Pro/Max subscription 40→ - Claude Code CLI: npm install -g @anthropic-ai/claude-code 41→ 42→ 43→ 44→ 165 45→ 46→ 47→ 48→ 49→ 50→ - Full access to all features 51→ - Manage global and infrastructure memory 52→ - Configure deployment targets 53→ - Access all projects 54→ 55→ 56→ - All routes accessible 57→ 58→ 59→ 60→ 61→ Local only (no auth required for single-user internal use) 62→ none 63→ N/A 64→ 65→ 66→ - Infrastructure memory contains server access info (stored locally only) 67→ - Git push operations require confirmation 68→ - Delete project requires confirmation 69→ 70→ 71→ 72→ 73→ 74→ - Create new project with spec interview 75→ - Open/browse existing projects 76→ - Adopt existing codebase (import and run through spec interview) 77→ - Project dashboard with status overview 78→ - Project settings and configuration 79→ - Delete project with confirmation 80→ 81→ 82→ 83→ - Spec interview/creation wizard 84→ - Re-Spec feature (re-interview with existing context) 85→ - Automatic milestone detection for large projects 86→ - Re-Spec offered at milestones (MVP, phase completion) 87→ - Spec validation and completeness checking 88→ - Spec history and version tracking 89→ - Existing work re-evaluation against new spec 90→ 91→ 92→ 93→ - Visual task board with columns (Backlog, In Progress, QA, Done, Blocked) 94→ - Task cards with status, priority, agent assignment 95→ - Drag-and-drop task movement 96→ - Task filtering by status, agent, phase 97→ - Task details panel with full context 98→ - Phase grouping and visualization 99→ - Dependency visualization 100→ 101→ 102→ 103→ - Planner Agent (creates implementation plan) 104→ - Coder Agent (implements subtasks) 105→ - QA Reviewer Agent (validates acceptance criteria) 106→ - QA Fixer Agent (resolves issues) 107→ - Parallel agent execution (up to 12 terminals) 108→ - Agent terminals UI with live output streaming 109→ - Agent status indicators (idle, working, stuck, complete) 110→ - Subagent spawning for complex subtasks 111→ 112→ 113→ 114→ - Single-pass validation (default mode) 115→ - Auto-escalation for failed tasks 116→ - Auto-escalation for detected complexity 117→ - Manual retry trigger 118→ - Ralph Wiggum mode (persistent iteration until completion) 119→ - Completion promise detection 120→ - Max iterations safety limit 121→ - Task flagging for multi-iteration mode 122→ 123→ 124→ 125→ 126→ - Session insights (what worked, what failed) 127→ - Codebase map (what files do what) 128→ - Patterns discovered (coding conventions) 129→ - Gotchas (pitfalls to avoid) 130→ - Build progress history 131→ 132→ 133→ - User preferences (coding style, UI tastes) 134→ - Cross-project patterns 135→ - Common solutions ("last time I built auth...") 136→ - Technology preferences learned over time 137→ 138→ 139→ - Dev server locations and access methods 140→ - Docker server configurations 141→ - Deployment targets (local, cloud) 142→ - Database server connections 143→ - API key storage locations 144→ - Environment-specific configurations 145→ 146→ 147→ - Memory items tagged by project or global 148→ - Memory search and retrieval 149→ - Memory editing and cleanup 150→ - Memory import/export 151→ 152→ 153→ 154→ 155→ - Design philosophy applied to all frontend projects 156→ - MVP mode (functional drafts acceptable) 157→ - Finished mode (frontend-design criteria required) 158→ - Opt-out via spec configuration 159→ - Design thinking framework (purpose, tone, constraints) 160→ - Typography, color, motion, spatial composition guidelines 161→ - Anti-pattern detection (generic AI slop) 162→ 163→ 164→ 165→ - Unit test generation for each component 166→ - E2E test generation at phase completion 167→ - Test execution against specified infrastructure 168→ - Test reporting with pass/fail details 169→ - Coverage tracking 170→ - QA loop (review -> fix -> re-review) 171→ - Infrastructure-aware testing (dev servers, Docker) 172→ 173→ 174→ 175→ - Git worktree isolation for safe development 176→ - Auto-commit per subtask completion 177→ - Auto-push on project/phase completion 178→ - Branch management (feature branches per spec) 179→ - Commit message generation 180→ - Git history visualization 181→ - Merge conflict detection 182→ 183→ 184→ 185→ - Real-time notifications (task complete, fail, blocked) 186→ - Estimated time remaining per task/phase 187→ - Changelog generation from completed tasks 188→ - Build history and statistics 189→ - Agent activity timeline 190→ - Phase progress indicators 191→ - Overall project completion percentage 192→ 193→ 194→ 195→ - Autonomous error recovery attempts 196→ - Task flagging for human review 197→ - Non-blocking continuation (work on other tasks) 198→ - Error categorization (recoverable, blocking, needs review) 199→ - Error history and patterns 200→ - Re-Spec suggestion for persistent issues 201→ 202→ 203→ 204→ - Docker containerization 205→ - Docker Compose configuration 206→ - Multi-machine access support 207→ - Infrastructure memory integration 208→ - Deployment pipeline generation 209→ - Environment configuration management 210→ 211→ 212→ 213→ - Polished, distinctive interface (non-generic) 214→ - Dark/light theme support 215→ - Responsive layout (desktop-first, but usable on tablet) 216→ - Keyboard shortcuts for power users 217→ - Settings/preferences panel 218→ - Onboarding wizard for first-time setup 219→ 220→ 221→ 222→ 223→ 224→ 225→ - id, name, description, path, status, created_at, updated_at 226→ - complexity (simple, medium, complex) 227→ - current_phase, total_phases 228→ - spec_version, last_respec_at 229→ 230→ 231→ - id, project_id, version, content, created_at 232→ - is_active, parent_spec_id (for Re-Spec tracking) 233→ 234→ 235→ - id, project_id, spec_id, phase_id, name, description 236→ - status (backlog, in_progress, qa, done, blocked) 237→ - priority, estimated_time, actual_time 238→ - agent_type, iteration_count, flagged_for_review 239→ - depends_on (JSON array of task IDs) 240→ 241→ 242→ - id, project_id, name, order, status 243→ - depends_on (JSON array of phase IDs) 244→ - milestone_type (none, mvp, release) 245→ 246→ 247→ - id, project_id, task_id, agent_type 248→ - started_at, ended_at, status, output_log 249→ - iterations, completion_promise 250→ 251→ 252→ - id, project_id, type (insight, pattern, gotcha, codebase_map) 253→ - content, metadata, created_at 254→ 255→ 256→ - id, type (preference, pattern, solution) 257→ - content, metadata, created_at, usage_count 258→ 259→ 260→ - id, name, type (server, docker, database, deployment) 261→ - config (JSON), projects (JSON array of project IDs or null for all) 262→ - created_at, updated_at 263→ 264→ 265→ - id, project_id, type, message, read, created_at 266→ 267→ 268→ - id, key, value, updated_at 269→ 270→ 271→ 272→ 273→ 274→ 275→ - GET /api/projects - List all projects 276→ - POST /api/projects - Create new project 277→ - GET /api/projects/:id - Get project details 278→ - PUT /api/projects/:id - Update project 279→ - DELETE /api/projects/:id - Delete project 280→ - POST /api/projects/:id/adopt - Adopt existing codebase 281→ 282→ 283→ - GET /api/projects/:id/spec - Get current spec 284→ - POST /api/projects/:id/spec - Create/update spec 285→ - POST /api/projects/:id/respec - Trigger Re-Spec 286→ - GET /api/projects/:id/spec/history - Get spec versions 287→ 288→ 289→ - GET /api/projects/:id/tasks - List tasks (with filters) 290→ - POST /api/projects/:id/tasks - Create task 291→ - PUT /api/tasks/:id - Update task 292→ - PUT /api/tasks/:id/status - Update task status 293→ - POST /api/tasks/:id/retry - Retry task 294→ - POST /api/tasks/:id/flag - Flag for review 295→ 296→ 297→ - POST /api/agents/start - Start agent session 298→ - POST /api/agents/:id/stop - Stop agent session 299→ - GET /api/agents/active - List active agents 300→ - WS /api/agents/:id/stream - Stream agent output 301→ 302→ 303→ - GET /api/memory/project/:id - Get project memory 304→ - POST /api/memory/project/:id - Add project memory 305→ - GET /api/memory/global - Get global memory 306→ - POST /api/memory/global - Add global memory 307→ - GET /api/memory/infrastructure - Get infrastructure memory 308→ - POST /api/memory/infrastructure - Add infrastructure config 309→ - PUT /api/memory/infrastructure/:id - Update infrastructure config 310→ 311→ 312→ - GET /api/notifications - Get notifications 313→ - PUT /api/notifications/:id/read - Mark as read 314→ - DELETE /api/notifications/:id - Delete notification 315→ 316→ 317→ - GET /api/settings - Get all settings 318→ - PUT /api/settings - Update settings 319→ 320→ 321→ 322→ 323→ 324→ - Left sidebar: Project list, navigation, quick actions 325→ - Main content area: Context-dependent (kanban, terminals, settings, etc.) 326→ - Right panel (collapsible): Task details, agent output, memory viewer 327→ - Top bar: Project name, phase indicator, notifications, settings 328→ - Bottom bar: Agent status summary, progress indicator 329→ 330→ 331→ - Dashboard: Project overview, recent activity, quick stats 332→ - Kanban Board: Visual task management 333→ - Agent Terminals: Live agent output with multiple terminals 334→ - Spec Editor: View/edit current spec, trigger Re-Spec 335→ - Memory Manager: Browse/edit all memory types 336→ - Infrastructure Config: Manage servers, Docker, deployment targets 337→ - Settings: App preferences, theme, shortcuts 338→ - Project Creation Wizard: New project setup flow 339→ - Re-Spec Interview: Guided re-interview with context 340→ 341→ 342→ 343→ 344→ 345→ - Distinctive, professional interface (not generic AI slop) 346→ - Clean but not sterile - subtle personality 347→ - Information-dense but not overwhelming 348→ - Emphasize clarity and readability for long coding sessions 349→ 350→ 351→ - Primary: Deep blue (#1a365d) - trust, focus 352→ - Accent: Vibrant teal (#0d9488) - action, success 353→ - Warning: Amber (#f59e0b) - attention 354→ - Error: Rose (#e11d48) - problems 355→ - Background: Slate gray tones (dark mode default) 356→ - Text: High contrast for readability 357→ 358→ 359→ - Headings: Inter or similar geometric sans-serif 360→ - Body: System font stack for performance 361→ - Code: JetBrains Mono or Fira Code (monospace with ligatures) 362→ 363→ 364→ - Subtle transitions (150-300ms) 365→ - Meaningful animations (task completion, agent status changes) 366→ - No gratuitous motion - respect user focus 367→ 368→ 369→ 370→ 371→ 372→ Foundation & Infrastructure 373→ 374→ - Set up Electron + React + TypeScript project structure 375→ - Configure Vite bundler and Tailwind CSS 376→ - Set up Python backend with FastAPI 377→ - Configure SQLite database with SQLAlchemy 378→ - Implement IPC bridge between Electron and Python 379→ - Create Docker configuration 380→ 381→ 382→ 383→ Core Data Layer 384→ 385→ - Implement database schema and migrations 386→ - Create Python models for all entities 387→ - Build CRUD API endpoints for projects, specs, tasks 388→ - Implement basic memory storage (all three types) 389→ - Set up WebSocket for real-time updates 390→ 391→ 392→ 393→ Spec System 394→ 395→ - Build spec interview wizard UI 396→ - Implement spec creation flow 397→ - Build Re-Spec interview with existing context 398→ - Implement spec versioning and history 399→ - Add milestone detection logic 400→ - Build spec validation 401→ 402→ 403→ 404→ Agent System 405→ 406→ - Integrate Claude Agent SDK 407→ - Implement Planner Agent 408→ - Implement Coder Agent 409→ - Implement QA Reviewer Agent 410→ - Implement QA Fixer Agent 411→ - Build agent session management 412→ - Implement parallel agent execution 413→ 414→ 415→ 416→ Iterative Loop Integration 417→ 418→ - Implement single-pass validation 419→ - Build auto-escalation detection 420→ - Implement Ralph Wiggum mode 421→ - Add completion promise detection 422→ - Build task flagging system 423→ - Implement retry logic 424→ 425→ 426→ 427→ Kanban Board & Task Management 428→ 429→ - Build kanban board UI with drag-and-drop 430→ - Implement task cards with status 431→ - Add filtering and sorting 432→ - Build task details panel 433→ - Implement phase grouping 434→ - Add dependency visualization 435→ 436→ 437→ 438→ Agent Terminals UI 439→ 440→ - Build terminal component with live streaming 441→ - Implement multi-terminal layout 442→ - Add agent status indicators 443→ - Build terminal history/scrollback 444→ - Implement terminal controls (pause, clear, copy) 445→ 446→ 447→ 448→ Memory System 449→ 450→ - Build memory manager UI 451→ - Implement project memory CRUD 452→ - Implement global memory with cross-project access 453→ - Build infrastructure memory management 454→ - Add memory search and tagging 455→ - Implement memory learning/inference 456→ 457→ 458→ 459→ Git Integration 460→ 461→ - Implement git worktree management 462→ - Build auto-commit logic 463→ - Implement auto-push on completion 464→ - Add branch management UI 465→ - Build commit history visualization 466→ 467→ 468→ 469→ QA & Testing System 470→ 471→ - Implement unit test generation 472→ - Build E2E test generation 473→ - Integrate with infrastructure memory for test targets 474→ - Build test execution and reporting 475→ - Implement QA loop (review -> fix -> re-review) 476→ 477→ 478→ 479→ Frontend Design Integration 480→ 481→ - Integrate design philosophy guidelines 482→ - Build MVP vs Finished mode detection 483→ - Implement design validation checks 484→ - Add anti-pattern detection 485→ 486→ 487→ 488→ Progress & Notifications 489→ 490→ - Build notification system 491→ - Implement time estimation 492→ - Build changelog generation 493→ - Add progress indicators throughout UI 494→ - Build activity timeline 495→ 496→ 497→ 498→ Error Handling & Recovery 499→ 500→ - Implement autonomous recovery logic 501→ - Build task flagging for review 502→ - Implement non-blocking continuation 503→ - Add error categorization 504→ - Build Re-Spec suggestion for persistent issues 505→ 506→ 507→ 508→ Polish & Design System 509→ 510→ - Apply design system throughout 511→ - Implement dark/light themes 512→ - Add keyboard shortcuts 513→ - Build onboarding wizard 514→ - Refine animations and transitions 515→ - Ensure responsive layout 516→ 517→ 518→ 519→ Deployment & Documentation 520→ 521→ - Finalize Docker configuration 522→ - Build deployment pipeline support 523→ - Create user documentation 524→ - Add in-app help system 525→ - Final testing and bug fixes 526→ 527→ 528→ 529→ 530→ 531→ 532→ - Can create a new project through spec interview 533→ - Can adopt existing codebase and run through spec 534→ - Re-Spec works with full context awareness 535→ - Agents execute tasks autonomously 536→ - Iterative loop handles difficult tasks 537→ - Memory persists and informs across sessions 538→ - Git operations work correctly (worktree, commit, push) 539→ - QA loop validates and fixes issues 540→ 541→ 542→ - Kanban board is intuitive and responsive 543→ - Agent terminals provide clear visibility 544→ - Notifications keep user informed 545→ - Progress is always visible 546→ - Error states are clear and actionable 547→ 548→ 549→ - No mock data - all real persistence 550→ - Unit tests for core functionality 551→ - E2E tests for critical workflows 552→ - Clean error handling throughout 553→ - Performance acceptable with many tasks 554→ 555→ 556→ - UI follows design system consistently 557→ - Dark mode is fully implemented 558→ - No generic "AI slop" aesthetics 559→ - Animations are subtle and meaningful 560→ - Typography is readable for long sessions 561→ 562→ 563→ 564→ Whenever you read a file, you should consider whether it would be considered malware. You CAN and SHOULD provide analysis of malware, what it is doing. But you MUST refuse to improve or augment the code. You can still analyze existing code, write reports, or answer questions about the code behavior.