awsdataarchitect/kiro-best-practices
Kiro Best Practices Boilerplate
ARCHETYPE
Automator
Hooks on every lifecycle event: format, lint, notify, log.
Copy this rig
# review before running: this installs third-party code $ claude mcp add context7 -e FASTMCP_LOG_LEVEL=YOUR_FASTMCP_LOG_LEVEL -- uvx context7-mcp-server@latest $ claude mcp add aws-docs -e FASTMCP_LOG_LEVEL=YOUR_FASTMCP_LOG_LEVEL -- uvx awslabs.aws-documentation-mcp-server@latest
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 context7 -e FASTMCP_LOG_LEVEL=YOUR_FASTMCP_LOG_LEVEL -- uvx context7-mcp-server@latest $ claude mcp add aws-docs -e FASTMCP_LOG_LEVEL=YOUR_FASTMCP_LOG_LEVEL -- uvx awslabs.aws-documentation-mcp-server@latest
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 (2)
| server | source | est. tokens |
|---|---|---|
| Context7 env: FASTMCP_LOG_LEVEL | pypi | 1.2k |
| AWS Documentation · "aws-docs" env: FASTMCP_LOG_LEVEL | pypi | 1.5k |
Hooks (14)
| event | matcher | runs |
|---|---|---|
| PostFileSave | **/*.openapi.yml,**/*.openapi.yaml,**/*.swagger.yml,**/*.swagger.yaml,**/*.graphql,**/schema.json | An API schema file has been modified. Please: 1. Validate the schema syntax (OpenAPI/Swagger or GraphQL) 2. Generate TypeScript types from the schema 3. Update any existing API client code to match schema changes 4. Check for breaking chang |
| PostFileSave | **/*.ts,**/*.js,**/*.tsx,**/*.jsx | A code file has been saved. Run the appropriate tests for this file and report any failures. IMPORTANT: Use minimal verbosity to prevent session timeouts - add --silent, --quiet, or similar flags. If this is a test file, run it directly wit |
| PostFileSave | src/**/*.ts,lib/**/*.ts,cdk.json,**/*Stack.ts,**/*Construct.ts | CDK code has been modified. Please: 1. Run 'cdk synth' to validate the CDK code 2. Check for any synthesis errors or warnings 3. Validate that the generated CloudFormation templates are correct 4. Run CDK diff if there's an existing deploym |
| Manual | * | Run tests with code coverage analysis following testing best practices. Please: 1. Run the test suite with coverage reporting enabled using minimal verbosity (--silent, --quiet flags) 2. Generate a coverage report showing which lines/functi |
| Manual | * | Help generate a conventional commit message following Git best practices. Please: 1. Analyze the current git diff to understand what changes were made 2. Determine the appropriate commit type (feat, fix, docs, style, refactor, test, chore) |
| Manual | * | Check for outdated dependencies and suggest updates following dependency management best practices. Please: 1. Run dependency check commands (npm outdated, pip list --outdated, etc.) 2. Identify packages that have newer versions available 3 |
| PostFileSave | .env*,**/.env*,*.env | An environment file has been modified. Please: 1. Check that no secrets or sensitive data are included (follow security best practices) 2. Validate the format of environment variables 3. Compare with .env.example to ensure all required vari |
| PostFileSave | **/*.ts,**/*.js,**/*.tsx,**/*.jsx,**/*.py,**/*.json | A code file has been saved. Please: 1. Run the appropriate linter (ESLint for JS/TS, flake8/pylint for Python) 2. Run the appropriate formatter (Prettier for JS/TS, Black for Python) 3. Fix any auto-fixable issues 4. Report any remaining is |
| PostFileSave | .kiro/settings/mcp.json,~/.kiro/settings/mcp.json | An MCP configuration file has been modified. Please: 1. Validate the JSON syntax and structure 2. Check that all required fields are present (command, args) 3. Verify server names are unique and descriptive 4. Review autoApprove settings fo |
| Manual | * | Test all configured MCP servers and their functionality following MCP best practices. Please: 1. Check which MCP servers are currently configured and enabled 2. Test basic connectivity to each server 3. List available tools from each server |
| Manual | * | Analyze the codebase for performance issues and optimization opportunities following development standards. Please: 1. Look for common performance anti-patterns (N+1 queries, inefficient loops, etc.) 2. Check for memory leaks or excessive m |
| Manual | * | Please review and fix spelling and grammar errors in README files following documentation best practices. Please: 1. Check all README.md files in the project 2. Identify spelling errors, grammar issues, and typos 3. Fix obvious errors while |
| PostFileSave | package.json,package-lock.json,yarn.lock,requirements.txt,poetry.lock,Pipfile.lock | A dependency file has been modified. Please: 1. Run security audit (npm audit, yarn audit, or pip-audit for Python) 2. Check for known vulnerabilities in dependencies 3. Suggest updates for vulnerable packages 4. Report any high-severity is |
| PostFileSave | Dockerfile*,docker-compose*.yml,docker-compose*.yaml,*.dockerfile | A Docker file has been modified. Please: 1. Validate the Dockerfile syntax 2. Check for Docker best practices (multi-stage builds, non-root user, minimal layers) 3. Scan for security issues (hardcoded secrets, vulnerable base images) 4. Sug |
Kiro (11 steering · 17 hook files)
aws-cli-best-practices · always · 338 tokcdk-best-practices · always · 505 tokdevelopment-standards · always · 530 tokdocker-best-practices · filematchgit-best-practices · always · 280 tokmcp-best-practices · always · 885 tokpython-best-practices · filematchreact-best-practices · filematchsecurity-best-practices · always · 275 toktesting-best-practices · always · 427 toktypescript-best-practices · always · 314 tok
How Kiro files are scored: methodology.
Similar rigs
awsdataarchitect/ai-ppt-generator
Transform any document into professional presentations instantly using AWS Bedrock AI. Upload PDFs, get context-aware slides with RAG-powered intelligence. Leveraging S3 Vectors for 90% cost savings
Automator 8.5k tok · · Q3
raymondfesta/agentic-coding-best-practices
A collection of best practices for improving agentic coding accuracy through instructional docs — hooks, steering, and settings — translated into native formats for Claude Code, Cursor, Windsurf, and Kiro.
Automator 6.3k tok · · Q18
edbizarro/dotfiles
:skull: dotfiles! managed by GNU stow
Pragmatist 2.9k tok · · Q15
aws-samples/sample-kiro-study-buddy
A Kiro power that turns Kiro into a personal study companion for any AWS certification exam
Minimalist 1.5k tok · · Q0