kiro-kit 0.1.3 → 0.2.1

package/dist/presets/backend/commands/plan.md

@@ -0,0 +1,24 @@
+---
+description: ⚡⚡⚡ Intelligent plan creation with prompt enhancement
+argument-hint:
+  - task
+---
+
+## Your mission
+<task>
+$ARGUMENTS
+</task>
+
+## Workflow
+- Analyze the given task and ask for more details if needed.
+- Decide to use `/plan:fast` or `/plan:hard` SlashCommands based on the complexity.
+- Execute SlashCommand: `/plan:fast <detailed-instructions-prompt>` or `/plan:hard <detailed-instructions-prompt>`
+- Activate `planning` skill.
+- Note: `detailed-instructions-prompt` is **an enhanced prompt** that describes the task in detail based on the provided task description.
+
+## Important Notes
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
+**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+**IMPORTANT:** Ensure token efficiency while maintaining high quality.
+**IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+**IMPORTANT**: **Do not** start implementing.

package/dist/presets/backend/commands/review/codebase.md

@@ -0,0 +1,50 @@
+---
+description: ⚡⚡⚡ Scan & analyze the codebase.
+argument-hint:
+  - tasks-or-prompt
+---
+
+Think harder to scan the codebase and analyze it follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules: 
+<tasks>$ARGUMENTS</tasks>
+
+---
+
+## Role Responsibilities
+- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
+- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+---
+
+## Workflow:
+
+**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
+
+### Research
+
+* Use 2 `researcher` subagents in parallel to search up to max 5 sources for the user's request, idea validation, best practices, challenges, and find the best possible solutions.
+* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
+* Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
+
+### Code Review
+
+* After finishing, use multiple `code-reviewer` subagents in parallel to review code. 
+* If there are any issues, duplicate code, or security vulnerabilities, ask main agent to improve the code and repeat the "Testing" process until all tests pass. 
+* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly, ask user to review the changes and approve them.
+* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
+
+### Plan
+* Use `planner` subagent to analyze reports from `researcher` and `scout` subagents to create an improvement plan following the progressive disclosure structure:
+  - Create a directory `plans/YYYYMMDD-HHmm-plan-name` (example: `plans/20251101-1505-authentication-and-profile-implementation`).
+  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
+  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
+
+### Final Report
+* Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
+* Ask the user if they want to commit and push to git repository, if yes, use `git-manager` subagent to commit and push to git repository.
+
+**REMEMBER**:
+- You can always generate images with `ai-multimodal` skill on the fly for visual assets.
+- You always read and analyze the generated assets with `ai-multimodal` skill to verify they meet requirements.
+- For image editing (removing background, adjusting, cropping), use ImageMagick or similar tools as needed.

package/dist/presets/backend/commands/skill/fix-logs.md

@@ -0,0 +1,22 @@
+---
+description: Fix the agent skill based on `logs.txt` file.
+argument-hint:
+  - prompt-or-path-to-skill
+---
+
+Think harder.
+Use `skill-creator` and `claude-code` skills.
+Use `docs-seeker` skills to search for documentation if needed.
+
+## Your mission
+Fix the agent skill based on the current `logs.txt` file (in the project root directory).
+
+## Requirements
+<user-prompt>$ARGUMENTS</user-prompt>
+
+## Rules of Skill Fixing:
+Base on the requirements:
+- If you're given an URL, it's documentation page, use `Explorer` subagent to explore every internal link and report back to main agent, don't skip any link.
+- If you receive a lot of URLs, use multiple `Explorer` subagents to explore them in parallel, then report back to main agent.
+- If you receive a lot of files, use multiple `Explorer` subagents to explore them in parallel, then report back to main agent.
+- If you're given a Github URL, use [`repomix`](https://repomix.com/guide/usage) command to summarize ([install it](https://repomix.com/guide/installation) if needed) and spawn multiple `Explorer` subagents to explore it in parallel, then report back to main agent.

package/dist/presets/backend/commands/use-mcp.md

@@ -0,0 +1,35 @@
+---
+description: Utilize tools of Model Context Protocol (MCP) servers
+argument-hint:
+  - task
+---
+Execute MCP operations via **Gemini CLI** to preserve context budget.
+
+## Execution Steps
+
+1. **Execute task via Gemini CLI** (using stdin pipe for MCP support):
+   ```bash
+   # IMPORTANT: Use stdin piping, NOT -p flag (deprecated, skips MCP init)
+   echo "$ARGUMENTS. Return JSON only per GEMINI.md instructions." | gemini -y -m gemini-2.5-flash
+   ```
+
+2. **Fallback to mcp-manager subagent** (if Gemini CLI unavailable):
+   - Use `mcp-manager` subagent to discover and execute tools
+   - If the subagent got issues with the scripts of `mcp-management` skill, use `mcp-builder` skill to fix them
+   - **DO NOT** create ANY new scripts
+   - The subagent can only use MCP tools if any to achieve this task
+   - If the subagent can't find any suitable tools, just report it back to the main agent to move on to the next step
+
+## Important Notes
+
+- **MUST use stdin piping** - the deprecated `-p` flag skips MCP initialization
+- Use `-y` flag to auto-approve tool execution
+- **GEMINI.md auto-loaded**: Gemini CLI automatically loads `GEMINI.md` from project root, enforcing JSON-only response format
+- **Parseable output**: Responses are structured JSON: `{"server":"name","tool":"name","success":true,"result":<data>,"error":null}`
+
+## Anti-Pattern (DO NOT USE)
+
+```bash
+# BROKEN - deprecated -p flag skips MCP server connections!
+gemini -y -m gemini-2.5-flash -p "..."
+```

package/dist/presets/backend/commands/watzup.md

@@ -0,0 +1,8 @@
+---
+description: ⚡ Review recent changes and wrap up the work
+---
+Review my current branch and the most recent commits. 
+Provide a detailed summary of all changes, including what was modified, added, or removed. 
+Analyze the overall impact and quality of the changes.
+
+**IMPORTANT**: **Do not** start implementing.

package/dist/presets/backend/hooks/discord-hook-setup.md

@@ -0,0 +1,412 @@
+# Discord Notification Hook Setup
+
+## Overview
+
+The Discord hook (`send-discord.sh`) sends rich embedded messages to a Discord channel when Kiro completes implementation tasks. Messages include session time, project info, and task summaries.
+
+## Features
+
+- Rich embedded messages with custom formatting
+- Session timestamp tracking
+- Project name and location display
+- Custom message content
+- Automatic .env file loading
+
+## Setup Instructions
+
+### 1. Create Discord Webhook
+
+1. Open your Discord server
+2. Navigate to **Server Settings** → **Integrations** → **Webhooks**
+3. Click **"New Webhook"**
+4. Configure webhook:
+   - **Name:** `Kiro Bot` (or your preference)
+   - **Channel:** Select your target notification channel
+5. Click **"Copy Webhook URL"**
+   - Format: `https://discord.com/api/webhooks/WEBHOOK_ID/WEBHOOK_TOKEN`
+
+### 2. Configure Environment Variables
+
+Environment variables are loaded with this priority (highest to lowest):
+1. **process.env** - System/shell environment variables
+2. **.kiro/.env** - Project-level Claude configuration
+3. **.kiro/hooks/.env** - Hook-specific configuration
+
+**Option A: Project Root `.env`** (recommended):
+```bash
+DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN
+```
+
+**Option B: `.kiro/.env`** (project-level override):
+```bash
+DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN
+```
+
+**Option C: `.kiro/hooks/.env`** (hook-specific):
+```bash
+DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN
+```
+
+**Example:**
+```bash
+DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/1234567890/AbCdEfGhIjKlMnOpQrStUvWxYz
+```
+
+See `.env.example` files for templates.
+
+### 3. Secure Your Configuration
+
+Add `.env` to `.gitignore` to prevent committing webhook URLs:
+
+```bash
+# .gitignore
+.env
+.env.*
+```
+
+### 4. Make Script Executable
+
+```bash
+chmod +x .kiro/hooks/send-discord.sh
+```
+
+### 5. Verify Setup
+
+Test the hook with a simple message:
+
+```bash
+./.kiro/hooks/send-discord.sh 'Test notification from Kiro'
+```
+
+**Expected output:**
+```
+Loading .env file...
+✅ Environment loaded, DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/12...
+✅ Discord notification sent
+```
+
+Check your Discord channel for the test message.
+
+## Usage
+
+### Manual Invocation
+
+Send a notification with a custom message:
+
+```bash
+./.kiro/hooks/send-discord.sh 'Task completed: Added user authentication feature'
+```
+
+**With multi-line messages:**
+```bash
+./.kiro/hooks/send-discord.sh 'Implementation Complete
+
+✅ Added user authentication
+✅ Created login/signup forms
+✅ Integrated JWT tokens
+✅ All tests passing'
+```
+
+**Important:** Escape special characters:
+```bash
+./.kiro/hooks/send-discord.sh 'Fixed bug in user'\''s profile page'
+```
+
+### Automated Usage (Kiro Workflow)
+
+Claude automatically calls this script when completing implementations. This is configured in `.kiro/workflows/development-rules.md`:
+
+```markdown
+- When you finish the implementation, send a full summary report to Discord channel
+  with `./.kiro/hooks/send-discord.sh 'Your message here'` script
+```
+
+Claude will automatically:
+1. Complete the implementation task
+2. Generate a summary report
+3. Send it to Discord using this hook
+
+### Integration Examples
+
+**From bash scripts:**
+```bash
+#!/bin/bash
+# deploy.sh
+
+if npm run build && npm run test; then
+    ./.kiro/hooks/send-discord.sh '✅ Build and tests passed - ready to deploy'
+else
+    ./.kiro/hooks/send-discord.sh '❌ Build or tests failed - deployment blocked'
+fi
+```
+
+**From npm scripts (package.json):**
+```json
+{
+  "scripts": {
+    "deploy": "npm run build && npm run test && ./.kiro/hooks/send-discord.sh '✅ Deployment successful'",
+    "notify": "./.kiro/hooks/send-discord.sh"
+  }
+}
+```
+
+## Message Format
+
+Discord messages are sent as rich embeds with the following structure:
+
+**Embed Components:**
+- **Title:** 🤖 Kiro Session Complete
+- **Description:** Your custom message content
+- **Color:** Purple (#57F287)
+- **Timestamp:** Automatic UTC timestamp
+- **Footer:** Project name and directory
+
+**Embedded Fields:**
+- ⏰ **Session Time:** Local time when notification sent
+- 📂 **Project:** Current project directory name
+
+**Example Discord Message:**
+```
+╔═══════════════════════════════╗
+║ 🤖 Kiro Session Complete
+╠═══════════════════════════════╣
+║ Implementation Complete
+║
+║ ✅ Added user authentication
+║ ✅ Created login/signup forms
+║ ✅ Integrated JWT tokens
+║ ✅ All tests passing
+╠═══════════════════════════════╣
+║ ⏰ Session Time: 14:30:45
+║ 📂 Project: claudekit-engineer
+╠═══════════════════════════════╣
+║ DevPocket API • claudekit-engineer
+║ Today at 14:30
+╚═══════════════════════════════╝
+```
+
+## Troubleshooting
+
+### "DISCORD_WEBHOOK_URL not set"
+
+**Cause:** Environment variable not loaded or `.env` file missing
+
+**Solutions:**
+1. Verify `.env` file exists in project root
+2. Check `.env` contains `DISCORD_WEBHOOK_URL=...` line
+3. Ensure no extra spaces around `=` sign
+4. Verify `.env` file has read permissions
+
+```bash
+# Check if .env exists
+ls -la .env
+
+# Verify content
+cat .env | grep DISCORD_WEBHOOK_URL
+```
+
+### "Failed to send Discord notification"
+
+**Cause:** Network error, invalid webhook, or webhook deleted
+
+**Solutions:**
+
+1. **Verify webhook URL is active:**
+   - Open Discord → Server Settings → Integrations → Webhooks
+   - Confirm webhook still exists
+   - If deleted, create new webhook and update `.env`
+
+2. **Test webhook directly:**
+   ```bash
+   curl -X POST "YOUR_WEBHOOK_URL" \
+     -H "Content-Type: application/json" \
+     -d '{"content": "Test message"}'
+   ```
+
+3. **Check network connectivity:**
+   ```bash
+   ping discord.com
+   ```
+
+4. **Verify webhook permissions:**
+   - Webhook must have permission to post in target channel
+   - Check channel permissions in Discord
+
+### Messages Not Appearing
+
+**Cause:** Channel visibility or webhook configuration issues
+
+**Solutions:**
+1. Verify you have access to the target channel
+2. Check channel is not muted or hidden
+3. Confirm webhook is assigned to correct channel
+4. Try sending to different channel
+
+### Special Characters Breaking Messages
+
+**Cause:** Unescaped quotes or shell special characters
+
+**Solutions:**
+
+**Use single quotes for outer string:**
+```bash
+./.kiro/hooks/send-discord.sh 'Message with "double quotes" works fine'
+```
+
+**Escape single quotes inside single-quoted strings:**
+```bash
+./.kiro/hooks/send-discord.sh 'User'\''s profile updated'
+```
+
+**Use double quotes and escape:**
+```bash
+./.kiro/hooks/send-discord.sh "Message with \"escaped quotes\""
+```
+
+**For complex messages, use heredoc:**
+```bash
+./.kiro/hooks/send-discord.sh "$(cat <<'EOF'
+Multi-line message
+With special characters: ' " $ `
+All work fine here
+EOF
+)"
+```
+
+### Script Permission Denied
+
+**Cause:** Script not executable
+
+**Solution:**
+```bash
+chmod +x ./.kiro/hooks/send-discord.sh
+```
+
+## Advanced Configuration
+
+### Multiple Discord Channels
+
+Send different notification types to different channels:
+
+**.env file:**
+```bash
+DISCORD_WEBHOOK_SUCCESS=https://discord.com/api/webhooks/.../success-channel
+DISCORD_WEBHOOK_ERROR=https://discord.com/api/webhooks/.../error-channel
+DISCORD_WEBHOOK_INFO=https://discord.com/api/webhooks/.../info-channel
+```
+
+**Create wrapper scripts:**
+```bash
+# send-discord-success.sh
+export DISCORD_WEBHOOK_URL="$DISCORD_WEBHOOK_SUCCESS"
+./.kiro/hooks/send-discord.sh "$1"
+
+# send-discord-error.sh
+export DISCORD_WEBHOOK_URL="$DISCORD_WEBHOOK_ERROR"
+./.kiro/hooks/send-discord.sh "$1"
+```
+
+### Custom Embed Colors
+
+Edit `send-discord.sh` to change embed color:
+
+```bash
+# Line 33: "color": 5763719
+# Change to:
+"color": 15158332  # Red
+"color": 3066993   # Green
+"color": 15844367  # Yellow
+"color": 3447003   # Blue
+```
+
+### Adding Custom Fields
+
+Edit `send-discord.sh` to add more fields:
+
+```bash
+# After line 48, add:
+{
+    "name": "🔧 Environment",
+    "value": "Production",
+    "inline": true
+},
+{
+    "name": "🌿 Branch",
+    "value": "$(git branch --show-current)",
+    "inline": true
+}
+```
+
+### Conditional Notifications
+
+Only send notifications for specific conditions:
+
+```bash
+#!/bin/bash
+# deploy.sh
+
+if npm run test; then
+    if [[ "$ENVIRONMENT" == "production" ]]; then
+        ./.kiro/hooks/send-discord.sh '✅ Production deployment successful'
+    fi
+else
+    # Always notify on failures
+    ./.kiro/hooks/send-discord.sh '❌ Tests failed - deployment aborted'
+fi
+```
+
+## Security Best Practices
+
+1. **Never commit webhook URLs:**
+   ```bash
+   # .gitignore
+   .env
+   .env.*
+   .env.local
+   ```
+
+2. **Use environment variables:** Never hardcode webhooks in scripts
+
+3. **Rotate webhooks regularly:**
+   - Delete old webhook in Discord
+   - Create new webhook
+   - Update `.env` file
+
+4. **Limit webhook permissions:**
+   - Only grant webhook access to necessary channels
+   - Use read-only channels for notifications
+
+5. **Monitor webhook usage:**
+   - Check Discord audit log regularly
+   - Look for unexpected webhook activity
+
+6. **Use separate webhooks per environment:**
+   ```bash
+   # .env.development
+   DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/.../dev-channel
+
+   # .env.production
+   DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/.../prod-channel
+   ```
+
+## Reference
+
+**Script Location:** `.kiro/hooks/send-discord.sh`
+
+**Configuration File:** `.env` (project root)
+
+**Required Environment Variable:** `DISCORD_WEBHOOK_URL`
+
+**Supported Shell:** Bash
+
+**Dependencies:**
+- `curl` (pre-installed on macOS/Linux)
+- `jq` (optional, for testing)
+
+**Discord API Documentation:** https://discord.com/developers/docs/resources/webhook
+
+**Kiro Documentation:** https://docs.claude.com/claude-code
+
+---
+
+**Last Updated:** 2025-10-22