Sponsored by

Find leads on Reddit on auto pilot

Topic: claude

14,433 skills in this topic.

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
skill-manager Manage, audit, and maintain your skill ecosystem. Use when the user asks to "check my skills", "audit skills", "find duplicate skills", "which skills am I using", "prune unused skills", "are my skills synced", "check for skill updates", "skill report", "skill health", or mentions skill maintenance, cleanup, or organization.
petekp/claude-code-setup 20
solution-explorer Exhaustively explore a problem and solution space before implementing a feature or making an architectural decision. Use when asked to implement a feature, design a system, choose between approaches, or any time there are multiple valid ways to solve a problem. Forces systematic exploration of alternatives to find the global optimum instead of settling on the first reasonable idea. Use this skill whenever the user says things like "implement X", "how should we build", "best way to", "design", "architect", "add a feature for", or describes a non-trivial feature they want built. Even if the user doesn't explicitly ask for exploration, use this skill when you recognize that the implementation has multiple viable paradigms worth comparing.
petekp/claude-code-setup 20
swift-apps Build, refactor, review, and debug native Apple-platform software in Swift. Use when working on `.swift` files, SwiftUI views, Observation-based state, `@Bindable` and binding flow, SwiftData-backed UI, scenes and windows, search/navigation structures, UIKit/AppKit interop, Liquid Glass adoption, macOS-native UX, or SwiftUI performance/accessibility. Trigger on requests to create or polish iOS, iPadOS, macOS, or visionOS features; clean up SwiftUI view structure; diagnose jank or invalidation storms; review app quality; or make a feature feel like a good Apple-platform citizen.
petekp/claude-code-setup 20
swiftui-expert-skill Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, macOS-specific APIs, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
petekp/claude-code-setup 20
tdd Test-driven development for features, bug fixes, regressions, and safe refactors using a failing-test-first workflow. Use when Codex needs to add or change behavior with proof, reproduce a bug in a test, write regression or characterization tests, make a refactor safer, or respond to prompts like "use TDD", "red-green-refactor", "write the test first", "add a regression test", "reproduce this in a test", "prove the fix", "cover this change with tests", or "make this safe to refactor". Prefer this skill when confidence should come from executable evidence instead of reasoning alone.
petekp/claude-code-setup 20
typography Apply professional typography principles to create readable, hierarchical, and aesthetically refined interfaces. Use when setting type scales, choosing fonts, adjusting spacing, designing text-heavy layouts, implementing dark mode typography, or when asked about readability, font pairing, line height, measure, typographic hierarchy, variable fonts, font loading, or OpenType features.
petekp/claude-code-setup 20
ubiquitous-language Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
petekp/claude-code-setup 20
unix-macos-engineer Expert Unix and macOS systems engineer for shell scripting, system administration, command-line tools, launchd, Homebrew, networking, and low-level system tasks. Use when the user asks about Unix commands, shell scripts, macOS system configuration, process management, or troubleshooting system issues.
petekp/claude-code-setup 20
vercel-react-best-practices React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
petekp/claude-code-setup 20
write-a-prd Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
petekp/claude-code-setup 20
agent-fungibility The philosophy and practical benefits of agent fungibility in multi-agent software development. Why homogeneous, interchangeable agents outperform specialized role-based systems at scale.
Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations 62