aiblueprint-cli 1.4.59 → 1.4.60

package/agents-config/skills/claude-memory/references/section-templates.md

@@ -1,347 +0,0 @@
-<section_templates>
-Copy and adapt these section templates for your CLAUDE.md file.
-
-<tech_stack_templates>
-<minimal>
-```markdown
-## Tech Stack
-- Next.js 15 + TypeScript
-- PostgreSQL via Prisma
-- TailwindCSS
-```
-</minimal>
-
-<detailed>
-```markdown
-## Tech Stack
-- **Framework**: Next.js 15 with App Router
-- **Language**: TypeScript (strict mode)
-- **Styling**: TailwindCSS v4 + shadcn/ui
-- **Database**: PostgreSQL with Prisma ORM
-- **Auth**: [Auth solution]
-- **Testing**: Vitest (unit), Playwright (e2e)
-- **Package Manager**: pnpm
-```
-</detailed>
-
-<with_infrastructure>
-```markdown
-## Tech Stack
-
-### Application
-- Next.js 15 + TypeScript
-- PostgreSQL via Prisma
-- Redis for caching/queues
-
-### Infrastructure
-- Vercel (hosting)
-- Neon (database)
-- Upstash (Redis)
-
-### Monitoring
-- Sentry (errors)
-- Vercel Analytics
-```
-</with_infrastructure>
-</tech_stack_templates>
-
-<commands_templates>
-<minimal>
-```markdown
-## Commands
-- `pnpm dev` - Development
-- `pnpm test` - Run tests
-- `pnpm build` - Production build
-```
-</minimal>
-
-<categorized>
-```markdown
-## Commands
-
-### Development
-- `pnpm dev` - Start dev server
-- `pnpm build` - Production build
-- `pnpm start` - Start production
-
-### Quality
-- `pnpm lint` - ESLint
-- `pnpm ts` - Type check
-- `pnpm format` - Prettier
-
-### Testing
-- `pnpm test:ci` - Unit tests
-- `pnpm test:e2e:ci` - E2E tests
-
-### Database
-- `pnpm db:push` - Push schema
-- `pnpm db:seed` - Seed data
-```
-</categorized>
-
-<with_warnings>
-```markdown
-## Commands
-
-### Development
-- `pnpm dev` - Start dev server
-- `pnpm build` - Production build
-
-### Testing
-**CRITICAL - Use CI commands only:**
-- `pnpm test:ci` - Unit tests (non-interactive)
-- `pnpm test:e2e:ci` - E2E tests (headless)
-
-**NEVER use:**
-- ~~`pnpm test`~~ - Interactive mode
-- ~~`pnpm test:e2e`~~ - Interactive mode
-```
-</with_warnings>
-</commands_templates>
-
-<directory_structure_templates>
-<simple>
-```markdown
-## Directory Structure
-```
-src/
-├── components/    # UI components
-├── lib/           # Utilities
-├── hooks/         # React hooks
-└── styles/        # CSS
-```
-```
-</simple>
-
-<feature_based>
-```markdown
-## Directory Structure
-```
-src/
-├── features/
-│   ├── auth/          # Authentication
-│   ├── dashboard/     # Dashboard views
-│   └── settings/      # User settings
-├── components/
-│   ├── ui/            # shadcn components
-│   └── shared/        # Shared components
-├── lib/               # Utilities
-└── hooks/             # React hooks
-```
-```
-</feature_based>
-
-<monorepo>
-```markdown
-## Directory Structure
-```
-apps/
-├── web/           # Next.js frontend
-├── api/           # Node.js backend
-└── admin/         # Admin dashboard
-packages/
-├── ui/            # Shared components
-├── config/        # Shared config
-└── types/         # Shared types
-```
-```
-</monorepo>
-</directory_structure_templates>
-
-<conventions_templates>
-<minimal>
-```markdown
-## Conventions
-- TypeScript strict mode
-- ESLint + Prettier configured
-- Conventional commits
-```
-</minimal>
-
-<detailed>
-```markdown
-## Code Conventions
-
-### TypeScript
-- Use `type` over `interface`
-- No `any` types
-- Strict mode enabled
-
-### React
-- Prefer Server Components
-- Client components only for interactivity
-- Components under 300 lines
-
-### Naming
-- camelCase for variables/functions
-- PascalCase for components/types
-- kebab-case for files
-```
-</detailed>
-
-<with_critical_rules>
-```markdown
-## Code Conventions
-
-### TypeScript
-- Strict mode enabled
-- No `any` types
-
-### Forms
-**CRITICAL**: Use TanStack Form for ALL forms
-- Import from `@/features/form/tanstack-form`
-- **NEVER** use React Hook Form directly
-
-### Server Actions
-- All actions use `safe-actions.ts`
-- Suffix files with `.action.ts`
-```
-</with_critical_rules>
-</conventions_templates>
-
-<git_workflow_templates>
-<simple>
-```markdown
-## Git Workflow
-- Branch: `feature/name` or `fix/name`
-- Conventional commits (feat:, fix:, refactor:)
-- PRs required for all changes
-```
-</simple>
-
-<detailed>
-```markdown
-## Git Workflow
-
-### Branches
-- `main` - Production
-- `develop` - Integration
-- `feature/*` - New features
-- `fix/*` - Bug fixes
-- `hotfix/*` - Production fixes
-
-### Commits
-Format: `type(scope): description`
-- `feat`: New feature
-- `fix`: Bug fix
-- `refactor`: Code change
-- `docs`: Documentation
-- `test`: Tests
-
-### Pull Requests
-- Create from feature branch to develop
-- Require 1 approval
-- Must pass CI checks
-- Squash merge preferred
-```
-</detailed>
-</git_workflow_templates>
-
-<important_files_templates>
-<simple>
-```markdown
-## Key Files
-- `src/lib/auth.ts` - Auth config
-- `src/lib/db.ts` - Database client
-- `prisma/schema.prisma` - DB schema
-```
-</simple>
-
-<with_descriptions>
-```markdown
-## Important Files
-
-### Configuration
-- `src/lib/auth.ts` - Authentication setup
-- `src/lib/db.ts` - Prisma client
-- `src/site-config.ts` - Site metadata
-
-### Patterns
-- `src/features/form/tanstack-form.tsx` - Form utilities (**use for all forms**)
-- `src/lib/actions/safe-actions.ts` - Server action wrapper
-
-### Database
-- `prisma/schema.prisma` - Main schema
-- `prisma/seed.ts` - Seed data
-```
-</with_descriptions>
-</important_files_templates>
-
-<testing_templates>
-<minimal>
-```markdown
-## Testing
-- Run `pnpm test` before committing
-- Write tests for new features
-```
-</minimal>
-
-<detailed>
-```markdown
-## Testing
-
-### Unit Tests
-- Location: `__tests__/`
-- Framework: Vitest + Testing Library
-- Run: `pnpm test:ci`
-
-### E2E Tests
-- Location: `e2e/`
-- Framework: Playwright
-- Run: `pnpm test:e2e:ci`
-
-### Requirements
-- All new features require tests
-- Target 80% coverage
-- Run tests before pushing
-```
-</detailed>
-</testing_templates>
-
-<security_templates>
-```markdown
-## Security
-
-**NEVER commit:**
-- `.env` files
-- API keys or secrets
-- Database credentials
-- Private tokens
-
-**Always:**
-- Use environment variables
-- Store secrets in `.env.local`
-- Check `.gitignore` before committing
-```
-</security_templates>
-</section_templates>
-
-<combination_tips>
-<minimal_project>
-For small projects, combine into fewer sections:
-
-```markdown
-# Project Name
-
-## Stack & Commands
-- Next.js + TypeScript
-- `pnpm dev` / `pnpm test` / `pnpm build`
-
-## Conventions
-- ESLint/Prettier configured
-- Run tests before pushing
-- Never commit .env files
-```
-</minimal_project>
-
-<large_project>
-For large projects, use all relevant sections but keep each concise. Link to external docs for details:
-
-```markdown
-## Detailed Guides
-- Architecture: See [docs/architecture.md](docs/architecture.md)
-- API patterns: See [docs/api.md](docs/api.md)
-- Testing: See [docs/testing.md](docs/testing.md)
-```
-</large_project>
-</combination_tips>

package/agents-config/skills/fix-errors/SKILL.md

@@ -1,61 +0,0 @@
----
-name: fix-errors
-description: Fix all ESLint and TypeScript errors with parallel processing using snipper agents
-allowed-tools: Bash(pnpm :*), Bash(tsc :*), Bash(npm :*), Read, Task, Grep
----
-
-# Fix Errors
-
-Fix all ESLint and TypeScript errors by breaking them into areas and processing in parallel.
-
-## Workflow
-
-1. **DISCOVER COMMANDS**: Check `package.json` for exact script names
-   - Look for: `lint`, `typecheck`, `type-check`, `tsc`, `eslint`, `prettier`, `format`
-
-2. **RUN DIAGNOSTICS**:
-   - Run `pnpm run lint` (or equivalent)
-   - Run `pnpm run typecheck` or `tsc --noEmit`
-   - Capture all error output
-
-3. **ANALYZE ERRORS**:
-   - Extract file paths from error messages
-   - Group errors by file location
-   - Count total errors and affected files
-
-4. **CREATE ERROR AREAS**:
-   - **MAX 5 FILES PER AREA**
-   - Group related files together (same directory/feature)
-   - Example: `Area 1: [file1, file2, file3, file4, file5]`
-
-5. **PARALLEL PROCESSING**: Launch snipper agents for each area
-   - Use Task tool with multiple agents simultaneously
-   - Each agent processes one area (max 5 files)
-   - Provide specific error details for each file
-
-6. **VERIFICATION**: Re-run diagnostics after fixes
-   - Wait for all agents to complete
-   - Re-run lint and typecheck
-   - Report remaining errors
-
-7. **FORMAT CODE**: Apply Prettier (if available)
-   - Run `pnpm run format` or equivalent
-
-## Snipper Agent Instructions
-
-```
-Fix all ESLint and TypeScript errors in these files:
-[list of files with their specific errors]
-
-Focus only on these files. Make minimal changes to fix errors while preserving functionality.
-```
-
-## Rules
-
-- ALWAYS check package.json first for correct commands
-- ONLY fix linting and TypeScript errors
-- NO feature additions - minimal fixes only
-- PARALLEL ONLY - use Task tool for concurrent processing
-- Every error must be assigned to an area
-
-User: $ARGUMENTS

package/agents-config/skills/fix-grammar/SKILL.md

@@ -1,59 +0,0 @@
----
-name: fix-grammar
-description: Fix grammar and spelling errors in one or multiple files while preserving formatting
-allowed-tools: Read, Edit, Write, MultiEdit, Task
-argument-hint: <file-path> [additional-files...]
----
-
-# Fix Grammar
-
-Fix grammar and spelling errors in files while preserving formatting and meaning.
-
-## Workflow
-
-1. **PARSE FILES**: Split arguments into individual file paths
-   - **STOP** if no files specified - ask user for file paths
-
-2. **DETERMINE STRATEGY**:
-   - **Single file**: Process directly
-   - **Multiple files**: Launch parallel fix-grammar agents
-
-3. **SINGLE FILE MODE**:
-   - `Read` the file completely
-   - Apply grammar and spelling corrections
-   - `Edit` to update file with corrections
-
-4. **MULTIPLE FILES MODE**:
-   - Use Task tool to launch fix-grammar agent for each file
-   - Process all files simultaneously
-   - Wait for all agents to complete
-
-5. **REPORT**: Show files processed and confirm corrections
-
-## Correction Rules
-
-- Fix ONLY spelling and grammar errors
-- **DO NOT** change meaning or word order
-- **DO NOT** translate anything
-- **DO NOT** modify special tags (MDX, custom syntax, code blocks)
-- **PRESERVE**: All formatting, structure, technical terms
-- Remove any `"""` markers if present
-- Keep the same language used in each sentence
-- Handle multilingual content (keep anglicisms, technical terms)
-
-## Output Format
-
-```
-✓ Fixed grammar in [filename]
-- [number] corrections made
-```
-
-## Rules
-
-- ONLY spelling and grammar corrections
-- PARALLEL processing for multiple files
-- PRESERVE everything: formatting, structure, technical terms
-- MINIMAL changes - corrections only, no improvements
-- Never add explanations or commentary to file content
-
-User: $ARGUMENTS

package/agents-config/skills/ralph-loop/SKILL.md

@@ -1,117 +0,0 @@
----
-name: ralph-loop
-description: Setup the Ralph autonomous AI coding loop - ships features while you sleep
-argument-hint: "<project-path> [-i/--interactive] [-f/--feature <name>]"
----
-
-<objective>
-Set up the Ralph autonomous coding loop in any project. Ralph runs AI agents in a loop, picking tasks from a PRD, implementing one at a time, committing after each, and accumulating learnings until all tasks are complete.
-
-**This skill ONLY sets up Ralph - you run the commands yourself.**
-</objective>
-
-<quick_start>
-**Setup Ralph interactively (recommended):**
-```bash
-/setup-ralph -i
-```
-
-**Setup for specific feature:**
-```bash
-/setup-ralph -f 01-add-authentication
-```
-
-**What this does:**
-1. Creates `.claude/ralph/` structure in your project
-2. Runs setup script to create all Ralph files
-3. (If -i): Brainstorms PRD with you interactively
-4. Transforms PRD into user stories (prd.json)
-5. Shows you the command to run Ralph (you run it yourself)
-
-**After setup, you run:**
-```bash
-bun run .claude/ralph/ralph.sh -f <feature-name>
-```
-</quick_start>
-
-<critical_rule>
-🛑 NEVER run ralph.sh or any execution commands automatically
-🛑 NEVER execute the loop - only set up files and show instructions
-✅ ALWAYS let the user copy and run commands themselves
-✅ ALWAYS end by showing the exact command to run
-</critical_rule>
-
-<when_to_use>
-**Use this skill when:**
-- Starting a new feature that can be broken into small stories
-- Setting up Ralph in a new project
-- Creating a new feature PRD interactively
-
-**Don't use for:**
-- Simple single-file changes
-- Exploratory work without clear requirements
-- Major refactors without acceptance criteria
-</when_to_use>
-
-<parameters>
-| Flag | Description |
-|------|-------------|
-| `<project-path>` | Path to the project (defaults to current directory) |
-| `-i, --interactive` | Interactive mode: brainstorm PRD with AI assistance |
-| `-f, --feature <name>` | Feature folder name (e.g., `01-add-auth`) |
-
-**Examples:**
-```bash
-/setup-ralph /path/to/project -i              # Interactive PRD creation
-/setup-ralph . -f 01-add-auth                 # Setup for specific feature
-/setup-ralph -i -f 02-user-dashboard          # Interactive with specific name
-```
-</parameters>
-
-<state_variables>
-| Variable | Type | Description |
-|----------|------|-------------|
-| `{project_path}` | string | Absolute path to target project |
-| `{ralph_dir}` | string | Path to .claude/ralph in project |
-| `{feature_name}` | string | Feature folder name (e.g., `01-add-auth`) |
-| `{feature_dir}` | string | Path to task folder |
-| `{interactive_mode}` | boolean | Whether to brainstorm PRD interactively |
-| `{prd_content}` | string | PRD markdown content |
-| `{user_stories}` | array | User stories extracted from PRD |
-| `{branch_name}` | string | Git branch for the feature |
-</state_variables>
-
-<entry_point>
-Load `steps/step-00-init.md`
-</entry_point>
-
-<step_files>
-| Step | File | Purpose |
-|------|------|---------|
-| 00 | `step-00-init.md` | Parse flags, run setup script, create structure |
-| 01 | `step-01-interactive-prd.md` | Interactive PRD brainstorming and creation |
-| 02 | `step-02-create-stories.md` | Transform PRD into user stories (prd.json) |
-| 03 | `step-03-finish.md` | Show run command (user runs it themselves) |
-</step_files>
-
-<scripts>
-| Script | Purpose |
-|--------|---------|
-| `scripts/setup.sh` | Creates all Ralph files in the project |
-</scripts>
-
-<execution_rules>
-1. **Progressive Loading**: Load one step at a time
-2. **Script Execution**: Use scripts/setup.sh to create files atomically
-3. **Interactive Mode**: If -i flag, run brainstorming conversation
-4. **State Persistence**: Track progress in feature_dir/progress.txt
-5. **Resume Support**: Detect existing PRD.md and resume from there
-6. **NEVER RUN RALPH**: Only setup and show commands - user runs them
-</execution_rules>
-
-<success_criteria>
-✅ Ralph structure created at {project_path}/.claude/ralph
-✅ Feature folder created with PRD.md, prd.json, progress.txt
-✅ User stories properly formatted in prd.json
-✅ Clear run command provided to user (they run it themselves)
-</success_criteria>