Sponsored by

Find leads on Reddit on auto pilot

Topic: skills

17,247 skills in this topic.

frontend-design Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
petekp/claude-code-setup 20
research-prompt Craft a high-quality prompt for a deep research agent (like ChatGPT Deep Research) through adaptive interviewing. Use when the user wants to research something but needs help formulating what to ask — when they say "I need to research X", "help me figure out what to ask about Y", "write a research prompt for Z", "I want to use deep research on...", or when they have a vague research need and want a precise, comprehensive prompt that will get excellent results from a research agent. Also use when the user mentions deep research, ChatGPT research, or preparing a query for an AI research tool.
petekp/claude-code-setup 20
grill-me Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
petekp/claude-code-setup 20
handoff Generate a resume-ready handoff prompt that lets another session or agent continue work without rediscovering context. Use when the user asks for a handoff, bootstrap prompt, session summary, save-state prompt, or wants to continue later in a fresh session, another model, or a different environment. Also use when context is getting full and the current goal, repo state, decisions, verification status, blockers, and exact next actions must be preserved in a compact prompt.
petekp/claude-code-setup 20
improve-codebase-architecture Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
petekp/claude-code-setup 20
literate-guide Create a narrative guide to a codebase or feature in the style of Knuth's Literate Programming — code and prose interwoven as a single essay, ordered for human understanding rather than compiler needs. Use when the user asks to 'explain this codebase as a story', 'write a literate guide', 'create a narrative walkthrough', 'tell the story of this code', 'Knuth-style documentation', 'weave a guide for this feature', or when they want deep, readable documentation that treats the program as literature. Also trigger when someone wants a document that a thoughtful reader could follow from start to finish and come away understanding both WHAT the code does and WHY every design choice was made.
petekp/claude-code-setup 20
manage-codex Autonomous Codex batch orchestrator. Use for "/manage-codex", "manage codex", "use codex", "dispatch to codex", or long-running Codex work.
petekp/claude-code-setup 20
manual-testing Guide users through targeted manual verification after code changes. Use when asked to "test this", "verify it works", "QA this", "walk me through testing", "smoke test", "sanity check", "regression test", "acceptance test", or after implementing a feature or bug fix that still needs human validation. Favor this skill for focused verification of the current change; use a broader exploratory-testing skill for open-ended bug hunting across an entire app.
petekp/claude-code-setup 20
method:autonomous-ratchet Autonomous-only artifact-centric method for overnight quality improvement runs on an existing codebase. 17 steps across 6 phases: Triage -> Stabilize -> Envision -> Plan -> Execute -> Finalize. Use when asked to run this overnight, improve while I sleep, ratchet quality autonomously, or do an autonomous quality pass. Do not use for interactive steering, greenfield feature work, architecture decisions, cleanup-only sweeps, one-off fixes, or repos without explicit build/test/verify commands.
petekp/claude-code-setup 20
method:create Codex-powered compiler for turning a natural-language workflow description into a method skill that matches the live corpus. 5 phases: Intake -> Analysis -> Authoring -> Validation -> Refinement. Codex workers handle analysis, file generation, and quality gate; Claude does intake and a final refinement pass optimized for Claude Code. Use when you want to create a method, compile a method, author a method skill, or turn this workflow into a method. Not for editing existing methods, not a runtime engine, and not for one-off prompts.
petekp/claude-code-setup 20
method:decision-pressure-loop Architecture decision workflow for choosing between meaningful architectural or protocol options under uncertainty before implementation begins. 8 steps across 5 phases: Framing -> Reality Mapping -> Option Exploration -> Pressure -> Publication. Use when the team needs a defensible decision with explicit tradeoffs, reopen conditions, and implementation-facing guidance — not when the goal is already code delivery.
petekp/claude-code-setup 20
method:dry-run Validate a Claude Code method skill for mechanical soundness by dry-running a concrete feature through every step. Use when you need to dry run, validate a method, trace a method skill, check mechanical soundness, or verify that a method's setup, paths, commands, artifact chains, headers, templates, gates, and topology are wired correctly. Invoke this after authoring or editing any method skill, and before trusting it for real work.
petekp/claude-code-setup 20
method:flow-audit-and-repair Forensic debugging workflow for broken end-to-end flows. 8 steps across 5 phases: Failure Framing → Forensics → Repair Design → Layered Repair → Reaudit. Use when an existing flow is broken, flaky, or operationally unsafe and the team needs a path from observed failure to verified repair — not for greenfield features or speculative design work.
petekp/claude-code-setup 20
method:janitor Artifact-centric method for systematic codebase cleanup — dead code, stale docs, orphaned artifacts, vestigial comments, and redundant abstractions. 8 steps across 5 phases: Survey -> Triage -> Prove -> Clean -> Verify. Dual-mode: interactive (user checkpoints) or autonomous (evidence-gated with deferred review). Use when asked to clean up dead code, do a janitor sweep, improve context hygiene for agents, remove stale docs, or find and remove unused code. Do not use for refactoring with behavior changes, architecture decisions, feature work, one-off deletions, dependency upgrades, or formatting cleanup.
petekp/claude-code-setup 20
method:research-to-implementation Artifact-driven method for taking a significant feature from idea to shipped code. 10 steps across 5 phases: Alignment → Evidence → Decision → Preflight → Delivery. Use when the user describes a non-trivial feature that needs research, design, and implementation — not for bug fixes, single-file changes, or quick wiring tasks.
petekp/claude-code-setup 20
method:router Routes `/method:router` requests to the best-fit method skill among the 7 methods. Not a method itself. Use for `/method:router` or `/method:router <args>` when choosing which method to start.
petekp/claude-code-setup 20
method:spec-hardening Artifact-driven method for turning a rough RFC, design spec, PRD, or method schema into a canonical amended spec, a build-ready execution packet, and a reviewed implementation plan without crossing into code. 10 steps across 6 phases: Intake -> Multi-Angle Review -> Amendment -> Contracting -> Planning -> Validation. Use when an existing draft exists but is not yet safe to build from.
petekp/claude-code-setup 20
pipeline Modular development pipeline orchestrator. Use for "/pipeline", "pipeline init", "pipeline resume", "pipeline status", or phased triage → align → execute workflows.
petekp/claude-code-setup 20
prd-to-issues Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
petekp/claude-code-setup 20
product-design Expert product design knowledge for software interfaces — 451 practices across 25 categories, each with tags, priority (core/situational/niche), and applies_when metadata for precise retrieval. Use this skill whenever the user is designing, reviewing, building, or discussing any part of a software interface. This includes: building forms or input flows, designing dashboards or data tables, choosing UI components (modals vs. sidebars, tabs vs. accordions, toggles vs. checkboxes), planning navigation or information architecture, handling errors and feedback, designing onboarding or empty states, building enterprise/B2B admin panels, creating design systems, implementing accessibility, optimizing perceived performance, designing search/filter/sort, building multi-step workflows or wizards, or reviewing existing designs for usability issues. Also trigger when the user asks about design best practices, UX heuristics, cognitive load, Gestalt principles, Fitts's Law, Hick's Law, or any named design principle. Even if the user doesn't explicitly say "design" — if they're building UI and making layout, component, or interaction decisions, this skill applies.
petekp/claude-code-setup 20
proposal-review Facilitate methodical review of proposals (technical designs, product specs, feature requests). Use when asked to "review this proposal", "give feedback on this doc", "help me review this RFC", or when presented with a document that needs structured feedback. Handles markdown files, GitHub gists/issues/PRs, and other text formats. Chunks proposals intelligently, predicts reviewer reactions, and produces feedback adapted to the proposal's format.
petekp/claude-code-setup 20
review-package Create a self-contained review package of current work for external review by another AI model or human reviewer. Bundles relevant files with a contextual README and instructional prompt. Triggers: "review package", "create review package", "hand off for review", "get a second opinion", "external code review", "cross-model review", "package for review", "prepare code review". Accepts an optional focus area argument to scope the analysis.
petekp/claude-code-setup 20
seam-ripper Ruthlessly analyze architectural seams—the interfaces, boundaries, and contracts between system components—to expose coupling problems, abstraction leaks, and design failures. Use when asked to review architecture, analyze coupling, find interface problems, improve module boundaries, audit dependencies, or redesign system structure. Produces uncompromising redesign proposals that prioritize correctness over backwards compatibility.
petekp/claude-code-setup 20
seo-audit When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
petekp/claude-code-setup 20