kiro-kit 0.1.0

package/dist/presets/_template/hooks/scout-block.js

@@ -0,0 +1,30 @@
+#!/usr/bin/env node
+// Security guard: blocks dangerous commands before execution.
+// Registered as PreToolUse hook.
+
+const BLOCKED_PATTERNS = [
+  /rm\s+(-rf|-fr)\s+[\/~]/i,
+  /rm\s+(-rf|-fr)\s+\./i,
+  /drop\s+(database|table|schema)/i,
+  /truncate\s+table/i,
+  /delete\s+from\s+\w+\s*;?\s*$/i,
+  /format\s+[a-z]:/i,
+  /mkfs\./i,
+  /dd\s+if=.*of=\/dev/i,
+  /chmod\s+-R\s+777\s+\//i,
+  />\s*\/dev\/sd[a-z]/i,
+  /:(){ :\|:& };:/,
+  /shutdown/i,
+  /reboot/i,
+  /init\s+0/i,
+];
+
+const input = process.argv.slice(2).join(' ') || '';
+const blocked = BLOCKED_PATTERNS.some((p) => p.test(input));
+
+if (blocked) {
+  process.stderr.write(`[scout-block] Blocked dangerous command: ${input}\n`);
+  process.exit(2);
+}
+
+process.exit(0);

package/dist/presets/_template/hooks/scout-block.ps1

@@ -0,0 +1,26 @@
+# Security guard: blocks dangerous commands before execution.
+# Registered as PreToolUse hook.
+
+$Input = $args -join ' '
+
+$BlockedPatterns = @(
+    'rm\s+(-rf|-fr)\s+[\/~]'
+    'drop\s+(database|table|schema)'
+    'truncate\s+table'
+    'format\s+[a-z]:'
+    'mkfs\.'
+    'dd\s+if=.*of=\/dev'
+    'chmod\s+-R\s+777\s+\/'
+    'shutdown'
+    'reboot'
+    'init\s+0'
+)
+
+foreach ($pattern in $BlockedPatterns) {
+    if ($Input -match $pattern) {
+        Write-Error "[scout-block] Blocked dangerous command: $Input"
+        exit 2
+    }
+}
+
+exit 0

package/dist/presets/_template/hooks/scout-block.sh

@@ -0,0 +1,31 @@
+#!/usr/bin/env bash
+# Security guard: blocks dangerous commands before execution.
+# Registered as PreToolUse hook.
+
+INPUT="$*"
+
+BLOCKED_PATTERNS=(
+  "rm -rf /"
+  "rm -fr /"
+  "rm -rf ~"
+  "rm -rf ."
+  "drop database"
+  "drop table"
+  "truncate table"
+  "mkfs."
+  "dd if="
+  "chmod -R 777 /"
+  "shutdown"
+  "reboot"
+  "init 0"
+  "format c:"
+)
+
+for pattern in "${BLOCKED_PATTERNS[@]}"; do
+  if echo "$INPUT" | grep -qi "$pattern"; then
+    echo "[scout-block] Blocked dangerous command: $INPUT" >&2
+    exit 2
+  fi
+done
+
+exit 0

package/dist/presets/_template/hooks/telegram-notify.js

@@ -0,0 +1,30 @@
+#!/usr/bin/env node
+// Sends a notification to Telegram via bot API.
+// Requires TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID in environment.
+
+const https = require('https');
+
+const TOKEN = process.env.TELEGRAM_BOT_TOKEN || '';
+const CHAT_ID = process.env.TELEGRAM_CHAT_ID || '';
+const message = process.argv.slice(2).join(' ') || 'Agent task completed.';
+
+if (!TOKEN || !CHAT_ID) {
+  process.stderr.write('[telegram-notify] TELEGRAM_BOT_TOKEN or TELEGRAM_CHAT_ID not set. Skipping.\n');
+  process.exit(0);
+}
+
+const payload = JSON.stringify({ chat_id: CHAT_ID, text: message });
+const options = {
+  hostname: 'api.telegram.org',
+  path: `/bot${TOKEN}/sendMessage`,
+  method: 'POST',
+  headers: { 'Content-Type': 'application/json', 'Content-Length': Buffer.byteLength(payload) },
+};
+
+const req = https.request(options, (res) => {
+  process.exit(res.statusCode >= 200 && res.statusCode < 300 ? 0 : 1);
+});
+
+req.on('error', () => process.exit(1));
+req.write(payload);
+req.end();

package/dist/presets/_template/hooks/telegram-notify.ps1

@@ -0,0 +1,22 @@
+# Sends a notification to Telegram via bot API.
+# Requires TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID in environment.
+
+$Message = if ($args.Count -gt 0) { $args -join ' ' } else { 'Agent task completed.' }
+
+$Token = $env:TELEGRAM_BOT_TOKEN
+$ChatId = $env:TELEGRAM_CHAT_ID
+
+if (-not $Token -or -not $ChatId) {
+    Write-Error "[telegram-notify] TELEGRAM_BOT_TOKEN or TELEGRAM_CHAT_ID not set. Skipping."
+    exit 0
+}
+
+$Body = @{ chat_id = $ChatId; text = $Message } | ConvertTo-Json
+$Uri = "https://api.telegram.org/bot$Token/sendMessage"
+
+try {
+    Invoke-RestMethod -Uri $Uri -Method Post -Body $Body -ContentType 'application/json'
+    exit 0
+} catch {
+    exit 1
+}

package/dist/presets/_template/hooks/telegram-notify.sh

@@ -0,0 +1,16 @@
+#!/usr/bin/env bash
+# Sends a notification to Telegram via bot API.
+# Requires TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID in environment.
+
+MESSAGE="${*:-Agent task completed.}"
+
+if [ -z "$TELEGRAM_BOT_TOKEN" ] || [ -z "$TELEGRAM_CHAT_ID" ]; then
+  echo "[telegram-notify] TELEGRAM_BOT_TOKEN or TELEGRAM_CHAT_ID not set. Skipping." >&2
+  exit 0
+fi
+
+curl -s -o /dev/null -w "%{http_code}" \
+  -H "Content-Type: application/json" \
+  -d "{\"chat_id\": \"$TELEGRAM_CHAT_ID\", \"text\": \"$MESSAGE\"}" \
+  "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/sendMessage" \
+  | grep -q "^2" && exit 0 || exit 1

package/dist/presets/_template/manifest.json

@@ -0,0 +1,17 @@
+{
+  "name": "_template",
+  "version": "1.0.0",
+  "description": "Baseline preset template - copy and customize for new presets",
+  "category": "frontend",
+  "files": [],
+  "mcpServers": {},
+  "hooks": {},
+  "tags": [],
+  "minCounts": {
+    "agents": 12,
+    "skills": 20,
+    "commands": 25,
+    "hooks": 6,
+    "workflows": 4
+  }
+}

package/dist/presets/_template/settings.json

@@ -0,0 +1,31 @@
+{
+  "statusLine": {
+    "type": "command",
+    "command": "node .kiro/statusline.js"
+  },
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": ".*",
+        "command": "node .kiro/hooks/scout-block.js"
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": ".*",
+        "command": "node .kiro/hooks/modularization-hook.js"
+      }
+    ],
+    "agentStop": [
+      {
+        "matcher": ".*",
+        "command": "node .kiro/hooks/discord-notify.js"
+      },
+      {
+        "matcher": ".*",
+        "command": "node .kiro/hooks/telegram-notify.js"
+      }
+    ]
+  },
+  "includeCoAuthoredBy": false
+}

package/dist/presets/_template/skills/.env.example

@@ -0,0 +1,12 @@
+# Skills-shared environment variables
+# Copy this file to .env and fill in your values.
+
+# API keys used by multiple skills
+# GEMINI_API_KEY=<your-gemini-api-key>
+# OPENAI_API_KEY=<your-openai-api-key>
+
+# Documentation search
+# DOCS_BASE_URL=<your-docs-base-url>
+
+# Image generation / multimodal
+# STABILITY_API_KEY=<your-stability-api-key>

package/dist/presets/_template/skills/INSTALLATION.md

@@ -0,0 +1,37 @@
+# Installing New Skills
+
+## Quick Start
+
+1. Create a new folder under `skills/` with a kebab-case name
+2. Add a `SKILL.md` file with required front-matter
+3. Optionally add `references/`, `scripts/`, `assets/` folders
+
+## SKILL.md Front-matter
+
+Required fields:
+
+```yaml
+---
+name: my-skill-name
+description: When and why this skill should be activated
+---
+```
+
+## File Organization
+
+- `SKILL.md` - Main skill definition (required)
+- `references/` - Documentation, API specs, guides the skill references
+- `scripts/` - Executable scripts (bash, node, python)
+- `assets/` - Static files (images, templates, configs)
+
+## Best Practices
+
+- Keep SKILL.md concise and focused on activation criteria
+- Use progressive disclosure: put details in reference files
+- Name the skill folder to match its `name` front-matter field
+- Test that the skill activates correctly for its intended triggers
+- Document any environment variables in `skills/.env.example`
+
+## Removing Skills
+
+Delete the skill folder. No other cleanup is needed.

package/dist/presets/_template/skills/README.md

@@ -0,0 +1,34 @@
+# Skills Directory
+
+Skills extend agent capabilities with specialized knowledge, workflows, or tool integrations.
+
+## Structure
+
+Each skill lives in its own folder with this layout:
+
+```
+skills/<skill-name>/
+  SKILL.md          - Skill definition with front-matter and instructions
+  references/       - Reference documentation files
+  scripts/          - Executable scripts the skill uses
+  assets/           - Images, templates, or other static assets
+```
+
+## Discovery
+
+Skills are discovered by the IDE via the `SKILL.md` file in each folder. The front-matter defines the skill name and when it should activate.
+
+## Sub-skill Containers
+
+A folder without a root `SKILL.md` but containing sub-folders with their own `SKILL.md` files is treated as a sub-skill container. Example:
+
+```
+skills/document-skills/
+  docx/SKILL.md
+  pdf/SKILL.md
+  xlsx/SKILL.md
+```
+
+## Adding Skills
+
+See `INSTALLATION.md` for instructions on adding new skills to this directory.

package/dist/presets/_template/skills/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,24 @@
+# Third-Party Notices
+
+This file lists third-party content included in or referenced by skills in this directory.
+
+## Attributions
+
+No third-party content is currently included in the baseline template. When adding skills that reference external documentation, APIs, or code, add attribution entries here.
+
+## Format
+
+```
+## [Package/Content Name]
+- Source: [URL]
+- License: [License type]
+- Usage: [How it is used in this skill]
+```
+
+## License Compliance
+
+When adding third-party content to skills:
+- Verify the license permits redistribution
+- Add an entry to this file
+- Include license text in the skill's `references/` folder if required
+- Do not include content under restrictive licenses without explicit permission

package/dist/presets/_template/skills/agent_skills_spec.md

@@ -0,0 +1,41 @@
+# Agent Skills Specification
+
+## Overview
+
+Skills are modular knowledge packages that extend agent capabilities. Each skill provides domain-specific instructions, reference material, and optional scripts.
+
+## Skill Structure
+
+A valid skill must contain:
+- `SKILL.md` with YAML front-matter (`name`, `description`)
+- Optional `references/` directory for documentation
+- Optional `scripts/` directory for executable tools
+- Optional `assets/` directory for static resources
+
+## Front-matter Schema
+
+```yaml
+---
+name: string        # kebab-case identifier (required)
+description: string # activation criteria description (required)
+---
+```
+
+## Activation
+
+Skills activate when the agent determines the current task matches the skill description. The description field should clearly state when the skill is relevant.
+
+## Progressive Disclosure
+
+Keep `SKILL.md` body concise. Place detailed documentation in `references/` to minimize token consumption when the skill is loaded.
+
+## Sub-skill Containers
+
+A directory without a root `SKILL.md` that contains sub-directories each with their own `SKILL.md` is a sub-skill container. Each sub-skill activates independently.
+
+## Naming Conventions
+
+- Folder name: kebab-case matching the `name` field
+- SKILL.md: uppercase filename (required for discovery)
+- Reference files: descriptive kebab-case names
+- Scripts: kebab-case with appropriate extension

package/dist/presets/_template/skills/template-skill/SKILL.md

@@ -0,0 +1,20 @@
+---
+name: template-skill
+description: Replace with description of when this skill should activate and what it provides.
+---
+
+# Template Skill
+
+Replace this content with the skill instructions.
+
+## When to Use
+
+Describe the scenarios where this skill should be activated.
+
+## Instructions
+
+Provide the specialized knowledge, workflows, or tool usage patterns here.
+
+## References
+
+Additional documentation is available in the `references/` directory.

package/dist/presets/_template/skills/template-skill/assets/.gitkeep

@@ -0,0 +1 @@
+

package/dist/presets/_template/skills/template-skill/references/.gitkeep

@@ -0,0 +1 @@
+

package/dist/presets/_template/skills/template-skill/scripts/.gitkeep

@@ -0,0 +1 @@
+

package/dist/presets/_template/specs/_templates/_template/.gitkeep

@@ -0,0 +1 @@
+

package/dist/presets/_template/statusline.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+// Statusline: outputs git branch + project name + time on one line.
+
+const { execSync } = require('child_process');
+const path = require('path');
+
+let branch = '';
+try {
+  branch = execSync('git rev-parse --abbrev-ref HEAD', { encoding: 'utf8', stdio: ['pipe', 'pipe', 'pipe'] }).trim();
+} catch (e) {
+  // Not a git repo
+}
+
+const projectName = path.basename(process.cwd());
+const time = new Date().toLocaleTimeString([], { hour: '2-digit', minute: '2-digit' });
+
+const parts = [];
+if (branch) parts.push(branch);
+parts.push(projectName);
+parts.push(time);
+
+process.stdout.write(parts.join(' | ') + '\n');

package/dist/presets/_template/statusline.ps1

@@ -0,0 +1,16 @@
+# Statusline: outputs git branch + project name + time on one line.
+# Gracefully omits git branch if not a git repository.
+
+$Branch = ''
+try {
+    $Branch = (git rev-parse --abbrev-ref HEAD 2>$null)
+} catch {}
+
+$Project = Split-Path -Leaf (Get-Location)
+$Time = Get-Date -Format 'HH:mm'
+
+if ($Branch) {
+    Write-Output "$Branch | $Project | $Time"
+} else {
+    Write-Output "$Project | $Time"
+}

package/dist/presets/_template/statusline.sh

@@ -0,0 +1,17 @@
+#!/usr/bin/env bash
+# Statusline: outputs git branch + project name + time on one line.
+# Gracefully omits git branch if not a git repository.
+
+BRANCH=""
+if git rev-parse --abbrev-ref HEAD >/dev/null 2>&1; then
+  BRANCH=$(git rev-parse --abbrev-ref HEAD)
+fi
+
+PROJECT=$(basename "$PWD")
+TIME=$(date +"%H:%M")
+
+if [ -n "$BRANCH" ]; then
+  echo "$BRANCH | $PROJECT | $TIME"
+else
+  echo "$PROJECT | $TIME"
+fi

package/dist/presets/_template/steering/.gitkeep

@@ -0,0 +1 @@
+

package/dist/presets/_template/workflows/development-rules.md

@@ -0,0 +1,33 @@
+# Development Rules
+
+Follow these principles in all implementation work: YAGNI (You Aren't Gonna Need It), KISS (Keep It Simple, Stupid), DRY (Don't Repeat Yourself).
+
+## File Naming
+
+- Use kebab-case for all file names
+- Names should describe purpose clearly without needing to read content
+- Long descriptive names are preferred over short ambiguous ones
+
+## File Size Management
+
+- Keep individual code files under 200 lines
+- Split large files into smaller, focused modules
+- Use composition over inheritance for complex components
+- Extract utility functions into separate modules
+- Create dedicated service classes for business logic
+
+## Code Quality
+
+- Write clean, readable, maintainable code
+- Follow established architectural patterns in the project
+- Handle edge cases and error scenarios with try-catch
+- Use secure coding patterns by default
+- Do not create new "enhanced" files; update existing files directly
+
+## Pre-commit Rules
+
+- Run linting before commit
+- Run tests before push
+- Keep commits focused on actual code changes
+- Never commit confidential information (dotenv, API keys, credentials)
+- Use conventional commit format

package/dist/presets/_template/workflows/documentation-management.md

@@ -0,0 +1,29 @@
+# Documentation Management
+
+## Documents to Maintain
+
+- Project Roadmap: living document tracking phases, milestones, progress
+- Project Changelog: record of all significant changes, features, fixes
+- System Architecture: component diagrams, data flow, integration points
+- Code Standards: conventions, patterns, naming rules
+
+## When to Update
+
+Update documentation automatically when:
+
+- A development phase status changes (In Progress to Complete)
+- Major features are implemented or released
+- Significant bugs are resolved or security patches applied
+- Project timeline or scope adjustments are made
+- External dependencies or breaking changes occur
+
+## Update Protocol
+
+1. Before: read current document status
+2. During: maintain version consistency and proper formatting
+3. After: verify links, dates, and cross-references are accurate
+4. Quality: ensure updates align with actual implementation progress
+
+## Changelog Format
+
+Use Keep a Changelog format with sections: Added, Changed, Deprecated, Removed, Fixed, Security. Tag entries with semantic versioning.

package/dist/presets/_template/workflows/orchestration-protocol.md

@@ -0,0 +1,25 @@
+# Orchestration Protocol
+
+## Sequential Chaining
+
+Chain tasks when they have dependencies or require outputs from previous steps:
+
+- Planning then Implementation then Testing then Review: feature development
+- Research then Design then Code then Documentation: new system components
+- Each step completes fully before the next begins
+- Pass context and outputs between steps in the chain
+
+## Parallel Execution
+
+Execute multiple tasks simultaneously when they are independent:
+
+- Code + Tests + Docs: when implementing separate non-conflicting components
+- Multiple feature branches: different work on isolated features
+- Cross-platform builds: platform-specific implementations
+
+## Coordination Rules
+
+- Ensure no file conflicts or shared resource contention in parallel work
+- Plan integration points before parallel execution begins
+- Use merge strategy to combine parallel outputs
+- Validate combined results after parallel work completes

package/dist/presets/_template/workflows/primary-workflow.md

@@ -0,0 +1,33 @@
+# Primary Workflow
+
+Follow this cycle for all implementation work: Plan, Implement, Test, Review.
+
+## 1. Planning
+
+- Analyze requirements and break into concrete tasks
+- Research relevant technical topics before implementation
+- Create implementation plan with TODO items
+
+## 2. Implementation
+
+- Write clean, readable, maintainable code
+- Follow established architectural patterns
+- Implement features according to specifications
+- Handle edge cases and error scenarios
+- After modifying code, run compile/build to check for errors
+
+## 3. Testing
+
+- Write comprehensive unit tests for new functionality
+- Ensure high code coverage on critical paths
+- Test error scenarios and edge cases
+- Validate performance requirements
+- Do not use mocks or fake data just to pass tests
+
+## 4. Review
+
+- Review code for standards compliance
+- Check for security concerns
+- Verify documentation is updated
+- Ensure backward compatibility
+- Confirm no regressions introduced

package/dist/presets/backend/.env.example

@@ -0,0 +1,24 @@
+# Project-level environment variables
+# Copy this file to .env and fill in your values.
+
+# Workspace root path (auto-detected by CLI)
+# WORKSPACE_ROOT=/path/to/project
+
+# API keys for external services
+# OPENAI_API_KEY=<your-openai-api-key>
+# ANTHROPIC_API_KEY=<your-anthropic-api-key>
+
+# Database connection
+# DATABASE_URL=postgresql://user:password@localhost:5432/dbname
+# REDIS_URL=redis://localhost:6379
+
+# Application environment
+# NODE_ENV=development
+# PORT=3000
+
+# Authentication secrets
+# JWT_SECRET=<your-jwt-secret>
+# SESSION_SECRET=<your-session-secret>
+
+# External service URLs
+# API_BASE_URL=http://localhost:3000/api

package/dist/presets/backend/.mcp.json.example

@@ -0,0 +1,34 @@
+{
+  "mcpServers": {
+    "filesystem": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-filesystem", "${WORKSPACE_ROOT}"]
+    },
+    "git": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-git", "--repository", "${WORKSPACE_ROOT}"]
+    },
+    "postgres": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-postgres"],
+      "env": {
+        "DATABASE_URL": "${DATABASE_URL}"
+      }
+    },
+    "docs-seeker": {
+      "command": "npx",
+      "args": ["-y", "@mcp/docs-seeker"],
+      "env": {
+        "DOCS_PATH": "${WORKSPACE_ROOT}/docs"
+      }
+    },
+    "fetch": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-fetch"]
+    },
+    "docker": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-docker"]
+    }
+  }
+}