pcc
Add pros, cons, and confidence to options in a Prompt. TRIGGER when the Architect asks for "/pcc", pros/cons/confidence, alternatives, options, approaches, or a ranked choice. DO NOT TRIGGER for a single implementation call, a convention Decision with repo Precedent, or a proposing-state turn where /propose is canonical.
naming
MANDATORY for naming any code identifier — variable, function, file, folder, class, database column, route, CSS class. Always returns a 5-10 candidate slate; the caller picks. TRIGGER when proposing or choosing a name, on /naming, on "rename", "ideas", "options", "what should I call", or any new file/class/method/column/route. DO NOT TRIGGER when editing a body that does not introduce or change an identifier, when restructuring code (Architecture, not naming), or when labeling UI for end Users.
modeling
Transform Shaping output into a concrete Modeling artifact — database schema, User experience, and Architecture. TRIGGER between Shaping and Slicing, or when the Architect asks to model an existing system before Execution.
laravel
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.
interview
Interview the Architect about a Plan or Proposal, one question at a time, to sharpen it before any code is written. Use when the Architect wants to stress-test or pin down a Plan before building.
independent-review
Run N identical parallel Subagents on the same Task for independent Verification. Use when the Architect wants consensus through redundancy — multiple Subagents independently analyze, review, or test the same thing, then results are compared for agreement, disagreements, and unique finds. Invocation /independent-review [count] "task"
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
handoff
Compact the current conversation into a handoff document for another Agent to pick up.
gh-issue
Create or update GitHub issues. Enforces self-contained issues that an Agent can implement without conversation Context. Use when the Architect says "create an issue", "file an issue", "gh issue", "update the issue", or wants to turn a Plan into a trackable issue.
marketing
Positioning, audience, and what-works judgment for the strategy call — the category the product competes in, who it's for, why it's different, and which growth move is real at this stage. TRIGGER when the brief needs a positioning thesis, an ICP or audience definition, differentiation, switching forces, or a read on which channel fits the product's stage. DO NOT TRIGGER to gather the raw customer evidence underneath positioning (research), to shape paid ad angles (advertising), or to size organic search demand (seo).
polish
Use when a draft's parts are all written but the seams between them are abrupt — smooths the transitions between sections so the piece reads as one continuous argument, not a stack of blocks. Owns the connective craft: handing momentum from one section to the next (problem→agitate→solve, story→lesson→call-to-action, feature→benefit→proof). TRIGGER when a draft is structurally complete and has cleared the strategy gate, and the sections need bridging. DO NOT TRIGGER for writing new copy from a brief (copywriting), running ship-gate checks (editing), or fixing a single line's clarity (that's the line check).
publish
Turns cleared copy into a dated deliverable file in the project's working directory, with a header recording the asset, date, and brief. TRIGGER when copy has cleared every editor's checks and is ready to ship, hand off, save, or export as a final draft. DO NOT TRIGGER while copy is still being written or revised — writing is the copywriting skill, clearing it is the editing skill. Publish is the last step, only for copy that is already cleared.
seo
Search demand, buyer-stage intent, and ranking reality for the strategy call — what people actually search, what they want at each stage, and what it honestly takes to be found in both classic search and AI answers. TRIGGER when the brief involves organic search demand, keyword intent by buyer stage, ranking feasibility, on-page essentials, or getting cited by AI search. DO NOT TRIGGER for paid search angles (advertising), broader positioning and channel choice (marketing), or gathering customer language (research).
execute
|
execute-plan
Orchestration Process for executing Plans. Assigns Slices to Subagents and runs Verification after each Slice. The Orchestrator coordinates — it does not implement.
domain-design
Build or sharpen a project's Domain.md and Decisions. Use when the Architect wants to pin down project language, record a Decision, or when another Skill needs to change Domain.md.
diagram
|
design
TRIGGER when building UI components, styling pages, or making visual/interaction Decisions. Guides design thinking, anti-patterns, CSS Architecture, and responsive patterns.
dent
Operate Dent via first-party API. Trigger: Dent API, Funnels, Offers, Pages, Articles, Courses, Spaces, Analytics. Do not trigger for WordPress-only work.
debug
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
debate
Run N independent architect Agents debating Architectural options through rounds. TRIGGER when the Architect wants multiple competing solutions evaluated, when 3+ distinct approaches need comparison, or when the Prompt says "debate", "competing solutions", "run architects", "architecture debate", or `/debate [count] "problem"`.
critical-path
Process for changes with a large blast radius — files with many callers or repo-p95 complexity, and actions that are destructive, hard to reverse, or visible outside the repo. TRIGGER before editing a file whose enrichment context shows callers ≥ 20 or complexity at the repo p95, and before any delete, force-push, schema drop, process kill, push, pull-request operation, shared-infrastructure change, or third-party upload.
commit
|
codex
Drive codex CLI runs as your Agents — you own Orchestration, codex does the work. One wrapper, `codex-run`, owns the mechanics (flags, output storage, stream parsing, failure detection); you write the Task Prompt and do the judgment. Calls /subagents for Orchestration doctrine on a codex-run substrate. TRIGGER when the Architect says "codex", "/codex", "codex-run", "use codex", "dispatch to codex", "run this through codex", "codex agents", "review with codex", "codex review", or asks to fan out work across codex runs. DO NOT TRIGGER for native Claude Code Subagents (use /subagents) — those run inside this Harness; codex is a separate CLI process.
code-first
Autonomous async Execution. The Architect hands off and walks away; the Agent drives the Task to done — makes every Architectural call via /trace + /pcc + ranking, executes through /subagents, verifies from each implementing Subagent's Evidence (they exercise their own flows, real browser for UI), and returns finished code plus the recorded Decisions for review. TRIGGER when the Architect says "code-first", "/code-first", "execute with /subagents", "execute directly & autonomously", "drive it and report back", "iterate until done", "I'm going to bed", "off to bed", or signals an AFK / overnight handoff. DO NOT TRIGGER when the Architect wants options before action — that is the default mode (propose via /pcc and wait).
journal
File a session's loose material into the knowledge wiki — each capture into its owning topic folder, the topic's Claude.md kept current. TRIGGER after a session hands you loose captures (notes, clippings, findings, screenshots) that need a home in the wiki. DO NOT TRIGGER to gather new research, or to consolidate the wiki itself (that is dream).
architecture
TRIGGER when presenting Architectural options, Architecting systems, or discussing tradeoffs. Append to any Prompt.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
create-subagent
Guide for creating specialized Claude Code subagents with proper YAML frontmatter, focused descriptions, system prompts, and tool configurations. Use when the user wants to create a new subagent, custom agent, specialized AI assistant, or mentions creating/designing/building agents or subagents.
penwa
Drive the OpenWA WhatsApp HTTP API from the terminal with curl. Use when sending WhatsApp messages (text/image/video/audio/document/location/contact/bulk), managing sessions and QR login, listing contacts/groups/chats, registering webhooks, or managing scoped API keys against an OpenWA server. Triggers on "OpenWA", "penwa", "send WhatsApp via API", "WhatsApp session", or mentions of base URL http://0.0.0.0:2785.
openwa
>-
ios-simulator
Control the iOS Simulator using xcrun simctl. Use when asked to take a screenshot of the simulator, navigate to a screen, open a deep link, launch or kill an app, control the status bar, list simulators, or interact with the running iOS simulator. Trigger terms: simulator, xcrun, simctl, screenshot simulator, deep link, open app, navigate mobile.
creating-financial-models
This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions
create-skill
Guide for creating well-structured Claude Code skills with proper YAML frontmatter, focused descriptions, and supporting files. Use when the user wants to create a new skill, build a custom skill, extend Claude's capabilities, or mentions creating/designing/building skills.
analyzing-financial-statements
This skill calculates key financial ratios and metrics from financial statement data for investment analysis
component-reuse-first
Search existing components before creating new ones. When a new component is unavoidable, design it for future reuse with proper props, composition, and placement in shared directories. Use when building UI, creating React/Vue/Svelte/Angular/SwiftUI components, adding buttons/forms/cards/modals/tables, scaffolding pages, or any time the user says "create a component", "add a component", "build a UI", or mentions component-like work.
webgl-expert
Expert guide for WebGL API development including 3D graphics, shaders (GLSL), rendering pipeline, textures, buffers, performance optimization, and canvas rendering. Use when working with WebGL, 3D graphics, canvas rendering, shaders, GPU programming, or when user mentions WebGL, OpenGL ES, GLSL, vertex shaders, fragment shaders, texture mapping, or 3D web graphics.
sentry-cli
Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.
secure-web-search
Guide for performing secure web searches with privacy protection, source verification, and information validation. Use when the user wants to search the web securely, verify sources, fact-check information, or mentions secure search, privacy, source validation, or web research.
connect-mcp-server
Guide for connecting MCP (Model Context Protocol) servers to Claude Code with HTTP, stdio, and SSE transports. Covers installation, configuration, authentication, environment variables, and security. Use when the user wants to connect MCP servers, add integrations, configure external services, or mentions MCP, servers, integrations, or external tools.
create-hooks
Guide for creating Claude Code hooks with proper configuration, shell commands, event handling, and security practices. Use when the user wants to create hooks, automate workflows, add event handlers, format code automatically, protect files, log actions, or mentions creating/configuring/building hooks.
create-command
Guide for creating custom Claude Code slash commands with proper structure, argument handling, frontmatter configuration, and best practices. Use when the user wants to create slash commands, custom commands, reusable prompts, or mentions creating/designing/building commands.
create-claude-plugin
Guide for creating Claude Code plugins that bundle skills, agents, commands, hooks, and MCP servers for distribution. Covers plugin structure, marketplace.json format, installation, testing, and publishing. Use when the user wants to create plugins, distribute skills/agents, build marketplaces, or mentions creating/packaging/publishing plugins.
streaming-assistant
Activate this skill when users need help with live streaming workflows including pre-stream setup, real-time source management during streams, audio verification, scene transitions, or stream health monitoring. Triggers include requests like "help me stream", "pre-stream checklist", "manage my stream", "check audio before streaming", "switch scenes during stream", or troubleshooting streaming issues. This skill orchestrates multiple tools to guide users through complete streaming sessions from setup to teardown.
audio-engineer
Activate this skill when users need help with audio configuration, troubleshooting, or optimization in OBS. Triggers include requests like "fix my audio", "adjust microphone levels", "mute desktop audio", "balance my audio sources", "check audio levels", or diagnosing audio issues like echo, distortion, or missing sound. This skill orchestrates audio tools to ensure professional sound quality.
preset-manager
Activate this skill when users need help with scene preset operations including saving, applying, organizing, or managing source visibility configurations. Triggers include requests like "save this layout", "apply my gaming preset", "switch to BRB mode", "create a preset", "list my presets", "rename preset", or managing saved configurations. This skill orchestrates preset tools for efficient scene state management.
scene-designer
Activate this skill when users need help creating, modifying, or arranging visual elements in OBS scenes. Triggers include requests like "add a text overlay", "create a new scene", "move my webcam", "resize the game capture", "add a browser source", "arrange my layout", or designing scene compositions. This skill orchestrates the 14 Design tools to build professional-looking stream layouts.
studio-mode-operator
Activate this skill when users need help with OBS Studio Mode's preview/program workflow — staging scene changes privately, rehearsing transitions, and committing them to the live output. Triggers include "enable studio mode", "preview the next scene", "rehearse a transition", "promote preview to program", "what's queued on preview", or "switch my transition to fade". This skill focuses on the two-scene discipline (program = what viewers see, preview = what's being prepared) rather than general streaming setup.
template-skill
Replace with a clear description of what this skill does and when Claude should use it. Be specific about the use cases, tools, or workflows this skill addresses.
nano-banana-videogen
Generate videos using Google Veo models via the nano-banana CLI. Use this skill when the user asks to create, generate, animate, or produce videos with AI. Supports text-to-video, image-to-video animation, dialogue with lip-sync, and scene extensions. Trigger on requests like "create a video", "animate this image", "make a video clip", "generate footage", "produce a short film", "add motion to this".
Page 992 of 1735 · 86738 results
