nkllon/kiro-ai-development-hackathon
Code with Kiro Hackathon: AI-Powered IDE for Spec-Driven Development
Copy this rig
# review before running: this installs third-party code $ claude mcp add voice-mode -e OPENAI_<redacted> -- uvx voice-mode $ claude mcp add github -e GITHUB_PERSONAL_ACCESS_<redacted> -- docker run --rm -i ghcr.io/github/github-mcp-server $ claude mcp add filesystem -- uvx mcp-server-filesystem --path . $ claude mcp add git -- uvx mcp-server-git
MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.
$ claude mcp add voice-mode -e OPENAI_<redacted> -- uvx voice-mode $ claude mcp add github -e GITHUB_PERSONAL_ACCESS_<redacted> -- docker run --rm -i ghcr.io/github/github-mcp-server $ claude mcp add filesystem -- uvx mcp-server-filesystem --path . $ claude mcp add git -- uvx mcp-server-git
This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:
{
"permissions": {
"deny": [
"Read(./.env)",
"Read(./.env.*)",
"Read(**/.env)",
"Read(~/.ssh/**)",
"Bash(git push --force:*)",
"Read(**/*.pem)",
"Read(.env)",
"Read(~/.aws/**)",
"Read(**/*.key)",
"Read(**/.env.*)",
"Bash(git push --force*)",
"Bash(rm -rf:*)",
"Bash(rm -rf *)",
"Bash(sudo *)",
"Bash(sudo:*)",
"Bash(rm -rf /)",
"Bash(git push -f:*)",
"Read(.env.*)",
"Bash(git reset --hard*)",
"Bash(rm -rf /*)"
],
"ask": [
"Bash(git push:*)",
"Bash(git push *)",
"Bash(gh pr merge *)",
"Bash(git commit:*)",
"Bash(rm *)",
"Bash(gh pr merge:*)",
"Bash(gh pr create *)",
"Bash(git reset --hard:*)",
"Bash(npm publish:*)",
"Bash(git rebase *)"
]
}
} MCP servers (5)
| server | source | est. tokens |
|---|---|---|
| voice-mode env: OPENAI_API_KEY | pypi | 2.5k |
| GitHub MCP · "github" env: GITHUB_PERSONAL_ACCESS_TOKEN | docker | 18.0k |
| simone env: PROJECT_PATH | local / custom | 2.5k |
| mcp-server-filesystem · "filesystem" | pypi | 2.5k |
| Git | pypi | 3.2k |
Cursor rules (2)
Kiro (5 steering · 31 specs)
Specs: artifact-classification-transfer-learning, artifact-driven-beast-mode, beast-mode-interface-governance, beast-mode-rebuild, beast-mode-reliability-requirements, competitive-launch-strategy, devpost-hackathon-integration, directus-cms-setup, directus-cms-systematic-implementation, directus-data-population, directus-reconciliation-systematic, directus-schema-design… (loaded on demand, not counted in context tax)
MCP config: 5 auto-approved tool(s)
How Kiro files are scored: methodology.