kiro-kit 0.2.2 → 0.2.4

package/dist/presets/frontend/skills/kiro/references/skills.md

@@ -0,0 +1,55 @@
+# Skills
+
+## Overview
+
+Skills are modular capabilities that Kiro activates automatically based on context. They provide specialized knowledge and workflows.
+
+## Structure
+
+```
+.kiro/skills/{skill-name}/
+  skill.md            # Main skill file (required)
+  references/         # Supporting documents (optional)
+    guide.md
+    examples.md
+```
+
+## skill.md Format
+
+```markdown
+---
+name: my-skill
+description: >-
+  When to activate this skill. Include trigger phrases
+  and use cases.
+---
+
+# Skill Title
+
+Content, instructions, and guidance...
+
+## References
+
+- `references/guide.md` - Detailed guide
+```
+
+## Front-Matter
+
+Required fields:
+- `name`: Skill identifier (kebab-case)
+- `description`: Activation description (when should Kiro use this skill)
+
+## Activation
+
+Skills activate automatically when:
+- User's message matches the description keywords
+- Context suggests the skill is relevant
+- User explicitly references the skill
+
+## Best Practices
+
+- Keep descriptions specific about when to activate
+- Use references for detailed content (keeps main file focused)
+- One skill per domain/topic
+- Include examples in the skill content
+- Reference external docs when available

package/dist/presets/frontend/skills/kiro/references/specs-workflow.md

@@ -0,0 +1,62 @@
+# Specs Workflow
+
+## Overview
+
+Specs are a structured way of building and documenting features. A spec formalizes the design and implementation process through requirements, design, and implementation tasks.
+
+## Spec Types
+
+### Feature Spec
+- Requirements -> Design -> Tasks (requirements-first)
+- Design -> Requirements -> Tasks (design-first)
+
+### Bugfix Spec
+- Bug condition methodology
+- Exploration tests to confirm bug exists
+- Fix implementation with property-based testing
+
+## File Structure
+
+```
+.kiro/specs/{feature-name}/
+  requirements.md    # User stories and acceptance criteria
+  design.md          # Technical design document
+  tasks.md           # Implementation task list
+```
+
+## Workflow
+
+1. **Start a spec**: Tell Kiro you want to build a feature
+2. **Choose approach**: Requirements-first or Design-first
+3. **Iterate on documents**: Review and refine with Kiro
+4. **Execute tasks**: Kiro implements tasks sequentially
+5. **Validate**: Tests verify correctness
+
+## Requirements Document
+
+Contains:
+- User stories with acceptance criteria
+- Correctness properties (formal specifications)
+- Constraints and assumptions
+
+## Design Document
+
+Contains:
+- High-level architecture
+- Data models and schemas
+- API contracts
+- Component interactions
+
+## Tasks Document
+
+Contains:
+- Ordered implementation tasks
+- Sub-tasks with checkboxes
+- Dependencies between tasks
+
+## Property-Based Testing
+
+Specs encourage formal correctness properties:
+- Define what "correct" means for your feature
+- Encode properties as executable tests
+- Use property-based testing frameworks (fast-check, hypothesis)

package/dist/presets/frontend/skills/kiro/references/steering-files.md

@@ -0,0 +1,84 @@
+# Steering Files
+
+## Overview
+
+Steering files provide additional context and instructions to the AI agent. They live in `.kiro/steering/` and influence all interactions.
+
+## Inclusion Modes
+
+### Always Included (default)
+```markdown
+---
+inclusion: always
+description: Project coding standards
+---
+
+Your instructions here...
+```
+
+### Conditional (fileMatch)
+Only included when matching files are read into context:
+```markdown
+---
+inclusion: fileMatch
+fileMatchPattern: "*.test.ts"
+description: Testing conventions
+---
+
+Your testing instructions here...
+```
+
+### Manual
+Only included when user explicitly references via `#` in chat:
+```markdown
+---
+inclusion: manual
+description: Database migration guide
+---
+
+Your migration guide here...
+```
+
+## Front-Matter Schema
+
+Required fields:
+- `inclusion`: "always" | "fileMatch" | "manual"
+- `description`: Brief description of the steering file
+
+Optional fields:
+- `fileMatchPattern`: Glob pattern (required for fileMatch inclusion)
+
+## Best Practices
+
+- Keep steering files focused on one topic
+- Use "always" sparingly to avoid context bloat
+- Use "fileMatch" for language/framework-specific conventions
+- Use "manual" for reference material not needed every time
+- Include file references with `#[[file:relative/path]]` syntax
+
+## Examples
+
+### Code Standards
+```markdown
+---
+inclusion: always
+description: TypeScript coding standards
+---
+
+- Use strict mode, no `any` types
+- Prefer interfaces for props, types for unions
+- Use Zod for runtime validation
+```
+
+### API Conventions (conditional)
+```markdown
+---
+inclusion: fileMatch
+fileMatchPattern: "**/api/**/*.ts"
+description: API route conventions
+---
+
+- Use parameterized queries
+- Validate input with Zod
+- Return consistent error format
+```

package/dist/presets/frontend/skills/kiro/references/troubleshooting.md

@@ -0,0 +1,42 @@
+# Troubleshooting
+
+## Common Issues
+
+### MCP Server Not Starting
+- Verify `uvx` is installed: run `uvx --version`
+- Check mcp.json syntax (valid JSON)
+- Ensure environment variables are set
+- Check Kiro's MCP Server view for error logs
+- Try restarting from command palette
+
+### Steering Files Not Loading
+- Verify front-matter has correct `inclusion` field
+- Check file is in `.kiro/steering/` directory
+- For fileMatch, verify pattern matches target files
+- Ensure no YAML syntax errors in front-matter
+
+### Skills Not Activating
+- Check skill.md has valid front-matter (name, description)
+- Verify skill directory is in `.kiro/skills/`
+- Ensure description contains relevant trigger keywords
+- Try referencing the skill explicitly
+
+### Hooks Not Triggering
+- Verify hook JSON schema is valid
+- Check event type matches expected trigger
+- For file events, verify patterns match file paths
+- Check command exists and is executable
+
+### Performance Issues
+- Reduce number of "always" steering files
+- Keep skill references focused and concise
+- Disable unused MCP servers
+- Clear workspace cache if needed
+
+## Debug Steps
+
+1. Check Kiro output panel for errors
+2. Verify `.kiro/` directory structure
+3. Validate JSON/YAML syntax in config files
+4. Try disabling extensions one by one
+5. Restart Kiro if issues persist

package/dist/presets/frontend/skills/kiro/skill.md

@@ -0,0 +1,194 @@
+---
+name: kiro
+description: >-
+  Use when users ask about Kiro IDE features, setup, configuration,
+  troubleshooting, specs, steering files, MCP servers, hooks, skills,
+  commands, or workspace management. Activate for questions like 'How
+  do I use Kiro?', 'What are specs?', 'How to set up MCP?', 'Create a
+  steering file', 'Fix Kiro issues', or 'Configure my workspace'.
+---
+
+# Kiro IDE Expert
+
+Kiro is an AI-powered development environment that helps developers focus on what matters: designing systems, exploring solutions, and making decisions. It combines autonomous planning, execution, and validation with extensibility through specs, steering files, skills, commands, hooks, and MCP servers.
+
+## When to Use This Skill
+
+Use when users need help with:
+- Understanding Kiro features and capabilities
+- Installation, setup, and workspace configuration
+- Creating and managing specs (requirements, design, tasks)
+- Writing steering files for project conventions
+- Creating or managing skills
+- Configuring MCP servers for external tool integration
+- Setting up hooks for automation
+- Using commands for development workflows
+- Troubleshooting Kiro issues
+- Multi-workspace and team collaboration
+- Advanced features (autonomy modes, context management)
+
+**Activation examples:**
+- "How do I use Kiro?"
+- "What are specs and how do I create one?"
+- "How to set up MCP servers?"
+- "Create a new steering file for X"
+- "Fix Kiro configuration issues"
+- "How do hooks work in Kiro?"
+
+## Core Architecture
+
+**Specs**: Structured feature development workflow (requirements -> design -> tasks) that guides implementation systematically
+
+**Steering Files**: Project-level instructions in `.kiro/steering/` that provide conventions, standards, and context to the AI agent
+
+**Skills**: Modular capabilities with instructions and references that Kiro activates automatically based on context
+
+**Commands**: User-defined operations in `.kiro/commands/` that expand to prompts for common workflows
+
+**Hooks**: Automated actions triggered by IDE events (file changes, tool use, task execution, prompt submission)
+
+**MCP Servers**: Model Context Protocol integrations connecting external tools and services via `.kiro/settings/mcp.json`
+
+## Quick Reference
+
+Load these references when needed for detailed guidance:
+
+### Getting Started
+- **Installation & Setup**: `references/getting-started.md`
+  - Prerequisites, installation, workspace setup, first run
+
+### Spec-Driven Development
+- **Specs Workflow**: `references/specs-workflow.md`
+  - Requirements, design, tasks, bugfix specs, property-based testing
+
+### Steering & Configuration
+- **Steering Files**: `references/steering-files.md`
+  - Always-included, conditional (fileMatch), manual inclusion, front-matter format
+
+- **Configuration**: `references/configuration.md`
+  - Settings hierarchy, MCP config, workspace vs user settings
+
+### Skills & Commands
+- **Skills**: `references/skills.md`
+  - Creating skills, skill.md format, references directory, activation patterns
+
+- **Commands**: `references/commands.md`
+  - Command file format, front-matter, argument hints, workflow patterns
+
+### Integration & Extension
+- **MCP Integration**: `references/mcp-integration.md`
+  - mcp.json configuration, common servers, auto-approve, troubleshooting
+
+- **Hooks**: `references/hooks.md`
+  - Event types (fileEdited, preToolUse, postToolUse, promptSubmit, etc.)
+  - Actions (askAgent, runCommand), hook schema, examples
+
+### Advanced Usage
+- **Autonomy Modes**: `references/autonomy-modes.md`
+  - Autopilot vs Supervised mode, when to use each
+
+- **Troubleshooting**: `references/troubleshooting.md`
+  - Common issues, MCP problems, performance, workspace diagnostics
+
+- **Best Practices**: `references/best-practices.md`
+  - Project organization, steering conventions, skill design, team workflows
+
+## Common Workflows
+
+### Spec-Driven Feature Development
+```
+1. Create a spec: Kiro guides you through requirements -> design -> tasks
+2. Execute tasks: Kiro implements each task from the spec sequentially
+3. Validate: Property-based tests verify correctness properties
+```
+
+### Steering File Setup
+```
+# .kiro/steering/my-conventions.md
+---
+inclusion: always
+description: Project coding conventions
+---
+
+Your conventions here...
+```
+
+### Hook Configuration
+```json
+{
+  "name": "Lint on Save",
+  "version": "1.0.0",
+  "when": {
+    "type": "fileEdited",
+    "patterns": ["*.ts", "*.tsx"]
+  },
+  "then": {
+    "type": "runCommand",
+    "command": "npm run lint"
+  }
+}
+```
+
+### MCP Server Setup
+```json
+{
+  "mcpServers": {
+    "my-server": {
+      "command": "uvx",
+      "args": ["my-mcp-server@latest"],
+      "env": {},
+      "disabled": false,
+      "autoApprove": []
+    }
+  }
+}
+```
+
+### Skill Creation
+```
+.kiro/skills/my-skill/
+  skill.md          # Main skill file with front-matter
+  references/       # Supporting reference documents
+    guide.md
+```
+
+## Instructions for Kiro
+
+When responding to Kiro-related questions:
+
+1. **Identify the topic** from the user's question
+2. **Load relevant references** from the Quick Reference section above
+3. **Provide specific guidance** using information from loaded references
+4. **Include examples** when helpful
+
+**Loading references:**
+- Read reference files only when needed for the specific question
+- Multiple references can be loaded for complex queries
+
+**For setup questions:** Load `references/getting-started.md`
+
+**For spec questions:** Load `references/specs-workflow.md`
+
+**For steering questions:** Load `references/steering-files.md`
+
+**For skill creation:** Load `references/skills.md`
+
+**For command questions:** Load `references/commands.md`
+
+**For MCP questions:** Load `references/mcp-integration.md`
+
+**For hook questions:** Load `references/hooks.md`
+
+**For configuration:** Load `references/configuration.md`
+
+**For autonomy modes:** Load `references/autonomy-modes.md`
+
+**For troubleshooting:** Load `references/troubleshooting.md`
+
+**For best practices:** Load `references/best-practices.md`
+
+**Documentation links:**
+- Kiro docs: https://kiro.dev/docs/
+- GitHub: https://github.com/aws/kiro
+
+Provide accurate, actionable guidance based on the loaded references and official documentation.

package/dist/presets/fullstack/manifest.json

@@ -939,73 +939,63 @@
       "type": "other"
     },
     {
-      "source": "skills/claude-code/references/advanced-features.md",
-      "target": ".kiro/skills/claude-code/references/advanced-features.md",
-      "type": "doc"
-    },
-    {
-      "source": "skills/claude-code/references/agent-skills.md",
-      "target": ".kiro/skills/claude-code/references/agent-skills.md",
-      "type": "doc"
-    },
-    {
-      "source": "skills/claude-code/references/api-reference.md",
-      "target": ".kiro/skills/claude-code/references/api-reference.md",
-      "type": "doc"
+      "source": "skills/kiro/skill.md",
+      "target": ".kiro/skills/kiro/skill.md",
+      "type": "skill"
     },
     {
-      "source": "skills/claude-code/references/best-practices.md",
-      "target": ".kiro/skills/claude-code/references/best-practices.md",
+      "source": "skills/kiro/references/autonomy-modes.md",
+      "target": ".kiro/skills/kiro/references/autonomy-modes.md",
       "type": "doc"
     },
     {
-      "source": "skills/claude-code/references/cicd-integration.md",
-      "target": ".kiro/skills/claude-code/references/cicd-integration.md",
+      "source": "skills/kiro/references/best-practices.md",
+      "target": ".kiro/skills/kiro/references/best-practices.md",
       "type": "doc"
     },
     {
-      "source": "skills/claude-code/references/configuration.md",
-      "target": ".kiro/skills/claude-code/references/configuration.md",
+      "source": "skills/kiro/references/commands.md",
+      "target": ".kiro/skills/kiro/references/commands.md",
       "type": "doc"
     },
     {
-      "source": "skills/claude-code/references/enterprise-features.md",
-      "target": ".kiro/skills/claude-code/references/enterprise-features.md",
+      "source": "skills/kiro/references/configuration.md",
+      "target": ".kiro/skills/kiro/references/configuration.md",
       "type": "doc"
     },
     {
-      "source": "skills/claude-code/references/getting-started.md",
-      "target": ".kiro/skills/claude-code/references/getting-started.md",
+      "source": "skills/kiro/references/getting-started.md",
+      "target": ".kiro/skills/kiro/references/getting-started.md",
       "type": "doc"
     },
     {
-      "source": "skills/claude-code/references/hooks-and-plugins.md",
-      "target": ".kiro/skills/claude-code/references/hooks-and-plugins.md",
+      "source": "skills/kiro/references/hooks.md",
+      "target": ".kiro/skills/kiro/references/hooks.md",
       "type": "doc"
     },
     {
-      "source": "skills/claude-code/references/ide-integration.md",
-      "target": ".kiro/skills/claude-code/references/ide-integration.md",
+      "source": "skills/kiro/references/mcp-integration.md",
+      "target": ".kiro/skills/kiro/references/mcp-integration.md",
       "type": "doc"
     },
     {
-      "source": "skills/claude-code/references/mcp-integration.md",
-      "target": ".kiro/skills/claude-code/references/mcp-integration.md",
+      "source": "skills/kiro/references/skills.md",
+      "target": ".kiro/skills/kiro/references/skills.md",
       "type": "doc"
     },
     {
-      "source": "skills/claude-code/references/slash-commands.md",
-      "target": ".kiro/skills/claude-code/references/slash-commands.md",
+      "source": "skills/kiro/references/specs-workflow.md",
+      "target": ".kiro/skills/kiro/references/specs-workflow.md",
       "type": "doc"
     },
     {
-      "source": "skills/claude-code/references/troubleshooting.md",
-      "target": ".kiro/skills/claude-code/references/troubleshooting.md",
+      "source": "skills/kiro/references/steering-files.md",
+      "target": ".kiro/skills/kiro/references/steering-files.md",
       "type": "doc"
     },
     {
-      "source": "skills/claude-code/skill.md",
-      "target": ".kiro/skills/claude-code/skill.md",
+      "source": "skills/kiro/references/troubleshooting.md",
+      "target": ".kiro/skills/kiro/references/troubleshooting.md",
       "type": "doc"
     },
     {

package/dist/presets/fullstack/skills/kiro/references/autonomy-modes.md

@@ -0,0 +1,26 @@
+# Autonomy Modes
+
+## Overview
+
+Kiro offers two modes for how the AI agent interacts with your workspace.
+
+## Autopilot Mode
+
+- Agent modifies files autonomously within the workspace
+- Best for: routine tasks, well-defined changes, trusted workflows
+- Changes are applied immediately
+- Use when you trust the agent's judgment for the task
+
+## Supervised Mode
+
+- User has opportunity to review and revert changes after application
+- Best for: complex refactors, unfamiliar codebases, learning
+- Changes can be inspected before accepting
+- Use when you want more control over modifications
+
+## Choosing a Mode
+
+- Start with Supervised for new projects or unfamiliar tasks
+- Switch to Autopilot for repetitive, well-understood operations
+- Use Supervised for security-sensitive changes
+- Autopilot works well for spec task execution

package/dist/presets/fullstack/skills/kiro/references/best-practices.md

@@ -0,0 +1,48 @@
+# Best Practices
+
+## Project Organization
+
+- Keep `.kiro/` directory in version control
+- Use consistent naming (kebab-case for directories)
+- Document custom skills and commands in project README
+- Share steering files across team via git
+
+## Steering Conventions
+
+- One topic per steering file
+- Use "always" only for critical, universal rules
+- Use "fileMatch" for language/framework-specific guidance
+- Keep files concise (under 100 lines ideally)
+- Include examples in steering content
+
+## Skill Design
+
+- Focus each skill on one domain
+- Write clear activation descriptions
+- Use references for detailed content
+- Keep main skill.md as an overview/router
+- Test activation with various phrasings
+
+## Hook Patterns
+
+- Use file hooks for linting and formatting
+- Use postTaskExecution for test validation
+- Use preToolUse for access control
+- Keep hook commands fast (under 30 seconds)
+- Log hook failures for debugging
+
+## Team Workflows
+
+- Standardize steering files across projects
+- Share skills via presets or git submodules
+- Document MCP server requirements in README
+- Use specs for all non-trivial features
+- Review spec documents before task execution
+
+## Cost Management
+
+- Use steering to keep responses focused
+- Avoid overly broad "always" steering
+- Disable unused MCP servers
+- Use Supervised mode for exploratory work
+- Keep skill references concise

package/dist/presets/fullstack/skills/kiro/references/commands.md

@@ -0,0 +1,61 @@
+# Commands
+
+## Overview
+
+Commands are user-defined operations in `.kiro/commands/` that expand to prompts. They provide shortcuts for common workflows.
+
+## File Format
+
+```markdown
+---
+description: Brief description of what this command does
+inclusion: manual
+argument-hint: "[pattern]"
+---
+
+## Arguments
+PATTERN: $1 (default: all)
+
+## Workflow
+1. Step one
+2. Step two
+3. Step three
+```
+
+## Front-Matter
+
+Required fields:
+- `description`: What the command does
+
+Optional fields:
+- `inclusion`: "manual" (default)
+- `argument-hint`: Hint for arguments shown to user
+
+## Arguments
+
+Use `$1`, `$2`, etc. for positional arguments passed by the user.
+
+## Nested Commands
+
+Commands can be organized in subdirectories:
+```
+.kiro/commands/
+  test.md
+  fix/
+    types.md
+    test.md
+    fast.md
+  git/
+    cm.md
+    cp.md
+    pr.md
+```
+
+Access nested commands with colon notation: `/fix:types`, `/git:cm`
+
+## Best Practices
+
+- Keep commands focused on one workflow
+- Include clear step-by-step instructions
+- Use argument hints to guide users
+- Document default behavior when no arguments provided