javi-forge 1.2.0 → 1.4.0

package/ai-config/skills/workflow/claude-automation-recommender/SKILL.md

@@ -1,299 +0,0 @@
----
-name: claude-automation-recommender
-description: >
-  Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers).
-  Trigger: automation recommendations, optimize Claude Code, setup Claude Code, improve workflows, MCP servers, hooks
-tools:
-  - Read
-  - Glob
-  - Grep
-  - Bash
-metadata:
-  author: project-starter-framework
-  version: "2.0"
-  tags: [claude-code, automation, mcp, hooks, skills, plugins]
-  updated: "2026-02"
----
-
-# Claude Automation Recommender
-
-Analyze codebase patterns to recommend tailored Claude Code automations across all extensibility options.
-
-**This skill is read-only.** It analyzes the codebase and outputs recommendations. It does NOT create or modify any files. Users implement the recommendations themselves or ask Claude separately to help build them.
-
-## Output Guidelines
-
-- **Recommend 1-2 of each type**: Don't overwhelm - surface the top 1-2 most valuable automations per category
-- **If user asks for a specific type**: Focus only on that type and provide more options (3-5 recommendations)
-- **Go beyond the reference lists**: The reference files contain common patterns, but use web search to find recommendations specific to the codebase's tools, frameworks, and libraries
-- **Tell users they can ask for more**: End by noting they can request more recommendations for any specific category
-
-## Automation Types Overview
-
-| Type | Best For |
-|------|----------|
-| **Hooks** | Automatic actions on tool events (format on save, lint, block edits) |
-| **Subagents** | Specialized reviewers/analyzers that run in parallel |
-| **Skills** | Packaged expertise, workflows, and repeatable tasks (invoked by Claude or user via `/skill-name`) |
-| **Plugins** | Collections of skills that can be installed |
-| **MCP Servers** | External tool integrations (databases, APIs, browsers, docs) |
-
-## Workflow
-
-### Phase 1: Codebase Analysis
-
-Gather project context:
-
-```bash
-# Detect project type and tools
-ls -la package.json pyproject.toml Cargo.toml go.mod pom.xml 2>/dev/null
-cat package.json 2>/dev/null | head -50
-
-# Check dependencies for MCP server recommendations
-cat package.json 2>/dev/null | grep -E '"(react|vue|angular|next|express|fastapi|django|prisma|supabase|stripe)"'
-
-# Check for existing Claude Code config
-ls -la .claude/ CLAUDE.md 2>/dev/null
-
-# Analyze project structure
-ls -la src/ app/ lib/ tests/ components/ pages/ api/ 2>/dev/null
-```
-
-**Key Indicators to Capture:**
-
-| Category | What to Look For | Informs Recommendations For |
-|----------|------------------|----------------------------|
-| Language/Framework | package.json, pyproject.toml, import patterns | Hooks, MCP servers |
-| Frontend stack | React, Vue, Angular, Next.js | Playwright MCP, frontend skills |
-| Backend stack | Express, FastAPI, Django | API documentation tools |
-| Database | Prisma, Supabase, raw SQL | Database MCP servers |
-| External APIs | Stripe, OpenAI, AWS SDKs | context7 MCP for docs |
-| Testing | Jest, pytest, Playwright configs | Testing hooks, subagents |
-| CI/CD | GitHub Actions, CircleCI | GitHub MCP server |
-| Issue tracking | Linear, Jira references | Issue tracker MCP |
-| Docs patterns | OpenAPI, JSDoc, docstrings | Documentation skills |
-
-### Phase 2: Generate Recommendations
-
-Based on analysis, generate recommendations across all categories:
-
-#### A. MCP Server Recommendations
-
-See [references/mcp-servers.md](references/mcp-servers.md) for detailed patterns.
-
-| Codebase Signal | Recommended MCP Server |
-|-----------------|------------------------|
-| Uses popular libraries (React, Express, etc.) | **context7** - Live documentation lookup |
-| Frontend with UI testing needs | **Playwright** - Browser automation/testing |
-| Uses Supabase | **Supabase MCP** - Direct database operations |
-| PostgreSQL/MySQL database | **Database MCP** - Query and schema tools |
-| GitHub repository | **GitHub MCP** - Issues, PRs, actions |
-| Uses Linear for issues | **Linear MCP** - Issue management |
-| AWS infrastructure | **AWS MCP** - Cloud resource management |
-| Slack workspace | **Slack MCP** - Team notifications |
-| Memory/context persistence | **Memory MCP** - Cross-session memory |
-| Sentry error tracking | **Sentry MCP** - Error investigation |
-| Docker containers | **Docker MCP** - Container management |
-
-#### B. Skills Recommendations
-
-See [references/skills-reference.md](references/skills-reference.md) for details.
-
-Create skills in `.claude/skills/<name>/SKILL.md`. Some are also available via plugins:
-
-| Codebase Signal | Skill | Plugin |
-|-----------------|-------|--------|
-| Building plugins | skill-development | plugin-dev |
-| Git commits | commit | commit-commands |
-| React/Vue/Angular | frontend-design | frontend-design |
-| Automation rules | writing-rules | hookify |
-| Feature planning | feature-dev | feature-dev |
-
-**Custom skills to create** (with templates, scripts, examples):
-
-| Codebase Signal | Skill to Create | Invocation |
-|-----------------|-----------------|------------|
-| API routes | **api-doc** (with OpenAPI template) | Both |
-| Database project | **create-migration** (with validation script) | User-only |
-| Test suite | **gen-test** (with example tests) | User-only |
-| Component library | **new-component** (with templates) | User-only |
-| PR workflow | **pr-check** (with checklist) | User-only |
-| Releases | **release-notes** (with git context) | User-only |
-| Code style | **project-conventions** | Claude-only |
-| Onboarding | **setup-dev** (with prereq script) | User-only |
-
-#### C. Hooks Recommendations
-
-See [references/hooks-patterns.md](references/hooks-patterns.md) for configurations.
-
-| Codebase Signal | Recommended Hook |
-|-----------------|------------------|
-| Prettier configured | PostToolUse: auto-format on edit |
-| ESLint/Ruff configured | PostToolUse: auto-lint on edit |
-| TypeScript project | PostToolUse: type-check on edit |
-| Tests directory exists | PostToolUse: run related tests |
-| `.env` files present | PreToolUse: block `.env` edits |
-| Lock files present | PreToolUse: block lock file edits |
-| Security-sensitive code | PreToolUse: require confirmation |
-
-#### D. Subagent Recommendations
-
-See [references/subagent-templates.md](references/subagent-templates.md) for templates.
-
-| Codebase Signal | Recommended Subagent |
-|-----------------|---------------------|
-| Large codebase (>500 files) | **code-reviewer** - Parallel code review |
-| Auth/payments code | **security-reviewer** - Security audits |
-| API project | **api-documenter** - OpenAPI generation |
-| Performance critical | **performance-analyzer** - Bottleneck detection |
-| Frontend heavy | **ui-reviewer** - Accessibility review |
-| Needs more tests | **test-writer** - Test generation |
-
-#### E. Plugin Recommendations
-
-See [references/plugins-reference.md](references/plugins-reference.md) for available plugins.
-
-| Codebase Signal | Recommended Plugin |
-|-----------------|-------------------|
-| General productivity | **anthropic-agent-skills** - Core skills bundle |
-| Document workflows | Install docx, xlsx, pdf skills |
-| Frontend development | **frontend-design** plugin |
-| Building AI tools | **mcp-builder** for MCP development |
-
-### Phase 3: Output Recommendations Report
-
-Format recommendations clearly. **Only include 1-2 recommendations per category** - the most valuable ones for this specific codebase. Skip categories that aren't relevant.
-
-```markdown
-## Claude Code Automation Recommendations
-
-I've analyzed your codebase and identified the top automations for each category. Here are my top 1-2 recommendations per type:
-
-### Codebase Profile
-- **Type**: [detected language/runtime]
-- **Framework**: [detected framework]
-- **Key Libraries**: [relevant libraries detected]
-
----
-
-### 🔌 MCP Servers
-
-#### context7
-**Why**: [specific reason based on detected libraries]
-**Install**: `claude mcp add context7`
-
----
-
-### 🎯 Skills
-
-#### [skill name]
-**Why**: [specific reason]
-**Create**: `.claude/skills/[name]/SKILL.md`
-**Invocation**: User-only / Both / Claude-only
-**Also available in**: [plugin-name] plugin (if applicable)
-```yaml
----
-name: [skill-name]
-description: [what it does]
-disable-model-invocation: true  # for user-only
----
-```
-
----
-
-### ⚡ Hooks
-
-#### [hook name]
-**Why**: [specific reason based on detected config]
-**Where**: `.claude/settings.json`
-
----
-
-### 🤖 Subagents
-
-#### [agent name]
-**Why**: [specific reason based on codebase patterns]
-**Where**: `.claude/agents/[name].md`
-
----
-
-**Want more?** Ask for additional recommendations for any specific category (e.g., "show me more MCP server options" or "what other hooks would help?").
-
-**Want help implementing any of these?** Just ask and I can help you set up any of the recommendations above.
-```
-
-## Decision Framework
-
-### When to Recommend MCP Servers
-- External service integration needed (databases, APIs)
-- Documentation lookup for libraries/SDKs
-- Browser automation or testing
-- Team tool integration (GitHub, Linear, Slack)
-- Cloud infrastructure management
-
-### When to Recommend Skills
-
-- Document generation (docx, xlsx, pptx, pdf — also in plugins)
-- Frequently repeated prompts or workflows
-- Project-specific tasks with arguments
-- Applying templates or scripts to tasks (skills can bundle supporting files)
-- Quick actions invoked with `/skill-name`
-- Workflows that should run in isolation (`context: fork`)
-
-**Invocation control:**
-- `disable-model-invocation: true` — User-only (for side effects: deploy, commit, send)
-- `user-invocable: false` — Claude-only (for background knowledge)
-- Default (omit both) — Both can invoke
-
-### When to Recommend Hooks
-- Repetitive post-edit actions (formatting, linting)
-- Protection rules (block sensitive file edits)
-- Validation checks (tests, type checks)
-
-### When to Recommend Subagents
-- Specialized expertise needed (security, performance)
-- Parallel review workflows
-- Background quality checks
-
-### When to Recommend Plugins
-- Need multiple related skills
-- Want pre-packaged automation bundles
-- Team-wide standardization
-
----
-
-## Configuration Tips
-
-### MCP Server Setup
-
-**Team sharing**: Check `.mcp.json` into repo so entire team gets same MCP servers
-
-**Debugging**: Use `--mcp-debug` flag to identify configuration issues
-
-**Prerequisites to recommend:**
-- GitHub CLI (`gh`) - enables native GitHub operations
-- Puppeteer/Playwright CLI - for browser MCP servers
-
-### Headless Mode (for CI/Automation)
-
-Recommend headless Claude for automated pipelines:
-
-```bash
-# Pre-commit hook example
-claude -p "fix lint errors in src/" --allowedTools Edit,Write
-
-# CI pipeline with structured output
-claude -p "<prompt>" --output-format stream-json | your_command
-```
-
-### Permissions for Hooks
-
-Configure allowed tools in `.claude/settings.json`:
-
-```json
-{
-  "permissions": {
-    "allow": ["Edit", "Write", "Bash(npm test:*)", "Bash(git commit:*)"]
-  }
-}
-```

package/ai-config/skills/workflow/claude-md-improver/SKILL.md

@@ -1,158 +0,0 @@
----
-name: claude-md-improver
-description: >
-  Audit and improve CLAUDE.md files in repositories.
-  Trigger: check CLAUDE.md, audit CLAUDE.md, update CLAUDE.md, improve CLAUDE.md, fix CLAUDE.md, quality report
-tools:
-  - Read
-  - Glob
-  - Grep
-  - Bash
-  - Edit
-metadata:
-  author: claude-plugins-official
-  version: "2.0"
-  tags: [claude-code, documentation, audit, quality]
-  updated: "2026-02"
----
-
-# CLAUDE.md Improver
-
-Audit, evaluate, and improve CLAUDE.md files across a codebase to ensure Claude Code has optimal project context.
-
-**This skill can write to CLAUDE.md files.** After presenting a quality report and getting user approval, it updates CLAUDE.md files with targeted improvements.
-
-## Workflow
-
-### Phase 1: Discovery
-
-Find all CLAUDE.md files in the repository:
-
-```bash
-find . -name "CLAUDE.md" -o -name ".claude.md" -o -name ".claude.local.md" 2>/dev/null | head -50
-```
-
-**File Types & Locations:**
-
-| Type | Location | Purpose |
-|------|----------|---------|
-| Project root | `./CLAUDE.md` | Primary project context (checked into git, shared with team) |
-| Local overrides | `./.claude.local.md` | Personal/local settings (gitignored, not shared) |
-| Global defaults | `~/.claude/CLAUDE.md` | User-wide defaults across all projects |
-| Package-specific | `./packages/*/CLAUDE.md` | Module-level context in monorepos |
-| Subdirectory | Any nested location | Feature/domain-specific context |
-
-**Note:** Claude auto-discovers CLAUDE.md files in parent directories, making monorepo setups work automatically.
-
-### Phase 2: Quality Assessment
-
-For each CLAUDE.md file, evaluate against quality criteria.
-
-**Quick Assessment Checklist:**
-
-| Criterion | Weight | Check |
-|-----------|--------|-------|
-| Commands/workflows documented | High | Are build/test/deploy commands present? |
-| Architecture clarity | High | Can Claude understand the codebase structure? |
-| Non-obvious patterns | Medium | Are gotchas and quirks documented? |
-| Conciseness | Medium | No verbose explanations or obvious info? |
-| Currency | High | Does it reflect current codebase state? |
-| Actionability | High | Are instructions executable, not vague? |
-
-**Quality Scores:**
-- **A (90-100)**: Comprehensive, current, actionable
-- **B (70-89)**: Good coverage, minor gaps
-- **C (50-69)**: Basic info, missing key sections
-- **D (30-49)**: Sparse or outdated
-- **F (0-29)**: Missing or severely outdated
-
-### Phase 3: Quality Report Output
-
-**ALWAYS output the quality report BEFORE making any updates.**
-
-Format:
-
-```
-## CLAUDE.md Quality Report
-
-### Summary
-- Files found: X
-- Average score: X/100
-- Files needing update: X
-
-### File-by-File Assessment
-
-#### 1. ./CLAUDE.md (Project Root)
-**Score: XX/100 (Grade: X)**
-
-| Criterion | Score | Notes |
-|-----------|-------|-------|
-| Commands/workflows | X/20 | ... |
-| Architecture clarity | X/20 | ... |
-| Non-obvious patterns | X/15 | ... |
-| Conciseness | X/15 | ... |
-| Currency | X/15 | ... |
-| Actionability | X/15 | ... |
-
-**Issues:**
-- [List specific problems]
-
-**Recommended additions:**
-- [List what should be added]
-```
-
-### Phase 4: Targeted Updates
-
-After outputting the quality report, ask user for confirmation before updating.
-
-**Update Guidelines (Critical):**
-
-1. **Propose targeted additions only** - Focus on genuinely useful info:
-   - Commands or workflows discovered during analysis
-   - Gotchas or non-obvious patterns found in code
-   - Package relationships that weren't clear
-   - Testing approaches that work
-   - Configuration quirks
-
-2. **Keep it minimal** - Avoid:
-   - Restating what's obvious from the code
-   - Generic best practices already covered
-   - One-off fixes unlikely to recur
-   - Verbose explanations when a one-liner suffices
-
-3. **Show diffs** - For each change, show:
-   - Which CLAUDE.md file to update
-   - The specific addition (as a diff or quoted block)
-   - Brief explanation of why this helps future sessions
-
-### Phase 5: Apply Updates
-
-After user approval, apply changes using the Edit tool. Preserve existing content structure.
-
-## What Makes a Great CLAUDE.md
-
-**Key principles:**
-- Concise and human-readable
-- Actionable commands that can be copy-pasted
-- Project-specific patterns, not generic advice
-- Non-obvious gotchas and warnings
-
-**Recommended sections** (use only what's relevant):
-- Commands (build, test, dev, lint)
-- Architecture (directory structure)
-- Key Files (entry points, config)
-- Code Style (project conventions)
-- Environment (required vars, setup)
-- Testing (commands, patterns)
-- Gotchas (quirks, common mistakes)
-- Workflow (when to do what)
-
-## User Tips to Share
-
-When presenting recommendations, remind users:
-
-- **`#` key shortcut**: During a Claude session, press `#` to have Claude auto-incorporate learnings into CLAUDE.md
-- **Keep it concise**: CLAUDE.md should be human-readable; dense is better than verbose
-- **Actionable commands**: All documented commands should be copy-paste ready
-- **Use `.claude.local.md`**: For personal preferences not shared with team (add to `.gitignore`)
-- **Global defaults**: Put user-wide preferences in `~/.claude/CLAUDE.md`

package/ai-config/skills/workflow/finishing-a-development-branch/SKILL.md

@@ -1,117 +0,0 @@
----
-name: finishing-a-development-branch
-description: >
-  Completa el ciclo de vida de un branch de desarrollo: tests, review, merge y limpieza.
-  Trigger: terminar branch, cerrar feature, hacer merge, finalizar desarrollo, branch ready
-tools:
-  - Bash
-  - Read
-metadata:
-  author: project-starter-framework
-  version: "1.0"
-  tags: [git, workflow, branches, merge, pr]
-  updated: "2026-02"
----
-
-# Finishing a Development Branch Skill
-
-## Flujo Completo
-
-### Fase 1: Preparación Local
-
-```bash
-# 1. Asegurate que el branch está actualizado
-git fetch origin
-git rebase origin/main
-
-# 2. Corré todos los tests
-go test ./... || npm test || pytest
-
-# 3. Verificá el linter
-golangci-lint run || npm run lint || ruff check .
-
-# 4. Revisá los cambios una última vez
-git diff origin/main...HEAD --stat
-git log origin/main..HEAD --oneline
-```
-
-### Fase 2: Limpieza del Branch
-
-```bash
-# Revisá los commits — ¿tienen sentido? ¿hay commits de WIP para squashear?
-git log origin/main..HEAD --oneline
-
-# Si hay commits de WIP, squashear (opcional):
-git rebase -i origin/main
-# En el editor: cambiar 'pick' por 'squash' o 'fixup' en commits WIP
-```
-
-### Fase 3: Push y PR
-
-```bash
-# Push del branch
-git push origin HEAD
-
-# Crear PR (con gh CLI)
-gh pr create \
-  --title "feat(scope): descripción concisa" \
-  --body "Closes #N
-
-## Cambios
-- Lista de cambios principales
-
-## Testing
-- Tests pasan localmente
-- Testeado manualmente en [ambiente]" \
-  --base main
-```
-
-### Fase 4: Post-Merge
-
-```bash
-# Después del merge aprobado:
-
-# 1. Volver a main y actualizar
-git checkout main
-git pull origin main
-
-# 2. Eliminar el branch local
-git branch -d feature/mi-branch
-
-# 3. Eliminar el branch remoto (si no lo hizo GitHub automáticamente)
-git push origin --delete feature/mi-branch
-
-# 4. Verificar en producción/staging si aplica
-```
-
-## Checklist de Branch Completion
-
-- [ ] Rebase sobre main actualizado
-- [ ] Todos los tests pasan
-- [ ] Linter sin errores
-- [ ] Commits limpios (sin WIP, sin mensajes genéricos)
-- [ ] PR creado con descripción completa
-- [ ] PR linkeado al issue/ticket
-- [ ] Reviewer asignado
-- [ ] Branch local y remoto eliminado post-merge
-
-## Manejo de Conflictos
-
-```bash
-# Durante el rebase si hay conflictos:
-git rebase origin/main
-# [resolver conflictos en cada archivo]
-git add .
-git rebase --continue
-
-# Si el rebase se complica:
-git rebase --abort  # volver al estado anterior
-# y resolverlo manualmente
-```
-
-## Related Skills
-
-- git-github
-- git-workflow
-- verification-before-completion
-- using-git-worktrees