superkit-mcp-server 1.2.7 → 1.3.0

package/agents/coder.md

@@ -1,3 +1,10 @@
+---
+name: coder
+description: Clean code implementation specialist. Use for writing new features, refactoring existing code, fixing bugs, and creating utilities. Triggers on implement, write, create, build, code, function, feature, refactor.
+tools: Read, Grep, Glob, Bash, Edit, Write
+model: inherit
+---
+
 # Coder Agent
 
 ## Role

package/agents/git-manager.md

@@ -1,3 +1,10 @@
+---
+name: git-manager
+description: Git version control specialist. Use for commits, branching, merging, rebasing, conflict resolution, and pull requests. Triggers on commit, branch, merge, rebase, git, conflict, stash, push, pull, PR, changelog.
+tools: Read, Grep, Glob, Bash
+model: inherit
+---
+
 # Git Manager Agent
 
 ## Role

package/agents/planner.md

@@ -1,3 +1,10 @@
+---
+name: planner
+description: Implementation planning specialist. Use when starting complex tasks that need breaking into subtasks, identifying dependencies, or creating step-by-step plans. Triggers on plan, design, architect, break down, strategy, roadmap, phases.
+tools: Read, Grep, Glob, Bash
+model: inherit
+---
+
 # Planner Agent
 
 ## Role

package/agents/reviewer.md

@@ -1,3 +1,10 @@
+---
+name: reviewer
+description: Code review and quality specialist. Use before merges, for security audits, performance reviews, and architecture reviews. Triggers on review, audit, check, quality, inspect, validate, before merge, code smell.
+tools: Read, Grep, Glob, Bash
+model: inherit
+---
+
 # Reviewer Agent
 
 ## Role

package/agents/scout.md

@@ -1,3 +1,10 @@
+---
+name: scout
+description: Codebase exploration specialist. Use to understand new codebases, find files related to a task, identify integration points, and trace code flow. Triggers on explore, find, search, understand, navigate, where is, what file, how does.
+tools: Read, Grep, Glob, Bash
+model: inherit
+---
+
 # Scout Agent
 
 ## Role

package/agents/tester.md

@@ -1,3 +1,10 @@
+---
+name: tester
+description: Testing and quality assurance specialist. Use for writing unit tests, integration tests, E2E tests, and covering edge cases. Triggers on test, spec, unit, integration, coverage, jest, vitest, playwright, cypress, verify.
+tools: Read, Grep, Glob, Bash, Edit, Write
+model: inherit
+---
+
 # Tester Agent
 
 ## Role

package/agents/ui-designer.md

@@ -1,3 +1,10 @@
+---
+name: ui-designer
+description: UI/UX design specialist. Use for designing new UI components, improving UX flows, creating mockups, design systems, and accessibility reviews. Triggers on design, ui, ux, mockup, wireframe, layout, component, style, accessibility, dark mode.
+tools: Read, Grep, Glob, Bash
+model: inherit
+---
+
 # UI/UX Designer Agent
 
 ## Role

package/commands/kit-setup.toml

@@ -29,7 +29,8 @@ When you finish answering, I will:
 1. Create file `docs/agents/product.md`
 2. Continue asking about Tech Stack
 3. Continue asking about Guidelines
-4. Complete setup!
+4. Ask about Claude Code agent installation (optional)
+5. Complete setup!
 
 **You can answer freely or following the format:**
 ```
@@ -38,4 +39,33 @@ Users: [who uses it]
 Goals: [goals]
 Features: [main features]
 ```
+
+---
+
+## Step 4: Claude Code Agent Installation (Optional)
+
+After completing Steps 1-3, ask the user:
+
+> "Are you using **Claude Code** as your AI assistant? If so, I can install the Super-Kit agents directly into your `.claude/agents/` folder so they appear in the `/agents` dialog — giving you one-click access to the Planner, Coder, Scout, Reviewer, Tester, and all other Super-Kit specialists."
+
+If the user says **yes**, ask:
+
+> "Where would you like to install them?
+> - **a) Global** — `~/.claude/agents/` (available in every project)
+> - **b) Project-local** — `.claude/agents/` in the current directory (this project only)"
+
+If the user chooses **global (a)**:
+- Use the `list_superkit_assets` MCP tool to get all agent names
+- For each agent, use the `load_superkit_agent` MCP tool to get its content
+- Write each agent file to `~/.claude/agents/{agent-name}.md`
+- The files already contain the required YAML frontmatter — copy them as-is
+
+If the user chooses **project-local (b)**:
+- Same process, but write to `.claude/agents/{agent-name}.md` relative to the current working directory
+- Create the `.claude/agents/` directory if it doesn't exist
+
+After writing all files, confirm:
+> "✅ Super-Kit agents installed! Open the `/agents` dialog in Claude Code to see them."
+
+If the user says **no** or skips, complete setup without this step.
 """

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "superkit-mcp-server",
-  "version": "1.2.7",
+  "version": "1.3.0",
   "type": "module",
   "description": "An MCP server for exploring and loading Super-Kit AI agent resources.",
   "main": "build/index.js",