Design & 3D modeling

Image toolkit: resize, compress, crop, watermark, convert, rotate, EXIF read/strip.

Checks a TLA+ model of something that moves between states (a checkout, an upload, a protocol, a job with retries) with the TLC model checker and draws it as a Mermaid statechart in the reader's words, marking each state that breaks a rule and the shortest path to it. Use when asked to 'draw the states', 'chart how this flow works', 'statechart', 'can this ever happen', 'check this flow keeps the rule', 'model the lifecycle', or to show a bug about order, duplicates, retries or late events as a path through states. Declines work with no states, such as a pure function. Not for architecture or sequence diagrams (vd:archify, vd:diagram-design).

Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern

Convert frontend code (Vite, React, Angular, Vue, etc.) to a Stitch Design by chaining static HTML extraction, design system extraction, and file upload. **ALWAYS** use this skill when the user's intent is to move existing web apps or React/Angular/Vue components into Stitch (e.g., requests to "save", "migrate", or "upload"). You must use this skill even for simple "save" operations, as it is the only way to ensure the design system is extracted and assets are properly linked.

Extract a comprehensive design system (DESIGN.md) directly from frontend source code — React, Vue, Svelte, Angular, plain HTML/CSS, or any web framework. Analyzes component files, stylesheets, Tailwind configs, theme definitions, and design tokens to produce a rich, Stitch-compatible design system document. Use this skill whenever the user wants to reverse-engineer a design system from an existing codebase, audit the visual language of a project, extract design tokens from source files, or understand the styling patterns in a frontend repo — even if they just say "what does this app look like?" or "pull out the design from this code."

Extract self-contained static HTML from a built web application or React components by inlining CSS and images. Use this skill whenever you need to capture a specific UI state, share a static version of a page, or prepare assets for Stitch upload, even if the user just asks to 'save the HTML' or 'mock the view'.

Generate new screens from text prompts or images, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP. Includes prompt enhancement pipeline, design mappings, professional UI/UX terminology, design tokens and theme system capabilities.

Manage design systems in Stitch using MCP tools. Includes retrieval of assets, creating/updating design systems in Stitch, and applying them to screens.

Upload local assets (images, mockups, extracted HTML, design markdown) to a Stitch project. ALWAYS use this skill when you need to upload visual assets, HTML pages, or design docs to Stitch, particularly when direct MCP tool calls fail or truncate due to base64 token limits.

Design custom T-shirts, preview artwork, personalize team shirts and prepare a checkout link.

The director of Full Production Studio. Takes a raw video idea and runs it through the whole pipeline (idea → script → visual plan → motion → edit → captions → export), picking the right skill at every stage and keeping one project brief in sync. Use when the user wants to make a whole video end-to-end, says "make me a video/reel/short about…", "where do I start", "اعملي فيديو عن…", "عايز أعمل ريل", or is unsure which skill to use.

The director of Full Production Studio. Takes a raw video idea and runs it through the whole pipeline (idea → script → visual plan → motion → edit → captions → export), picking the right skill at every stage and keeping one project brief in sync. Use when the user wants to make a whole video end-to-end, says "make me a video/reel/short about…", "where do I start", "اعملي فيديو عن…", "عايز أعمل ريل", or is unsure which skill to use.

Use when several independent views can change a decision: a multi-domain design, uncertain cause, architecture tradeoff or blocker needing new evidence. Assign distinct evidence angles and let the accountable owner decide. Use direct single-agent work for a clear task and unblock for restoration that needs no additional view.

Thread-safe data persistence in Swift using actors — in-memory cache with file-backed storage, eliminating data races by design. Use when persisting data in Swift and a data race or thread-safety problem needs designing out.

Thread-safe data persistence in Swift using actors — in-memory cache with file-backed storage, eliminating data races by design. Use when persisting data in Swift and a data race or thread-safety problem needs designing out.

Thread-safe data persistence in Swift using actors — in-memory cache with file-backed storage, eliminating data races by design.

Polished system design diagrams (SVG/PNG) from a tiny YAML spec, ~18x fewer tokens than raw SVG.

Design scalable systems: requirements, architecture, data models, trade-offs, and scaling strategies. Use for architecture and interviews.

You MUST use this whenever something is broken, before proposing or making any fix, including quick fixes and when the user is in a hurry: a bug, a failing or red test, a build or CI failure, a crash, a performance problem, unexpected behavior. Finds the root cause in four phases (investigate, compare, test one hypothesis, fix with a failing test first) instead of guessing, and stops after three failed fixes to question the design. Not for writing new features.

Build production-ready design systems with Tailwind CSS, including design tokens, component variants, responsive patterns, and accessibility.

Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.

Use when building flex or grid layouts, positioning elements (absolute/relative/fixed/sticky), managing z-index/inset, or @container queries.

Use when setting font family/size/weight, aligning or wrapping text (balance/pretty), applying text-shadow or decoration, or letter/line spacing.

Find AI design tools, compare catalog records, and inspect stored evidence and limitations.

Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from feature-design-assistant output, (2) resuming interrupted work, (3) batch executing tasks. Triggers on 'start implementation', 'run tasks', 'resume'.

Creative-direction layer for music videos and short-form edits in the angelcore / cloud-trance / hyperpop family — a named-genre aesthetic vocabulary, mood + color + light system, beat-synced editing grammar, and a pipeline chaining ECC's video skills from b-roll generation to distribution. Use when a video must feel intentional rather than merely functional — music videos, fancams, moodboard-driven reels, or giving AI-generated b-roll a coherent visual direction.

Generate new video against a distilled style pack and cut it into a finished piece - plan takes from the reference's cut rhythm, generate on fal, grade with the pack's measured LUT, cut at the measured cadence, weave in existing footage, composite overlay plates, mint 3D props, and verify the result numerically. Use when the user wants to make a video in a captured style, supplement existing footage, or assemble generated clips into a real edit.

Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.

Use for file-driven multimodal image, video, and 3D-asset discovery; taste interviews; distill or apply workflows; style-pack validation; editable EDL/FCPXML export; provenance audits; and offline planning that must fail closed before provider generation.

Define a multi-agent team for ANY task on ANY system as an explicit deployment topology - pick the shape from the task's dominant risk, specify the runtime/communication/trust layers, place model capability by lane, present it as a diagram + table + trust-boundary note + open choices, and deploy ONLY after the user agrees to the proposed shape. Use when the user asks to "define/design/lay out the team", "what topology are we deploying", "how should the agents be arranged", "design the team for <task>", "what formation for <task>", or wants a team expressed as a topology (nodes, edges, models, trust boundaries) rather than spawned ad hoc. Substrate-agnostic - Cotal mesh, harness subagents, Workflow stages, containers, or any orchestration system.

Define a multi-agent team for ANY task on ANY system as an explicit deployment topology - pick the shape from the task's dominant risk, specify the runtime/communication/trust layers, place model capability by lane, present it as a diagram + table + trust-boundary note + open choices, and deploy ONLY after the user agrees to the proposed shape. Use when the user asks to "define/design/lay out the team", "what topology are we deploying", "how should the agents be arranged", "design the team for <task>", "what formation for <task>", or wants a team expressed as a topology (nodes, edges, models, trust boundaries) rather than spawned ad hoc. Substrate-agnostic - Cotal mesh, harness subagents, Workflow stages, containers, or any orchestration system.

Your project's design system for coding agents: tokens, components, contrast checks, guidelines.

実装前に呼ぶ。High/Medium リスク変更のテストオラクル（期待値の根拠）とファルシフィケーション項目を定義する。

Draw reliable, well-aligned text/ASCII architecture diagrams with nested boxes, arrows, and connectors. Use when user asks to draw/create text diagrams, ASCII art diagrams, box diagrams, or architecture diagrams in plain text. For rendered SVG or HTML diagrams, use vd:diagram-design instead.

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

Run a Virtual Think Tank — a structured multi-persona debate — before planning or making architectural/design/strategic decisions. Use this skill whenever the user is about to plan a system, make a technology choice, evaluate trade-offs, decide on an approach, or faces any decision where multiple perspectives would sharpen the outcome. Also trigger when the user says "think tank", "debate this", "perspectives on", "trade-offs", "should I use X or Y", "help me decide", "before we plan", or asks for pros/cons of competing approaches. This skill should run BEFORE any implementation planning begins — it produces a structured analysis that feeds into better plans.

Works out what could go wrong in a system's design before it is built — who would attack it, how, and which defences are worth having. Use this whenever the user is designing a system that handles sensitive data, money, or authentication, asks what the security risks are, mentions threat modeling or STRIDE, or is starting a feature with a meaningful attack surface. This is design-time and systematic; for finding vulnerabilities in code that exists, use security-analysis.

Turn text or an image into an animation-ready 3D model (GLB): generate, rig, animate, retexture.

Free text/image → 3D: generate, rig, avatar-ify, and refine GLB models. No auth, no payment.

Text-to-speech, speech-to-text, audio-to-face lipsync, and motion-capture clips for 3D agents.

Drive a local Blender headlessly: inspect, convert, render and script 3D files.

Extract validated image data URIs from Solana SPL Memos and return them inline to MCP clients.

Image understanding for AI agents — analyze and describe any image via the three.ws pipeline.

Free text/image to 3D for Grok Bot, plus your three.ws agents once signed in. Never spends.

Convert a confirmed design/requirements doc into a persisted markdown task list with per-task status checkboxes, for projects that have no issue tracker (private/local-only repos). Use when a design doc has just been approved and the project has no GitHub issues (e.g. local-only git repos holding sensitive data), instead of to-issues/to-prd.

Aide's skills, the per-project .aide/config keys, how a project's own test/lint/build commands are detected, and where specs are stored. Use when: running a project's test, lint or build command; looking up which Aide skill does what; reading or writing .aide/config; deciding where a spec belongs. Do NOT use for: how to run tests correctly (that is the testing rule), the spec files' own layout (use the spec-structure skill).

Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio/video, extract text from recordings, or label speakers in interviews or meetings.

Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio/video, extract text from recordings, or label speakers in interviews or meetings.

Transform raw podcast transcripts into polished, readable documents. This skill removes filler words, fixes grammar, adds structure, and preserves authentic voice. Use when processing podcast transcripts, interview recordings, video captions, or any spoken content that needs cleanup while maintaining 100% fidelity to meaning.

This skill should be used when working with pre-trained transformer models for natural language processing, computer vision, audio, or multimodal tasks. Use for text generation, classification, question answering, translation, summarization, image classification, object detection, speech recognition, and fine-tuning models on custom datasets.