amhuppert/steer
claude/ai-resources-plugin/skills/steer/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add amhuppert/my-ai-resources steerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 3:47 AM134.2s1 file scanned
SKILL.md
- name:
- steer
- description:
- 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.
- disable-model-invocation:
- true
- argument-hint:
- [topic-name]
- allowed-tools:
- Read, Glob, Grep
Steer Reflection
Reflect on the current conversation to evaluate codebase navigation effectiveness. Present findings so the user can decide what to persist via /kiro:steering-custom.
Arguments
Topic name: $ARGUMENTS
If no topic name provided, derive one from the conversation's primary task using kebab-case (e.g., voice-to-text, installer-scripts, mcp-server).
Step 1: Reflect on Navigation
Analyze the full conversation history. For each question below, cite specific examples from the conversation:
- Efficiency — How many tool calls were spent on navigation (file reads, searches, globs)? How many were productive vs. wasted?
- Dead ends — List specific instances of searching for something and not finding it, or reading files that turned out to be irrelevant.
- Missing context — What information, if available at the start, would have made navigation significantly easier? Consider:
- Key file paths discovered late
- Directory structures that weren't obvious
- Naming conventions that caused confusion
- Relationships between files that weren't documented
- Improvement opportunities — What concrete changes would make this type of task easier next time?
Step 2: Synthesize Actionable Guidance
Based on the reflection, draft a concise summary of navigation guidance that could become a steering document. Present it using this structure:
<constraints> - Maximum 40 lines - Include only actionable navigation guidance, not general observations - Use specific file paths and directory names - Scope to the feature/task — not the whole codebase </constraints> <template> # {Topic Title}Key Files
path/to/file- what it contains and when it's relevant
Navigation Tips
- Concise, actionable tips for finding what you need for this type of task
Common Pitfalls
- Things that look relevant but aren't
- Non-obvious file locations or naming conventions </template>
Omit any section from the template that has no meaningful content. Do not pad with generic advice.
Step 3: Present and Suggest Next Steps
Present the full reflection and synthesized guidance to the user. Then suggest:
To persist these insights as a steering document, run
/kiro:steering-customand reference the topic {topic-name}.
Do NOT write any files. The user decides what to persist and when.
Related Skills
amhuppert/hotkey-helper
tools
VerifiedTrustedCommunity
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.
2SKILL.mdUpdated Jun 2, 2026
amhuppert/knip
development
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated May 27, 2026
amhuppert/react-scan
tools
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated May 20, 2026
amhuppert/knowledge-base-ingest
documentation
VerifiedTrustedCommunity
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".
1SKILL.mdUpdated May 17, 2026