javi-forge 1.2.0 → 1.4.0

package/ai-config/commands/workflows/compound.md

@@ -1,89 +0,0 @@
----
-name: compound
-description: Post-completion workflow — summarize what was learned, append to learnings.md, and suggest CLAUDE.md improvements. Triggered after significant task completion.
-category: workflows
----
-
-# /workflows:compound
-
-Capture learnings after completing significant work and improve project AI configuration.
-
-## Usage
-
-```
-/workflows:compound [<feature-name>]
-```
-
-Run this after completing a feature, fixing a complex bug, or finishing a refactoring session.
-
-## What It Does
-
-1. **Summarizes the work**: What was built, changed, or discovered
-2. **Extracts learnings**: Patterns found, mistakes made, approaches that worked
-3. **Appends to learnings.md**: Persistent knowledge base at project root
-4. **Suggests CLAUDE.md improvements**: 1-3 specific, actionable improvements
-
-## PostToolUse Pattern
-
-This command is designed to trigger after significant task completion. Add to your workflow:
-```
-After every /workflows:work completion → run /workflows:compound
-After every major debugging session → run /workflows:compound
-After every architecture decision → run /workflows:compound
-```
-
-## Process
-
-```
-STEP 1: Review what was just completed
-         → Read tasks/<feature-name>/plan.md (if exists)
-         → Read tasks/<feature-name>/files-edited.md (if exists)
-         → Reflect on the conversation/session
-
-STEP 2: Synthesize learnings
-         → What patterns were discovered?
-         → What went wrong and how was it resolved?
-         → What would you do differently next time?
-         → What project-specific context would help future sessions?
-
-STEP 3: Append to learnings.md
-         → Create if it doesn't exist
-         → Add dated entry with feature name
-
-STEP 4: Suggest CLAUDE.md improvements
-         → Review current CLAUDE.md
-         → Propose 1-3 specific additions or changes
-```
-
-## learnings.md Format
-
-```markdown
-## YYYY-MM-DD — <feature-name or topic>
-
-### What Was Done
-[Brief summary of work completed]
-
-### Key Learnings
-- [Learning 1: specific and reusable]
-- [Learning 2: specific and reusable]
-
-### What Went Wrong
-- [Issue encountered and how it was resolved]
-
-### Patterns to Reuse
-- [Approach that worked well and should be applied again]
-```
-
-## CLAUDE.md Suggestion Format
-
-```
-Suggested CLAUDE.md improvements:
-
-1. **Add command to run tests**: `npm test` — discovered during this session that
-   tests need to be run with --watch=false in CI context
-
-2. **Document auth pattern**: Project uses custom JWT middleware — add to CLAUDE.md
-   so future sessions don't re-discover this
-
-3. **Note environment variables**: DATABASE_URL must be set — add to setup section
-```

package/ai-config/commands/workflows/diagnose.md

@@ -1,70 +0,0 @@
----
-name: diagnose
-description: Chained diagnosis workflow — investigate issue, verify with devil's advocate, then solve. Uses ACH (Analysis of Competing Hypotheses).
-category: workflows
-chain:
-  - investigate
-  - verify
-  - solve
-suggests_next:
-  - /workflows:compound
-  - /workflows:review
----
-
-# /workflows:diagnose
-
-Structured diagnosis workflow for complex bugs and issues.
-
-## Usage
-
-```
-/workflows:diagnose <issue-description>
-```
-
-## Chain Steps
-
-### Step 1: Investigate
-Gather evidence and generate hypotheses using the debug-mode skill.
-
-1. Reproduce the issue (or understand the reproduction steps)
-2. Gather context: error messages, stack traces, recent changes, logs
-3. Generate 3-5 competing hypotheses ranked by likelihood
-4. Map evidence to hypotheses (which evidence supports/contradicts each)
-
-Output: ACH matrix
-
-```
-## ACH Matrix: <issue>
-| Evidence | H1 (70%) | H2 (20%) | H3 (10%) |
-|----------|----------|----------|----------|
-| Error at line 42 | Consistent | Inconsistent | Neutral |
-| Works in staging | Inconsistent | Consistent | Consistent |
-```
-
-**After completion, suggest**: "Investigation complete. Run step 2 for devil's advocate verification, or jump to step 3 if confident."
-
-### Step 2: Verify (Devil's Advocate)
-Challenge the leading hypothesis:
-
-1. **Assume H1 is wrong** — what evidence would you expect to see?
-2. **Check for that evidence** — does it exist?
-3. **Try to reproduce with H1 fixed** — does the fix actually work?
-4. If H1 survives the challenge, proceed to fix. Otherwise, promote H2.
-
-**After completion, suggest**: "Verification complete. H[N] confirmed. Run step 3 to implement the fix."
-
-### Step 3: Solve
-Implement the fix based on the verified hypothesis:
-
-1. Write the fix
-2. Verify the original reproduction steps pass
-3. Run the full test suite
-4. Document what was wrong and why (for Engram)
-
-**After completion, suggest**: "Fix applied. Next: `/workflows:compound` to capture learnings, or `/workflows:review` for code review."
-
-## Rules
-
-1. Never skip step 2 for Medium+ complexity issues
-2. Always document the root cause in Engram
-3. If 3 rounds of investigation don't converge, escalate to user

package/ai-config/commands/workflows/discover.md

@@ -1,86 +0,0 @@
----
-name: discover
-description: Chained discovery workflow — brainstorm ideas, identify assumptions, prioritize experiments, then execute. Progressive suggestions after each step.
-category: workflows
-chain:
-  - brainstorm
-  - identify-assumptions
-  - prioritize
-  - experiment
-suggests_next:
-  - /workflows:plan
-  - /workflows:work
----
-
-# /workflows:discover
-
-End-to-end discovery workflow that chains 4 steps with progressive suggestions.
-
-## Usage
-
-```
-/workflows:discover <topic>
-```
-
-## Chain Steps
-
-### Step 1: Brainstorm
-Generate 5-10 ideas related to the topic. No filtering, quantity over quality.
-
-Output format:
-```
-## Ideas for: <topic>
-1. [idea] — [one-line rationale]
-2. [idea] — [one-line rationale]
-...
-```
-
-**After completion, suggest**: "Ideas generated. Run step 2 to identify assumptions, or pick specific ideas to explore."
-
-### Step 2: Identify Assumptions
-For the top 3-5 ideas, list the key assumptions that must be true for each to work.
-
-Output format:
-```
-## Assumptions
-### Idea 1: [name]
-- [assumption] — risk: high/medium/low
-- [assumption] — risk: high/medium/low
-```
-
-**After completion, suggest**: "Assumptions mapped. Run step 3 to prioritize by risk, or go back to brainstorm more."
-
-### Step 3: Prioritize
-Rank ideas by: (1) impact, (2) effort, (3) assumption risk. Create a 2x2 matrix.
-
-Output format:
-```
-## Priority Matrix
-| Idea | Impact | Effort | Risk | Priority |
-|------|--------|--------|------|----------|
-```
-
-**After completion, suggest**: "Priority matrix ready. Run step 4 to design experiments for the top picks."
-
-### Step 4: Experiment Design
-For the top 2-3 ideas, design a minimal experiment to validate the riskiest assumption.
-
-Output format:
-```
-## Experiments
-### Experiment 1: [name]
-- Validates: [assumption]
-- Method: [how to test]
-- Success criteria: [what proves it works]
-- Effort: [time estimate]
-```
-
-**After completion, suggest**: "Experiments designed. Next steps: `/workflows:plan` to plan implementation, or `/workflows:work` to start building."
-
-## Chaining Rules
-
-1. Each step can be run independently or as part of the chain
-2. Output of each step is input context for the next
-3. Progressive suggestions appear after every step completion
-4. User can skip steps or go back at any point
-5. The full chain takes ~15 minutes of agent time

package/ai-config/commands/workflows/plan.md

@@ -1,77 +0,0 @@
----
-name: plan
-description: Decompose a feature into structured tasks with goal, acceptance criteria, estimates, risks, and dependencies. Saves to tasks/<feature-name>/plan.md
-category: workflows
----
-
-# /workflows:plan
-
-Decompose a feature or task into a structured, actionable plan before writing any code.
-
-## Usage
-
-```
-/workflows:plan <feature-name>
-```
-
-## What It Does
-
-1. **Clarifies the goal**: What problem does this solve? What's the success state?
-2. **Defines acceptance criteria**: Concrete, testable conditions for "done"
-3. **Breaks down tasks**: Ordered list with time estimates and dependencies
-4. **Identifies risks**: What could go wrong and how to mitigate it
-5. **Saves the plan**: Writes to `tasks/<feature-name>/plan.md`
-
-## Process
-
-```
-STEP 1: Ask clarifying questions if the feature is ambiguous
-STEP 2: Draft the plan using the template below
-STEP 3: Save to tasks/<feature-name>/plan.md
-STEP 4: Confirm with user before starting implementation
-```
-
-## Plan Template
-
-```markdown
-# Plan: <feature-name>
-
-## Goal
-[One paragraph: what this feature does and why it matters]
-
-## Acceptance Criteria
-- [ ] [Testable condition 1]
-- [ ] [Testable condition 2]
-- [ ] [Testable condition 3]
-
-## Task List
-
-| # | Task | Estimate | Depends On | Status |
-|---|------|----------|------------|--------|
-| 1 | [Task description] | 30m | — | pending |
-| 2 | [Task description] | 1h | 1 | pending |
-| 3 | [Task description] | 45m | 2 | pending |
-
-## Risks
-
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| [Risk 1] | Low/Med/High | Low/Med/High | [How to handle it] |
-
-## Dependencies
-- External services: [list any]
-- Other features/branches: [list any]
-- Team: [list any people/approvals needed]
-
-## Notes
-[Anything else relevant to implementation]
-```
-
-## Output Location
-
-Plan is saved to: `tasks/<feature-name>/plan.md`
-
-If the directory doesn't exist, create it:
-```bash
-mkdir -p tasks/<feature-name>
-```

package/ai-config/commands/workflows/review.md

@@ -1,78 +0,0 @@
----
-name: review
-description: Multi-perspective code review using code-reviewer and security-auditor agents on staged changes. Reads review policy before reviewing. Outputs inline comments with severity.
-category: workflows
----
-
-# /workflows:review
-
-Run a multi-perspective review on staged changes before committing or opening a PR.
-
-## Usage
-
-```
-/workflows:review [--scope staged|branch|<file-path>]
-```
-
-## What It Does
-
-1. **Loads review policy**: Reads `.ai-config/prompts/review-policy.md` for project standards
-2. **Gathers changes**: Gets staged diff or branch diff depending on scope
-3. **Runs code-reviewer perspective**: Quality, SOLID, DRY, naming, test coverage
-4. **Runs security-auditor perspective**: OWASP, injection, auth/authz, secrets
-5. **Outputs consolidated report**: Inline comments grouped by file with severity
-
-## Process
-
-```
-STEP 1: Load .ai-config/prompts/review-policy.md (if exists)
-         → Use project-specific standards for what constitutes a violation
-
-STEP 2: Gather diff
-         git diff --staged                    # for staged changes
-         git diff main...HEAD                 # for branch changes
-
-STEP 3: Code Quality Review (code-reviewer agent)
-         → Check each changed file for quality issues
-
-STEP 4: Security Review (security-auditor agent)
-         → Check for vulnerabilities, secrets, auth issues
-
-STEP 5: Consolidate and output report
-```
-
-## Output Format
-
-### Per-file findings:
-
-```
-## src/path/to/file.ts
-
-🔴 [CRITICAL] line 42 — Hardcoded secret in source
-   Problem: API key visible in source code
-   Fix: Move to environment variable, add to .gitignore
-
-🟡 [WARNING] line 87 — Function violates Single Responsibility
-   Problem: processPayment() handles validation + DB + email
-   Fix: Extract into validatePayment(), savePayment(), notifyUser()
-
-🔵 [SUGGESTION] line 103 — Variable name is unclear
-   Problem: `d` is not descriptive
-   Fix: Rename to `durationMs` or `delaySeconds`
-```
-
-### Summary block:
-
-```
-## Review Summary
-Critical: N  |  Warnings: N  |  Suggestions: N
-Recommendation: ✅ APPROVE | ⚠️ APPROVE WITH NOTES | ❌ REQUEST CHANGES
-```
-
-## Severity Guide
-
-| Severity | Symbol | Meaning | Action |
-|----------|--------|---------|--------|
-| Critical | 🔴 | Bug, security, data loss | Must fix before merge |
-| Warning | 🟡 | Quality, SOLID, test gap | Should fix |
-| Suggestion | 🔵 | Style, naming, minor | Consider fixing |

package/ai-config/commands/workflows/work.md

@@ -1,75 +0,0 @@
----
-name: work
-description: Execute the current plan by creating a git worktree, checking off tasks, and tracking files edited. Reads plan from tasks/<feature-name>/plan.md
-category: workflows
----
-
-# /workflows:work
-
-Execute the plan for a feature, tracking progress and edited files as you go.
-
-## Usage
-
-```
-/workflows:work <feature-name>
-```
-
-## What It Does
-
-1. **Reads the plan**: Loads `tasks/<feature-name>/plan.md`
-2. **Creates git worktree**: Isolates work in a dedicated branch/worktree
-3. **Executes tasks in order**: Respects task dependencies from the plan
-4. **Tracks progress**: Checks off tasks as they complete
-5. **Records file changes**: Appends to `tasks/<feature-name>/files-edited.md`
-
-## Process
-
-```
-STEP 1: Read tasks/<feature-name>/plan.md
-         → If not found, prompt user to run /workflows:plan first
-
-STEP 2: Create git worktree
-         git worktree add ../worktrees/<feature-name> -b feature/<feature-name>
-
-STEP 3: For each task in the plan (in dependency order):
-         a. Mark task as "in-progress" in the plan
-         b. Implement the task
-         c. Run tests if applicable
-         d. Mark task as "done" ✅ in plan.md
-         e. Append edited files to files-edited.md
-
-STEP 4: When all tasks complete, summarize what was done
-```
-
-## files-edited.md Format
-
-```markdown
-## Files Changed — <feature-name>
-
-### <task-name>
-- `src/path/to/file.ts` — [what changed]
-- `tests/path/to/file.test.ts` — [what changed]
-
-### <next-task>
-- ...
-```
-
-## Git Worktree Commands
-
-```bash
-# Create worktree for the feature
-git worktree add ../worktrees/<feature-name> -b feature/<feature-name>
-
-# List active worktrees
-git worktree list
-
-# Remove worktree after merging
-git worktree remove ../worktrees/<feature-name>
-```
-
-## Rules
-
-- Do not skip tasks unless they're blocked (document why in the plan)
-- Commit after each logical unit of work: `git commit -m "feat: <task-name>"`
-- Update `tasks/<feature-name>/plan.md` task statuses in real time
-- If a task reveals new sub-tasks, add them to the plan before proceeding

package/ai-config/config.yaml

@@ -1,18 +0,0 @@
-# .ai-config/config.yaml
-# Declarative configuration for sync-ai-config.sh
-# Run: ./scripts/sync-ai-config.sh  (no args = reads this file)
-#
-# yaml-language-server: $schema=../schemas/ai-config.schema.json
-
-# Targets to sync when running without arguments
-targets:
-  - claude
-  - opencode
-  - cursor
-  - aider
-  - gemini
-
-# Sync options
-sync:
-  # Claude mode: 'overwrite' or 'merge' (merge appends/updates generated section)
-  claude_mode: overwrite

package/ai-config/hooks/_TEMPLATE.md

@@ -1,96 +0,0 @@
----
-# =============================================================================
-# HOOK TEMPLATE
-# =============================================================================
-# Hooks se ejecutan en respuesta a eventos del AI CLI
-# =============================================================================
-
-name: mi-hook
-description: Descripción del hook
-
-# Evento que dispara el hook
-# Opciones: PreToolUse, PostToolUse, Stop, SessionStart, SessionEnd
-event: PreToolUse
-
-# Filtrar por herramientas específicas (opcional)
-# Si no se especifica, aplica a todas
-tools:
-  - Bash
-  - Write
-
-# Filtrar por patrón en el contenido (opcional)
-match_pattern: "rm -rf|drop table|delete from"
-
-# Acción: block | warn | log | execute
-action: block
-
-metadata:
-  author: tu-usuario
-  version: "1.0"
----
-
-# [Nombre del Hook]
-
-> [Descripción de una línea]
-
-## Propósito
-
-[Qué hace este hook y por qué existe]
-
-## Evento
-
-- **Trigger:** [PreToolUse | PostToolUse | Stop | etc.]
-- **Herramientas:** [Lista de herramientas o "todas"]
-- **Condición:** [Cuándo se activa]
-
-## Lógica
-
-```
-SI [condición]
-ENTONCES [acción]
-SINO [alternativa]
-```
-
-## Implementación
-
-### Para Claude Code
-
-```json
-{
-  "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "Bash",
-        "command": "echo 'Validating...'"
-      }
-    ]
-  }
-}
-```
-
-### Para OpenCode
-
-```yaml
-hooks:
-  pre_tool_use:
-    - tool: Bash
-      action: validate
-```
-
-## Ejemplos
-
-### Ejemplo 1: Hook activa
-
-**Contexto:**
-```
-[Descripción del contexto]
-```
-
-**Resultado:**
-```
-[Qué hace el hook]
-```
-
-## Notas
-
-[Consideraciones adicionales]

package/ai-config/hooks/block-dangerous-commands.md

@@ -1,75 +0,0 @@
----
-name: block-dangerous-commands
-description: Bloquea comandos peligrosos antes de ejecutar
-event: PreToolUse
-tools:
-  - Bash
-match_pattern: "rm -rf /|rm -rf ~|drop database|truncate table|:(){ :|:& };:|mkfs|dd if=|> /dev/sd|chmod -R 777 /|curl.*| bash|wget.*| sh"
-action: block
-metadata:
-  author: project-starter-framework
-  version: "1.0"
----
-
-# Block Dangerous Commands Hook
-
-> Previene ejecución de comandos potencialmente destructivos.
-
-## Propósito
-
-Interceptar comandos de Bash que podrían causar daño irreversible al sistema o datos.
-
-## Comandos Bloqueados
-
-| Patrón | Riesgo |
-|--------|--------|
-| `rm -rf /` | Borrar sistema completo |
-| `rm -rf ~` | Borrar home directory |
-| `drop database` | Eliminar base de datos |
-| `truncate table` | Vaciar tablas |
-| `:(){ :|:& };:` | Fork bomb |
-| `mkfs` | Formatear disco |
-| `dd if=` | Escritura directa a disco |
-| `> /dev/sd*` | Sobrescribir disco |
-| `chmod -R 777 /` | Permisos inseguros |
-| `curl \| bash` | Ejecución remota |
-| `wget \| sh` | Ejecución remota |
-
-## Comportamiento
-
-1. **Detecta** comando peligroso en input de Bash
-2. **Bloquea** ejecución
-3. **Notifica** al usuario con explicación
-4. **Sugiere** alternativa segura si existe
-
-## Implementación Claude Code
-
-```json
-{
-  "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "Bash",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo '$TOOL_INPUT' | grep -qE 'rm -rf /|rm -rf ~|drop database' && echo 'BLOCKED: Dangerous command detected' && exit 1 || exit 0"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-## Excepciones
-
-Si necesitás ejecutar un comando bloqueado legítimamente:
-
-1. Revisar el comando manualmente
-2. Usar `--no-verify` o equivalente
-3. Documentar la razón
-
-## Notas
-
-Este hook es una capa de seguridad adicional, no reemplaza el sentido común.