amhuppert
- 48 skills
- 0 followers
- 1 week ago last updated
- ▌ Understand Objective · amhuppert bundleUse to thoroughly understand a software development objective before design & implementation: research, identify ambiguities, ask clarifying questions.
- ▌ Code Standards Review · amhuppert bundleReview a codebase for adherence to code standards. Uses specialized agents with progressive disclosure to determine which standards apply.
- ▌ Assess Project Context · amhuppert bundleAssess / rate the default project context (CLAUDE.md, onboarding). Scores how well it conveys the project to AI across six dimensions, with improvement recommendations.
- ▌ Configure Editor Schema · amhuppert bundleWire an existing JSON Schema into VS Code, Cursor, and/or Zed so it provides validation and IntelliSense for matching JSON or YAML files.
- ▌ Agent Offloading · amhuppert bundleCovers 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.
- ▌ Designed Friction · amhuppert bundleMake 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.
- ▌ Agent Feedback Tiers · amhuppert bundleDefine 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.
- ▌ Agent Retrospectives · amhuppert bundleRun 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.
- ▌ CLI Tools For Agents · amhuppert bundleDesign 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.
- ▌ Earned Guidance Docs · amhuppert bundleApplies 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.
- ▌ Mechanical Guardrails · amhuppert bundleConverts 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.
- ▌ Agent Structured Output · amhuppert bundleCovers 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.
- ▌ AI Readable Tool Output · amhuppert bundleCovers 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.
- ▌ Query Output Disclosure · amhuppert bundleDesign 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.
- ▌ Live System Verification · amhuppert bundleVerify 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.
- ▌ Logging For Agent Debugging · amhuppert bundleDesign 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.
- ▌ Progressive Disclosure Tooling · amhuppert bundleStructure 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.
- ▌ Changelog Review · amhuppert bundleReview the Claude Code changelog and summarize recent changes and their significance.
- ▌ Create Reference · amhuppert bundleCreate or update an AI-optimized reference document for a tool, library, framework, or API via thorough research.
- ▌ Setup Perf Stack · amhuppert bundleBootstrap web performance debugging tooling: install chrome-devtools-mcp and related MCP servers/skills.
- ▌ Optimize Tsconfig · amhuppert bundleOptimize tsconfig.json for build speed, watch mode, and tsc memory. Use for slow tsc, too many file watchers, or TypeScript performance audits.
- ▌ Review Guide HTML · amhuppert bundleRender 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.
- ▌ Shama Add Context · amhuppert bundleAdd 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.
- ▌ Shama Init Config · amhuppert bundleInitialize 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.
- ▌ Browser Automation · amhuppert bundleAutomate browser interaction with Playwright: open pages, take screenshots, verify UI, test flows, debug pages, inspect elements.
- ▌ Explainer Document · amhuppert bundleWrite a concise explainer / learning document / beginner guide that teaches a topic to someone unfamiliar with it.
- ▌ Init Design Config · amhuppert bundleInitialize DESIGN-AGENTS.md config for the /design workflow, populated from project context.
- ▌ Nano Banana Prompt · amhuppert bundleCreate a high-quality image generation prompt for Google's Nano Banana 2 (NB2) model on Gemini.
- ▌ Change Review Guide · amhuppert bundleWrite 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 Requirements · amhuppert bundleCreate a PRD / product requirements document with app summary, design principles, and detailed requirements.
- ▌ Model Price Compare · amhuppert bundleCompare AI model prices across Anthropic, OpenAI, and Google. Generates pages-per-dollar / cost-per-token visualizations.
- ▌ Investigate Web Perf · amhuppert bundleTrace-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 Context · amhuppert bundleSave current session context to a handoff file so a future AI agent can continue with no prior context.
- ▌ Knip · amhuppert bundleDetect 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.
- ▌ Latex · amhuppert bundleGenerate LaTeX documents (or convert markdown to LaTeX) with professional typography. Optionally compile to PDF.
- ▌ Steer · amhuppert bundleReflect 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.
- ▌ Design · amhuppert bundleCreate 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 · amhuppert bundleCompress and optimize AI instructions to be clearer, more concise, and more efficient.
- ▌ React Scan · amhuppert bundleInstall 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.
- ▌ Reflection · amhuppert bundleReflect on the conversation and propose improvements to durable AI-agent instruction files such as CLAUDE.md and AGENTS.md.
- ▌ Audit Agent Instructions · amhuppertAudit 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.
- ▌ Cheat Sheet · amhuppert bundleCreate a 1-2 page cheat sheet / quick reference for a tool, language, or framework.
- ▌ Create Plan · amhuppert bundleCreate a decision-complete implementation plan that can be executed mechanically without further design decisions.
- ▌ Write Tests · amhuppert bundleWrite automated tests. Guides test selection, mocking strategy, and writing tests that verify behavior over implementation.
- ▌ Web Debugger · amhuppert bundleDebug a running web app via the web-debugger SDK: app logs, application state, runtime snapshots, React state, query cache.
- ▌ Hotkey Helper · amhuppert bundleUse 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.
- ▌ Transcript Path · amhuppert bundleLocate the on-disk Claude Code transcript file (.jsonl under ~/.claude/projects/) for the current or a specified conversation.
- ▌