aiblueprint-cli 1.4.99 → 1.4.101

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aiblueprint-cli",
-  "version": "1.4.99",
+  "version": "1.4.101",
   "description": "AIBlueprint CLI for setting up AI coding configurations",
   "author": "AIBlueprint",
   "license": "MIT",

package/agents-config/skills/apex/templates/00-context.md

@@ -1,55 +0,0 @@
-# APEX Task: {{task_id}}
-
-**Created:** {{timestamp}}
-**Task:** {{task_description}}
-
----
-
-## Configuration
-
-| Flag | Value |
-|------|-------|
-| Auto mode (`-a`) | {{auto_mode}} |
-| Examine mode (`-x`) | {{examine_mode}} |
-| Save mode (`-s`) | {{save_mode}} |
-| Test mode (`-t`) | {{test_mode}} |
-| Economy mode (`-e`) | {{economy_mode}} |
-| Branch mode (`-b`) | {{branch_mode}} |
-| PR mode (`-pr`) | {{pr_mode}} |
-| Interactive mode (`-i`) | {{interactive_mode}} |
-| Tasks mode (`-k`) | {{tasks_mode}} |
-| Verify mode (`-v`) | {{verify_mode}} |
-| Branch name | {{branch_name}} |
-
----
-
-## User Request
-
-```
-{{original_input}}
-```
-
----
-
-## Acceptance Criteria
-
-_To be defined in step-01-analyze.md_
-
----
-
-## Progress
-
-| Step | Status | Timestamp |
-|------|--------|-----------|
-| 00-init | ⏸ Pending | |
-| 01-analyze | ⏸ Pending | |
-| 02-plan | ⏸ Pending | |
-| 02b-tasks | {{tasks_status}} | |
-| 03-execute | ⏸ Pending | |
-| 04-validate | ⏸ Pending | |
-| 05-examine | {{examine_status}} | |
-| 06-resolve | {{examine_status}} | |
-| 07-tests | {{test_status}} | |
-| 08-run-tests | {{test_status}} | |
-| 10-verify | {{verify_status}} | |
-| 09-finish | {{pr_status}} | |

package/agents-config/skills/apex/templates/01-analyze.md

@@ -1,10 +0,0 @@
-# Step 01: Analyze
-
-**Task:** {{task_description}}
-**Started:** {{timestamp}}
-
----
-
-## Context Discovery
-
-_Findings will be appended here as exploration progresses..._

package/agents-config/skills/apex/templates/02-plan.md

@@ -1,10 +0,0 @@
-# Step 02: Plan
-
-**Task:** {{task_description}}
-**Started:** {{timestamp}}
-
----
-
-## Planning Progress
-
-_Implementation plan will be written here..._

package/agents-config/skills/apex/templates/03-execute.md

@@ -1,10 +0,0 @@
-# Step 03: Execute
-
-**Task:** {{task_description}}
-**Started:** {{timestamp}}
-
----
-
-## Implementation Log
-
-_Changes will be logged here as implementation progresses..._

package/agents-config/skills/apex/templates/04-validate.md

@@ -1,10 +0,0 @@
-# Step 04: Validate
-
-**Task:** {{task_description}}
-**Started:** {{timestamp}}
-
----
-
-## Validation Progress
-
-_Validation results will be appended here..._

package/agents-config/skills/apex/templates/05-examine.md

@@ -1,10 +0,0 @@
-# Step 05: Examine
-
-**Task:** {{task_description}}
-**Started:** {{timestamp}}
-
----
-
-## Adversarial Review
-
-_Review findings will be documented here..._

package/agents-config/skills/apex/templates/06-resolve.md

@@ -1,10 +0,0 @@
-# Step 06: Resolve
-
-**Task:** {{task_description}}
-**Started:** {{timestamp}}
-
----
-
-## Resolution Log
-
-_Fixes will be logged here..._

package/agents-config/skills/apex/templates/07-tests.md

@@ -1,10 +0,0 @@
-# Step 07: Tests
-
-**Task:** {{task_description}}
-**Started:** {{timestamp}}
-
----
-
-## Test Analysis and Creation
-
-_Test strategy and implementation will be documented here..._

package/agents-config/skills/apex/templates/08-run-tests.md

@@ -1,10 +0,0 @@
-# Step 08: Run Tests
-
-**Task:** {{task_description}}
-**Started:** {{timestamp}}
-
----
-
-## Test Runner Log
-
-_Test execution results will be logged here..._

package/agents-config/skills/apex/templates/09-finish.md

@@ -1,10 +0,0 @@
-# Step 09: Finish
-
-**Task:** {{task_description}}
-**Started:** {{timestamp}}
-
----
-
-## Pull Request Creation
-
-_PR creation process will be logged here..._

package/agents-config/skills/apex/templates/10-verify.md

@@ -1,9 +0,0 @@
-# Step 10: Verify - {{task_id}}
-
-**Task:** {{task_description}}
-
----
-
-## Verification Results
-
-_Results will be appended during execution_

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

@@ -1,195 +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 | Always (if save_mode) |
-| `05-examine.md` | Adversarial review findings | Only if examine_mode enabled |
-| `06-resolve.md` | Finding resolution log | Only if examine_mode enabled |
-| `07-tests.md` | Test analysis and creation | Only if test_mode enabled |
-| `08-run-tests.md` | Test runner log | Only if test_mode enabled |
-| `09-finish.md` | PR creation log | Only if pr_mode enabled |
-| `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` |
-| `{{examine_mode}}` | Examine mode flag | `true` or `false` |
-| `{{save_mode}}` | Save mode flag | `true` or `false` |
-| `{{test_mode}}` | Test mode flag | `true` or `false` |
-| `{{economy_mode}}` | Economy mode flag | `true` or `false` |
-| `{{branch_mode}}` | Branch mode flag | `true` or `false` |
-| `{{pr_mode}}` | PR 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` |
-| `{{examine_status}}` | Progress status for examine steps | `⏸ Pending` or `⏭ Skip` |
-| `{{test_status}}` | Progress status for test steps | `⏸ Pending` or `⏭ Skip` |
-| `{{pr_status}}` | Progress status for PR step | `⏸ Pending` or `⏭ Skip` |
-
-## Setup Script
-
-### `setup-templates.sh`
-
-Initializes all template files in the output directory with variables replaced.
-
-**Usage:**
-```bash
-bash scripts/setup-templates.sh \
-  "task_id" \
-  "task_description" \
-  "auto_mode" \
-  "examine_mode" \
-  "save_mode" \
-  "test_mode" \
-  "economy_mode" \
-  "branch_mode" \
-  "pr_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
-├── 05-examine.md      # Only if examine_mode
-├── 06-resolve.md      # Only if examine_mode
-├── 07-tests.md        # Only if test_mode
-├── 08-run-tests.md    # Only if test_mode
-└── 09-finish.md       # Only if pr_mode
-```
-
-## 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 × 9 steps = ~1,800 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 × 9 steps = ~450 tokens
-
-**Total savings:** ~1,350 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/prompt-creator/SKILL.md

@@ -1,285 +0,0 @@
----
-name: prompt-creator
-description: Expert prompt engineering for creating effective prompts for Claude, GPT, and other LLMs. Use when writing system prompts, user prompts, few-shot examples, or optimizing existing prompts for better performance.
----
-
-<objective>
-Create highly effective prompts using proven techniques from Anthropic and OpenAI research. This skill covers all major prompting methodologies: clarity, structure, examples, reasoning, and advanced patterns.
-
-Every prompt created should be clear, specific, and optimized for the target model.
-</objective>
-
-<quick_start>
-<workflow>
-
-1. **Clarify purpose**: What should the prompt accomplish?
-2. **Identify model**: Claude, GPT, or other (techniques vary slightly)
-3. **Select techniques**: Choose from core techniques based on task complexity
-4. **Structure content**: Use XML tags (Claude) or markdown (GPT) for organization
-5. **Add examples**: Include few-shot examples for format-sensitive outputs
-6. **Define success**: Add clear success criteria
-7. **Test and iterate**: Refine based on outputs
-   </workflow>
-
-<core_structure>
-Every effective prompt has:
-
-```xml
-<context>
-Background information the model needs
-</context>
-
-<task>
-Clear, specific instruction of what to do
-</task>
-
-<requirements>
-- Specific constraints
-- Output format
-- Edge cases to handle
-</requirements>
-
-<examples>
-Input/output pairs demonstrating expected behavior
-</examples>
-
-<success_criteria>
-How to know the task was completed correctly
-</success_criteria>
-```
-
-</core_structure>
-</quick_start>
-
-<core_techniques>
-<technique name="be_clear_and_direct">
-**Priority**: Always apply first
-
-- State exactly what you want
-- Avoid ambiguous language ("try to", "maybe", "generally")
-- Use "Always..." or "Never..." instead of "Should probably..."
-- Provide specific output format requirements
-
-See: [references/clarity-principles.md](references/clarity-principles.md)
-</technique>
-
-<technique name="use_xml_tags">
-**When**: Claude prompts, complex structure needed
-
-Claude was trained with XML tags. Use them for:
-
-- Separating sections: `<context>`, `<task>`, `<output>`
-- Wrapping data: `<document>`, `<schema>`, `<example>`
-- Defining boundaries: Clear start/end of sections
-
-See: [references/xml-structure.md](references/xml-structure.md)
-</technique>
-
-<technique name="few_shot_examples">
-**When**: Output format matters, pattern recognition easier than rules
-
-Provide 2-4 input/output pairs:
-
-```xml
-<examples>
-<example number="1">
-<input>User clicked signup button</input>
-<output>track('signup_initiated', { source: 'homepage' })</output>
-</example>
-</examples>
-```
-
-See: [references/few-shot-patterns.md](references/few-shot-patterns.md)
-</technique>
-
-<technique name="chain_of_thought">
-**When**: Complex reasoning, math, multi-step analysis
-
-Add explicit reasoning instructions:
-
-- "Think step by step before answering"
-- "First analyze X, then consider Y, finally conclude Z"
-- Use `<thinking>` tags for Claude's extended thinking
-
-See: [references/reasoning-techniques.md](references/reasoning-techniques.md)
-</technique>
-
-<technique name="system_prompts">
-**When**: Setting persistent behavior, role, constraints
-
-System prompts set the foundation:
-
-- Define Claude's role and expertise
-- Set constraints and boundaries
-- Establish output format expectations
-
-See: [references/system-prompt-patterns.md](references/system-prompt-patterns.md)
-</technique>
-
-<technique name="prefilling">
-**When**: Enforcing specific output format (Claude-specific)
-
-Start Claude's response to guide format:
-
-```
-Assistant: {"result":
-```
-
-Forces JSON output without preamble.
-</technique>
-
-<technique name="context_management">
-**When**: Long-running tasks, multi-session work, large context usage
-
-For Claude 4.5 with context awareness:
-
-- Inform about automatic context compaction
-- Add state tracking (JSON, progress.txt, git)
-- Use test-first patterns for complex implementations
-- Enable autonomous task completion across context windows
-
-See: [references/context-management.md](references/context-management.md)
-</technique>
-</core_techniques>
-
-<prompt_creation_workflow>
-<step_0>
-**Gather requirements** using AskUserQuestion:
-
-1. What is the prompt's purpose?
-   - Generate content
-   - Analyze/extract information
-   - Transform data
-   - Make decisions
-   - Other
-
-2. What model will use this prompt?
-   - Claude (use XML tags)
-   - GPT (use markdown structure)
-   - Other/multiple
-
-3. What complexity level?
-   - Simple (single task, clear output)
-   - Medium (multiple steps, some nuance)
-   - Complex (reasoning, edge cases, validation)
-
-4. Output format requirements?
-   - Free text
-   - JSON/structured data
-   - Code
-   - Specific template
-     </step_0>
-
-<step_1>
-**Draft the prompt** using this template:
-
-```xml
-<context>
-[Background the model needs to understand the task]
-</context>
-
-<objective>
-[Clear statement of what to accomplish]
-</objective>
-
-<instructions>
-[Step-by-step process, numbered if sequential]
-</instructions>
-
-<constraints>
-[Rules, limitations, things to avoid]
-</constraints>
-
-<output_format>
-[Exact structure of expected output]
-</output_format>
-
-<examples>
-[2-4 input/output pairs if format matters]
-</examples>
-
-<success_criteria>
-[How to verify the task was done correctly]
-</success_criteria>
-```
-
-</step_1>
-
-<step_2>
-**Apply relevant techniques** based on complexity:
-
-- **Simple**: Clear instructions + output format
-- **Medium**: Add examples + constraints
-- **Complex**: Add reasoning steps + edge cases + validation
-  </step_2>
-
-<step_3>
-**Review checklist**:
-
-- [ ] Is the task clearly stated?
-- [ ] Are ambiguous words removed?
-- [ ] Is output format specified?
-- [ ] Are edge cases addressed?
-- [ ] Would a person with no context understand it?
-      </step_3>
-      </prompt_creation_workflow>
-
-<anti_patterns>
-<pitfall name="vague_instructions">
-❌ "Help with the data"
-✅ "Extract email addresses from the CSV, remove duplicates, output as JSON array"
-</pitfall>
-
-<pitfall name="negative_prompting">
-❌ "Don't use technical jargon"
-✅ "Write in plain language suitable for a non-technical audience"
-</pitfall>
-
-<pitfall name="no_examples">
-❌ Describing format in words only
-✅ Showing 2-3 concrete input/output examples
-</pitfall>
-
-<pitfall name="missing_edge_cases">
-❌ "Process the file"
-✅ "Process the file. If empty, return []. If malformed, return error with line number."
-</pitfall>
-
-See: [references/anti-patterns.md](references/anti-patterns.md)
-</anti_patterns>
-
-<reference_guides>
-**Core principles:**
-
-- [references/clarity-principles.md](references/clarity-principles.md) - Being clear and direct
-- [references/xml-structure.md](references/xml-structure.md) - Using XML tags effectively
-
-**Techniques:**
-
-- [references/few-shot-patterns.md](references/few-shot-patterns.md) - Example-based prompting
-- [references/reasoning-techniques.md](references/reasoning-techniques.md) - Chain of thought, step-by-step
-- [references/system-prompt-patterns.md](references/system-prompt-patterns.md) - System prompt templates
-- [references/context-management.md](references/context-management.md) - Context windows, long-horizon reasoning, state tracking
-
-**Best practices by vendor:**
-
-- [references/anthropic-best-practices.md](references/anthropic-best-practices.md) - Claude-specific techniques
-- [references/openai-best-practices.md](references/openai-best-practices.md) - GPT-specific techniques
-
-**Quality:**
-
-- [references/anti-patterns.md](references/anti-patterns.md) - Common mistakes to avoid
-- [references/prompt-templates.md](references/prompt-templates.md) - Ready-to-use templates
-  </reference_guides>
-
-<success_criteria>
-A well-crafted prompt has:
-
-- Clear, unambiguous objective
-- Specific output format with example
-- Relevant context provided
-- Edge cases addressed
-- No vague language (try, maybe, generally)
-- Appropriate technique selection for task complexity
-- Success criteria defined
-  </success_criteria>