NodeJSmith
82 verified skills82 total stars
mine.define
Use when the user says: "spec this out", "help me define what I want to build", "interview me about this idea", "design this change", "write a design doc", or needs to define WHAT and HOW to build something. Proportional discovery interview + codebase investigation → design.md.
development1
mine.commit-push
Use when the user says: "commit and push". Commits and pushes changes to the current branch.
tools1
mine.clean-code
Use when the user says: "clean code check", "style review", "LLM smell check", "code hygiene", "nitpick this", "style check", "find style sins", "nitpicker review", "anal retentive review", "exhaustive style review", "no-filter style report". Dispatches three parallel stylistic checkers — llm-checker (training-bias patterns), lazy-checker (deferred debt), and nitpicker (style hygiene) — and consolidates findings into a report organized by checker with a Summary section for orchestration consumption.
development1
mine.review
Use when the user says: "review my changes", "run the reviewers", "code and integration review", "readability review", "maintainability review", "sniff test this", "WTF check", "code smells", "is this code any good", "fresh eyes on this branch", "review this directory", "check this module". Dispatches three parallel reviewers — code, integration, and a readability pass — and consolidates findings into one prioritized report.
development1
mine.ship
Use when the user says: "ship it" or "commit push and PR". Commits, pushes, and creates a PR in one step.
tools1
mine.issues-triage
Use when the user says: 'triage issues', 'classify issues by complexity', 'assess issue complexity', 'find quick wins', 'which issues are small', 'batch issue assessment'. Batch codebase-aware issue triage — parallel Haiku subagents assess actual complexity and effort by reading the code, not just titles.
development1
mine.plan
Use when the user says: "draft a plan", "create work packages", "generate WPs", "review this plan", or "check the plan". Turns a design doc into task files and validates them against a traceability-focused checklist.
testing1
mine.gap-close
Use when the user says: 'close gaps in this design', 'fill gaps in the spec', 'lightweight design review', 'gap-close this doc', 'completeness review', or wants to verify a doc has all required content before implementation.
testing1
i-teach-impeccable
Use when the user says: "setup impeccable", "design context setup", "teach impeccable", "design this UI", "look and feel", "establish design tokens", "plan the look and feel", "UI planning", "design system for this project", "craft the interface". Gathers design context and concrete tokens, saves to design/context.md.
content-media1
cm-get-token-insights
Use when the user asks about Claude token usage, wants to see how much they are spending on Claude, understand cache hit rates, review Claude Code workflow patterns, or get cost optimization recommendations.
development1
i-shape
Use when the user says: "shape this feature", "plan the UX", "design brief", "UX planning". Plan UX/UI for a feature before writing code via structured discovery interview.
development1
mine.create-pr
Use when the user says: "create PR" or "open pull request". Reviews branch changes and creates a PR on GitHub or Azure DevOps.
development1
cli-audit
Use when the user says: "audit this CLI", "CLI quality check", "full CLI review", "CLI UX audit". Comprehensive CLI tool quality audit across all dimensions — hardening, output, clarity, affordances, and complexity.
tools1
cli-harden
Use when the user says: "harden this CLI", "CLI edge cases", "make this CLI resilient", "handle CLI errors", "CLI robustness". Review CLI tools for edge-case resilience and production readiness.
tools1
cli-affordances
Use when the user says: "improve CLI discoverability", "CLI help UX", "CLI flag design", "CLI affordances", "CLI command structure". Review CLI tool discoverability — flag design, subcommand structure, help quality, and progressive disclosure.
tools1
cli-output
Use when the user says: "fix CLI output", "CLI output formatting", "improve CLI output", "CLI readability", "CLI table formatting". Review and improve how CLI tools present information.
tools1
cli-distill
Use when the user says: "simplify this CLI", "too many flags", "CLI too complex", "reduce CLI complexity", "streamline CLI". Simplify CLI tools — reduce flags, improve defaults, lower cognitive load per invocation.
tools1
mine.challenge
Use when the user says: "challenge this", "poke holes in this", or "what's wrong with this approach". Adversarial review with triage-driven critic selection, parallel critics (1–3 on first run; max 2 on re-challenges). Assumes the target is wrong, finds out why, and argues for a better approach.
tools1
cli-clarify
Use when the user says: "fix CLI messages", "improve CLI help text", "CLI error messages", "CLI UX writing", "confusing CLI output". Improve the clarity of CLI tool communication — errors, help text, prompts, and status messages.
tools1
mine.audit
Use when the user says: "audit the codebase", "find tech debt", or "health check". Systematic codebase health audit — surfaces aging code, brittle designs, missing tests, and accumulated debt, ranked by impact.
development1
mine.orchestrate
Use when the user says: "execute the plan", "orchestrate implementation", or "start executing". Runs tasks task-by-task with implementer + reviewer subagent loop.
data-ai1
mine.wp
Use when the user says: "move WP to doing", "WP status", or "kanban". Deprecated — lane management removed; redirects to /mine.status.
tools1
cm-recall-conversations
Use when the user asks to recall, search, or continue past conversations. Triggers on "what did we discuss", "continue where we left off", "remember when", "as I mentioned", "you suggested", "we decided", "search my conversations", "find the conversation where", "what did we work on". Also triggers on implicit signals like past-tense references ("the bug we fixed"), possessives without context ("my project"), or assumptive questions ("do you remember").
testing1
i-layout
Use when the user says: "fix the layout", "arrange this", "visual hierarchy", "spacing issues", "crowded UI". Improve layout, spacing, and visual rhythm.
testing1
i-clarify
Use when the user says: "improve the copy", "error messages are confusing", "UX writing". Improve UX clarity, reduce confusion, and improve information hierarchy.
development1
i-adapt
Use when the user says: "responsive design", "make it mobile-friendly", "adapt for mobile". Make interfaces work across screen sizes with responsive design.
content-media1
mine.brainstorm
Use when the user says: "brainstorm options", "generate ideas", "explore ideas", "what are our options", or wants divergent thinking before committing to an approach. Four parallel thinkers generate ideas, rank by user-chosen criteria.
data-ai1
i-polish
Use when the user says: "polish this UI", "final pass", "pixel-perfect", "normalize the design", "make it consistent", "align with design system". Final quality pass for alignment, spacing, consistency, and design system alignment.
testing1
i-teach-impeccable
Use when the user says: "setup impeccable", "design context setup", "teach impeccable", "design this UI", "look and feel", "establish design tokens", "plan the look and feel", "UI planning", "design system for this project", "craft the interface". Gathers design context and concrete tokens, saves to design/context.md.
content-media1
i-frontend-design
Use when building frontend components or pages. Core design skill for creating distinctive, production-grade interfaces that avoid generic AI aesthetics.
development1
mine.prior-art
Use when the user says: "prior art", "how do others do this", "what patterns exist", "industry standards for X", or wants to survey external approaches.
tools1
i-bolder
Use when the user says: "make it bolder", "more distinctive", "too generic". Make designs more distinctive and visually striking.
content-media1
i-distill
Use when the user says: "too complex", "simplify this UI", "strip it down". Simplify complex interfaces without losing function.
tools1
i-harden
Use when the user says: "production hardening", "handle edge cases in UI", "make it resilient", "improve onboarding", "empty states", "first-run experience". Improve interface resilience, error states, onboarding flows, and edge cases.
tools1
mine.mockup
Use when the user says: "mockup this UI", "show me what it looks like", "HTML mockup", "UI preview", or "generate a mockup". Generate self-contained HTML mockup files. Reads design/context.md if present for consistent styling.
development1
i-delight
Use when the user says: "add delight", "make it more fun", "moments of joy". Add micro-interactions and moments of delight to interfaces.
tools1
i-shape
Use when the user says: "shape this feature", "plan the UX", "design brief", "UX planning". Plan UX/UI for a feature before writing code via structured discovery interview.
development1
i-overdrive
Use when the user says: "go all out", "make it extraordinary", "overdrive", "wow factor", "push the limits". Push interfaces past conventional limits with advanced techniques.
development1
i-quieter
Use when the user says: "too busy", "too noisy", "reduce visual clutter". Reduce visual noise and clutter in interfaces.
tools1
mine.eval-repo
Use when the user says: "evaluate this repo", "should I use this library", or wants to assess a third-party dependency. Checks test coverage, code quality, maintenance health, bus factor, and maturity.
development1
mine.implementation-review
Use when mine.orchestrate Phase 3 runs the post-execution quality gate. Reviews changed files against design doc and task files using a Sonnet subagent.
testing1
mine.nitpick
Use when the user says: "nitpick this", "style check", "code hygiene", "find style sins", "nitpicker review", "anal retentive review", "exhaustive style review", "no-filter style report". Dispatches a hyper-critical style reviewer who flags every organization and hygiene issue — magic numbers, scattered constants, nested ternaries, messy CSS, dead code, naming inconsistencies — with no severity filter. Everything gets reported.
development1
mine.wtf
Use when the user says: "sniff test this", "WTF check", "code smells", "is this code any good", "fresh eyes on this branch", "review this directory", "check this module". Dispatches three parallel reviewers — code, integration, and a WTF readability pass — and consolidates findings into one prioritized report.
development1
i-colorize
Use when the user says: "fix the colors", "color system", "palette needs work". Improve color palettes, contrast, and theming.
tools1
i-typeset
Use when the user says: "fix the typography", "improve the type", "font choices". Improve typography, font choices, hierarchy, sizing, and readability.
tools1
i-optimize
Use when the user says: "optimize frontend performance", "improve load time", "fix rendering". Improve frontend performance and rendering efficiency.
development1
i-critique
Use when the user says: "critique this UI", "design critique", "review this interface", "does this look AI-generated". Evaluate design effectiveness with actionable feedback.
data-ai1
i-colorize
Use when the user says: "fix the colors", "color system", "palette needs work". Improve color palettes, contrast, and theming.
tools1
i-animate
Use when the user says: "add animations", "motion design", "transitions". Add meaningful animations and transitions to interfaces.
content-media1
i-bolder
Use when the user says: "make it bolder", "more distinctive", "too generic". Make designs more distinctive and visually striking.
content-media1
cm-get-token-insights
Use when the user asks about Claude token usage, wants to see how much they are spending on Claude, understand cache hit rates, review Claude Code workflow patterns, or get cost optimization recommendations.
development1
cm-extract-learnings
Use when the user says: "extract learnings", "save this for next time", "remember this pattern", "consolidate memories", "dream", "clean up memories".
tools1
i-audit
Use when the user says: "audit this UI", "frontend quality", "full UI audit", "design audit". Comprehensive audit of interface quality across accessibility, performance, theming, and responsive design.
development1
i-clarify
Use when the user says: "improve the copy", "error messages are confusing", "UX writing". Improve UX clarity, reduce confusion, and improve information hierarchy.
development1
i-adapt
Use when the user says: "responsive design", "make it mobile-friendly", "adapt for mobile". Make interfaces work across screen sizes with responsive design.
content-media1
i-animate
Use when the user says: "add animations", "motion design", "transitions". Add meaningful animations and transitions to interfaces.
content-media1
i-critique
Use when the user says: "critique this UI", "design critique", "review this interface", "does this look AI-generated". Evaluate design effectiveness with actionable feedback.
data-ai1
i-delight
Use when the user says: "add delight", "make it more fun", "moments of joy". Add micro-interactions and moments of delight to interfaces.
tools1
i-harden
Use when the user says: "production hardening", "handle edge cases in UI", "make it resilient", "improve onboarding", "empty states", "first-run experience". Improve interface resilience, error states, onboarding flows, and edge cases.
tools1
i-optimize
Use when the user says: "optimize frontend performance", "improve load time", "fix rendering". Improve frontend performance and rendering efficiency.
development1
mine.address-pr-issues
Use when the user says: "address PR comments", "fix review feedback", "fix failing CI", or "resolve merge conflicts". Triages and resolves PR blockers on GitHub or Azure DevOps.
development1
mine.build
Use when the user says: "build this", "implement this", "make this change", or "start a feature". Smart entry point that routes to direct implementation or the full caliper v2 workflow based on complexity.
development1
mine.debug
Use when encountering any bug, test failure, or unexpected behavior — invoked manually or nudged by the pytest loop detector hook
development1
mine.grill
Use when the user says: "grill me on this", "poke holes in my idea", "help me think this through", "what am I not thinking about", or wants multi-angle questioning before committing to building something. Pre-pipeline exploration that sharpens thinking.
development1
mine.mutation-test
Use when the user says: "mutation test", "do my tests actually catch bugs", or wants to verify test quality. Intentionally breaks code to check if tests catch real bugs. No framework needed.
development1
mine.research
Use when the user says: "research adding X", "feasibility study", "evaluate approach", or wants a focused investigation before committing. Dispatches the researcher agent for codebase investigation and presents a structured brief.
development1
mine.tool-gaps
Use when the user says: "find tool gaps", "session archaeology", or "missing cli features". Mines session history for recurring patterns that should be scripts or CLI tools.
tools1
mine.visual-qa
Use when the user says: "visual QA", "screenshot review", "review the UI visually", "take screenshots and find issues", or "UX review". Screenshots a live app via Playwright, then analysis agents review the captures — first impressions, cross-page consistency, and unstructured design narrative.
testing1
mine.worktree-rebase
Use when the user says: "rebase this worktree" or "sync worktree to parent branch". Detects the parent repo's current branch and rebases this worktree onto it.
tools1
i-audit
Use when the user says: "audit this UI", "frontend quality", "full UI audit", "design audit". Comprehensive audit of interface quality across accessibility, performance, theming, and responsive design.
development1
i-distill
Use when the user says: "too complex", "simplify this UI", "strip it down". Simplify complex interfaces without losing function.
tools1
i-layout
Use when the user says: "fix the layout", "arrange this", "visual hierarchy", "spacing issues", "crowded UI". Improve layout, spacing, and visual rhythm.
testing1
i-overdrive
Use when the user says: "go all out", "make it extraordinary", "overdrive", "wow factor", "push the limits". Push interfaces past conventional limits with advanced techniques.
development1
i-frontend-design
Use when building frontend components or pages. Core design skill for creating distinctive, production-grade interfaces that avoid generic AI aesthetics.
development1
i-polish
Use when the user says: "polish this UI", "final pass", "pixel-perfect", "normalize the design", "make it consistent", "align with design system". Final quality pass for alignment, spacing, consistency, and design system alignment.
testing1
i-quieter
Use when the user says: "too busy", "too noisy", "reduce visual clutter". Reduce visual noise and clutter in interfaces.
tools1
i-typeset
Use when the user says: "fix the typography", "improve the type", "font choices". Improve typography, font choices, hierarchy, sizing, and readability.
tools1
cm-recall-conversations
Use when the user asks to recall, search, or continue past conversations. Triggers on "what did we discuss", "continue where we left off", "remember when", "as I mentioned", "you suggested", "we decided", "search my conversations", "find the conversation where", "what did we work on". Also triggers on implicit signals like past-tense references ("the bug we fixed"), possessives without context ("my project"), or assumptive questions ("do you remember").
testing1
mine.decompose
Use when the user says: 'decompose this', 'find decomposition opportunities', 'what should I split', 'break this apart', 'this file is too big', 'split opportunities', 'extract candidates', 'find god classes'. Analyzes code for decomposition opportunities — prioritized by Git behavioral signals and structural metrics, with concrete split suggestions.
development1
mine.create-issue
Use when the user says: 'create an issue', 'file an issue', 'open an issue', 'write an issue', 'new issue for this'. Codebase-aware issue creation — investigates the code to produce well-structured issues with acceptance criteria, affected areas, and enough detail for automated triage.
development1
cm-extract-learnings
Use when the user says: "extract learnings", "save this for next time", "remember this pattern", "consolidate memories", "dream", "clean up memories".
tools1
mine.write-skill
Use when the user says: "create a skill", "write a skill", "new skill", or wants to author a new SKILL.md. Guided skill creation following Claudefiles conventions.
documentation1