Design & 3D modeling

Compatibility package: mcp-video now installs Kinocut (formerly mcp-video).

Let Claude listen to audio and watch video: transcribe, summarize and edit recordings and links.

AI-Ready design system MCP: melta UI tokens, component contracts, 107 rules, check_html self-verify

Generate memes using the memegen.link API. Use when users request memes, want to add humor to content, or need visual aids for social media. Supports 100+ popular templates with custom text and styling.

Memi is the design layer for agentic AI.

Memi is the read-only design engineering audit and skill layer for coding agents.

Use before adding memory to an agent or when a memory store keeps growing (long context vs RAG vs graph vs agentic memory, what to expire). Prices the design with memory_cost_profiler.py and refuses one without a forgetting policy via forgetting_policy_linter.py.

Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.

Create high-converting Meta (Facebook/Instagram) ad creative using the 6 Elements framework, proven ad formats, and research-driven copywriting. Optimized for lo-fi, native-feeling ads that don't look like ads.

Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan.

Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.

Mobile game development principles. Touch input, battery, performance, app stores.

Establish or maintain a business module's local agent instructions, domain-context links, and interface ownership when implementing a new module or changing its responsibilities. Reuse project-level rules and existing ECC workflows; ordinary bug fixes, styling, and read-only design discussions do not start module documentation setup.

Establish or maintain a business module's local agent instructions, domain-context links, and interface ownership when implementing a new module or changing its responsibilities. Reuse project-level rules and existing ECC workflows; ordinary bug fixes, styling, and read-only design discussions do not start module documentation setup.

Establish or maintain a business module's local agent instructions, domain-context links, and interface ownership when implementing a new module or changing its responsibilities. Reuse project-level rules and existing ECC workflows; ordinary bug fixes, styling, and read-only design discussions do not start module documentation setup.

AI video editing for Uzbek creators: reels, lessons, podcast clips, captions.

When interface motion earns its place and how it is built: the frequency and purpose gate, the cheapest tool, properties, easing, duration and springs as starting recipes, interruption and reduced motion. Pull before adding, changing or reviewing an animation or a transition.

Complete production-ready guide for Motion Canvas with ESM/CommonJS workarounds, full setup templates, and troubleshooting for programmatic video creation using TypeScript

Taste rules for Remotion motion graphics — timing, easing, springs, typography, color, texture, and scene continuity, with concrete numbers. Use whenever you create, animate, retime, or polish a video, composition, scene, or transition in this repo.

Code-only motion design pipeline (no After Effects) for Raphaël / Howseen: launch films, showreels, product promos, LinkedIn/X videos, meme clips. Use when asked to make a motion design video, a promo/launch film, a showreel, "remake this video", a video from a prompt (e.g. "make a 15s motion graphics video…"), to change a video's music/SFX, or to prepare memes for posts. Covers the brief → beat map → stills → seek(t) HTML engine → Playwright render → ffmpeg → music/SFX → QA flow, plus asset sourcing (Mixkit, Pexels, Unsplash, svgl, 21st.dev) and every gotcha hit so far.

The studio's Motion Designer. Owns stage 4 (motion graphics) for the studio-director, taking a Motion Brief and delivering a finished motion package (look, storyboard, animated titles, lower thirds, kinetic text, transitions, renders with alpha) plus a handoff report back to the director. Picks and runs the right motion skills (motion-design, remotion-motion-graphics, remotion-graphics, motion-design-html, arabic-motion-typography, web-sims, sound-design, review-loop). Use when the director reaches the motion stage, or when the user asks for motion graphics, an animated intro/outro, a logo reveal, kinetic typography, lower thirds, animated captions or explainer animation, or says "موشن جرافيك", "انيميشن للنص", "انترو متحرك", "عايز موشن للفيديو".

The studio's Motion Designer. Owns stage 4 (motion graphics) for the studio-director, taking a Motion Brief and delivering a finished motion package (look, storyboard, animated titles, lower thirds, kinetic text, transitions, renders with alpha) plus a handoff report back to the director. Picks and runs the right motion skills (motion-design, remotion-motion-graphics, remotion-graphics, motion-design-html, arabic-motion-typography, web-sims, sound-design, review-loop). Use when the director reaches the motion stage, or when the user asks for motion graphics, an animated intro/outro, a logo reveal, kinetic typography, lower thirds, animated captions or explainer animation, or says "موشن جرافيك", "انيميشن للنص", "انترو متحرك", "عايز موشن للفيديو".

Use when starting or resuming any motion film (launch video, product promo, social ad, README GIF, social loop) — locks the six-block brief (inputs, direction, structure, build, gotchas, start = G0; genre ad|demo), builds the dense beat map (a gesture every 0.5-1 s, ≤ 0.75 s gesture-free, CTA still ≤ 1.2 s), routes the G0 art-direction board, and runs the staged pipeline (one still per beat) with its owner gates.

Use when turning a locked brief and beat map into a film file — deterministic seek(t) scene split into classic scripts (springs, springSum, stagger, density validator, actor, CSS 3D, cursor interaction, pinned lit three.js), zero-dependency Chrome capture, staged render (stills one per beat → draft → master with subframe motion blur, stills by default), ffmpeg mp4 + GIF, VHS terminal films, audio on a measured beat grid, and verification of the delivered file.

Material-UI v7 component library patterns including sx prop styling, theme integration, responsive design, and MUI-specific hooks. Use when working with MUI components, styling with sx prop, theme customization, or MUI utilities.

Multiplayer game development principles. Architecture, networking, synchronization.

Fit a music track to a video and lay it under the video, such as a launch film, a product demo, an ad, a reel or a Remotion or HyperFrames composition. Makes the track exactly as long as the cut by cutting or looping whole bars, lands its drop on a chosen second, ends it with a fade that resolves on a beat, ducks it under a voice-over, sets its loudness, writes every beat and bar as frame numbers, and with the video given writes the video with the track under it. Use it whenever a track (from a music model, a library or the user) has to fit a video's length, has to go under a finished video, or the cuts should land on the beat.

Generate AI images using Nano Banana Pro (Gemini). Use this skill when the user needs images - thumbnails, social posts, blog headers, or creative visuals. Follows an iterative workflow - brainstorm concepts, select direction, generate in multiple styles, then produce via API.

Turn PDFs, Word, EPUB and X posts into narrated audio with word-level timestamps.

Nixamp audio and video player library and playlists (nixamp.com)

Hand-crafted UI components and design systems for agents, so builds don't look like AI slop.

Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems.

Free website check: rebuild preview in every design, AI-readiness test, fixed price.

BJJ video analysis — YOLO pose detection + Claude AI technique analysis.

AI/VFX, CGI, motion & animation production preflight by objekts: locks, continuity, PoCs, estimates.

Claude Agent SDK build harness with a Planner/Builder/Evaluator loop. Owns subagent topology, tool-budget design, harness loop shapes, and agent evaluation. Use for /oc-agent, "Claude Agent SDK", "build an agent", "subagent", "tool budget", "agent loop", "harness", "multi-agent", "agent eval", "orchestrator-worker". Model routing comes from oc-claude-api; agent-forge owns topology + harness shape.

Claude Agent SDK build harness with a Planner/Builder/Evaluator loop. Owns subagent topology, tool-budget design, harness loop shapes, and agent evaluation. Use for /oc-agent, "Claude Agent SDK", "build an agent", "subagent", "tool budget", "agent loop", "harness", "multi-agent", "agent eval", "orchestrator-worker". Model routing comes from oc-claude-api; agent-forge owns topology + harness shape.

Claude Agent SDK build harness with a Planner/Builder/Evaluator loop. Owns subagent topology, tool-budget design, harness loop shapes, and agent evaluation. Use for /oc-agent, "Claude Agent SDK", "build an agent", "subagent", "tool budget", "agent loop", "harness", "multi-agent", "agent eval", "orchestrator-worker". Model routing comes from oc-claude-api; agent-forge owns topology + harness shape.

Claude Agent SDK build harness with a Planner/Builder/Evaluator loop. Owns subagent topology, tool-budget design, harness loop shapes, and agent evaluation. Use for /oc-agent, "Claude Agent SDK", "build an agent", "subagent", "tool budget", "agent loop", "harness", "multi-agent", "agent eval", "orchestrator-worker". Model routing comes from oc-claude-api; agent-forge owns topology + harness shape.

Unified app development: idea → spec → design → build with Generator/Evaluator QA loop → launch. Use for /oc-app, /oc-discover, /oc-spec, /oc-design, /oc-roadmap, /oc-scaffold, /oc-build, /oc-launch, "build me an app", "I have an app idea", or any software project. Chains to (when you invoke it): oc-stack-forge and oc-ux-engineer.

Unified app development: idea → spec → design → build with Generator/Evaluator QA loop → launch. Use for /oc-app, /oc-discover, /oc-spec, /oc-design, /oc-roadmap, /oc-scaffold, /oc-build, /oc-launch, "build me an app", "I have an app idea", or any software project. Chains to (when you invoke it): oc-stack-forge and oc-ux-engineer.

Unified app development: idea → spec → design → build with Generator/Evaluator QA loop → launch. Use for /oc-app, /oc-discover, /oc-spec, /oc-design, /oc-roadmap, /oc-scaffold, /oc-build, /oc-launch, "build me an app", "I have an app idea", or any software project. Chains to (when you invoke it): oc-stack-forge and oc-ux-engineer.

Unified app development: idea → spec → design → build with Generator/Evaluator QA loop → launch. Use for /oc-app, /oc-discover, /oc-spec, /oc-design, /oc-roadmap, /oc-scaffold, /oc-build, /oc-launch, "build me an app", "I have an app idea", or any software project. Chains to (when you invoke it): oc-stack-forge and oc-ux-engineer.

Data-pipeline harness with a Designer/Builder/Contract-Verifier loop. Owns the data estate: ingestion patterns (batch, stream, CDC), transformation layering (staging → intermediate → marts), dbt project design, and observable data contracts with freshness/volume/schema SLAs. Use for /oc-data-ops, "data pipeline", "ingestion", "ELT", "dbt", "data warehouse modeling", "data contract", "warehouse schema drift", "stale data", "data quality checks", "volume anomaly", "sync SaaS data into the warehouse", "medallion architecture", "backfill strategy". Invoked by oc-app-architect Phase 2 when discovery surfaces a data-heavy backend. Warehouse/queue choice comes from oc-stack-forge. NOT single-metric analytics (oc-signal-forge), NOT dashboards (oc-dash-forge), NOT live-pipeline engine swaps (oc-migration-ops), NOT API contract / schema-to-code drift (oc-api-dev), NOT the SaaS connector mechanics (OAuth/webhooks — oc-integrations-engineer builds the connector; this skill owns the pipeline + cont

Data-pipeline harness with a Designer/Builder/Contract-Verifier loop. Owns the data estate: ingestion patterns (batch, stream, CDC), transformation layering (staging → intermediate → marts), dbt project design, and observable data contracts with freshness/volume/schema SLAs. Use for /oc-data-ops, "data pipeline", "ingestion", "ELT", "dbt", "data warehouse modeling", "data contract", "warehouse schema drift", "stale data", "data quality checks", "volume anomaly", "sync SaaS data into the warehouse", "medallion architecture", "backfill strategy". Invoked by oc-app-architect Phase 2 when discovery surfaces a data-heavy backend. Warehouse/queue choice comes from oc-stack-forge. NOT single-metric analytics (oc-signal-forge), NOT dashboards (oc-dash-forge), NOT live-pipeline engine swaps (oc-migration-ops), NOT API contract / schema-to-code drift (oc-api-dev), NOT the SaaS connector mechanics (OAuth/webhooks — oc-integrations-engineer builds the connector; this skill owns the pipeline + cont

Data-pipeline harness with a Designer/Builder/Contract-Verifier loop. Owns the data estate: ingestion patterns (batch, stream, CDC), transformation layering (staging → intermediate → marts), dbt project design, and observable data contracts with freshness/volume/schema SLAs. Use for /oc-data-ops, "data pipeline", "ingestion", "ELT", "dbt", "data warehouse modeling", "data contract", "warehouse schema drift", "stale data", "data quality checks", "volume anomaly", "sync SaaS data into the warehouse", "medallion architecture", "backfill strategy". Invoked by oc-app-architect Phase 2 when discovery surfaces a data-heavy backend. Warehouse/queue choice comes from oc-stack-forge. NOT single-metric analytics (oc-signal-forge), NOT dashboards (oc-dash-forge), NOT live-pipeline engine swaps (oc-migration-ops), NOT API contract / schema-to-code drift (oc-api-dev), NOT the SaaS connector mechanics (OAuth/webhooks — oc-integrations-engineer builds the connector; this skill owns the pipeline + cont

Data-pipeline harness with a Designer/Builder/Contract-Verifier loop. Owns the data estate: ingestion patterns (batch, stream, CDC), transformation layering (staging → intermediate → marts), dbt project design, and observable data contracts with freshness/volume/schema SLAs. Use for /oc-data-ops, "data pipeline", "ingestion", "ELT", "dbt", "data warehouse modeling", "data contract", "warehouse schema drift", "stale data", "data quality checks", "volume anomaly", "sync SaaS data into the warehouse", "medallion architecture", "backfill strategy". Invoked by oc-app-architect Phase 2 when discovery surfaces a data-heavy backend. Warehouse/queue choice comes from oc-stack-forge. NOT single-metric analytics (oc-signal-forge), NOT dashboards (oc-dash-forge), NOT live-pipeline engine swaps (oc-migration-ops), NOT API contract / schema-to-code drift (oc-api-dev), NOT the SaaS connector mechanics (OAuth/webhooks — oc-integrations-engineer builds the connector; this skill owns the pipeline + cont

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.