@softspark/ai-toolkit 3.5.1 → 4.0.1

package/app/skills/search/SKILL.md

@@ -1,64 +0,0 @@
----
-name: search
-description: "Searches the KB with semantic + hybrid modes. Triggers: search KB, semantic search, hybrid search, knowledge base query."
-user-invocable: true
-effort: medium
-argument-hint: "[query]"
-allowed-tools: Read, Grep, Glob
----
-
-# Knowledge Base Search
-
-$ARGUMENTS
-
-## Search Methods
-
-### Method 1: MCP Tools (requires rag-mcp MCP server)
-
-If the `rag-mcp` MCP server is configured, use these tools:
-
-| Tool | Best For | Speed |
-|------|----------|-------|
-| `smart_query` | Default (90% of queries), auto-routing | 2-4s |
-| `hybrid_search_kb` | Raw vector + text search | <1s |
-| `get_document` | Full document content | <1s |
-| `crag_search` | Vague queries (Corrective RAG) | 1-3s |
-| `multi_hop_search` | Complex multi-step reasoning | 20-30s |
-
-```python
-# Primary search
-smart_query("your search query", limit=10)
-
-# Full document retrieval
-get_document(path="kb/reference/architecture.md")
-```
-
-### Method 2: Local File Search (fallback, always available)
-
-If MCP tools are unavailable, use built-in tools:
-
-```
-# Search file contents
-Grep: pattern="your query" path="kb/"
-
-# Search file names
-Glob: pattern="kb/**/*.md"
-
-# Read specific document
-Read: "kb/reference/architecture.md"
-```
-
-## Search Tips
-
-1. **Be specific** - "nginx rate limiting" > "rate limiting"
-2. **Try MCP first**, fall back to Grep/Glob if unavailable
-3. **Use multi-hop** for "compare X with Y" questions (MCP only)
-4. **Always cite sources**: `[PATH: kb/reference/doc.md]`
-
-## Examples
-
-```
-/search rate limiting configuration
-/search how to deploy to production
-/search database migration patterns
-```

package/app/skills/teams/SKILL.md

@@ -1,63 +0,0 @@
----
-name: teams
-description: "Launches multi-agent teams for review, debugging, feature dev, security audits, migrations. Triggers: multi-agent workflow, agent teams, team review, parallel agent collaboration."
-effort: max
-user-invocable: true
-argument-hint: "<preset> [task-description]"
-allowed-tools: Bash, Read, Write, Edit, Glob, Grep, Agent, TeamCreate, TeamDelete, SendMessage, TaskCreate, TaskList, TaskUpdate, TaskGet
----
-
-# /teams: Agent Teams Presets
-
-$ARGUMENTS
-
-Launches a pre-configured Agent Teams composition for your task. Requires `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`.
-
-## Available Presets
-
-| Preset | Agents | Use Case |
-|--------|--------|----------|
-| `review` | code-reviewer, security-auditor, performance-optimizer | PR code review |
-| `debug` | debugger, backend-specialist, incident-responder | Multi-file bug investigation |
-| `feature` | orchestrator, backend-specialist, frontend-specialist, test-engineer | Full feature implementation |
-| `fullstack` | backend-specialist, frontend-specialist, database-architect, devops-implementer | Full-stack task |
-| `research` | technical-researcher, data-analyst, prompt-engineer | Deep research task |
-| `security` | security-architect, security-auditor, backend-specialist | Security audit |
-| `migration` | database-architect, backend-specialist, devops-implementer | Database migration |
-
-See [reference/presets.md](reference/presets.md) for detailed ownership, aggregation strategies, and output formats for each preset.
-
-## Usage
-
-```
-/teams review              # Launch review team on current changes
-/teams debug               # Launch debug team for current issue
-/teams feature add auth    # Launch feature team with task context
-/teams security            # Launch security audit team
-```
-
-## Workflow
-
-1. **Parse** `$ARGUMENTS`: extract `<preset>` and optional `[task-description]`
-2. **Validate** preset is one of: review, debug, feature, fullstack, research, security, migration
-3. **Check environment**: verify `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` is set; warn if missing
-4. **Display** team composition and ownership rules from [reference/presets.md](reference/presets.md)
-5. **Confirm** with user before launching
-6. **Launch agents**: spawn each agent with its assigned scope using the Agent tool:
-   ```
-   Agent({ description: "code-reviewer: PR review lead", prompt: "[task + ownership rules]" })
-   Agent({ description: "security-auditor: security findings", prompt: "[task + domain scope]" })
-   ```
-7. **Aggregate results**: apply the preset's aggregation strategy (consensus, relay, or map-reduce)
-8. **Produce output**: write the defined output document (e.g., `REVIEW.md`, `DEBUG_REPORT.md`)
-
-### Error Handling
-
-- If an agent fails or times out: log the failure, continue with remaining agents, note the gap in the output
-- If agents produce conflicting findings: the lead agent resolves conflicts; flag unresolved disagreements for user review
-
-## Environment
-
-```bash
-export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
-```

package/app/skills/teams/reference/presets.md

@@ -1,52 +0,0 @@
-# Agent Teams Preset Definitions
-
-Detailed configuration for each `/teams` preset. Each preset defines agents, ownership, aggregation strategy, and output format.
-
-## review
-
-- **Agents**: code-reviewer (lead), security-auditor, performance-optimizer
-- **Ownership**: code-reviewer owns review summary; others own their domain reports
-- **Aggregation**: consensus (flag issues found by 2+ agents as high priority)
-- **Output**: `REVIEW.md` with severity-ranked findings
-
-## debug
-
-- **Agents**: debugger (lead), backend-specialist, incident-responder
-- **Ownership**: debugger owns root-cause analysis; others own hypothesis testing
-- **Aggregation**: relay (debugger synthesizes findings from others)
-- **Output**: `DEBUG_REPORT.md` with root cause and fix
-
-## feature
-
-- **Agents**: orchestrator (lead), backend-specialist, frontend-specialist, test-engineer
-- **Ownership**: orchestrator owns plan; specialists own their files; test-engineer owns tests
-- **Aggregation**: map-reduce (orchestrator integrates all outputs)
-- **Output**: implemented feature + tests
-
-## fullstack
-
-- **Agents**: backend-specialist, frontend-specialist, database-architect, devops-implementer
-- **Ownership**: each agent owns their layer (API, UI, DB, infra)
-- **Aggregation**: relay (backend-specialist synthesizes integration)
-- **Output**: full stack implementation
-
-## research
-
-- **Agents**: technical-researcher (lead), data-analyst, prompt-engineer
-- **Ownership**: technical-researcher owns synthesis; others own domain findings
-- **Aggregation**: consensus (areas of agreement highlighted)
-- **Output**: `RESEARCH.md` with findings and recommendations
-
-## security
-
-- **Agents**: security-architect (lead), security-auditor, backend-specialist
-- **Ownership**: security-architect owns threat model; auditor owns findings; backend owns remediation
-- **Aggregation**: relay (security-architect integrates all)
-- **Output**: `SECURITY_AUDIT.md` with CVSS-scored findings
-
-## migration
-
-- **Agents**: database-architect (lead), backend-specialist, devops-implementer
-- **Ownership**: database-architect owns schema; backend owns code changes; devops owns deployment
-- **Aggregation**: relay (database-architect coordinates sequence)
-- **Output**: migration scripts + rollback plan + deployment runbook