← all publishers

amhuppert

@amhuppert source repo

Report this profile Claim this profile

• 99 skills
• 0 followers
• last month last updated

1. ▌
   Transcript Path 2 · amhuppert

   Locate the on-disk Claude Code transcript file (.jsonl under ~/.claude/projects/) for the current or a specified conversation.
   6 installs
2. ▌
   Add Design Agent 2 · amhuppert bundle

   Create a research or review agent for the /design workflow.
   4 installs
3. ▌
   Changelog Review 2 · amhuppert

   Review the Claude Code changelog and summarize recent changes and their significance.
   6 installs
4. ▌
   Create Reference 2 · amhuppert

   Create or update an AI-optimized reference document for a tool, library, framework, or API via thorough research.
   6 installs
5. ▌
   Setup Perf Stack 2 · amhuppert

   Bootstrap web performance debugging tooling: install chrome-devtools-mcp and related MCP servers/skills.
   5 installs
6. ▌
   Optimize Tsconfig 2 · amhuppert bundle

   Optimize tsconfig.json for build speed, watch mode, and tsc memory. Use for slow tsc, too many file watchers, or TypeScript performance audits.
   5 installs
7. ▌
   Review Guide HTML 2 · amhuppert bundle

   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.
   5 installs
8. ▌
   Shama Add Context 2 · amhuppert

   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.
   6 installs
9. ▌
   Shama Init Config 2 · amhuppert

   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.
   6 installs
10. ▌
    Browser Automation 2 · amhuppert bundle

    Automate browser interaction with Playwright: open pages, take screenshots, verify UI, test flows, debug pages, inspect elements.
    6 installs
11. ▌
    Steer 2 · amhuppert

    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.
    5 installs
12. ▌
    Design 2 · amhuppert bundle

    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}/.
    3 installs
13. ▌
    Compress 2 · amhuppert

    Compress and optimize AI instructions to be clearer, more concise, and more efficient.
    6 installs
14. ▌
    Wait What 2 · amhuppert

    Stop. That last message did not land: re-pitch it.
    7 installs
15. ▌
    React Scan 2 · amhuppert bundle

    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.
    5 installs
16. ▌
    Reflection 2 · amhuppert

    Reflect on the conversation and propose improvements to durable AI-agent instruction files such as CLAUDE.md and AGENTS.md.
    8 installs
17. ▌
    Cheat Sheet 2 · amhuppert bundle

    Create a 1-2 page cheat sheet / quick reference for a tool, language, or framework.
    1 install
18. ▌
    Create Plan 2 · amhuppert

    Create a decision-complete implementation plan that can be executed mechanically without further design decisions.
    6 installs
19. ▌
    Write Tests 2 · amhuppert

    Write automated tests. Guides test selection, mocking strategy, and writing tests that verify behavior over implementation.
    6 installs
20. ▌
    Web Debugger 2 · amhuppert

    Debug a running web app via the web-debugger SDK: app logs, application state, runtime snapshots, React state, query cache.
    5 installs
21. ▌
    Hotkey Helper 2 · amhuppert bundle

    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.
    5 installs
22. ▌
    Compare Reports 2 · amhuppert bundle

    Compare two reports written by different AI agents from the same prompt — score both across accuracy, prompt adherence, organization, readability, and usefulness, then produce a polished self-contained HTML comparison report that declares a winner. Use whenever the user wants to compare, judge, grade, rank, or pick between two AI-generated reports, answers, research outputs, or documents ("which of these is better?", "evaluate these two responses", "A/B test these reports", "grade these two drafts"), even if they don't mention HTML, scoring, or the word "report".
    5 installs
23. ▌
    Knip 2 · amhuppert bundle

    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.
    5 installs
24. ▌
    Latex 2 · amhuppert bundle

    Generate LaTeX documents (or convert markdown to LaTeX) with professional typography. Optionally compile to PDF.
    5 installs
25. ▌
    Designed Friction 2 · amhuppert

    Make a tool's deliberate constraints legible to agents — one-line rationale at the point of refusal, mechanisms stated where a wrong inference is invited, both sides of a ledger reported, and a published taxonomy of which friction is the product versus which is a defect. Use when agents work around or lobby against a constraint you intend to keep, when a tool refuses actions without saying why, when agents avoid a permitted action they have mis-priced, when designing refusal and status output, or when deciding what an agent should report as a bug versus absorb as the design.
    7 installs
26. ▌
    Agent Feedback Tiers 2 · amhuppert

    Define a three-tier feedback vocabulary — hint, reminders, instruction — for steering agents from tool output, with strict tier contracts and an evidence-gated admission rule for reminders. Use when designing tool output that guides agents, adding hints or reminders to a CLI or tool, deciding where mid-flow guidance belongs, or reviewing whether guidance text is in the right tier.
    7 installs
27. ▌
    Agent Retrospectives 2 · amhuppert

    Run structured retrospectives on any agent setup — instructions (AGENTS.md, CLAUDE.md, system prompts), skills, slash commands, workflows, processes, and tooling — after real use, mining finished runs for durable improvements. Covers the quality → cost → speed review order, deterministic extraction before judgment, spot-checking agent self-reports, and routing every finding to a concrete owner. Use when asked for a "retrospective on how the agent did", "post-mortem on this run", "improve my CLAUDE.md from this session", "audit how the workflow performed", or after rolling out new instructions, skills, or tooling and wanting to know what to change.
    6 installs
28. ▌
    CLI Tools For Agents 2 · amhuppert

    Design a purpose-built project CLI as the primary tool surface for AI coding agents, instead of in-process tool or MCP servers. Covers text-by- default output with opt-in --json (format follows the consumer), the exit- code taxonomy, structured errors, file-based payloads with a validate verb, preflight verbs for gated transitions with findings named by the transition they block, job-shaped long operations, identity resolution, a doctor self-check, and build-parity stamps. Use when building a CLI for agents, migrating away from in-process tool servers, designing tool output and error contracts, deciding between text and JSON output for an agent- facing tool, designing a lint or check command that runs ahead of a gate, choosing severity levels for findings, or deciding how agents should invoke project actions.
    6 installs
29. ▌
    Earned Guidance Docs 2 · amhuppert

    Applies an evidence-earned discipline to agent-facing documentation — a durable rule is written down only after it has bitten, and historical rationale lives in a dated lessons log rather than in code comments. Also covers instruction architecture: a small tool-agnostic root contract plus read-on-demand reference docs treated as persistent project memory with a drift-sync lifecycle. Use when setting up AGENTS.md or CLAUDE.md, when an instruction file keeps growing, when starting a lessons file such as PERFORMANCE.md, when deciding whether a rule has earned a place in agent guidance, or when agents appear to ignore instructions because the document is full of speculative advice.
    4 installs
30. ▌
    Mechanical Guardrails 2 · amhuppert

    Converts recurring "please don't" guidance into structural enforcement agents cannot drift past — deleting the foot-gun API, making illegal states unrepresentable in types, shrink-only ratchets, coverage assertions, checked-in budgets, declare-or-fail registries, derived artifacts, and round-trip contract tests. Use when agents keep reintroducing a pattern you documented against, when asking how to make a convention stick, when planning a migration off a legacy API, when a wrapping or registration convention has silently drifted, or when code review is the only thing standing between the codebase and a defect class.
    8 installs
31. ▌
    Agent Structured Output 2 · amhuppert

    Covers how to get reliable machine-readable output from AI agents — separate the thinking turn from the formatting turn, keep schemas flat and bounded, offload substantive content to files and return a small manifest, inject orchestrator-owned fields after parsing, and validate the manifest and the referenced files at the boundary. Includes schema design do/don't lists, prompting rules, the failure model, layered extraction, and one bounded repair turn. Use when an agent's JSON response drives workflow state, when designing a response schema or JSON Schema/Zod contract for an agent, when structured output keeps failing validation, or when deciding what belongs in JSON versus in a generated file.
    6 installs
32. ▌
    AI Readable Tool Output 2 · amhuppert

    Covers configuring development tooling — linters, type checkers, test runners, formatters — so AI agents can consume their output efficiently: keep success output O(1) rather than O(n), preserve every failure detail, strip colors, bail early, and truncate huge diffs. Includes tool-by-tool flags and config for ESLint, TypeScript, Vitest, Jest, and Prettier, the `:ai` package script convention, and a backend-neutral `AI_OUTPUT=1` switch. Use when an agent burns context on passing-test noise, when setting up pre-commit hooks or agent-invoked check commands, when asked to "make the test output quieter for the agent", when deciding what a command should print on success, or when configuring a project's lint/typecheck/test scripts for agent use.
    6 installs
33. ▌
    Query Output Disclosure 2 · amhuppert

    Design progressive disclosure for the data agent-facing query commands return — bounded summary/outline defaults with stable zoom-in handles, explicit omission lines naming the exact follow-up command, and an escalation ladder from counts to scoped detail to file spillover. Includes a pattern menu (detail levels, field selection, filtering, pagination, search, ranked aggregation, sampling, delta output) and how query output doubles as an instruction surface. Use when designing list/show/search/status verbs for an agent CLI, when a query command can return large output, when an agent burns context reading query results, or when choosing default output size and drill-down flags for a read command.
    6 installs
34. ▌
    Live System Verification 2 · amhuppert

    Verify features against the live running system — real user flows, real API and model calls, and durable backend state — before calling them done. Covers scratch-datastore isolation, evidence engineering with greppable markers, round-trip persistence checks, and the change classes that only break live. Use when asked to "verify it actually works", "test end to end", "confirm this works in the real app", or before declaring a feature complete on the strength of a green test suite.
    7 installs
35. ▌
    Logging For Agent Debugging 2 · amhuppert

    Design structured logging that AI agents can actually debug from — a stable documented event vocabulary, ambient trace context, scoped routing with a global timeline, documented query gotchas, a bounded log-analysis CLI, and forensic per-run logs for long agent executions. Use when designing logging for a project agents will debug, when an agent cannot find what it needs in the logs, when building an agent-friendly log query or performance-analysis tool, or when adding observability to multi-step agent runs.
    5 installs
36. ▌
    Progressive Disclosure Tooling 2 · amhuppert

    Structure a CLI or tool surface as a progressive-disclosure graph where every subcommand's --help is a self-contained mini-skill, and derive every guidance surface from one typed registry so documentation drift becomes structurally impossible. Use when writing --help text, designing tool help systems, organizing command documentation for agents, or fighting drift between help text, parsers, and skill docs.
    5 installs
37. ▌
    Explainer Document 2 · amhuppert

    Write a concise explainer / learning document / beginner guide that teaches a topic to someone unfamiliar with it.
    6 installs
38. ▌
    Init Design Config 2 · amhuppert

    Initialize DESIGN-AGENTS.md config for the /design workflow, populated from project context.
    4 installs
39. ▌
    Nano Banana Prompt 2 · amhuppert bundle

    Create a high-quality image generation prompt for Google's Nano Banana 2 (NB2) model on Gemini.
    3 installs
40. ▌
    Change Review Guide 2 · amhuppert

    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.
    6 installs
41. ▌
    Create Requirements 2 · amhuppert

    Create a PRD / product requirements document with app summary, design principles, and detailed requirements.
    6 installs
42. ▌
    Model Price Compare 2 · amhuppert bundle

    Compare AI model prices across Anthropic, OpenAI, and Google. Generates pages-per-dollar / cost-per-token visualizations.
    10 installs
43. ▌
    Investigate Web Perf 2 · amhuppert bundle

    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.
    5 installs
44. ▌
    Save Current Context 2 · amhuppert

    Save current session context to a handoff file so a future AI agent can continue with no prior context.
    5 installs
45. ▌
    Understand Objective 2 · amhuppert

    Use to thoroughly understand a software development objective before design & implementation: research, identify ambiguities, ask clarifying questions.
    5 installs
46. ▌
    Code Standards Review 2 · amhuppert bundle

    Review a codebase for adherence to code standards. Uses specialized agents with progressive disclosure to determine which standards apply.
    3 installs
47. ▌
    Assess Project Context 2 · amhuppert

    Assess / rate the default project context (CLAUDE.md, onboarding). Scores how well it conveys the project to AI across six dimensions, with improvement recommendations.
    4 installs
48. ▌
    Configure Editor Schema 2 · amhuppert bundle

    Wire an existing JSON Schema into VS Code, Cursor, and/or Zed so it provides validation and IntelliSense for matching JSON or YAML files.
    3 installs
49. ▌
    Agent Offloading 2 · amhuppert

    Covers the agent-offloading principle for AI-assisted development — offload everything deterministic (git operations, validation commands, iteration accounting, output parsing, message routing) from the agent onto code, and reserve the agent for judgment, language understanding, and code synthesis. Includes the division-of-labor table, decision heuristics, orchestrator-owned fields, and typed side channels for agent-produced artifacts. Use when designing an agent workflow or orchestration loop, deciding whether a check belongs in a script or a prompt, tempted to ask an agent to track its own iterations or decide when to halt, or when parsing structured data out of agent response text.
    4 installs
50. ▌
    Wait What · amhuppert bundle

    Stop. That last message did not land: re-pitch it.
    4 installs
51. ▌
    Compare Reports · amhuppert bundle

    Compare two reports written by different AI agents from the same prompt — score both across accuracy, prompt adherence, organization, readability, and usefulness, then produce a polished self-contained HTML comparison report that declares a winner. Use whenever the user wants to compare, judge, grade, rank, or pick between two AI-generated reports, answers, research outputs, or documents ("which of these is better?", "evaluate these two responses", "A/B test these reports", "grade these two drafts"), even if they don't mention HTML, scoring, or the word "report".
    5 installs
52. ▌
    Understand Objective · amhuppert bundle

    Use to thoroughly understand a software development objective before design & implementation: research, identify ambiguities, ask clarifying questions.
    6 installs
53. ▌
    Code Standards Review · amhuppert bundle

    Review a codebase for adherence to code standards. Uses specialized agents with progressive disclosure to determine which standards apply.
    4 installs
54. ▌
    Assess Project Context · amhuppert bundle

    Assess / rate the default project context (CLAUDE.md, onboarding). Scores how well it conveys the project to AI across six dimensions, with improvement recommendations.
    5 installs
55. ▌
    Configure Editor Schema · amhuppert bundle

    Wire an existing JSON Schema into VS Code, Cursor, and/or Zed so it provides validation and IntelliSense for matching JSON or YAML files.
    7 installs
56. ▌
    Agent Offloading · amhuppert bundle

    Covers the agent-offloading principle for AI-assisted development — offload everything deterministic (git operations, validation commands, iteration accounting, output parsing, message routing) from the agent onto code, and reserve the agent for judgment, language understanding, and code synthesis. Includes the division-of-labor table, decision heuristics, orchestrator-owned fields, and typed side channels for agent-produced artifacts. Use when designing an agent workflow or orchestration loop, deciding whether a check belongs in a script or a prompt, tempted to ask an agent to track its own iterations or decide when to halt, or when parsing structured data out of agent response text.
    6 installs
57. ▌
    Designed Friction · amhuppert bundle

    Make a tool's deliberate constraints legible to agents — one-line rationale at the point of refusal, mechanisms stated where a wrong inference is invited, both sides of a ledger reported, and a published taxonomy of which friction is the product versus which is a defect. Use when agents work around or lobby against a constraint you intend to keep, when a tool refuses actions without saying why, when agents avoid a permitted action they have mis-priced, when designing refusal and status output, or when deciding what an agent should report as a bug versus absorb as the design.
    7 installs
58. ▌
    Agent Feedback Tiers · amhuppert bundle

    Define a three-tier feedback vocabulary — hint, reminders, instruction — for steering agents from tool output, with strict tier contracts and an evidence-gated admission rule for reminders. Use when designing tool output that guides agents, adding hints or reminders to a CLI or tool, deciding where mid-flow guidance belongs, or reviewing whether guidance text is in the right tier.
    5 installs
59. ▌
    Agent Retrospectives · amhuppert bundle

    Run structured retrospectives on any agent setup — instructions (AGENTS.md, CLAUDE.md, system prompts), skills, slash commands, workflows, processes, and tooling — after real use, mining finished runs for durable improvements. Covers the quality → cost → speed review order, deterministic extraction before judgment, spot-checking agent self-reports, and routing every finding to a concrete owner. Use when asked for a "retrospective on how the agent did", "post-mortem on this run", "improve my CLAUDE.md from this session", "audit how the workflow performed", or after rolling out new instructions, skills, or tooling and wanting to know what to change.
    6 installs
60. ▌
    CLI Tools For Agents · amhuppert bundle

    Design a purpose-built project CLI as the primary tool surface for AI coding agents, instead of in-process tool or MCP servers. Covers text-by- default output with opt-in --json (format follows the consumer), the exit- code taxonomy, structured errors, file-based payloads with a validate verb, preflight verbs for gated transitions with findings named by the transition they block, job-shaped long operations, identity resolution, a doctor self-check, and build-parity stamps. Use when building a CLI for agents, migrating away from in-process tool servers, designing tool output and error contracts, deciding between text and JSON output for an agent- facing tool, designing a lint or check command that runs ahead of a gate, choosing severity levels for findings, or deciding how agents should invoke project actions.
    7 installs
61. ▌
    Earned Guidance Docs · amhuppert bundle

    Applies an evidence-earned discipline to agent-facing documentation — a durable rule is written down only after it has bitten, and historical rationale lives in a dated lessons log rather than in code comments. Also covers instruction architecture: a small tool-agnostic root contract plus read-on-demand reference docs treated as persistent project memory with a drift-sync lifecycle. Use when setting up AGENTS.md or CLAUDE.md, when an instruction file keeps growing, when starting a lessons file such as PERFORMANCE.md, when deciding whether a rule has earned a place in agent guidance, or when agents appear to ignore instructions because the document is full of speculative advice.
    6 installs
62. ▌
    Mechanical Guardrails · amhuppert bundle

    Converts recurring "please don't" guidance into structural enforcement agents cannot drift past — deleting the foot-gun API, making illegal states unrepresentable in types, shrink-only ratchets, coverage assertions, checked-in budgets, declare-or-fail registries, derived artifacts, and round-trip contract tests. Use when agents keep reintroducing a pattern you documented against, when asking how to make a convention stick, when planning a migration off a legacy API, when a wrapping or registration convention has silently drifted, or when code review is the only thing standing between the codebase and a defect class.
    7 installs
63. ▌
    Agent Structured Output · amhuppert bundle

    Covers how to get reliable machine-readable output from AI agents — separate the thinking turn from the formatting turn, keep schemas flat and bounded, offload substantive content to files and return a small manifest, inject orchestrator-owned fields after parsing, and validate the manifest and the referenced files at the boundary. Includes schema design do/don't lists, prompting rules, the failure model, layered extraction, and one bounded repair turn. Use when an agent's JSON response drives workflow state, when designing a response schema or JSON Schema/Zod contract for an agent, when structured output keeps failing validation, or when deciding what belongs in JSON versus in a generated file.
    4 installs
64. ▌
    AI Readable Tool Output · amhuppert bundle

    Covers configuring development tooling — linters, type checkers, test runners, formatters — so AI agents can consume their output efficiently: keep success output O(1) rather than O(n), preserve every failure detail, strip colors, bail early, and truncate huge diffs. Includes tool-by-tool flags and config for ESLint, TypeScript, Vitest, Jest, and Prettier, the `:ai` package script convention, and a backend-neutral `AI_OUTPUT=1` switch. Use when an agent burns context on passing-test noise, when setting up pre-commit hooks or agent-invoked check commands, when asked to "make the test output quieter for the agent", when deciding what a command should print on success, or when configuring a project's lint/typecheck/test scripts for agent use.
    4 installs
65. ▌
    Query Output Disclosure · amhuppert bundle

    Design progressive disclosure for the data agent-facing query commands return — bounded summary/outline defaults with stable zoom-in handles, explicit omission lines naming the exact follow-up command, and an escalation ladder from counts to scoped detail to file spillover. Includes a pattern menu (detail levels, field selection, filtering, pagination, search, ranked aggregation, sampling, delta output) and how query output doubles as an instruction surface. Use when designing list/show/search/status verbs for an agent CLI, when a query command can return large output, when an agent burns context reading query results, or when choosing default output size and drill-down flags for a read command.
    5 installs
66. ▌
    Live System Verification · amhuppert bundle

    Verify features against the live running system — real user flows, real API and model calls, and durable backend state — before calling them done. Covers scratch-datastore isolation, evidence engineering with greppable markers, round-trip persistence checks, and the change classes that only break live. Use when asked to "verify it actually works", "test end to end", "confirm this works in the real app", or before declaring a feature complete on the strength of a green test suite.
    6 installs
67. ▌
    Logging For Agent Debugging · amhuppert bundle

    Design structured logging that AI agents can actually debug from — a stable documented event vocabulary, ambient trace context, scoped routing with a global timeline, documented query gotchas, a bounded log-analysis CLI, and forensic per-run logs for long agent executions. Use when designing logging for a project agents will debug, when an agent cannot find what it needs in the logs, when building an agent-friendly log query or performance-analysis tool, or when adding observability to multi-step agent runs.
    6 installs
68. ▌
    Progressive Disclosure Tooling · amhuppert bundle

    Structure a CLI or tool surface as a progressive-disclosure graph where every subcommand's --help is a self-contained mini-skill, and derive every guidance surface from one typed registry so documentation drift becomes structurally impossible. Use when writing --help text, designing tool help systems, organizing command documentation for agents, or fighting drift between help text, parsers, and skill docs.
    6 installs
69. ▌
    Changelog Review · amhuppert bundle

    Review the Claude Code changelog and summarize recent changes and their significance.
    8 installs
70. ▌
    Create Reference · amhuppert bundle

    Create or update an AI-optimized reference document for a tool, library, framework, or API via thorough research.
    8 installs
71. ▌
    Setup Perf Stack · amhuppert bundle

    Bootstrap web performance debugging tooling: install chrome-devtools-mcp and related MCP servers/skills.
    6 installs
72. ▌
    Optimize Tsconfig · amhuppert bundle

    Optimize tsconfig.json for build speed, watch mode, and tsc memory. Use for slow tsc, too many file watchers, or TypeScript performance audits.
    7 installs
73. ▌
    Review Guide HTML · amhuppert bundle

    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.
    6 installs
74. ▌
    Shama Add Context · amhuppert bundle

    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.
    6 installs
75. ▌
    Shama Init Config · amhuppert bundle

    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.
    7 installs
76. ▌
    Browser Automation · amhuppert bundle

    Automate browser interaction with Playwright: open pages, take screenshots, verify UI, test flows, debug pages, inspect elements.
    6 installs
77. ▌
    Explainer Document · amhuppert bundle

    Write a concise explainer / learning document / beginner guide that teaches a topic to someone unfamiliar with it.
    6 installs
78. ▌
    Init Design Config · amhuppert bundle

    Initialize DESIGN-AGENTS.md config for the /design workflow, populated from project context.
    4 installs
79. ▌
    Nano Banana Prompt · amhuppert bundle

    Create a high-quality image generation prompt for Google's Nano Banana 2 (NB2) model on Gemini.
    6 installs
80. ▌
    Change Review Guide · amhuppert bundle

    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.
    8 installs
81. ▌
    Create Requirements · amhuppert bundle

    Create a PRD / product requirements document with app summary, design principles, and detailed requirements.
    5 installs
82. ▌
    Model Price Compare · amhuppert bundle

    Compare AI model prices across Anthropic, OpenAI, and Google. Generates pages-per-dollar / cost-per-token visualizations.
    7 installs
83. ▌
    Investigate Web Perf · amhuppert bundle

    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.
    6 installs
84. ▌
    Save Current Context · amhuppert bundle

    Save current session context to a handoff file so a future AI agent can continue with no prior context.
    4 installs
85. ▌
    Knip · amhuppert bundle

    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.
    8 installs
86. ▌
    Latex · amhuppert bundle

    Generate LaTeX documents (or convert markdown to LaTeX) with professional typography. Optionally compile to PDF.
    7 installs
87. ▌
    Steer · amhuppert bundle

    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.
    6 installs
88. ▌
    Design · amhuppert bundle

    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}/.
    8 installs
89. ▌
    Compress · amhuppert bundle

    Compress and optimize AI instructions to be clearer, more concise, and more efficient.
    4 installs
90. ▌
    React Scan · amhuppert bundle

    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.
    7 installs
91. ▌
    Reflection · amhuppert bundle

    Reflect on the conversation and propose improvements to durable AI-agent instruction files such as CLAUDE.md and AGENTS.md.
    8 installs
92. ▌
    Audit Agent Instructions · amhuppert

    Audit agent instruction and context files (CLAUDE.md, AGENTS.md, steering files, skills) against current context-engineering best practices. Use when asked to audit, review, or modernize agent instructions.
    5 installs
93. ▌
    Cheat Sheet · amhuppert bundle

    Create a 1-2 page cheat sheet / quick reference for a tool, language, or framework.
    4 installs
94. ▌
    Create Plan · amhuppert bundle

    Create a decision-complete implementation plan that can be executed mechanically without further design decisions.
    6 installs
95. ▌
    Write Tests · amhuppert bundle

    Write automated tests. Guides test selection, mocking strategy, and writing tests that verify behavior over implementation.
    4 installs
96. ▌
    Web Debugger · amhuppert bundle

    Debug a running web app via the web-debugger SDK: app logs, application state, runtime snapshots, React state, query cache.
    6 installs
97. ▌
    Hotkey Helper · amhuppert bundle

    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.
    2 installs
98. ▌
    Transcript Path · amhuppert bundle

    Locate the on-disk Claude Code transcript file (.jsonl under ~/.claude/projects/) for the current or a specified conversation.
    5 installs
99. ▌
    Add Design Agent · amhuppert bundle

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