AI Resources

Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.

Generate LaTeX documents (or convert markdown to LaTeX) with professional typography. Optionally compile to PDF.

Reflect on codebase navigation effectiveness at end of conversation. Surfaces dead ends, inefficiencies, missing context. Does not write files — pair with /kiro:steering-custom to persist.

Create or iterate on a software design via a multi-agent workflow with parallel research and review phases. Stores artifacts in memory-bank/planning/{name}/.

Compress and optimize AI instructions to be clearer, more concise, and more efficient.

Install and use react-scan tooling for component-level React render attribution: "set up react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "measure component renders programmatically", or automated render checks with Playwright (react-scan + playwright, lite headless API for CI). Covers install across Next.js/Vite/Remix/script-tag/browser-extension and the render-attribution → fix → validate loop. For trace-based triage of LCP/INP regressions, ForcedReflow, bundle bloat, or memory leaks, use investigate-web-perf instead.

Reflect on the conversation and propose improvements to durable AI-agent instruction files such as CLAUDE.md and AGENTS.md.

Create a 1-2 page cheat sheet / quick reference for a tool, language, or framework.

Create a decision-complete implementation plan that can be executed mechanically without further design decisions.

Write automated tests. Guides test selection, mocking strategy, and writing tests that verify behavior over implementation.

Debug a running web app via the web-debugger SDK: app logs, application state, runtime snapshots, React state, query cache.

Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is this combo available", "does this shortcut conflict", "recommend a keybinding", "check this combo against my setup", or any mention of choosing, binding, or changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.

Locate the on-disk Claude Code transcript file (.jsonl under ~/.claude/projects/) for the current or a specified conversation.

Create a research or review agent for the /design workflow.

Review the Claude Code changelog and summarize recent changes and their significance.

Create or update an AI-optimized reference document for a tool, library, framework, or API via thorough research.

Bootstrap web performance debugging tooling: install chrome-devtools-mcp and related MCP servers/skills.

Optimize tsconfig.json for build speed, watch mode, and tsc memory. Use for slow tsc, too many file watchers, or TypeScript performance audits.

Render a change-review-guide as an interactive, self-contained HTML page (and optionally regenerated markdown) from a YAML content file, with the file index and stats pulled from git.

Add terms, context, or instructions to Shama voice-to-text files for clipboard mode (Ctrl+Opt+Space) or shell-command mode (Ctrl+Opt+S), at project or global level.

Initialize Shama voice-to-text config for the project — create voice.json, voice-vocabulary.md, voice-context.md, and register the project in Shama's registry.toml.

Automate browser interaction with Playwright: open pages, take screenshots, verify UI, test flows, debug pages, inspect elements.

Write a concise explainer / learning document / beginner guide that teaches a topic to someone unfamiliar with it.

Initialize DESIGN-AGENTS.md config for the /design workflow, populated from project context.

Create a high-quality image generation prompt for Google's Nano Banana 2 (NB2) model on Gemini.

Write a reviewer's guide to a set of code changes: purpose, the fundamental decisions, a file-by-file review path, and the diff noise to skip.

Create a PRD / product requirements document with app summary, design principles, and detailed requirements.

Compare AI model prices across Anthropic, OpenAI, and Google. Generates pages-per-dollar / cost-per-token visualizations.

Trace-based triage of web performance issues via chrome-devtools-mcp: LCP/INP regressions, slow page loads and interactions, ForcedReflow/layout thrashing, CLS, bundle bloat, memory leaks. Captures Chrome performance traces and analyzes them with performance insights. Requires setup-perf-stack. For installing react-scan, component-level React render attribution (unnecessary re-renders, unstable props), or automated render checks with Playwright, use react-scan instead.

Save current session context to a handoff file so a future AI agent can continue with no prior context.

Use to thoroughly understand a software development objective before design & implementation: research, identify ambiguities, ask clarifying questions.

Review a codebase for adherence to code standards. Uses specialized agents with progressive disclosure to determine which standards apply.

Assess / rate the default project context (CLAUDE.md, onboarding). Scores how well it conveys the project to AI across six dimensions, with improvement recommendations.

Wire an existing JSON Schema into VS Code, Cursor, and/or Zed so it provides validation and IntelliSense for matching JSON or YAML files.