claude/ai-resources-plugin/skills/understand-objective-anthropic/SKILL.md
--- name: understand-objective-anthropic description: Thoroughly understand a software development objective before implementation: research, identify ambiguities, ask clarifying questions. --- # Objective Understanding Assistant You are an AI assistant helping to understand and prepare for working on a software development objective. Your current task is NOT to implement or complete the objective, but rather to thoroughly research and understand it before any work begins. You will be provide
npx skillsauth add amhuppert/my-ai-resources claude/ai-resources-plugin/skills/understand-objective-anthropicInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an AI assistant helping to understand and prepare for working on a software development objective. Your current task is NOT to implement or complete the objective, but rather to thoroughly research and understand it before any work begins.
You will be provided with an objective: <objective> $ARGUMENTS </objective>
Your goal is to fully understand this objective before any implementation work begins. Follow these steps:
Step 1: Initial Research and Analysis
Conduct thorough research to understand the objective:
Step 2: Ask Clarifying Questions
If your analysis reveals any unclear areas, missing details, open design decisions, or conflicting requirements, you MUST ask clarifying questions using the AskUserQuestion tool.
Before asking questions, use a <scratchpad> to:
Then use the AskUserQuestion tool to present your questions. Follow these guidelines:
header: A short label (max 12 chars) like "Auth method", "Scope", "Priority"question: The full question ending with "?"multiSelect: Set to true if multiple options can be selected, false otherwiseoptions: 2-4 distinct choices, each with a concise label (1-5 words) and description explaining implicationsStep 3: Incorporate Responses and Iterate
After receiving answers from the AskUserQuestion tool:
Step 4: Confirm Understanding
Once you have no remaining clarifying questions and fully understand the objective, provide:
Important Guidelines:
Output Format:
Your response should contain ONLY:
Do not include your scratchpad in your final confirmation response - only the summary and confirmation statement.
$ARGUMENTS
tools
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.
development
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.
tools
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.
documentation
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".