aiblueprint-cli 1.4.59 → 1.4.61

package/agents-config/skills/apex/templates/README.md

@@ -1,176 +0,0 @@
-# APEX Template System
-
-## Overview
-
-This directory contains template files used to initialize APEX workflow outputs when save mode (`-s`) is enabled. This template system significantly reduces token usage by moving repetitive content out of step files.
-
-## Template Files
-
-| Template | Purpose | Created When |
-|----------|---------|--------------|
-| `00-context.md` | Workflow configuration and progress tracking | Always (if save_mode) |
-| `01-analyze.md` | Analysis findings | Always (if save_mode) |
-| `02-plan.md` | Implementation plan | Always (if save_mode) |
-| `03-execute.md` | Implementation log | Always (if save_mode) |
-| `04-validate.md` | Validation results and workflow completion | Always (if save_mode) |
-| `step-complete.md` | Completion marker template | Referenced in steps |
-
-## Template Variables
-
-Templates use `{{variable}}` syntax for placeholders:
-
-| Variable | Description | Example |
-|----------|-------------|---------|
-| `{{task_id}}` | Kebab-case task identifier | `01-add-auth-middleware` |
-| `{{task_description}}` | Plain text task description | `add authentication middleware` |
-| `{{timestamp}}` | ISO 8601 timestamp | `2026-01-12T10:30:00Z` |
-| `{{auto_mode}}` | Auto mode flag | `true` or `false` |
-| `{{save_mode}}` | Save mode flag | `true` or `false` |
-| `{{economy_mode}}` | Economy mode flag | `true` or `false` |
-| `{{branch_mode}}` | Branch mode flag | `true` or `false` |
-| `{{interactive_mode}}` | Interactive mode flag | `true` or `false` |
-| `{{branch_name}}` | Git branch name | `feature/add-auth` |
-| `{{original_input}}` | Raw user input | `/apex -a -s add auth` |
-
-## Setup Script
-
-### `setup-templates.sh`
-
-Initializes all template files in the output directory with variables replaced.
-
-**Usage:**
-```bash
-bash scripts/setup-templates.sh \
-  "feature_name" \
-  "task_description" \
-  "auto_mode" \
-  "save_mode" \
-  "economy_mode" \
-  "branch_mode" \
-  "interactive_mode" \
-  "branch_name" \
-  "original_input"
-```
-
-**Output:**
-```
-.claude/output/apex/01-add-auth-middleware/
-├── 00-context.md      # Always created
-├── 01-analyze.md      # Always created
-├── 02-plan.md         # Always created
-├── 03-execute.md      # Always created
-└── 04-validate.md     # Always created
-```
-
-## Progress Update Script
-
-### `update-progress.sh`
-
-Updates the progress table in `00-context.md` without manual markdown editing.
-
-**Usage:**
-```bash
-bash scripts/update-progress.sh <task_id> <step_number> <step_name> <status>
-```
-
-**Examples:**
-```bash
-# Mark step 01 as in progress
-bash scripts/update-progress.sh "01-add-auth" "01" "analyze" "in_progress"
-
-# Mark step 01 as complete
-bash scripts/update-progress.sh "01-add-auth" "01" "analyze" "complete"
-
-# Mark step 02 as in progress
-bash scripts/update-progress.sh "01-add-auth" "02" "plan" "in_progress"
-```
-
-**Status Values:**
-- `in_progress` → `⏳ In Progress`
-- `complete` → `✓ Complete`
-
-## Token Savings
-
-### Before Optimization
-
-Each step file contained full template content inline:
-
-```markdown
-### 1. Initialize Save Output (if save_mode)
-
-**If `{save_mode}` = true:**
-
-Create `{output_dir}/01-analyze.md`:
-```markdown
-# Step 01: Analyze
-
-**Task:** {task_description}
-**Started:** {ISO timestamp}
-
----
-
-## Context Discovery
-```
-
-Update `00-context.md` progress:
-```markdown
-| 01-analyze | ⏳ In Progress | {timestamp} |
-```
-```
-
-**Token cost per step:** ~200 tokens × 5 steps = ~1,000 tokens
-
-### After Optimization
-
-Step files now reference templates and scripts:
-
-```markdown
-### 1. Initialize Save Output (if save_mode)
-
-**If `{save_mode}` = true:**
-
-The file `{output_dir}/01-analyze.md` has already been created by the setup script.
-
-Update progress:
-```bash
-bash {skill_dir}/scripts/update-progress.sh "{task_id}" "01" "analyze" "in_progress"
-```
-
-Append your findings to `01-analyze.md` as you work.
-```
-
-**Token cost per step:** ~50 tokens × 5 steps = ~250 tokens
-
-**Total savings:** ~750 tokens per workflow execution (75% reduction)
-
-## How It Works
-
-1. **Initialization (step-00-init.md):**
-   - Runs `setup-templates.sh` once at workflow start
-   - Creates all template files with variables replaced
-   - Output directory is ready with pre-initialized files
-
-2. **Each Step:**
-   - Runs `update-progress.sh` to mark step as "in_progress"
-   - Appends findings/logs to the pre-created step file
-   - Runs `update-progress.sh` again to mark step as "complete"
-
-3. **Benefits:**
-   - AI doesn't need to hold template content in context
-   - Consistent formatting across all workflows
-   - Easy to update templates without editing step files
-   - Scripts handle the tedious markdown updates
-
-## Updating Templates
-
-To modify template content:
-
-1. Edit the template file in `templates/`
-2. Changes apply to all future workflows automatically
-3. No need to update step files
-
-## Maintenance
-
-- Templates are stateless (no workflow-specific logic)
-- Scripts are idempotent (safe to run multiple times)
-- Variables use `{{var}}` syntax to avoid conflicts with markdown

package/agents-config/skills/apex/templates/step-complete.md

@@ -1,7 +0,0 @@
----
-
-## Step Complete
-
-**Status:** ✓ Complete
-**Next:** {{next_step}}
-**Timestamp:** {{timestamp}}

package/agents-config/skills/claude-memory/SKILL.md

@@ -1,293 +0,0 @@
----
-name: claude-memory
-description: Create and optimize CLAUDE.md memory files or .claude/rules/ modular rules for Claude Code projects. Comprehensive guidance on file hierarchy, content structure, path-scoped rules, best practices, and anti-patterns. Use when working with CLAUDE.md files, .claude/rules directories, setting up new projects, or improving Claude Code's context awareness.
-argument-hint: [init | optimize | task description]
----
-
-<core_principle>
-Memory files consume tokens from the context window. ~100-150 instruction slots available for your customizations. Keep files minimal — only include what the agent cannot discover on its own.
-
-**Two approaches:**
-- **CLAUDE.md** — Single file, best for small projects (< 100 lines)
-- **.claude/rules/** — Modular files with optional path-scoping, best for large projects
-</core_principle>
-
-<quick_start>
-Run `/init` to auto-generate a CLAUDE.md. Or create manually:
-
-```markdown
-# Project Name
-
-## Tech Stack
-- [Primary framework]
-- [Key non-obvious libraries]
-
-## Commands
-- `npm run dev` - Dev server
-- `npm test` - Run tests
-- `npm run build` - Build
-
-## Rules
-- [2-3 critical project-specific rules]
-```
-
-- Press `#` during a session to add memory items quickly
-- Use `/memory` to open CLAUDE.md in your editor
-</quick_start>
-
-<file_hierarchy>
-
-| Priority | Location | Scope |
-|----------|----------|-------|
-| 1 (Highest) | Enterprise policy (managed by IT) | All org users |
-| 2 | `./CLAUDE.md` or `./.claude/CLAUDE.md` | Team via git |
-| 2 | `./.claude/rules/*.md` | Team via git |
-| 3 | `~/.claude/CLAUDE.md` | All your projects |
-| 3 | `~/.claude/rules/*.md` | All your projects |
-| 4 (Lowest) | `./CLAUDE.local.md` (auto-gitignored) | Just you |
-
-Claude recurses UP from current directory, loading all CLAUDE.md files found. Also discovers CLAUDE.md in subtrees when reading files in those directories.
-
-**Monorepo strategy:** Root file defines WHEN; subtree files define HOW.
-```
-root/CLAUDE.md           # Universal: tech stack, git workflow
-apps/web/CLAUDE.md       # Frontend-specific
-apps/api/CLAUDE.md       # Backend-specific
-```
-</file_hierarchy>
-
-<rules_directory>
-The `.claude/rules/` directory splits instructions into focused markdown files.
-
-**Use `.claude/rules/` when:** many concerns, different rules for different file types, team maintains different areas.
-**Use CLAUDE.md when:** small project, universal rules, single source of truth.
-
-Path-scoped rules use YAML frontmatter:
-```yaml
----
-paths:
-  - "src/api/**/*.ts"
----
-# API Rules
-- All endpoints must include input validation
-```
-
-Supported patterns: `**/*.ts`, `src/**/*`, `src/**/*.{ts,tsx}`, `{src,lib}/**/*.ts`
-
-Rules without `paths` frontmatter load unconditionally.
-
-See [references/rules-directory-guide.md](references/rules-directory-guide.md) for complete guide including symlinks, user-level rules, and migration.
-</rules_directory>
-
-<content_structure>
-Structure CLAUDE.md with only these sections:
-
-1. **Project purpose** (1-3 lines) — What the project is
-2. **Tech stack** (compact) — Only non-obvious technologies
-3. **Commands** — Non-obvious dev, build, and test commands
-4. **Important files** — Architecture-critical, non-obvious files only
-5. **Rules** — Prohibitions and constraints that prevent mistakes (highest-value lines)
-6. **Workflow** (optional) — Only if non-standard
-
-**Do NOT include:**
-- Repository overviews (agent discovers structure itself)
-- Code style rules (linters enforce these)
-- Generic best practices ("write clean code", "DRY", "SOLID")
-- Redundant specs (copies of config files, env vars, schema descriptions)
-- Marketing/goals (vision statements, KPIs, roadmaps)
-- Verbose explanations (paragraphs where one line suffices)
-
-See [references/section-templates.md](references/section-templates.md) for ready-to-use templates.
-See [references/project-patterns.md](references/project-patterns.md) for framework-specific patterns.
-</content_structure>
-
-<writing_rules>
-**Golden rule:** If someone with zero project context reads your CLAUDE.md and gets confused, Claude will too.
-
-**Be specific, never vague:**
-```
-❌ "Format code properly" / "Write good tests" / "Follow best practices"
-✅ "Run `pnpm lint` before committing" / "Tests in `__tests__/` using Vitest"
-```
-
-**Prohibitions > positive guidance:**
-```
-❌ "Try to use TanStack Form for forms"
-✅ "NEVER use native form/useState for forms — ALWAYS use TanStack Form"
-```
-
-**Show, don't tell:** When format matters, show a concrete example (3-5 lines max).
-
-**Emphasis hierarchy:** CRITICAL > NEVER > ALWAYS > IMPORTANT > YOU MUST
-- Put critical rules **first** in each section
-- Use **bold + keyword** for non-negotiable rules: `**CRITICAL**: Never commit secrets`
-
-See [references/prompting-techniques.md](references/prompting-techniques.md) for advanced techniques.
-</writing_rules>
-
-<size_limits>
-- **Ideal:** < 100 lines
-- **Maximum:** 150 lines before performance degrades
-- **Over 200 lines:** directives start getting lost
-
-When exceeding limits, split into `.claude/rules/` files or link to separate docs:
-```markdown
-- **API patterns**: See [docs/api-patterns.md](docs/api-patterns.md)
-- **Testing guide**: See [docs/testing-guide.md](docs/testing-guide.md)
-```
-
-CLAUDE.md supports importing: `@docs/coding-standards.md` (relative/absolute paths, `~` expansion, up to 5 levels deep, not evaluated inside code blocks).
-</size_limits>
-
-<workflow>
-**ALWAYS ASK FIRST: Storage Strategy**
-
-Before creating or updating memory files, use AskUserQuestion:
-- **Option 1: Single CLAUDE.md** — < 100 lines, simple project, universal rules
-- **Option 2: Modular .claude/rules/** — 100+ lines, different rules for different files
-
-**Creating new memory:**
-1. Start with `/init` or minimal template
-2. Add tech stack and commands first
-3. Add rules only as you encounter friction
-4. Test with real tasks, iterate based on Claude's behavior
-
-**Maintaining:**
-1. Review quarterly or when project changes significantly
-2. Remove outdated instructions
-3. Add patterns that required repeated explanation
-4. Use `#` for quick additions during work
-
-**Troubleshooting:**
-
-| Problem | Solution |
-|---------|----------|
-| Claude ignores instructions | Reduce file size, add emphasis (CRITICAL, NEVER) |
-| Context overflow | Use `/clear`, split into .claude/rules/ |
-| Instructions conflict | Consolidate, use hierarchy (root vs subtree) |
-| Path rules not applying | Verify glob pattern matches target files |
-</workflow>
-
-<init_workflow>
-## `/claude-memory init` — Create Minimal CLAUDE.md
-
-When the user argument contains "init", execute this workflow to scaffold a CLAUDE.md with only the essential sections.
-
-### Step 1: Detect project context
-
-Read `package.json` (or equivalent: `pyproject.toml`, `Cargo.toml`, `go.mod`, etc.) to detect:
-- Project name
-- Tech stack (framework, language)
-- Available scripts/commands (dev, build, test)
-
-Also check for existing linter configs (ESLint, Biome, Prettier, tsconfig) — do NOT include rules they already enforce.
-
-### Step 2: Identify important files
-
-Scan for non-obvious architecture-critical files. Look for:
-- Auth config files
-- Server action wrappers, API helpers
-- Database schema files
-- Custom middleware or shared utilities
-- Skip standard framework files (package.json, tsconfig, next.config, etc.)
-
-### Step 3: Generate CLAUDE.md
-
-Create the file with ONLY these sections. Each section should be compact — the whole file should be under 50 lines.
-
-```markdown
-# [Project Name]
-[One-line description of what this project is]
-
-## Tech Stack
-- [Only non-obvious technologies — skip deps detectable from config files]
-
-## Commands
-- `[dev command]` - Dev server
-- `[build command]` - Build
-- `[test command]` - Tests
-- [Any non-obvious commands like db:push, seed, etc.]
-
-## Important Files
-- [Only files the agent wouldn't discover naturally]
-
-## Rules
-- [Leave empty with a comment: "Add project-specific rules as you encounter friction"]
-```
-
-### Step 4: Present and write
-
-Show the generated file to the user. Write it to `./CLAUDE.md` after approval.
-
-**Rules:**
-- NEVER include directory structure, code style rules, generic best practices, or marketing text
-- NEVER include anything a linter or TypeScript already enforces
-- Target: 20-50 lines. If it's longer, you're including too much
-- The Rules section starts empty — it gets populated over time as mistakes happen
-</init_workflow>
-
-<optimize_workflow>
-## `/claude-memory optimize` — Deep CLAUDE.md Cleanup
-
-When the user argument contains "optimize", execute this workflow.
-
-**CRITICAL — Step 0 is MANDATORY. Do NOT skip it. Do NOT start optimizing without reading the guide first.**
-
-### Step 0: Read the optimization guide (REQUIRED FIRST)
-
-YOU MUST use the Read tool on `{SKILL_PATH}/references/optimize-guide.md` BEFORE doing anything else.
-This file contains the research data (ETH Zurich study), the 6 bloat categories with specific examples, target metrics, and before/after examples. Without reading it, you will miss removal criteria and produce a subpar optimization.
-
-### Step 1: Inventory
-
-Read every CLAUDE.md, CLAUDE.local.md, and `.claude/rules/*.md` in the project. Count total lines.
-
-### Step 2: Read linter configs
-
-Read ESLint/Biome/Prettier/TypeScript configs. Any CLAUDE.md line duplicating an enforced rule → delete.
-
-### Step 3: Apply the 6 bloat categories from the guide
-
-For each line ask: "Can the agent discover this by reading the project, or does a linter enforce this?" If yes → delete.
-
-Remove everything matching:
-1. Linter-enforced rules (ESLint, Prettier, Biome, TypeScript strict)
-2. Marketing / goals / vision (zero code value)
-3. Obvious info the agent discovers itself (directory structure, framework defaults, deps from package.json)
-4. Verbose explanations (paragraphs where 1 line suffices, tutorials, history)
-5. Redundant specs (copies of config files, schema descriptions, env var lists)
-6. Generic best practices ("write clean code", "DRY", "SOLID")
-
-### Step 4: Keep only essentials
-
-- Project purpose (1-3 lines)
-- Tech stack (compact, non-obvious only)
-- Core commands (non-obvious only)
-- Testing commands
-- Important files (non-obvious only)
-- Project-specific rules (prohibitions + constraints)
-- Workflow (only if non-standard)
-
-### Step 5: Compress
-
-- Paragraphs → bullet points
-- 3-line rules → 1-line rules
-- Zero filler words ("In order to", "It's important to note that")
-- Merge related items
-
-### Step 6: Present diff
-
-Show before/after with line counts. For each removal, cite which bloat category it falls under.
-Let user approve before applying changes.
-
-**Target:** < 100 lines ideal, < 150 max.
-</optimize_workflow>
-
-<reference_guides>
-- **Optimization guide**: [references/optimize-guide.md](references/optimize-guide.md) — Research-backed bloat checklist, 6 removal categories, before/after examples
-- **Rules directory**: [references/rules-directory-guide.md](references/rules-directory-guide.md) — Complete .claude/rules/ guide with path-scoping, YAML syntax, symlinks, migration
-- **Prompting techniques**: [references/prompting-techniques.md](references/prompting-techniques.md) — Emphasis strategies, clarity techniques, constraint patterns
-- **Section templates**: [references/section-templates.md](references/section-templates.md) — Copy-paste templates for each section type
-- **Comprehensive example**: [references/comprehensive-example.md](references/comprehensive-example.md) — Full production SaaS CLAUDE.md
-- **Project patterns**: [references/project-patterns.md](references/project-patterns.md) — Next.js, Express, Python, Monorepo patterns
-</reference_guides>

package/agents-config/skills/claude-memory/references/comprehensive-example.md

@@ -1,175 +0,0 @@
-<comprehensive_example>
-This is a full-featured CLAUDE.md example for a production SaaS application. Use as inspiration, adapting to your specific project.
-
-```markdown
-# Thumbnail.io - AI Thumbnail Generator
-
-## About
-AI-powered YouTube thumbnail generator SaaS. Users create thumbnails via text prompts, reference persons, and inspiration images.
-
-## Tech Stack
-- **Framework**: Next.js 15 with App Router
-- **Language**: TypeScript (strict mode)
-- **Styling**: TailwindCSS v4 + shadcn/ui
-- **Database**: PostgreSQL with Prisma ORM
-- **Auth**: Better Auth with organization support
-- **Email**: React Email with Resend
-- **Payments**: Stripe (subscriptions + credits)
-- **Testing**: Vitest (unit), Playwright (e2e)
-- **Package Manager**: pnpm
-
-## Directory Structure
-```
-app/                  # Next.js App Router pages
-src/
-├── components/       # UI components (shadcn in ui/, custom in nowts/)
-├── features/         # Feature modules with actions, queries, schemas
-├── lib/              # Utilities and configurations
-├── hooks/            # Custom React hooks
-emails/               # React Email templates
-prisma/               # Database schema and migrations
-e2e/                  # End-to-end tests
-__tests__/            # Unit tests
-```
-
-## Key Features
-- **Editor**: `@/features/editor/` - Main thumbnail generation
-- **Persons**: `@/features/person/` - Reference person management
-- **Credits**: `@/features/credits/` - Usage-based credit system
-- **Forms**: `@/features/form/tanstack-form.tsx` - TanStack Form setup
-
-## Commands
-
-### Development
-- `pnpm dev` - Start development server with Turbopack
-- `pnpm build` - Build application
-- `pnpm ts` - TypeScript type checking
-- `pnpm lint` - ESLint with auto-fix
-- `pnpm clean` - Lint + type check + format
-
-### Testing
-**CRITICAL - Always use CI commands:**
-- `pnpm test:ci` - Unit tests (non-interactive)
-- `pnpm test:e2e:ci` - E2E tests (headless)
-
-**NEVER use interactive commands:**
-- ~~`pnpm test`~~ - Interactive mode breaks Claude Code
-- ~~`pnpm test:e2e`~~ - Interactive mode breaks Claude Code
-
-### Database
-- `pnpm prisma:seed` - Seed database
-- `pnpm better-auth:migrate` - Generate auth schema
-
-## Code Conventions
-
-### TypeScript
-- Use `type` over `interface` (enforced by ESLint)
-- No enums - use maps instead
-- Strict mode - no `any` types
-- Prefer `??` over `||`
-
-### React/Next.js
-- Prefer Server Components over Client Components
-- Use `"use client"` only for Web API access
-- Wrap client components in `Suspense` with fallback
-- **ALWAYS** use `PageProps<"/route/path">` for page components
-
-### Forms
-**CRITICAL - Use TanStack Form for ALL forms:**
-
-```tsx
-import { Form, useForm } from "@/features/form/tanstack-form";
-
-const form = useForm({
-  schema: MySchema,
-  defaultValues: { field: "" },
-  onSubmit: async (values) => { /* handle */ },
-});
-
-return (
-  <Form form={form}>
-    <form.AppField name="field">
-      {(field) => (
-        <field.Field>
-          <field.Label>Label</field.Label>
-          <field.Content>
-            <field.Input placeholder="..." />
-            <field.Message />
-          </field.Content>
-        </field.Field>
-      )}
-    </form.AppField>
-    <form.SubmitButton>Submit</form.SubmitButton>
-  </Form>
-);
-```
-
-**NEVER use React Hook Form directly.**
-
-### Server Actions
-- Suffix files with `.action.ts`
-- Use `@src/lib/actions/safe-actions.ts` for all actions
-- Use `resolveActionResult` helper for mutations
-
-### API Routes
-- All routes in `/app/api` MUST use `@src/lib/zod-route.ts`
-- All HTTP requests MUST use `@src/lib/up-fetch.ts` (never raw `fetch`)
-
-### Authentication
-- Server: `getUser()` (optional) or `getRequiredUser()` (required)
-- Client: `useSession()` from auth-client.ts
-- Organization: `getCurrentOrgCache()`
-
-## Styling Preferences
-- Use typography components from `@src/components/ui/typography.tsx`
-- Prefer `flex flex-col gap-4` over `space-y-4`
-- Use Card component from `@src/components/ui/card.tsx`
-- Never use emojis (prefer Lucide icons)
-- Never use gradients unless explicitly requested
-
-## TypeScript Imports
-- `@/*` → `@src`
-- `@email/*` → `@emails`
-- `@app/*` → `@app`
-
-## Workflow
-
-### Before Editing Files
-🚨 **CRITICAL** 🚨
-**Read at least 3 files** before editing:
-1. Similar files (understand patterns)
-2. Imported dependencies (understand APIs)
-
-### Debugging
-- Add logs at each step
-- Ask user to send logs for debugging
-
-## Important Files
-- `src/lib/auth.ts` - Auth configuration
-- `src/features/dialog-manager/` - Global dialog system
-- `src/features/form/tanstack-form.tsx` - Form setup (**CRITICAL**)
-- `src/lib/actions/safe-actions.ts` - Server action utilities
-- `src/lib/zod-route.ts` - API route utilities
-- `src/site-config.ts` - Site configuration
-
-## Database
-- Main schema: `prisma/schema/schema.prisma`
-- Auth schema: `prisma/schema/better-auth.prisma` (auto-generated)
-- All queries must include `tenant_id` for multi-tenant support
-```
-</comprehensive_example>
-
-<usage_notes>
-This example demonstrates:
-
-- Clear tech stack documentation
-- Directory structure visualization
-- Critical command distinctions (CI vs interactive)
-- Specific code patterns with examples
-- Emphasis on critical rules
-- File location references
-- Workflow requirements
-- Import path conventions
-
-Adapt sections to match your project's actual structure and conventions.
-</usage_notes>