Design & Media

mohitmishra786 Skill

Design system architecture, select technology stacks, create database schemas, and define API contracts

taewanu Bundle

Turn a photo of a hand-drawn concept diagram (architecture flow, boxes/arrows, coverage brackets, annotations) into a clean, self-contained HTML diagram in a fixed hand-drawn house style. Runs a multi-stage workflow whose critic actually SEES the rendered output (Chrome-headless screenshot) and refines it, so the diagram reads clearly instead of faithfully reproducing a messy sketch. Use when the user photographs a whiteboard/notebook sketch and wants it digitized: "이 손그림 다이어그램 깔끔하게", "스케치 사진 html로", "화이트보드 정리해줘", "그린 거 디지털로", "digitize this sketch", "turn my whiteboard photo into a diagram", "clean up this hand-drawn diagram", "render this sketch as html". For CONCEPT diagrams, not UI wireframes (those go to v0/Figma) and not a correctness audit.

toolbox-playground Bundle

UI/UX and visual design skill. Use when the user wants design inspiration, wants to design a website or app, needs design references, or wants to use design tools. Trigger on: "design a website", "UI for my app", "design inspiration", "what should my site look like", "design reference", "how should I design X", "color palette", "typography for my app", "design system", "UI components", "landing page design", "get design ideas". Also trigger when the user mentions: Figma, v0.dev, getdesign.md, Dribbble, Mobbin, Excalidraw, or any design tool by name. Do NOT trigger for: implementing already-designed UI in code (use software-development skill), generating standalone images (use media-content-creation skill).

olakunlevpn Bundle

OUTPUT IS ALWAYS A SINGLE `.html` FILE (never `.md`, never separate per-slide files) containing multiple slides navigated by arrow keys. Use this skill whenever the user asks for a slide deck, presentation, talk, "Friday demo", "share-out slides", "exec readout", "kickoff deck", "lightning talk", arrow-key deck, keynote-style outline, or any artifact whose primary shape is "a sequence of slides you advance through". Pair with `artifact-css` for the underlying design system. Do NOT use for single-page reports — those are `artifact-report`.

olakunlevpn Bundle

OUTPUT IS ALWAYS A SINGLE `.html` FILE (never `.md`, never separate per-screen files) containing multiple screens navigated by clickable hotspots and/or a hash router. Use this skill whenever the user asks for a clickable prototype, clickable mockup, multi-screen flow, user-flow walkthrough, "click-through demo", "tap-through prototype", interactive wireframe, or any artifact whose primary shape is "a sequence of screens linked by hotspots". Pair with `artifact-css` for the underlying design system. Do NOT use for slide decks (use `artifact-deck`) or for fully-functional editors (use `artifact-editor`).

olakunlevpn Bundle

OUTPUT IS ALWAYS A SINGLE `.html` FILE (never `.md`, never Figma exports) showing design primitives next to their source code. Use this skill whenever the user asks for a design system page, design tokens reference, component variants sheet, "show all the buttons", "all states of the card component", "swatch the palette", living style guide, brand kit, or any artifact whose primary shape is "rendered components paired with their source / spec". Pair with `artifact-css` for the underlying design system. Do NOT use for one-off feature mockups (use `artifact-flow`) or for animation playgrounds (use `artifact-sandbox`).

olakunlevpn Bundle

OUTPUT IS ALWAYS A `.html` FILE (never `.md`, never plain markdown) with working jQuery UI widgets and JavaScript wired up. Use this skill whenever the user asks for an interactive editor, triage board, kanban board, "thing I can drag around", feature flag panel, feature flag dashboard, prompt tuner, prompt playground, parameter panel, "let me adjust X live", "give me a UI to play with this", or any HTML artifact that the user is expected to manipulate (drag, sort, tweak sliders, toggle flags, edit and export). Pair with `artifact-css` for the underlying design system and `jQuery 4.0.0 + jQuery UI 1.14.2` for the interactivity (sortable, draggable, slider, datepicker, dialog, autocomplete widgets). Do NOT use for static dashboards that just display data — only when the user must change something and ideally export the result.

olakunlevpn Bundle

OUTPUT IS ALWAYS A SINGLE `.html` FILE (never `.md`, never plain markdown). Use this skill whenever the user asks for a status update, weekly report, monthly report, status report, engineering update, project update, incident report, post-mortem, retro, retrospective, PR description, or PR writeup that should be delivered as a polished HTML document. Trigger when the user wants to "summarize what shipped this week", "write up the incident", "draft a post-mortem", or any similar recurring written deliverable that benefits from a small chart, a timeline, a colored highlight, or a structured table over a flat markdown summary. Pair with artifact-css for the underlying design system. Do NOT use for casual chat summaries that the user just wants to read in the conversation - only when an HTML artifact is the deliverable.

olakunlevpn Bundle

OUTPUT IS ALWAYS A `.html` FILE (never `.md`, never plain markdown). Use this skill whenever the user asks for a code review writeup, PR review, annotated diff, "review this patch", "give feedback on this change", "leave inline comments on this PR", "summarize what's wrong with this code", or any reviewer-side artifact that pairs concrete diff hunks with human commentary, suggestions, and approve/request-changes verdicts as a polished HTML document. This is the reviewer-side companion to `artifact-report`'s PR writeup (which is author-side). Pair with `artifact-css` for the underlying design system. Do NOT use for casual one-line feedback or for purely conversational review chats — only when an HTML artifact with annotated diffs is the deliverable.

olakunlevpn Bundle

OUTPUT IS ALWAYS A SINGLE `.html` FILE (never `.md`, never separate image files) containing inline SVG diagrams with annotations, legends, and optional hover labels. Use this skill whenever the user asks for a flowchart, system diagram, module map, dependency graph, architecture diagram, sequence diagram, ER diagram, SVG figure sheet, "draw me a diagram of", "map the modules", "visualize the data flow", or any artifact whose primary shape is "boxes and arrows that explain a system". Pair with `artifact-css` for the underlying design system. Do NOT use Mermaid syntax or markdown — render diagrams as native inline SVG.

olakunlevpn Bundle

OUTPUT IS ALWAYS A SINGLE `.html` FILE (never `.md`, never separate CSS/JS files) containing a live, tunable demo of one CSS/JS technique. Use this skill whenever the user asks for an animation playground, animation sandbox, "let me tune the easing", "show me different timings of X", interactive demo of one effect, CSS demo, transition tuner, or any artifact whose primary shape is "one thing animating, with sliders to tune it". Pair with `artifact-css` for the underlying design system and `jQuery 4.0.0 + jQuery UI 1.14.2` for the slider widgets. Do NOT use for full editor UIs (use `artifact-editor`) — sandbox is single-effect focused.

olakunlevpn Bundle

OUTPUT IS ALWAYS A `.html` FILE (never `.md`, never plain markdown) with real jQuery UI interactivity. Use this skill whenever the user asks for an explainer, primer, "how does X work", "explain Y", "TL;DR for Z", concept overview, feature explainer, deep dive, research summary, architecture writeup, or any pedagogical artifact that should be delivered as a polished interactive HTML document with collapsible sections, tabbed code samples, an inline glossary, and a scannable summary block at the top. Pair with `artifact-css` for the underlying design system and `jQuery 4.0.0 + jQuery UI 1.14.2` for the interactivity (accordion, tabs, tooltip widgets). Do NOT use for one-paragraph definitional answers — only when an HTML artifact with progressive disclosure is the deliverable.

ommakes Bundle

Rules and patterns for building UI with shadcn/ui, Tailwind v4 or StyleX, and Motion against a Vois design token set. Use when building components, pages, or any UI that should conform to the workspace design system. Covers spacing, typography, color tokens, component architecture, animation, accessibility, and modern CSS/StyleX patterns.

hanzili Skill

Post content across social platforms from your real signed-in browser. Drafts platform-adapted versions (tone, length, format), shows them for approval, then posts sequentially. Works with LinkedIn, Twitter/X, Reddit, Hacker News, and Product Hunt.

igorescodro Bundle

Use when implementing a new Kuvio component for the Alkaa Design System after design spec and structure decisions are finalized

iker-gonzalez Skill

Use when the user wants to draft, schedule, or publish a social media post through Antwork's MCP connector — single posts or a multi-platform fan-out. Handles voice-aware drafting, the draft→publish/schedule two-step, per-platform character limits, and account health. Trigger on phrases like "post to LinkedIn/X/Threads", "schedule a tweet", "publish this", "draft a post", or any explicit mention of posting through Antwork.

kevin-liu-01 Skill

Generate, parse, and compile a unified DESIGN.md (33 categories, 519 tokens) that compiles to CSS, Tailwind v4, and W3C JSON. Use when creating a new design reference, extracting tokens from an existing site (`sigil design extract`), switching a project's visual identity, generating compiled token output, or auditing a design against the spec. Triggers on "DESIGN.md", "design reference", "compile tokens", "extract design system", "sigil design", or "design.md format".

kevin-liu-01 Bundle

Design engineering principles for making Sigil interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.

liueggy Bundle

Extract design tokens, text styles, and variables from a Figma design system and produce a design-tokens.json plus ready-to-use QML singletons. Use this skill whenever someone wants to pull their design system out of Figma — whether they say "export tokens from Figma", "get design tokens", "set up my design system", "read our Figma design system", "get Figma variables into QML", "pull our color palette from Figma", "import design tokens", "extract colors/typography/spacing from Figma", or similar. Trigger this skill at the start of any design-system workflow that involves a Figma source.

liueggy Skill

Extract component metadata from a Figma design system and generate production-ready QML controls. Use this skill whenever someone wants to turn Figma components into QML files — whether they say "generate components from Figma", "create QML controls based on a design system", "convert Figma components to QML", "build the component library", "extract button/input/checkbox from Figma", or anything similar. Requires design-tokens.json and QML design system singletons to already exist (from the token extraction skill). Uses Figma MCP to inspect components one at a time and maps variants, states, sizing, and token usage to idiomatic Qt Quick Controls 2 patterns. Trigger this skill at the component generation step of any QML design-system workflow.

lizliz404 Bundle

交互式项目流 / logo stream / 无限横向内容流 / hover·长按预览 / rAF。Use when building continuous clickable content streams that need collision-safe transport, static interaction mode, user motion controls, accessible previews, and measured performance.

podman-desktop Skill

Prepare and execute Design System component modernization. Drafts GitHub subtask issues, applies the Storybook HMR patch, and guides the modernization workflow. Use when starting work on a new component modernization, creating subtask issues, or when the user mentions design system modernization.

looties-io Bundle

Cinematic motion design workflow for Hyperframes/Hyperframer and HTML-to-video product films. Use when creating or revising SaaS, app, ecommerce, launch, social, or brand videos that need the /website-to-hyperframes or Website-to-Video pipeline, Hyperframes compositions, catalog-backed blocks/components/transitions, GSAP timelines, VFX-friendly motion, kinetic typography, responsive 16:9/9:16 variants, mock UI states, and export validation.

madteacher Bundle

Create, refine, and review design artifacts in HTML, CSS, SVG, and JavaScript: interfaces, landing pages, wireframes, interactive prototypes, presentations, design variations, tweakable mockups, and design audits. Use when the user asks to design a screen, flow, deck, visual direction, multiple options, extract a design system or component set, or review work for accessibility, hierarchy, interaction states, and generic AI aesthetics.

masscodeio Skill

Use when defining or reviewing massCode UI foundation rules such as typography, renderer styling consistency, TailwindCSS v4 usage, and when raw markup starts competing with established UI text patterns.

mondaycom Skill

Ensures Vibe design system (@vibe/core) components follow best practices and accessibility standards. Use when writing or reviewing UI code in monday.com apps that import from @vibe/core or @vibe/core/next.

nocodemrli Bundle

Design, preview, implement, and assess mini-program interfaces against an approved prototype, screenshot, visual reference, design system, or bounded UI request while preserving product semantics and existing accepted behavior. Use when users ask to reproduce a mini-program screen, refine visual hierarchy, adapt layouts across device sizes, handle safe areas or keyboards, inspect touch targets, scrolling, media, or gesture conflicts, compare an implementation with a reference, or prepare a device-verification matrix. Separates proposed visual previews, user approval, source integration, local checks, and real-device evidence; never invents product functionality for visual completeness or claims device validation without device-specific proof.

pesty-marketing Bundle

Apply Master UI Design + Practical UI frameworks to build or audit interface designs (components, layouts, typography, color, forms, buttons, navigation, copywriting). Invoke when user says "use ui-design," "audit this UI," "review the design," or asks for help building/improving an interface, component, or screen. General-purpose (not Pesty-specific; use the pesty-design skill for that).

senmushare Bundle

Define or review UI/UX direction, systems, layout, typography, color, data visualization, responsive behavior, interaction, motion, accessibility, and visual or interaction prototype validation. Not for product scope, routine implementation, library APIs, or independent audits.

corlab-tech Skill

Launches an autonomous, pixel-perfect UI implementation loop using Figma MCP and Chrome.

corlab-tech Skill

Carbon Design System icon usage for React components. MANDATORY when any component includes an icon. Use when implementing UI components that need icons, building atoms/molecules/organisms with icon elements, or adding icons to buttons, inputs, navigation, or any other UI element. Covers icon imports, sizing, color, alignment, touch targets, and the V-Shield Design System icon labeling system.

corlab-tech Skill

Autonomous pixel-perfect Stencil component implementation using Figma MCP, Storybook, and Playwright MCP for visual testing and fixing.

corlab-tech Bundle

Autonomous pixel-perfect UI implementation loop for Next.js/React using Figma MCP and Playwright. Converts Figma designs to production-ready components with iterative visual validation. **AUTO-TRIGGERS** on ANY request to implement Figma designs including: 'implement this Figma', 'build this page/component from Figma', 'create from Figma design', 'implement design', 'build this block', 'create component from design'. Use for: (1) Building pages/components from Figma, (2) Pixel-perfect accuracy, (3) Responsive layouts, (4) Design token conversion.

corlab-tech Bundle

D3.js data visualization in React/Next.js components with PIXEL-PERFECT Figma matching. Use when building interactive charts, graphs, network diagrams, geographic maps, or any custom data visualization with D3.js inside React components. Covers pixel-perfect Figma extraction workflow, iterative visual validation via Playwright, two integration approaches (useRef+useEffect imperative vs declarative React rendering), responsive sizing, TypeScript typing, SSR/Next.js compatibility, accessibility, and performance. Triggers on: 'create a chart', 'add a D3 visualization', 'build a graph component', 'data visualization', 'interactive chart', 'force-directed graph', 'bar chart', 'line chart', 'heatmap', 'scatter plot', 'pie chart', 'chord diagram'.

corlab-tech Bundle

STRICT pixel-perfect Figma to Storybook workflow with ENFORCED extraction and iterative component implementation. MANDATORY: Extract exact design → Implement → Iterate until perfect → Move to next. NO shortcuts, NO assumptions, NO batch processing. Use when implementing Figma designs as Storybook components with 100% accuracy requirement.

corlab-tech Skill

Import vector illustrations from Figma as reusable React atom components. Use when a component or page needs a custom illustration (NOT a standard Carbon icon). Triggers on requests like 'implement this illustration from Figma', 'add this Figma illustration', 'create illustration component', or when a Figma node contains a multi-layer vector illustration (lock, envelope, microscope, etc.). BEFORE creating a new illustration, always check if it already exists in `apps/web-app/src/components/atoms/Illustration*.tsx` and `apps/web-app/public/assets/illustrations/`.