After making code changes, run the project's build and tests to verify correctness before presenting the result. Self-correct if failures are found. Use automatically after any code modification.
CI/CD and infrastructure conventions. Use when working on GitHub Actions workflows, AWS infrastructure, deployment configs, Jenkinsfiles, or observability (New Relic, Coralogix).
Shared vocabulary for designing deep modules. Use when designing or improving a module's interface, finding deepening opportunities, deciding where a seam goes, or making code more testable.
Disciplined diagnosis loop for hard bugs and performance regressions. Use when a bug is reported, a test is failing unexpectedly, or behaviour doesn't match expectations.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Pre-validate toolchain and environment before heavy operations (builds, deploys, installs). Use automatically before running npm install, deploy commands, or AWS operations.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Compact the current conversation into a handoff document so another agent or session can continue the work. Use when switching directories, passing to a separate Kiro CLI agent, or ending a session that will be resumed later.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. Run periodically (fortnightly) per repo.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Push the current branch to QA for a staging build. Use when the user says "QA build", "push to QA", "deploy to staging", "test in staging", or "create a QA build".
Investigate a question against high-trust primary sources and capture the findings as a Markdown file. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated.
★not rated 1 yesterdayA42 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: