Most popular Claude skills · page 150

Agent skills for Claude Code, Claude.ai and other agents, ranked by popularity: GitHub stars, forks, and how many curated lists and repos include them.

22,429 skills · showing 7153–7200

  1. 7153Nextjs Anti Patternswsimmonds/claude-nextjs-skillsIdentify and fix common Next.js App Router anti-patterns and mistakes. Use when reviewing code for Next.js best practices, debugging performance issues, migrating from Pages Router patterns, or preventing common pitfalls. Activates for code review, performance optimization, or detecting inappropriate useEffect/useState usage. CRITICAL: For browser detection, keep the logic in the user-facing component (or a composed helper that it renders) rather than isolating it in unused files.115
  2. 7154Nextjs App Router Fundamentalswsimmonds/claude-nextjs-skillsGuide for working with Next.js App Router (Next.js 13+). Use when migrating from Pages Router to App Router, creating layouts, implementing routing, handling metadata, or building Next.js 13+ applications. Activates for App Router migration, layout creation, routing patterns, or Next.js 13+ development tasks.115
  3. 7155Nextjs Client Cookie Patternwsimmonds/claude-nextjs-skillsPattern for client components calling server actions to set cookies in Next.js. Covers the two-file pattern of a client component with user interaction (onClick, form submission) that calls a server action to modify cookies. Use when building features like authentication, preferences, or session management where client-side triggers need to set/modify server-side cookies.115
  4. 7156Nextjs Dynamic Routes Paramswsimmonds/claude-nextjs-skillsGuide for Next.js App Router dynamic routes and pathname parameters. Use when building pages that depend on URL segments (IDs, slugs, nested paths), accessing the `params` prop, or fetching resources by identifier. Helps avoid over-nesting by defaulting to the simplest route structure (e.g., `app/[id]` instead of `app/products/[id]` unless the URL calls for it).115
  5. 7157Nextjs Pathname Id Fetchwsimmonds/claude-nextjs-skillsFocused pattern for fetching data using URL parameters in Next.js. Covers creating dynamic routes ([id], [slug]) and accessing route parameters in server components to fetch data from APIs. Use when building pages that display individual items (product pages, blog posts, user profiles) based on a URL parameter. Complements nextjs-dynamic-routes-params with a simplified, common-case pattern.115
  6. 7158Nextjs Server Client Componentswsimmonds/claude-nextjs-skillsGuide for choosing between Server Components and Client Components in Next.js App Router. CRITICAL for useSearchParams (requires Suspense + 'use client'), navigation (Link, redirect, useRouter), cookies/headers access, and 'use client' directive. Activates when prompt mentions useSearchParams, Suspense, navigation, routing, Link component, redirect, pathname, searchParams, cookies, headers, async components, or 'use client'. Essential for avoiding mixing server/client APIs.115
  7. 7159Nextjs Server Navigationwsimmonds/claude-nextjs-skillsGuide for implementing navigation in Next.js Server Components using Link component and redirect() function. Covers the difference between server and client navigation methods. Use when adding links, redirects, or navigation logic in server components without converting them to client components unnecessarily.115
  8. 7160Nextjs Use Search Params Suspensewsimmonds/claude-nextjs-skillsPattern for using useSearchParams hook with Suspense boundary in Next.js. Covers the required combination of 'use client' directive and Suspense wrapper when accessing URL query parameters in client components. Use when building search interfaces, filters, pagination, or any feature that needs to read/manipulate URL query parameters client-side.115
  9. 7161Observability DesignOwl-Listener/ai-design-skillsMaking multi-agent workflows visible and debuggable for designers and developers.207
  10. 7162Orchestrate Projectdanielvm-git/bigpowersMeta-skill that enforces the 6-phase core loop (discover → elaborate → plan → build → verify → release) with hard gates. Use to coordinate multi-phase projects with guaranteed quality checkpoints. One-time command for the entire project lifecycle.292
  11. 7163Organize Workspacedanielvm-git/bigpowersScans the active workspace for disposable artifacts—logs, caches, stale build output, and stray draft markdown—and proposes consolidation of scattered assets. Produces a reviewable list, asks for explicit confirmation before any delete or move, and optionally revises .gitignore. Use when the user says "clean my room", "organize workspace", "workspace cleanup", "remove temp files", "organize assets", "gitignore", or wants a safe tidy pass.292
  12. 7164Output Quality RubricsOwl-Listener/ai-design-skillsDefining what "good" looks like for AI outputs — accuracy, relevance, helpfulness.207
  13. 7165Persona ArchitectureOwl-Listener/ai-design-skillsDefining AI character, voice, and personality traits.207
  14. 7166Plan Refactordanielvm-git/bigpowersCreate a detailed refactor plan with tiny commits via user interview, then save it as specs/REFACTOR_LATEST.md. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.292
  15. 7167Plan Releasedanielvm-git/bigpowersRELEASE-INDEX BUILDER — Sequence elaborated epics into specs/release-plan.yaml with WSJF ordering and BCP baselines. NOT a planning-spine substitute: it does not scope work (scope-work) or write story tasks (plan-work). Use after elaborate-spec when the user wants a versioned release index of epics.292
  16. 7168Plan Testsdanielvm-git/bigpowersDesign a risk-scaled test architecture for an epic before implementation begins. Produces prioritized scenarios, test level distribution, and fixture plans based on TEA and bigpowers principles.292
  17. 7169Plan Workdanielvm-git/bigpowersPLANNING SPINE STEP 3 of 3 — Plan the work: write detailed implementation tasks into the active epic capsule (specs/epics/eNN-slug/). Produces countable-story-format .md specs and runnable -tasks.yaml files. Use after slice-tasks (step 2). Not a substitute for scope-work (step 1) or slice-tasks (step 2).292
  18. 7170Progressive DisclosureOwl-Listener/ai-design-skillsRevealing AI capability gradually to match user mental models.207
  19. 7171Prompt VersioningOwl-Listener/ai-design-skillsManaging prompt iterations, testing changes, and tracking what works.207
  20. 7172Publish Packagedanielvm-git/bigpowersPackage registry publishing for npm, crates.io, PyPI, and Homebrew. Verifies prerequisites, runs the publish command, confirms success, and surfaces actionable error hints on failure.292
  21. 7173Quick Fixdanielvm-git/bigpowersStreamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger.292
  22. 7174Release Branchdanielvm-git/bigpowersMake the merge/PR/keep/discard decision for a feature branch, verify coverage gates, create the PR with gh, and clean up the worktree. Use when a feature is done and ready to ship, or when user says "release", "merge", or "open a PR".292
  23. 7175Request Reviewdanielvm-git/bigpowersDispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes. The reviewer has no shared state with the coding agent and gives a genuine second opinion. Use after audit-code passes, before committing, or when user wants an independent code review.292
  24. 7176Research Firstdanielvm-git/bigpowersLook-before-build — search registries, repo, existing skills, and web for prior art before implementing. Appends Prior Art to the spec. Use after survey-context and before elaborate-spec, when adding dependencies, or when the task may already be solved.292
  25. 7177Reset Baselinedanielvm-git/bigpowersRestore the project to a known clean state between agent runs or experiments. Use between benchmark runs, after a failed spike, or when user wants a clean working tree.292
  26. 7178Respond Reviewdanielvm-git/bigpowersAct on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.292
  27. 7179Run Benchmarkdanielvm-git/bigpowersRun skill quality benchmarks from specs/benchmarks/ definitions — N-run with/without-skill delta grading, train/validation split, pass@k + benchmark.json reports. Use before and after evolve-skill to prove quality changes are improvements, not regressions.292
  28. 7180Run Evalsdanielvm-git/bigpowersEval-Driven Development — define capability and regression evals before building; code graders use verify commands, model graders use explicit rubrics; log pass@k. Use before develop-tdd on new features, or when measuring agent capability over runs.292
  29. 7181Run Planningdanielvm-git/bigpowersDISCOVER-PHASE ADVANCER — Drive the discover-phase checklist (specs/planning-status.yaml) through survey-context → scope-work → research-first → elaborate-spec → plan-release → slice-tasks. NOT a duplicate of plan-work or the planning spine; it orchestrates the pre-coding discover phase only.292
  30. 7182Scope Workdanielvm-git/bigpowersPLANNING SPINE STEP 1 of 3 — Scope the work: define what is in and out of scope and save as specs/product/SCOPE_LATEST.yaml. Use before slice-tasks or plan-release on any new initiative. Not a substitute for slice-tasks (step 2) or plan-work (step 3).292
  31. 7183Search Skillsdanielvm-git/bigpowersFind the right bigpowers skill from natural-language intent using a local lexical index over SKILL.md frontmatter. Use when unsure which skill to invoke, or at start of research-first.292
  32. 7184Security Reviewdanielvm-git/bigpowersAI-powered security analysis of code changes — traces data flow, detects injection, auth bypass, secrets exposure, and unsafe deserialization across files. Use when reviewing pending changes, before release-branch, during verify-work Phase 5, during build-epic Step 0 threat modeling, or when the user says "security review" or "scan for vulns".292
  33. 7185Seed Conventionsdanielvm-git/bigpowersGenerate CLAUDE.md and CONVENTIONS.md for a brand-new project through a brief interview, and create the specs/ directory with evolved bigpowers structure (product/, tech-architecture/, verifications/, epics/archive/). Entry point for greenfield projects. Use when starting a new project from scratch, when user asks to set up AI agent conventions, or when there is no CLAUDE.md yet.292
  34. 7186Session Statedanielvm-git/bigpowersTrack implementation decisions and progress in specs/state.yaml to prevent context rot. Use at the start of a session to load context, and whenever a significant decision is made or a milestone is reached.292
  35. 7187Setup Environmentdanielvm-git/bigpowersPre-install dependencies and configure tools before development work begins. Use at session start on a fresh clone, before kickoff-branch, or when user says setup environment or install deps.292
  36. 7188Simple Englishdanielvm-git/bigpowersWrite or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so the result is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the 53 rules of the standard (Issue 9) with a deterministic lint gate.292
  37. 7189Simulate Agentsdanielvm-git/bigpowersRun Mock User and Auditor agents against a feature in fresh contexts before human review. Use after verify-work, before request-review, when user wants pre-review simulation.292
  38. 7190Slice Tasksdanielvm-git/bigpowersPLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.292
  39. 7191Smoke Testdanielvm-git/bigpowersPost-deploy health-check against a live URL. Validates HTTP status, response content, and critical endpoints. Runnable standalone OR as the final step of the deploy skill.292
  40. 7192Spike Prototypedanielvm-git/bigpowersThrow-away prototype for unknown problem spaces. Output is learning notes in specs/archive/spikes/SPIKE-<name>.md, not production code. Use when the domain or technology is unexplored, when estimates are impossible without experimentation, or when user says "spike", "prototype", or "proof of concept".292
  41. 7193State ManagementOwl-Listener/ai-design-skillsManaging shared context, memory, and state across multiple agents.207
  42. 7194Stocktake Skillsdanielvm-git/bigpowersSequential subagent batch audit of the bigpowers skill catalog — Quick Scan (changed only) or Full (all skills). Use during sustain phase, before a major release, or when catalog drift is suspected.292
  43. 7195Survey Contextdanielvm-git/bigpowersPer-task context bootstrap — reads existing specs/ and tech-architecture docs to map the current lifecycle phase and suggest the next skill. Use at the start of any task, when returning after a break, or when unsure what to do next. For deriving a tech-stack doc from scratch, use map-codebase first.292
  44. 7196System Prompt StructureOwl-Listener/ai-design-skillsAnatomy of effective system prompts — role, context, constraints, format.207
  45. 7197Task DecompositionOwl-Listener/ai-design-skillsBreaking complex user goals into subtasks that agents can handle.207
  46. 7198Task Success MetricsOwl-Listener/ai-design-skillsMeasuring whether the AI actually helped users accomplish their goals.207
  47. 7199Template DesignOwl-Listener/ai-design-skillsCreating reusable, parameterised prompt templates for consistent outputs.207
  48. 7200Terse Modedanielvm-git/bigpowersFallback ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use ONLY when context is critically long and compressing output is necessary to continue. Not a strategy — token discipline comes from code shape (small functions, unique names, headless tests), not terser prompts. Use when user says "caveman mode", "terse mode", "less tokens", "be brief", or invokes /terse-mode.292