设计与三维建模

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

使用 memegen.link API 生成梗图。当用户请求梗图、想为内容增添幽默，或需要用于社交媒体的视觉素材时使用。支持 100 多个热门模板，可自定义文字和样式。

Memi is the design layer for agentic AI.

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

在向智能体添加记忆之前，或当记忆存储持续增长时使用（长上下文 vs RAG vs 图 vs 智能体记忆，哪些内容应过期）。用 memory_cost_profiler.py 评估设计成本，并通过 forgetting_policy_linter.py 拒绝没有遗忘策略的设计。

使用 Mermaid 语法创建软件图的综合指南。适用于通过图示创建、可视化或记录软件，包括类图（领域建模、面向对象设计）、时序图（应用流程、API 交互、代码执行）、流程图（流程、算法、用户旅程）、实体关系图（数据库结构）、C4 架构图（系统上下文、容器、组件）、状态图、Git 图、饼图、甘特图及其他类型。触发请求包括“画图”“可视化”“建模”“梳理地图”“展示流程”，以及解释系统架构、数据库设计、代码结构或用户/应用流程。

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.

定义并设计产品指标仪表盘，包括关键指标、数据源、可视化类型和告警阈值。适用于创建指标仪表盘、定义 KPI、搭建产品分析或制定数据监控计划。

面向iOS和Android应用的移动优先设计思维与决策。涵盖触摸交互、性能模式、平台惯例。传授原则而非固定数值。适用于构建React Native、Flutter或原生移动应用时。

移动游戏开发原则。触摸输入、电池、性能、应用商店。

在实现新业务模块或变更其职责时，建立或维护该模块的本地智能体指令、领域上下文链接和接口归属。复用项目级规则和现有 ECC 工作流；普通缺陷修复、样式调整和只读设计讨论不启动模块文档设置。

在实现新业务模块或变更其职责时，建立或维护该模块的本地智能体指令、领域上下文链接和接口归属。复用项目级规则和现有 ECC 工作流；普通缺陷修复、样式调整和只读设计讨论不启动模块文档设置。

在实现新业务模块或变更其职责时，建立或维护该模块的本地智能体指令、领域上下文链接和接口归属。复用项目级规则和现有 ECC 工作流；普通缺陷修复、样式调整和只读设计讨论不启动模块文档设置。

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.

Motion Canvas 的完整生产就绪指南，包含 ESM/CommonJS 变通方案、完整设置模板，以及使用 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 组件库模式，包括 sx 属性样式、主题集成、响应式设计和 MUI 专用钩子。适用于 MUI 组件、使用 sx 属性设置样式、主题定制或 MUI 实用工具。

多人游戏开发原则：架构、网络和同步。

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)

为智能体手工打造的 UI 组件和设计系统，使构建成果不像 AI 粗制滥造之物。

分布式NoSQL数据库（Cassandra、DynamoDB）的专业指导。侧重于心智模型、查询优先建模、单表设计，以及在高规模系统中避免热分区。

免费网站检查：以每种设计重建预览、AI-readiness 测试、固定价格。

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.