my-ai-resources

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.

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.

Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/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.

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.

This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.

Investigate web perf issues: LCP/INP regressions, slow interactions, unnecessary React re-renders, bundle bloat, memory leaks, ForcedReflow. Uses chrome-devtools-mcp traces. Requires setup-perf-stack.

Delegate knowledge-base ingestion to the `knowledge-base-ingester` sub-agent so the source document, primary/current trees, and ingest workflow stay out of the main conversation's context window. Run this when the user explicitly invokes `/ai-resources:kb-ingest`; do not auto-trigger from natural-language ingestion requests (those should use the `knowledge-base-ingest` skill directly).

This skill should be used when integrating source material into a knowledge base, including when the user asks to "integrate this document into the knowledge base", "add this transcript to the memory bank", "ingest this document", "update the knowledge base", "analyze a new source document", or "sync current-state docs with this source".

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

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

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

Configure AI-optimal validation: pre-commit hooks, CommandCenter.json, and low-noise linter/test/typecheck output for AI agents.

Approve and execute a previously created implementation plan with no deviation.

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

Break frontend feature requirements into parallelizable subtasks (API, UI, integration) with dependencies and a Mermaid diagram.

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

Walk through recent code changes pedagogically: a two-phase markdown guide (overview, then detailed explanations) in dependency order.

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

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

Commit staged git changes after generating and approving a message.

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

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

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

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

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}/.

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

Resolve git merge conflicts. Use when git status shows unmerged paths or files contain conflict markers (<<<<<<< / ======= / >>>>>>>).

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

Jog the user's memory after they've been away: a brief, scannable summary of progress, next steps, and open questions.

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

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

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

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

Reflect on the conversation and propose improvements to CLAUDE.md configuration files.

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

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

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

Thoroughly understand a software development objective before implementation: research, identify ambiguities, ask clarifying questions.

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