
Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.
Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations.
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability.
Add strategic color to features that are too monochromatic or lack visual interest. Makes interfaces more engaging and expressive.
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.
Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean.
Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful.
Socratic deep interview with mathematical ambiguity gating before autonomous execution
Expert multi-AI code review with quality and security analysis
Multi-AI implementation using Codex and Gemini CLIs (Double Diamond Develop phase). Use when: AUTOMATICALLY ACTIVATE when user requests building or implementation:. "build X" or "implement Y" or "create Z". "develop a feature for X"
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready.
Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode
Alias for /omc-plan --consensus
Self-referential loop until task completion with configurable verification reviewer
Manage isolated dev environments with git worktrees and tmux sessions
Configure popular MCP servers for enhanced agent capabilities
Configure notification integrations (Telegram, Discord, Slack) via natural language
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Evaluate design effectiveness from a UX perspective. Assesses visual hierarchy, information architecture, emotional resonance, and overall design quality with actionable feedback.
Project remaining workflow cost from per-phase averages — warns on budget ceiling overruns. Use when: AUTOMATICALLY ACTIVATE when user asks about workflow costs:. "cost projection", "estimate remaining cost". "budget forecast", "how much will this cost"
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Ask Claude, Codex, or Gemini via local CLI and capture a reusable artifact
Full autonomous execution from idea to working code
Cancel any active OMC mode (autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, team)
Configure HUD display options (layout, presets, display elements)
Deep codebase initialization with hierarchical AGENTS.md documentation
Invoke parallel document-specialist agents for external web searches and documentation lookup
Full OpenCode delegation workflow — routing rules, agent-to-role mapping, model routing, invocation patterns, and examples for delegating tasks to OpenCode (GitHub Copilot). Use when delegating heavy work to OpenCode or making one-shot queries via opencode-ask.
Extract a learned skill from the current conversation
Resolve git merge, rebase, and cherry-pick conflicts interactively. Use this skill whenever the user mentions merge conflicts, conflict markers, failed merges, rebase conflicts, or asks to resolve conflicts in their repository. Also trigger when the user says things like "fix my merge", "I have conflicts", "help me rebase", or "resolve the conflicts". Even if they don't say "merge conflict" explicitly, if context suggests they're dealing with conflicting changes in git, use this skill.
Normalize design to match your design system and ensure consistency
Diagnose and fix oh-my-claudecode installation issues
Setup and configure oh-my-claudecode (the ONLY command you need to learn)
Spawn claude, codex, or gemini CLI workers in tmux panes for parallel task execution
Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues that separate good from great.
Design or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly.
Improve interface performance across loading speed, rendering, animations, images, and bundle size. Makes experiences faster and smoother.
Strategic planning with optional interview workflow
Tone down overly bold or visually aggressive designs. Reduces intensity while maintaining design quality and impact.
Automated release workflow for oh-my-claudecode
Orchestrate parallel scientist agents for comprehensive analysis with AUTO mode
Manage local skills - list, add, remove, search, edit, setup wizard
N coordinated agents on shared task list using Claude Code native teams
QA cycling workflow - test, verify, fix, repeat until goal met
Parallel execution engine for high-throughput task completion
Agentic memory system for writers - track characters, relationships, scenes, and themes
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
Multi-AI validation, scoring, and review using Codex and Gemini CLIs (Double Diamond Deliver phase). Use when: AUTOMATICALLY ACTIVATE when user requests validation, scoring, or review:. "review X" or "validate Y" or "test Z". "score this", "quality check", "validate before shipping"
Multi-AI requirements scoping using Codex and Gemini CLIs (Double Diamond Define phase). Use when: AUTOMATICALLY ACTIVATE when user requests clarification or scoping:. "define the requirements for X". "clarify the scope of Y"
Auto-detect work context (Dev vs Knowledge) for workflow tailoring
Multi-AI research using Codex and Gemini CLIs (Double Diamond Discover phase). Use when: AUTOMATICALLY ACTIVATE when user requests research or exploration:. "research X" or "explore Y" or "investigate Z". "what are the options for X" or "what are my choices for Y"
System architecture and API design with multi-AI consensus
OpenClaw instance administration — manage hosts across macOS, Ubuntu/Debian, Docker, OCI, and Proxmox. Use when: AUTOMATICALLY ACTIVATE when user asks about:. "manage openclaw" or "openclaw status" or "openclaw health". "update openclaw" or "upgrade openclaw" or "openclaw doctor"
Present options with trade-offs for informed decision-making. Use when: AUTOMATICALLY ACTIVATE when user requests options or choices:. "fix or provide options" or "fix them or provide me options". "give me options" or "what are my options"
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review. Use when: AUTOMATICALLY ACTIVATE when user requests auditing:. "audit and check the entire app". "audit X for Y" or "check for broken features"
Debug issues methodically — use when stuck on errors, test failures, or unexpected behavior. Use when: AUTOMATICALLY ACTIVATE when encountering bugs or failures:. "fix this bug" or "debug Y" or "troubleshoot X". "why is X failing" or "why isn't X working" or "why doesn't X work"
Extract patterns and anatomy from URLs — use to reverse-engineer content strategies from live pages. Use when: Use PROACTIVELY when user wants to:. "analyze this article", "analyze this content". "deconstruct this content", "break down this post"
Trace codepaths in diffs, map against tests, auto-generate missing coverage. Use when: AUTOMATICALLY ACTIVATE when user requests coverage analysis:. "check test coverage" or "coverage audit". "what's not tested" or "find untested code"
Structured four-way AI debates between Claude, Sonnet, Gemini, and Codex. Use when: AUTOMATICALLY ACTIVATE when user says:. "/debate <question>". "run a debate about X"
Generate slide decks from briefs with optional multi-AI research. Use when: AUTOMATICALLY ACTIVATE when user requests:. "create a deck", "build slides", "make a presentation". "generate a pitch deck", "create board presentation"
Convert markdown to DOCX, PPTX, XLSX office documents. Use when: AUTOMATICALLY ACTIVATE when user requests:. Export knowledge work to office formats (e.g., "export to Word", "create PowerPoint", "convert to DOCX"). Generate professional documents from research (e.g., "create presentation from this synthesis")
Persist design documents with branch tracking, revision chains, and cross-session discovery. Use when: AUTOMATICALLY ACTIVATE when user says:. "save design" or "save this design". "design document" or "create a design doc"
GitHub Copilot CLI as optional zero-cost provider via copilot -p programmatic mode. Use when: AUTOMATICALLY ACTIVATE when user says:. "copilot provider" or "add copilot" or "github copilot" or "use copilot"
Post-ship doc sync across project markdown. Use when: "sync docs", "update docs", "document changes", "release notes".
Environment diagnostics — check providers, auth, config, hooks, scheduler, and more. Use when: AUTOMATICALLY ACTIVATE when user asks about:. "doctor" or "run doctor" or "diagnostics". "check my setup" or "is everything working"
Reverse-engineer design systems, tokens, and components from live products or screenshots (beta — token extraction, component analysis, and URL modes are in progress)
Wrap up a branch — run tests, create PR, merge or discard — use when implementation is done. Use when: AUTOMATICALLY ACTIVATE when user requests task completion with git operations:. "commit and push" or "git commit and push". "complete all tasks and commit and push"
Lock in user goals upfront and validate outputs against them — use to prevent scope drift
Pick up where you left off from a previous session — use after context resets, compaction, or new conversations. Use when: AUTOMATICALLY ACTIVATE when user mentions:. "resume" or "continue" or "pick up where I left off". "what was I doing" or "restore session"
Track project blockers, bugs, and gaps across sessions — use when issues pile up or need triage. Use when: AUTOMATICALLY ACTIVATE when user mentions:. "issue" or "issues" or "problem". "track this" or "remember this blocker"
Run tasks in a loop until goals are met — use for iterative refinement, polling, or convergence. Use when: AUTOMATICALLY ACTIVATE when user requests iterative execution:. "loop X times" or "loop around N times". "loop around 5 times auditing, enhancing, testing"
Switch to Knowledge Work mode for research and writing — use when task is non-code focused
AI-optimized PRD creation with 100-point scoring framework
Roll back to a previous checkpoint via git — use when a change went wrong and you need to revert. Use when: AUTOMATICALLY ACTIVATE when user mentions:. "rollback" or "revert" or "undo". "go back to" or "restore checkpoint"
URL validation and content wrapping for untrusted sources. Use when: This skill provides SECURITY UTILITIES - it should be referenced by other skills,. not invoked directly by users. Auto-integrate when:. Fetching content from URLs
Review code in two passes: spec compliance then quality — use for thorough PR or feature reviews. Use when: Use when completing a major feature, preparing a PR, or when user says. "staged review", "full review", "review against spec", or "two-stage review".
Show where you are in the workflow and what to do next — use for progress checks and orientation. Use when: AUTOMATICALLY ACTIVATE when user asks about:. "status" or "progress" or "where am I". "what's next" or "next step"
Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress. Use when: AUTOMATICALLY ACTIVATE when user requests task management:. "add to the todo's" or "add this to todos". "resume tasks" or "continue tasks" or "pick up where we left off"
Brainstorm creatively with pattern spotting and paradox hunting — use for ideation and exploration. Use when: Use PROACTIVELY when user wants to:. "brainstorm", "think through this with me". "help me explore ideas", "creative session"
Verify claims with actual evidence before declaring success — use to prevent false completion. Use when: Use when about to claim work is complete, fixed, or passing.. Auto-invoke before: commits, PRs, task completion, moving to next task.. ALWAYS use before expressing satisfaction ("Done!", "Fixed!", "All passing!").
Process screenshot-based UI/UX feedback to fix visual issues. Use when: AUTOMATICALLY ACTIVATE when user provides visual feedback:. "[Image X] The /settings should be Y". "[Image X] these button styles need to be fixed"
Zero-context implementation plans with bite-sized tasks. Use when: Use when you have a spec or requirements for a multi-step task.. Auto-invoke when user says "plan how to implement X", "create implementation plan", . "break down this feature into tasks".
Configure Claude Octopus providers and preferences. Use when: Use this skill when the user wants to "configure Claude Octopus", "setup octopus",. "configure providers", "set up API keys for octopus", or mentions octopus configuration.
Craft better prompts using proven optimization techniques — use when your prompt needs refinement. Use when: Use PROACTIVELY when user wants to:. "create a prompt for", "write a prompt for". "optimize this prompt", "improve this prompt"
Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.
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.
NLSpec authoring — structured specification from multi-AI research
Claude-Codex-Gemini tri-model orchestration via /ask codex + /ask gemini, then Claude synthesizes results
Build features with tests-before-code rigor — use for new features needing test coverage. Use when: Use when implementing any feature, bugfix, or behavior change.. Auto-invoke when user says "implement X", "add feature Y", "fix bug Z".
Multi-tentacled orchestration using Double Diamond methodology. Use when: PRIORITY TRIGGERS (always invoke immediately):. "/octo:multi" (explicit command). "run this with all providers", "run with all providers"
Unified setup entrypoint for install, diagnostics, and MCP configuration
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. Generates creative, polished code that avoids generic AI aesthetics.
Adapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.
Quick execution for ad-hoc tasks without workflow overhead. Use when: Use this skill when user says "quick fix", "ad-hoc task", or explicitly. requests fast execution without full workflow overhead.
Use this skill when implementing a Figma design as code (design → code) — the read-FROM-Figma direction. Triggers: 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'code this up from Figma', 'design to code', or a figma.com design URL provided alongside a codebase. Encodes the workflow for reading a node out of Figma with get_design_context and adapting its reference output to the target project — reusing existing components, tokens, and conventions, and honoring Code Connect mappings, component docs, design annotations, and design tokens by priority. Complements figma-code-connect (component mapping) and figma-generate-design / figma-use (the reverse, code → design direction).
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, modal, dialog, drawer, sidebar, panel, or any composed multi-section view in Figma from code or a description. Discovers design system components, variables, and styles from Code Connect files, existing screens, and library search, then imports them and assembles views incrementally section-by-section using design system tokens instead of hardcoded values.
DEFAULT PIPELINE for all tasks requiring execution. You (Claude) are the strategic orchestrator. Codex agents are your implementation army - hyper-focused coding specialists. Trigger on ANY task involving code, file modifications, codebase research, multi-step work, or implementation. This is NOT optional - Codex agents are the default for all execution work. Only skip if the user explicitly asks you to do something yourself.
Generate a FigJam project plan board from a PRD plus codebase context. Interactive flow: research → propose sections → per-section deep research → per-section content + block-shape proposal → create FigJam → skeleton → fill → diagrams → wrap. Each content block (section, nested section, intro callout, table, multi-column text, sticky column, diagram section, metadata strip) has its own subskill reference file. Use when the user asks for 'project plan in FigJam', 'interactive project plan', '/generate-project-plan', or provides a PRD and wants per-section confirmation on content + rendering.
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `create_new_file` tool call. NEVER call `create_new_file` directly without loading this skill first. Trigger whenever the user wants a new blank Figma file — a new design, FigJam, or Slides file — or when you need a fresh file before calling `use_figma`. Usage — /figma-create-new-file [editorType] [fileName] (e.g. /figma-create-new-file figjam My Whiteboard, /figma-create-new-file slides Q3 Review)
Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files.
Translates Figma motion and animations into production-ready application code. Use when implementing animation/motion from a Figma design — user mentions "implement this motion", "add animation from Figma", "animate this component", provides a Figma URL whose node is animated, or when `get_design_context` returns motion data or instructs you to call `get_motion_context`.
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, create individual components with proper variant sets and variable bindings, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. Also use when the user asks to create or generate any component in Figma — even a single one — since components require proper variable foundations, variant states, and design token bindings to be production-quality. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.
This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.
This skill should be used when the user asks to analyze a UI screen recording and map interaction states into Figma. Trigger for requests such as "put video frames in Figma", "extract states from my recording", "map interactions from video to Figma", "analyze this screen recording", "create a storyboard from my video", "deconstruct this interaction in Figma", "annotate the UI states in my recording", or "pull the key moments from this video into Figma". Also trigger when the user references a video file (.mp4, .mov, .webm, .avi) together with Figma, design review, interaction analysis, prototypes, or UI states. The skill extracts key visual moments from a video, infers interaction triggers, and builds an annotated Figma Design storyboard using native Figma annotations and uploaded screenshot assets.