plugins/cache/omc/oh-my-claudecode/4.8.2/skills/setup/SKILL.md
Unified setup entrypoint for install, diagnostics, and MCP configuration
npx skillsauth add moliboy5000/.claude setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use /oh-my-claudecode:setup as the unified setup/configuration entrypoint.
/oh-my-claudecode:setup # full setup wizard
/oh-my-claudecode:setup doctor # installation diagnostics
/oh-my-claudecode:setup mcp # MCP server configuration
/oh-my-claudecode:setup wizard --local # explicit wizard path
Route by the first argument:
wizard, local, global, or --force -> run /oh-my-claudecode:omc-setup {{ARGUMENTS}}doctor -> run /oh-my-claudecode:omc-doctor {{ARGUMENTS_AFTER_DOCTOR}}mcp -> run /oh-my-claudecode:mcp-setup {{ARGUMENTS_AFTER_MCP}}Examples:
/oh-my-claudecode:omc-setup {{ARGUMENTS}}
/oh-my-claudecode:omc-doctor {{ARGUMENTS_AFTER_DOCTOR}}
/oh-my-claudecode:mcp-setup {{ARGUMENTS_AFTER_MCP}}
/oh-my-claudecode:omc-setup, /oh-my-claudecode:omc-doctor, and /oh-my-claudecode:mcp-setup remain valid compatibility entrypoints./oh-my-claudecode:setup in new documentation and user guidance.Task: {{ARGUMENTS}}
tools
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.).
development
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.
development
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.
development
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.