autoforge-ai 0.1.0

package/.claude/commands/expand-project.md

@@ -0,0 +1,234 @@
+---
+description: Expand an existing project with new features
+---
+
+# PROJECT DIRECTORY
+
+This command **requires** the project directory as an argument via `$ARGUMENTS`.
+
+**Example:** `/expand-project generations/my-app`
+
+If `$ARGUMENTS` is empty, inform the user they must provide a project path and exit.
+
+---
+
+# GOAL
+
+Help the user add new features to an existing project. You will:
+1. Understand the current project by reading its specification
+2. Discuss what NEW capabilities they want to add
+3. Create features directly in the database (no file generation needed)
+
+This is different from `/create-spec` because:
+- The project already exists with features
+- We're ADDING to it, not creating from scratch
+- Features go directly to the database
+
+---
+
+# YOUR ROLE
+
+You are the **Project Expansion Assistant** - an expert at understanding existing projects and adding new capabilities. Your job is to:
+
+1. Read and understand the existing project specification
+2. Ask about what NEW features the user wants
+3. Clarify requirements through focused conversation
+4. Create features that integrate well with existing ones
+
+**IMPORTANT:** Like create-spec, cater to all skill levels. Many users are product owners. Ask about WHAT they want, not HOW to build it.
+
+---
+
+# FIRST: Read and Understand Existing Project
+
+**Step 1:** Read the existing specification:
+- Read `$ARGUMENTS/.autoforge/prompts/app_spec.txt`
+
+**Step 2:** Present a summary to the user:
+
+> "I've reviewed your **[Project Name]** project. Here's what I found:
+>
+> **Current Scope:**
+> - [Brief description from overview]
+> - [Key feature areas]
+>
+> **Technology:** [framework/stack from spec]
+>
+> What would you like to add to this project?"
+
+**STOP HERE and wait for their response.**
+
+---
+
+# CONVERSATION FLOW
+
+## Phase 1: Understand Additions
+
+Start with open questions:
+
+> "Tell me about what you want to add. What new things should users be able to do?"
+
+**Follow-up questions:**
+- How does this connect to existing features?
+- Walk me through the user experience for this new capability
+- Are there new screens or pages needed?
+- What data will this create or use?
+
+**Keep asking until you understand:**
+- What the user sees
+- What actions they can take
+- What happens as a result
+- What errors could occur
+
+## Phase 2: Clarify Details
+
+For each new capability, understand:
+
+**User flows:**
+- What triggers this feature?
+- What steps does the user take?
+- What's the success state?
+- What's the error state?
+
+**Integration:**
+- Does this modify existing features?
+- Does this need new data/fields?
+- What permissions apply?
+
+**Edge cases:**
+- What validation is needed?
+- What happens with empty/invalid input?
+- What about concurrent users?
+
+## Phase 3: Derive Features
+
+**Count the testable behaviors** for additions:
+
+For each new capability, estimate features:
+- Each CRUD operation = 1 feature
+- Each UI interaction = 1 feature
+- Each validation/error case = 1 feature
+- Each visual requirement = 1 feature
+
+**Present breakdown for approval:**
+
+> "Based on what we discussed, here's my feature breakdown for the additions:
+>
+> **[New Category 1]:** ~X features
+> - [Brief description of what's covered]
+>
+> **[New Category 2]:** ~Y features
+> - [Brief description of what's covered]
+>
+> **Total: ~N new features**
+>
+> These will be added to your existing features. The agent will implement them in order. Does this look right?"
+
+**Wait for approval before creating features.**
+
+---
+
+# FEATURE CREATION
+
+Once the user approves, create features using the MCP tool.
+
+**Signal that you're ready to create features by saying:**
+
+> "Great! I'll create these N features now."
+
+**Then call the `feature_create_bulk` tool to save them directly to the database:**
+
+```
+feature_create_bulk(features=[
+  {
+    "category": "functional",
+    "name": "Brief feature name",
+    "description": "What this feature tests and how to verify it works",
+    "steps": [
+      "Step 1: Action to take",
+      "Step 2: Expected result",
+      "Step 3: Verification"
+    ]
+  },
+  {
+    "category": "style",
+    "name": "Another feature name",
+    "description": "Description of visual/style requirement",
+    "steps": [
+      "Step 1: Navigate to page",
+      "Step 2: Check visual element",
+      "Step 3: Verify styling"
+    ]
+  }
+])
+```
+
+**CRITICAL:**
+- Call the `feature_create_bulk` MCP tool with ALL features at once
+- Use valid JSON (double quotes, no trailing commas)
+- Include ALL features you promised to create
+- Each feature needs: category, name, description, steps (array of strings)
+- The tool will return the count of created features - verify it matches your expected count
+
+---
+
+# FEATURE QUALITY STANDARDS
+
+**Categories to use:**
+- `security` - Authentication, authorization, access control
+- `functional` - Core functionality, CRUD operations, workflows
+- `style` - Visual design, layout, responsive behavior
+- `navigation` - Routing, links, breadcrumbs
+- `error-handling` - Error states, validation, edge cases
+- `data` - Data integrity, persistence, relationships
+
+**Good feature names:**
+- Start with what the user does: "User can create new task"
+- Or what happens: "Login form validates email format"
+- Be specific: "Dashboard shows task count per category"
+
+**Good descriptions:**
+- Explain what's being tested
+- Include the expected behavior
+- Make it clear how to verify success
+
+**Good test steps:**
+- 2-5 steps for simple features
+- 5-10 steps for complex workflows
+- Each step is a concrete action or verification
+- Include setup, action, and verification
+
+---
+
+# AFTER FEATURE CREATION
+
+Once features are created, tell the user:
+
+> "I've created N new features for your project!
+>
+> **What happens next:**
+> - These features are now in your pending queue
+> - The agent will implement them in priority order
+> - They'll appear in the Pending column on your kanban board
+>
+> **To start implementing:** Close this chat and click the Play button to start the agent.
+>
+> Would you like to add more features, or are you done for now?"
+
+If they want to add more, go back to Phase 1.
+
+---
+
+# IMPORTANT GUIDELINES
+
+1. **Preserve existing features** - We're adding, not replacing
+2. **Integration focus** - New features should work with existing ones
+3. **Quality standards** - Same thoroughness as initial features
+4. **Incremental is fine** - Multiple expansion sessions are OK
+5. **Don't over-engineer** - Only add what the user asked for
+
+---
+
+# BEGIN
+
+Start by reading the app specification file at `$ARGUMENTS/.autoforge/prompts/app_spec.txt`, then greet the user with a summary of their existing project and ask what they want to add.

package/.claude/commands/gsd-to-autoforge-spec.md

@@ -0,0 +1,10 @@
+---
+allowed-tools: Read, Write, Bash, Glob, Grep
+description: Convert GSD codebase mapping to AutoForge app_spec.txt
+---
+
+# GSD to AutoForge Spec
+
+Convert `.planning/codebase/*.md` (from `/gsd:map-codebase`) to AutoForge's `.autoforge/prompts/app_spec.txt`.
+
+@.claude/skills/gsd-to-autoforge-spec/SKILL.md

package/.claude/commands/review-pr.md

@@ -0,0 +1,75 @@
+---
+description: Review pull requests
+---
+
+Pull request(s): $ARGUMENTS
+
+- If no PR numbers are provided, ask the user to provide PR number(s).
+- At least 1 PR is required.
+
+## TASKS
+
+1. **Retrieve PR Details**
+   - Use the GH CLI tool to retrieve the details (descriptions, diffs, comments, feedback, reviews, etc)
+
+2. **Assess PR Complexity**
+
+   After retrieving PR details, assess complexity based on:
+   - Number of files changed
+   - Lines added/removed
+   - Number of contributors/commits
+   - Whether changes touch core/architectural files
+
+   ### Complexity Tiers
+
+   **Simple** (no deep dive agents needed):
+   - ≤5 files changed AND ≤100 lines changed AND single author
+   - Review directly without spawning agents
+
+   **Medium** (1-2 deep dive agents):
+   - 6-15 files changed, OR 100-500 lines, OR 2 contributors
+   - Spawn 1 agent for focused areas, 2 if changes span multiple domains
+
+   **Complex** (up to 3 deep dive agents):
+   - >15 files, OR >500 lines, OR >2 contributors, OR touches core architecture
+   - Spawn up to 3 agents to analyze different aspects (e.g., security, performance, architecture)
+
+3. **Analyze Codebase Impact**
+   - Based on the complexity tier determined above, spawn the appropriate number of deep dive subagents
+   - For Simple PRs: analyze directly without spawning agents
+   - For Medium PRs: spawn 1-2 agents focusing on the most impacted areas
+   - For Complex PRs: spawn up to 3 agents to cover security, performance, and architectural concerns
+
+4. **PR Scope & Title Alignment Check**
+   - Compare the PR title and description against the actual diff content
+   - Check whether the PR is focused on a single coherent change or contains multiple unrelated changes
+   - If the title/description describe one thing but the PR contains significantly more (e.g., title says "fix typo in README" but the diff touches 20 files across multiple domains), flag this as a **scope mismatch**
+   - A scope mismatch is a **merge blocker** — recommend the author split the PR into smaller, focused PRs
+   - Suggest specific ways to split the PR (e.g., "separate the refactor from the feature addition")
+   - Reviewing large, unfocused PRs is impractical and error-prone; the review cannot provide adequate assurance for such changes
+
+5. **Vision Alignment Check**
+   - Read the project's README.md and CLAUDE.md to understand the application's core purpose
+   - Assess whether this PR aligns with the application's intended functionality
+   - If the changes deviate significantly from the core vision or add functionality that doesn't serve the application's purpose, note this in the review
+   - This is not a blocker, but should be flagged for the reviewer's consideration
+
+6. **Safety Assessment**
+   - Provide a review on whether the PR is safe to merge as-is
+   - Provide any feedback in terms of risk level
+
+7. **Improvements**
+   - Propose any improvements in terms of importance and complexity
+
+8. **Merge Recommendation**
+   - Based on all findings, provide a clear merge/don't-merge recommendation
+   - If all concerns are minor (cosmetic issues, naming suggestions, small style nits, missing comments, etc.), recommend **merging the PR** and note that the reviewer can address these minor concerns themselves with a quick follow-up commit pushed directly to master
+   - If there are significant concerns (bugs, security issues, architectural problems, scope mismatch), recommend **not merging** and explain what needs to be resolved first
+
+9. **TLDR**
+   - End the review with a `## TLDR` section
+   - In 3-5 bullet points maximum, summarize:
+     - What this PR is actually about (one sentence)
+     - The key concerns, if any (or "no significant concerns")
+     - **Verdict: MERGE** / **MERGE (with minor follow-up)** / **DON'T MERGE** with a one-line reason
+   - This section should be scannable in under 10 seconds

package/.claude/templates/app_spec.template.txt

@@ -0,0 +1,331 @@
+<!--
+  Project Specification Template
+  ==============================
+
+  This is a placeholder template. Replace with your actual project specification.
+
+  You can either:
+  1. Use the /create-spec command to generate this interactively with Claude
+  2. Manually edit this file following the structure below
+
+  See existing projects in generations/ for examples of complete specifications.
+-->
+
+<project_specification>
+  <project_name>YOUR_PROJECT_NAME</project_name>
+
+  <overview>
+    Describe your project in 2-3 sentences. What are you building? What problem
+    does it solve? Who is it for? Include key features and design goals.
+  </overview>
+
+  <technology_stack>
+    <frontend>
+      <framework>React with Vite</framework>
+      <styling>Tailwind CSS</styling>
+      <state_management>React hooks and context</state_management>
+      <routing>React Router for navigation</routing>
+      <port>3000</port>
+    </frontend>
+    <backend>
+      <runtime>Node.js with Express</runtime>
+      <database>SQLite with better-sqlite3</database>
+      <port>3001</port>
+    </backend>
+    <communication>
+      <api>RESTful endpoints</api>
+    </communication>
+  </technology_stack>
+
+  <prerequisites>
+    <environment_setup>
+      - Node.js 18+ installed
+      - npm or pnpm package manager
+      - Any API keys or external services needed
+    </environment_setup>
+  </prerequisites>
+
+  <core_features>
+    <!--
+      List features grouped by category. Each feature should be:
+      - Specific and testable
+      - Independent where possible
+      - Written as a capability ("User can...", "System displays...")
+    -->
+
+    <authentication>
+      - User registration with email/password
+      - User login with session management
+      - User logout
+      - Password reset flow
+      - Profile management
+    </authentication>
+
+    <main_functionality>
+      <!-- Replace with your app's primary features -->
+      - Create new items
+      - View list of items with pagination
+      - Edit existing items
+      - Delete items with confirmation
+      - Search and filter items
+    </main_functionality>
+
+    <user_interface>
+      - Responsive layout (mobile, tablet, desktop)
+      - Dark/light theme toggle
+      - Loading states and skeletons
+      - Error handling with user feedback
+      - Toast notifications for actions
+    </user_interface>
+
+    <data_management>
+      - Data validation on forms
+      - Auto-save drafts
+      - Export data functionality
+      - Import data functionality
+    </data_management>
+
+    <!-- Add more feature categories as needed -->
+  </core_features>
+
+  <database_schema>
+    <tables>
+      <users>
+        - id (PRIMARY KEY)
+        - email (UNIQUE, NOT NULL)
+        - password_hash (NOT NULL)
+        - name
+        - avatar_url
+        - preferences (JSON)
+        - created_at, updated_at
+      </users>
+
+      <!-- Add more tables for your domain entities -->
+      <items>
+        - id (PRIMARY KEY)
+        - user_id (FOREIGN KEY -> users.id)
+        - title (NOT NULL)
+        - description
+        - status (enum: draft, active, archived)
+        - created_at, updated_at
+      </items>
+
+      <!-- Add additional tables as needed -->
+    </tables>
+  </database_schema>
+
+  <api_endpoints_summary>
+    <authentication>
+      - POST /api/auth/register
+      - POST /api/auth/login
+      - POST /api/auth/logout
+      - GET /api/auth/me
+      - PUT /api/auth/profile
+      - POST /api/auth/forgot-password
+      - POST /api/auth/reset-password
+    </authentication>
+
+    <items>
+      - GET /api/items (list with pagination, search, filters)
+      - POST /api/items (create)
+      - GET /api/items/:id (get single)
+      - PUT /api/items/:id (update)
+      - DELETE /api/items/:id (delete)
+    </items>
+
+    <!-- Add more endpoint categories as needed -->
+  </api_endpoints_summary>
+
+  <ui_layout>
+    <main_structure>
+      Describe the overall layout structure:
+      - Header with navigation and user menu
+      - Sidebar for navigation (collapsible on mobile)
+      - Main content area
+      - Footer (optional)
+    </main_structure>
+
+    <sidebar>
+      - Logo/brand at top
+      - Navigation links
+      - Quick actions
+      - User profile at bottom
+    </sidebar>
+
+    <main_content>
+      - Page header with title and actions
+      - Content area with cards/lists/forms
+      - Pagination or infinite scroll
+    </main_content>
+
+    <modals_overlays>
+      - Confirmation dialogs
+      - Form modals for create/edit
+      - Settings modal
+      - Help/keyboard shortcuts reference
+    </modals_overlays>
+  </ui_layout>
+
+  <design_system>
+    <color_palette>
+      - Primary: #3B82F6 (blue)
+      - Secondary: #10B981 (green)
+      - Accent: #F59E0B (amber)
+      - Background: #FFFFFF (light), #1A1A1A (dark)
+      - Surface: #F5F5F5 (light), #2A2A2A (dark)
+      - Text: #1F2937 (light), #E5E5E5 (dark)
+      - Border: #E5E5E5 (light), #404040 (dark)
+      - Error: #EF4444
+      - Success: #10B981
+      - Warning: #F59E0B
+    </color_palette>
+
+    <typography>
+      - Font family: Inter, system-ui, -apple-system, sans-serif
+      - Headings: font-semibold
+      - Body: font-normal, leading-relaxed
+      - Code: JetBrains Mono, Consolas, monospace
+    </typography>
+
+    <components>
+      <buttons>
+        - Primary: colored background, white text, rounded
+        - Secondary: border style, hover fill
+        - Ghost: transparent, hover background
+        - Icon buttons: square with hover state
+      </buttons>
+
+      <inputs>
+        - Rounded borders with focus ring
+        - Clear placeholder text
+        - Error states with red border
+        - Disabled state styling
+      </inputs>
+
+      <cards>
+        - Subtle border or shadow
+        - Rounded corners (8px)
+        - Hover state for interactive cards
+      </cards>
+    </components>
+
+    <animations>
+      - Smooth transitions (150-300ms)
+      - Fade in for new content
+      - Slide animations for modals/sidebars
+      - Loading spinners
+      - Skeleton loaders
+    </animations>
+  </design_system>
+
+  <key_interactions>
+    <!-- Describe the main user flows -->
+    <user_flow_1>
+      1. User arrives at landing page
+      2. Clicks "Get Started" or "Sign Up"
+      3. Fills registration form
+      4. Receives confirmation
+      5. Redirected to main dashboard
+    </user_flow_1>
+
+    <user_flow_2>
+      1. User clicks "Create New"
+      2. Form modal opens
+      3. User fills in details
+      4. Clicks save
+      5. Item appears in list with success toast
+    </user_flow_2>
+
+    <!-- Add more key interactions as needed -->
+  </key_interactions>
+
+  <implementation_steps>
+    <step number="1">
+      <title>Project Setup and Database</title>
+      <tasks>
+        - Initialize frontend with Vite + React
+        - Set up Express backend
+        - Create SQLite database with schema
+        - Configure CORS and middleware
+        - Set up environment variables
+      </tasks>
+    </step>
+
+    <step number="2">
+      <title>Authentication System</title>
+      <tasks>
+        - Implement user registration
+        - Build login/logout flow
+        - Add session management
+        - Create protected routes
+        - Build user profile page
+      </tasks>
+    </step>
+
+    <step number="3">
+      <title>Core Features</title>
+      <tasks>
+        - Build main CRUD operations
+        - Implement list views with pagination
+        - Add search and filtering
+        - Create form validation
+        - Handle error states
+      </tasks>
+    </step>
+
+    <step number="4">
+      <title>UI Polish and Responsiveness</title>
+      <tasks>
+        - Implement responsive design
+        - Add dark/light theme
+        - Create loading states
+        - Add animations and transitions
+        - Implement toast notifications
+      </tasks>
+    </step>
+
+    <step number="5">
+      <title>Testing and Refinement</title>
+      <tasks>
+        - Test all user flows
+        - Fix edge cases
+        - Optimize performance
+        - Ensure accessibility
+        - Final UI polish
+      </tasks>
+    </step>
+  </implementation_steps>
+
+  <success_criteria>
+    <functionality>
+      - All features work as specified
+      - No console errors in browser
+      - Proper error handling throughout
+      - Data persists correctly in database
+    </functionality>
+
+    <user_experience>
+      - Intuitive navigation and workflows
+      - Responsive on all device sizes
+      - Fast load times (< 2s)
+      - Clear feedback for all actions
+      - Accessible (keyboard navigation, ARIA labels)
+    </user_experience>
+
+    <technical_quality>
+      - Clean, maintainable code structure
+      - Consistent coding style
+      - Proper separation of concerns
+      - Secure authentication
+      - Input validation and sanitization
+    </technical_quality>
+
+    <design_polish>
+      - Consistent visual design
+      - Smooth animations
+      - Professional appearance
+      - Both themes fully implemented
+      - No layout issues or overflow
+    </design_polish>
+  </success_criteria>
+</project_specification>