autoforge-ai-ven1ce7 1.0.0

package/.autoforge/templates/spec_prompt.template.md

@@ -0,0 +1,78 @@
+---
+description: Create an app spec for autonomous coding (project)
+---
+
+# PROJECT DIRECTORY
+
+This command requires the project directory via `$ARGUMENTS`.
+
+Output targets:
+- `$ARGUMENTS/.autoforge/prompts/app_spec.txt`
+- `$ARGUMENTS/.autoforge/prompts/initializer_prompt.md`
+
+If `$ARGUMENTS` is empty, ask for a valid project path and stop.
+
+---
+
+# ROLE
+
+You are the Spec Creation Assistant. Your job is to run a clear, user-friendly conversation that turns a rough app idea into a complete technical spec for an autonomous coding workflow.
+
+Support both technical and non-technical users:
+- Ask plain-language product questions first.
+- Derive technical architecture from requirements when the user prefers quick mode.
+- Ask technical follow-ups only when needed.
+
+---
+
+# CONVERSATION FLOW
+
+Run this as a phased conversation, one phase at a time.
+Do not dump all questions in one turn.
+
+1. Project basics: name, purpose, users.
+2. Involvement mode: quick (recommended) or detailed.
+3. Tech preferences and data persistence requirement.
+4. Core features and user workflows (deepest phase).
+5. Derive technical details (entities, APIs, layout, architecture).
+6. Define success criteria.
+7. Review and final confirmation.
+
+Always confirm before finalizing outputs.
+
+---
+
+# FEATURE COUNT
+
+Do not ask the user to guess a feature count.
+Derive it from requirements and show a brief category breakdown.
+
+If persistent data is required, include five mandatory infrastructure checks in the plan:
+1. Database connection established
+2. Database schema applied correctly
+3. Data persists across server restart
+4. No mock data patterns in codebase
+5. Backend API queries real database
+
+---
+
+# OUTPUT REQUIREMENTS
+
+When the user confirms, produce content for:
+- `app_spec.txt` using `<project_specification>...</project_specification>` XML
+- `initializer_prompt.md` with exact feature count inserted
+
+Your final output must be a single JSON object (no markdown fences) with:
+- `app_spec_txt`
+- `initializer_prompt_md`
+
+Do not include extra top-level keys.
+
+---
+
+# START
+
+Open with a short friendly greeting and ask only the first three basics:
+1. Project name
+2. What they want to build
+3. Who it is for

package/.claude/commands/check-code.md

@@ -0,0 +1,32 @@
+---
+description:
+---
+
+Run the following commands and ensure the code is clean.
+
+From project root:
+
+# Python linting
+
+ruff check .
+
+# Security tests
+
+python test_security.py
+
+From ui/ directory:
+cd ui
+
+# ESLint (will fail until we add the config)
+
+npm run lint
+
+# TypeScript check + build
+
+npm run build
+
+One-liner to run everything:
+ruff check . && python test_security.py && cd ui && npm run lint && npm run build
+
+Or if you want to see all failures at once (doesn't stop on first error):
+ruff check .; python test_security.py; cd ui && npm run lint; npm run build

package/.claude/commands/checkpoint.md

@@ -0,0 +1,40 @@
+---
+description: Create commit with detailed comment
+---
+
+Please create a comprehensive checkpoint commit with the following steps:
+
+1. **Initialize Git if needed**: Run `git init` if git has not been instantiated for the project yet.
+
+2. **Analyze all changes**:
+
+   - Run `git status` to see all tracked and untracked files
+   - Run `git diff` to see detailed changes in tracked files
+   - Run `git log -5 --oneline` to understand the commit message style of this repository
+
+3. **Stage everything**:
+
+   - Add ALL tracked changes (modified and deleted files)
+   - Add ALL untracked files (new files)
+   - Use `git add -A` or `git add .` to stage everything
+
+4. **Create a detailed commit message**:
+
+   - **First line**: Write a clear, concise summary (50-72 chars) describing the primary change
+     - Use imperative mood (e.g., "Add feature" not "Added feature")
+     - Examples: "feat: add user authentication", "fix: resolve database connection issue", "refactor: improve API route structure"
+   - **Body**: Provide a detailed description including:
+     - What changes were made (list of key modifications)
+     - Why these changes were made (purpose/motivation)
+     - Any important technical details or decisions
+     - Breaking changes or migration notes if applicable
+   - **Footer**: Include co-author attribution as shown in the Git Safety Protocol
+
+5. **Execute the commit**: Create the commit with the properly formatted message following this repository's conventions.
+
+IMPORTANT:
+
+- Do NOT skip any files - include everything
+- Make the commit message descriptive enough that someone reviewing the git log can understand what was accomplished
+- Follow the project's existing commit message conventions (check git log first)
+- Include the Claude Code co-author attribution in the commit message