Menu
SkillsMP has collected 31 skills from ryanportfolio/claude-starter. Open a skill to review its source and details.
Showing 31 of 31 collected skills.
Add a new skill to this repo so it's available in every Claude Code web session. Use when the user says $addskill, asks to "add a skill", "install a skill", "create a skill", or wants a third-party skill (e.g. superpowers) to show up in the available-skills…
Use when the user asks to brainstorm, explore, compare approaches, or design a feature, or when a requested product, interface, workflow, architecture, or behavior change has unresolved goals, competing directions, material tradeoffs, or high-cost ambiguity.…
Research current GitHub agent skills for frontend design, UI, UX, web, accessibility, motion, and creative implementation; determine which guidance is actually relevant to the active repository; and synthesize one lean repo-local design skill. Use when a user…
Research current GitHub agent skills for frontend design, UI, UX, web, accessibility, motion, and creative implementation; determine which guidance is actually relevant to the active repository; and synthesize one lean repo-local design skill. Use when a user…
Devil's advocate on change just made — argue honest case AGAINST before it lands. "Any reason not to?" Deliberate second-thoughts pass on diff in front of you. Surfaces scope creep, blast radius, irreversibility, simpler path skipped, YAGNI, "doesn't belong…
Code-quality and performance checklist for this project's stack. Use BEFORE making non-trivial changes — new features, refactors, perf work, bug fixes — to spot common pitfalls (N+1 queries, duplicate query-cache keys, non-passive scroll listeners, missing…
Use when a git merge/rebase/cherry-pick is in progress and has left unmerged paths or conflict markers (<<<<<<< / ======= / >>>>>>>) — especially when two parallel sessions edited the same file (the same page/component) and one side now conflicts. Reviews…
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Remove AI writing patterns and add human voice. Use when the user says $humanizer, $unslop, asks to "humanize", "de-AI", "de-slop", or "un-ChatGPT" text, wants a draft rewritten (blog, essay, PR, docs, memo, email), voice-matched writing, or an AI-tell review…
Critically review recent code changes (uncommitted diff, latest commit, or active PR) for bugs, schema drift, edge cases, observability gaps, and project-specific rule violations. Use when the user asks to review, audit, check, stress-test, or "look hard at"…
One-time first-session setup for a project spawned from the claude-starter template. Use when the user says $init-project, "set up this project", "configure the starter", "initialize the template" — or proactively when you notice CLAUDE.md still contains…
Build a throwaway, self-contained HTML "lab" to prototype and live-tune a visual or feel element BEFORE writing it into real code — game juice (particles, hit-flash, screen shake, weapon/enemy feel, color, timing) or web/UI work (a component, layout, spacing…
Use at the end of a confirmed-successful problem-solving session where the path from problem to fix took more than one attempt and surfaced gotchas worth carrying forward. Trigger when the user invokes $learning, says "capture learnings", "what did we learn",…
Turn on Auto-Merge Mode for the session — going forward, every completed task is automatically committed, pushed, opened as a PR, and merged into main (with conflict resolution), no per-merge confirmation. Use when the user says $merge, "auto-merge for the…
End-to-end safe shipping workflow — audit working tree, branch off main if needed, stage only intended files, verify, commit, push, open PR. Use when the user says $safe-ship, asks to "ship these changes", "commit and PR", "make a PR for this", "open a PR for…
Use when executing implementation plans with independent tasks in the current session. Supports sequential execution (one task at a time, review-gated) or parallel execution (independent tasks dispatched at once, each writing a disjoint file set, reviewed and…
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Honest second look at the recommendation the model just made — why it matters, the real reasoning behind it, and (the point) what it could be missing, quick and well-rounded. ONLY use when the user explicitly types the `$why` slash command. Do NOT trigger on…
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when a git merge/rebase/cherry-pick is in progress and has left unmerged paths or conflict markers (<<<<<<< / ======= / >>>>>>>) — especially when two parallel sessions edited the same file (the same page/component) and one side now conflicts. Reviews…
Use at the end of a confirmed-successful problem-solving session where the path from problem to fix took more than one attempt and surfaced gotchas worth carrying forward. Trigger when the user invokes /learning, says "capture learnings", "what did we learn",…
Use when executing implementation plans with independent tasks in the current session. Supports sequential execution (one task at a time, review-gated) or parallel execution (independent tasks dispatched at once, each writing a disjoint file set, reviewed and…
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code