设计与三维建模

Analytics & signals backend harness with a Designer/Builder/Evaluator loop. Derives new metrics from the question they answer, builds the instrumentation + harvester + transform, and adversarially verifies the signal is correct AND answers the question before wiring it to a consumer. Use for /oc-signal, "new metric", "instrument this", "analytics backend", "data harvesting", "is this metric right", "wire up a signal", "derive a KPI". Hands the validated signal (stable read contract) to oc-dash-forge for rendering. NOT pipeline telemetry (oc-telemetry-ops), NOT dashboards (oc-dash-forge), NOT prod uptime (oc-monitoring-ops), NOT estate-level data pipelines — ingestion/dbt/warehouse layering is oc-data-ops; when a metric needs a pipeline that doesn't exist, chain to /oc-data-ops design and build the signal on the contracted mart.

Analytics & signals backend harness with a Designer/Builder/Evaluator loop. Derives new metrics from the question they answer, builds the instrumentation + harvester + transform, and adversarially verifies the signal is correct AND answers the question before wiring it to a consumer. Use for /oc-signal, "new metric", "instrument this", "analytics backend", "data harvesting", "is this metric right", "wire up a signal", "derive a KPI". Hands the validated signal (stable read contract) to oc-dash-forge for rendering. NOT pipeline telemetry (oc-telemetry-ops), NOT dashboards (oc-dash-forge), NOT prod uptime (oc-monitoring-ops), NOT estate-level data pipelines — ingestion/dbt/warehouse layering is oc-data-ops; when a metric needs a pipeline that doesn't exist, chain to /oc-data-ops design and build the signal on the contracted mart.

Analytics & signals backend harness with a Designer/Builder/Evaluator loop. Derives new metrics from the question they answer, builds the instrumentation + harvester + transform, and adversarially verifies the signal is correct AND answers the question before wiring it to a consumer. Use for /oc-signal, "new metric", "instrument this", "analytics backend", "data harvesting", "is this metric right", "wire up a signal", "derive a KPI". Hands the validated signal (stable read contract) to oc-dash-forge for rendering. NOT pipeline telemetry (oc-telemetry-ops), NOT dashboards (oc-dash-forge), NOT prod uptime (oc-monitoring-ops), NOT estate-level data pipelines — ingestion/dbt/warehouse layering is oc-data-ops; when a metric needs a pipeline that doesn't exist, chain to /oc-data-ops design and build the signal on the contracted mart.

Analytics & signals backend harness with a Designer/Builder/Evaluator loop. Derives new metrics from the question they answer, builds the instrumentation + harvester + transform, and adversarially verifies the signal is correct AND answers the question before wiring it to a consumer. Use for /oc-signal, "new metric", "instrument this", "analytics backend", "data harvesting", "is this metric right", "wire up a signal", "derive a KPI". Hands the validated signal (stable read contract) to oc-dash-forge for rendering. NOT pipeline telemetry (oc-telemetry-ops), NOT dashboards (oc-dash-forge), NOT prod uptime (oc-monitoring-ops), NOT estate-level data pipelines — ingestion/dbt/warehouse layering is oc-data-ops; when a metric needs a pipeline that doesn't exist, chain to /oc-data-ops design and build the signal on the contracted mart.

UI/UX design harness with Design Planner/Generator/Evaluator loop. Use for /oc-uxe, "review the UX", "design iteration", "component library", "accessibility audit", "is the UI consistent", or any design quality question. Routes data-heavy screens (dashboards, BI, analytics) to oc-dash-forge via /oc-uxe dash.

UI/UX design harness with Design Planner/Generator/Evaluator loop. Use for /oc-uxe, "review the UX", "design iteration", "component library", "accessibility audit", "is the UI consistent", or any design quality question. Routes data-heavy screens (dashboards, BI, analytics) to oc-dash-forge via /oc-uxe dash.

UI/UX design harness with Design Planner/Generator/Evaluator loop. Use for /oc-uxe, "review the UX", "design iteration", "component library", "accessibility audit", "is the UI consistent", or any design quality question. Routes data-heavy screens (dashboards, BI, analytics) to oc-dash-forge via /oc-uxe dash.

UI/UX design harness with Design Planner/Generator/Evaluator loop. Use for /oc-uxe, "review the UX", "design iteration", "component library", "accessibility audit", "is the UI consistent", or any design quality question. Routes data-heavy screens (dashboards, BI, analytics) to oc-dash-forge via /oc-uxe dash.

Generates 1200x630 OG social preview images (PNG/SVG). Tools: generate_og_image, get_quota.

Design, author, evaluate, and package a reusable Microsoft Copilot Studio agent skill. Use when a task-specific capability must be created or shared across Copilot Studio agents powered by the GitHub Copilot harness. Do not use for Cowork packages, SharePoint site skills, GitHub repository skills, agent identity, knowledge-source design, or tool/connector implementation alone.

Design, author, evaluate, and package a task-focused Microsoft Copilot Cowork skill. Use when converting a recurring personal Microsoft 365 workflow into a Cowork SKILL.md or M365 app-package skill. Do not use for SharePoint site skills, Copilot Studio agent skills, GitHub Copilot repository skills, or connector development alone.

Design, author, audit, and canon-seal portable Glee-fully Agent Skills across the Trunk, Branch, Twig, Function, and Function-ette hierarchy. Use when converting a Glee-fully Tool or Tool-ette into SKILL.md, selecting Persona Density, defining a Twig's Best for boundary, or reviewing a skill for scope, sibling, logic, and release readiness.

Guide a consented still-photo session through verified camera or desktop tools with readiness cues, bounded posing time, stop handling, and saved-file verification. Use for headshot source capture or short posed photo sequences. Distinguishes installed software from usable controls and sequential stills from a true burst. Does not authorize video, device installation, or photo editing.

Foundation skill for ALL Mermaid diagram work. Load this first for any task involving Mermaid syntax, diagrams, flowcharts, process maps, architecture sketches, or visualizing relationships/workflows/structures. Handles audience declaration, diagram type selection across all 27 current Mermaid types (stable and beta), the OKHP3 design system, file naming and the diagram registry, and the three-gate validation framework. Routes to okhp3-mermaid-bpmn, okhp3-mermaid-architecture, or okhp3-mermaid-data for domain-specific vocabulary, and to okhp3-mermaid-publish for rendering/output.

Design and operationalize outcome models that compress noisy event histories into calibrated forecasts and constrained decisions. Use when a user asks about feature reduction, probability, expected value, aggregation, or moving a prediction method between sports, business, sales, advertising, finance, or prediction markets. Load a domain adapter when one fits.

Design and operationalize outcome models that compress noisy event histories into calibrated forecasts and constrained decisions. Use when a user asks about feature reduction, probability, expected value, aggregation, or moving a prediction method between sports, business, sales, advertising, finance, or prediction markets. Load a domain adapter when one fits.

Identify deviations, gaps, and exception paths between an as-is process capture and its intended design. Use this skill when the user wants to find where a process breaks down, where steps are missing or inconsistent, where exception handling is undefined, or where current execution differs from documented procedure. Use when they say "what's wrong with the current process", "find the gaps", "where does this break", or "analyze exceptions". Produces a gap analysis report and exception catalog.

Identify deviations, gaps, and exception paths between an as-is process capture and its intended design. Use this skill when the user wants to find where a process breaks down, where steps are missing or inconsistent, where exception handling is undefined, or where current execution differs from documented procedure. Use when they say \"what's wrong with the current process\", \"find the gaps\", \"where does this break\", or \"analyze exceptions\". Records gaps only — it does not propose solutions or redesign; for that, hand off to okhp3-future-state-change-strategy. Produces a gap analysis report and exception catalog.

Create or refine a realistic professional headshot from supplied or explicitly authorized recent photos. Use for LinkedIn portraits, authentic clothing and background choices, likeness-preserving revisions, or expression references. Produces a reviewable image and source/delivery record. Profile uploads, account changes, broad photo searches, and live camera capture require separately scoped instructions.

Design a secure modernization target for a reclaimed web application, including architecture, data, identity, integrations, observability, and deployment decisions. Do not turn a proposal into implementation prematurely.

Draft a Reddit text, link, image, or media submission for a supplied community. Use when the user needs a community-aware Reddit post that respects supplied rules, post form, title requirements, and flair context. It prepares a draft only and does not submit, vote, join communities, message moderators, apply flair, or manipulate engagement.

The complete Replit design iteration loop as a single coherent workflow — extract → sandbox → variant → graduate. Use when redesigning, improving, or creating variants of any UI component or page. Covers the "extract first, never approximate" rule, DESIGN subagent brief anatomy, variant labelling conventions on canvas, and the graduation decision gate. Activate for "redesign", "improve this component", "show me options", "create variants", "put on canvas", "graduate this mockup", "design alternatives", or any request that implies iterating on UI — whether the component exists already or is being built from scratch.

The complete Replit design iteration loop as a single coherent workflow — extract → sandbox → variant → graduate. Use when redesigning, improving, or creating variants of any UI component or page. Covers the "extract first, never approximate" rule, DESIGN subagent brief anatomy, variant labelling conventions on canvas, and the graduation decision gate. Activate for "redesign", "improve this component", "show me options", "create variants", "put on canvas", "graduate this mockup", "design alternatives", or any request that implies iterating on UI — whether the component exists already or is being built from scratch.

OverKill Hill P³ SharePoint List database architecture reviewer. Use when designing, reviewing, or hardening SharePoint Online Lists used as lightweight databases, controlled vocabularies, lookup-backed registries, or CMDB-lite data stores. Also activate when the user asks about list thresholds, indexed columns, lookup relationships, required fields, content types, attachments, offline sync, Quick Edit, SharePoint UI-only build constraints, or whether a SharePoint list setting is safe for database-like use. This is the authoritative SharePoint-list-as-database architecture skill for this repo -- use it even when the user only says "SharePoint list settings" or "list build".

Review a SharePoint List schema, views, indexes, and visible configuration against supplied design rules. Use when a list owner needs a prioritized health report before changing fields, views, or settings. Do not use to alter a list or claim settings that the current host cannot inspect.

Design, author, evaluate, and deploy-plan a personal or site Copilot in SharePoint skill. Use when creating a task-focused SharePoint Library or List SKILL.md. Do not use for Cowork, Copilot Studio, GitHub Copilot, external-system, or custom-code workflows.

Reconstruct a successful one-off and design tests for a repeatable success class. Use for "bottle lightning", "it worked once but we lost the recipe", or separating essential conditions from incidental details. Produce an evidence ledger and a proposed re-strike protocol, not proven causality, an exact replay guarantee, or autonomous experiments.

Draft a TikTok video or photo post caption and publishing handoff from supplied material. Use when the user needs post text, on-screen-text notes, and a review checklist for a named TikTok post. It prepares a draft only and does not record, edit, upload, set privacy, schedule, or publish.

Draft a YouTube comment or reply from supplied video and conversation context. Use when the user wants to respond to a viewer, answer feedback, add a correction, or join a discussion below a video or channel post. It returns draft text only and does not reply, heart, pin, hide, or moderate comments.

Draft a YouTube channel post or participant Community post from supplied destination context. Use for text, image, video, poll, or quiz posts that need a platform-native prompt and audience boundary. It prepares a draft only and does not test eligibility, schedule, or publish.

Draft a YouTube video publishing brief and metadata bundle from supplied video facts. Use when the user needs a title, description, chapters, CTA, or disclosure and setting handoff for a YouTube video or Short. It prepares text only and does not upload, edit, schedule, or publish a video.

Video, audio, and image processing for AI agents: convert, transcribe, upscale - 150+ operations.

Turn Claude into a creative studio: DNA-locked characters, images, video, voiceover — 55 tools.

Claude Code / MCP skills for the dev pipeline: discover, spec, design, build, ship, operate.

Omni Flash and Veo video, Nano Banana images on Google Flow, from any MCP client

Design systems and the pages built on them, one question at a time. Use for tokens, DESIGN.md, a landing page, an app or a redesign ("make it look professional"), a style direction, a taste poll.

Design systems and the pages built on them, one question at a time. Use for tokens, DESIGN.md, a landing page, an app or a redesign ("make it look professional"), a style direction, a taste poll.

Design systems and the pages built on them, one question at a time. Use for tokens, DESIGN.md, a landing page, an app or a redesign ("make it look professional"), a style direction, a taste poll.

Exports an OpenDesigner system to CSS variables, Tailwind, DTCG, Swift, Compose, Figma or Paper, and writes it into Figma or Paper when connected. Use for "export tokens" or "put it in Figma".

Exports an OpenDesigner system to CSS variables, Tailwind, DTCG, Swift, Compose, Figma or Paper, and writes it into Figma or Paper when connected. Use for "export tokens" or "put it in Figma".

Exports an OpenDesigner system to CSS variables, Tailwind, DTCG, Swift, Compose, Figma or Paper, and writes it into Figma or Paper when connected. Use for "export tokens" or "put it in Figma".

Changes an existing OpenDesigner system (an opendesigner/ folder), such as a new colour, rounder corners, dark mode or a component. Reads DESIGN.md, decisions and locks first, asks only what is new.

Changes an existing OpenDesigner system (an opendesigner/ folder), such as a new colour, rounder corners, dark mode or a component. Reads DESIGN.md, decisions and locks first, asks only what is new.

Changes an existing OpenDesigner system (an opendesigner/ folder), such as a new colour, rounder corners, dark mode or a component. Reads DESIGN.md, decisions and locks first, asks only what is new.

Learns a look from a website, screenshot, Figma file, repo CSS or brand book. Measures it, maps it to dials, or writes a taste index. Copies structure and quality, never a brand's identity.

Learns a look from a website, screenshot, Figma file, repo CSS or brand book. Measures it, maps it to dials, or writes a taste index. Copies structure and quality, never a brand's identity.

Learns a look from a website, screenshot, Figma file, repo CSS or brand book. Measures it, maps it to dials, or writes a taste index. Copies structure and quality, never a brand's identity.

A launch checklist for anything visual (page, video, deck, share image, UI) that catches the silly mistakes that look cheap or wrong. Use before any render, export, deploy, post or publish.

A launch checklist for anything visual (page, video, deck, share image, UI) that catches the silly mistakes that look cheap or wrong. Use before any render, export, deploy, post or publish.

A launch checklist for anything visual (page, video, deck, share image, UI) that catches the silly mistakes that look cheap or wrong. Use before any render, export, deploy, post or publish.