Design & Media

blencorp Bundle

Builds Department of Veterans Affairs web and native-mobile interfaces with the official VA Design System, web components, React bindings, CSS library, mobile component library, tokens, patterns, and content guidance. Use for VA-governed products.

blencorp Bundle

Builds Louisiana state digital services with the official Pelican Design System, Bootstrap-based package, components, foundations, accessibility guidance, and compiled assets. Use for Louisiana products authorized to adopt Pelican.

blencorp Bundle

Builds accessible CMS digital-service interfaces with the official CMS Design System core CSS, JavaScript, React components, utilities, tokens, and USWDS foundation. Use for CMS products that do not require a documented CMS child system.

blencorp Bundle

Builds National Cancer Institute interfaces with the official NCI Design System Sass, JavaScript, components, templates, CDN bundles, and USWDS foundation. Use for NCI-governed products and respect its registry and compiler constraints; it is not a generic NIH or HHS design system.

blencorp Bundle

Builds SAM.gov Angular interfaces with the official SAM Design System package and documentation. Use for SAM.gov product work whose Angular version and package peer dependencies are compatible; do not use it as a general GSA or federal system.

blencorp Bundle

Builds Utah government interfaces with the official Utah Design System Sass/CSS, React components, required Utah header package, tokens, examples, and documentation. Use for Utah state products and prefer the documented CSS patterns over treating React as the only implementation.

blencorp Bundle

Builds Texas state-agency websites with the official Texas Design System's copy-ready HTML, CSS tokens, JavaScript interactions, templates, and txds-prefixed BEM components. Use for authorized Texas agency sites; version 1.0.0 is a one-time reference delivery, and the adopting agency owns maintenance after handoff.

blencorp Bundle

Routes federal, state, District of Columbia, and U.S. territorial digital-service work to the correct official public design system. Use when selecting a government design system, checking whether a jurisdiction has reusable public implementation, or avoiding unsupported cross-jurisdiction substitutions.

blencorp Bundle

Builds Commonwealth of Pennsylvania interfaces from the official Keystone Design System foundations, tokens, components, code examples, content guidance, and AEM-aware documentation. Use for Pennsylvania products; implement from the published guidance and examples, since no portable package is published.

blencorp Bundle

Builds CMS.gov public-facing interfaces with the official CMS.gov child design system layered on CMS Design System core. Use for CMS.gov-owned products, not every application operated by CMS.

blencorp Bundle

Builds the Virginia Commonwealth Branding Bar and follows VITA web standards for authorized state websites. Use for Virginia state sites; the branding bar is the currently published implementation, with the broader Commonwealth Design System still in progress.

blencorp Bundle

Maintains CDC Data Integration Building Blocks interfaces from the official DIBBs Design System source, Sass configuration, overrides, and example markup. Use only for DIBBs product work or an explicitly approved derivative; no independent package is published.

blencorp Bundle

Builds Login.gov interfaces with the official Identity Design System and its USWDS-compatible Sass, JavaScript, assets, and Login.gov-specific patterns. Use for Login.gov-owned authentication and identity experiences, not generic federal sign-in pages.

blencorp Bundle

Maintains USDA Farm Production and Conservation or Farm Service Agency interfaces with the official FSA Design System documentation, the fsa-style npm package, and its source. Use for those products and check current maintenance, since releases are older than most systems here; do not represent it as current USDA-wide guidance.

blencorp Bundle

Builds Maryland government interfaces with the official Maryland Web Design System package, web components, statewide alerts, foundations, and accessibility guidance. Use for Maryland state services, not the unrelated University of Maryland design system; the current release is alpha-tagged, so pin the exact version.

blencorp Bundle

Builds Medicare.gov interfaces with the official CMS Medicare.gov child design system layered on CMS Design System core. Use only for Medicare.gov products and explicitly governed related experiences.

blencorp Bundle

Builds NASA web modernization interfaces with the official Horizon Design System Core theme layered on USWDS. Use for NASA projects within Horizon's consolidation strategy; the package is pre-1.0, so pin the exact version, and keep Horizon's NASA-brand scope.

blencorp Bundle

Builds Massachusetts digital-service foundations with the current Massachusetts Design System token, asset, and style packages. Use for new Mass.gov work; components are still being released, and Mayflower is not recommended for new work.

blencorp Bundle

Builds HealthCare.gov interfaces with the official CMS child design system and its branded theme layered on CMS Design System core. Use only for HealthCare.gov products and approved closely related experiences.

bxmaximum Skill

Covers Bitrix UI library — main.popup, main.sidepanel, ui.system.dialog, ui.dialogs.messagebox, ui.system.menu, ui.system.input, ui.alerts, ui.notification (toasts), ui.entity-selector (Dialog, TagSelector, providers), main.ui.grid, main.ui.filter, ui.icon-set, ui.lottie, ui.a11y, typography. Applied when building admin interfaces and public UI with kernel components. Key terms — Extension::load, Popup, SidePanel, system-dialog, MessageBox, ui.alerts, entity-selector, grid, filter, ui.a11y, UI kit.

dragoon0x Skill

Scale, weight, line height, and tracking as a coherent system. Use when building type scales, auditing typography consistency, or diagnosing why text feels off.

buildgreatproducts Bundle

Use when the user wants to turn an image reference — a screenshot, mockup, Figma URL, or live website they love — into their Design System. Triggers on phrases like "build my design system", "create my DESIGN.md", "design from image", "image to design system", "translate this screenshot into a design system", "extract design tokens", "make my design.md", "here's a site I love, capture its design", or when the user shares an image/URL in a design context with no other clear intent. Produces two mirrored artifacts: docs/DESIGN.md (Google-format YAML tokens + prose, the source of truth coding agents read) and docs/DESIGN.html (a self-contained live style guide for the human). Reads the image(s), asks only the context questions the ProductOS docs don't already answer, derives the tokens, reconciles them with the Product Identity, and writes both files together. Design phase Step 3 — runs after the UX Writing Guide and supplies the colours, fonts, and tokens the identity leaves undecided.

buildgreatproducts Skill

Use when the user is building or refactoring UI in their product codebase and wants designer-quality frontend code — not just functional code. Triggers on phrases like "design better", "make this UI feel more designed", "elevate the design quality", "build this with design best practices", "follow UX heuristics", "make this feel professional", "apply design polish", "review this for craft", or any request to apply UX/UI craft heuristics to code generation or review. Pairs with `docs/DESIGN.md`: the design system file owns **style** (colors, typography, spacing tokens, components), this skill owns **craft** (hierarchy, interaction, accessibility, motion, polish). Reference DESIGN.md tokens by name for every visual decision; apply the 50-item heuristics catalogue below for every craft decision. When a heuristic implies a token DESIGN.md doesn't have, flag it as a New Pattern for `studio-develop-design-review` to promote — never invent a value inline.

buildgreatproducts Skill

Use when the user has a `docs/DESIGN.md` and uncommitted changes in their product codebase (new components, modified styles, new screens) and wants a design-system adherence review before committing or merging. Triggers on phrases like "design review", "review my design system adherence", "check my changes against DESIGN.md", "design system check", "what design tokens am I missing", or "promote my new patterns to DESIGN.md". Runs in the app repo — the repository that contains `productos/`. Reads `docs/DESIGN.md`, inspects uncommitted git changes (working tree + staged), classifies each visual change as an Inconsistency, a New Pattern, or Already-Aligned, and writes a prioritized, timestamped report to `design-review/` (a new file per run): a fix to-do list, a promotion checklist for `docs/DESIGN.md`, and a paste-ready fix prompt for a coding agent. Optionally references `productos/design/1-Product-Identity.md` for tone if present; works standalone.

buildgreatproducts Skill

Use when the user has a synthesised `docs/PRODUCT.md` (the plain-English roll-up of their Define-phase work) and wants to build their minimum viable brand identity from it. Triggers on phrases like "help me create my product identity", "build my brand identity", "design my brand", "name my product", "what's my brand worldview", "develop my brand voice", "define my visual style", or any request to guide a founder through the five word-level elements (Name, Worldview, Contrarian Belief, Tone of Voice, Visual Style) of a Product Identity. Reads `docs/PRODUCT.md`, does live research on the category's names and visual defaults, walks the user through each element in the voice of a senior brand strategist and design director, and rewrites `productos/design/1-Product-Identity.md` in place — every section ending in a concrete artifact, assembled into a one-glance Brand Card. Colours, fonts, and tokens are deliberately downstream — the Design System step derives them from a real image reference.

buildgreatproducts Skill

Use when the user has a finished `productos/design/1-Product-Identity.md` and `docs/PRODUCT.md` and wants paste-ready prompts for AI design tools (Pencil, paper.design, Claude Design, or MagicPath) that produce on-brand designs immediately. Triggers on phrases like "generate design prompts", "create AI design prompts", "make screen prompts for my product", "give me prompts for Claude Design / Pencil / paper / MagicPath", "prompts to design my screens", "draft my screens with AI", "give me a design prompt for [screen]", "what should I prompt my AI design tool with", or any request to translate the Product Identity into design-tool prompts. Reads both source files and writes `productos/design/Design-Prompts.md` with three prompts: Prompt 1 is always a comprehensive UI design system foundation (colors, typography, components, layout, motion) so screens share a consistent component vocabulary; Prompts 2 and 3 are two priority screens for the product type.

buildgreatproducts Skill

Use when the user already has a product codebase and wants to reverse-engineer the design system already in the code into a Google-format `docs/DESIGN.md` — extracting the colors, typography, spacing, radii, elevation, and components actually used, flagging internal inconsistencies (competing values for one role — several "primary" blues, forked paddings, mixed radii, stray hex), resolving each with the user, then writing the file. Triggers on "design system from code", "reverse-engineer my design system", "I have a codebase but no DESIGN.md", "audit my codebase for design tokens", "consolidate my design tokens". Runs in the app repo — the repository that contains `productos/` — and reads CSS variables, Tailwind config, theme files and components; surfaces inconsistencies to resolve interactively; writes `docs/DESIGN.md` in Google's exact format (YAML tokens + eight sections), matching `studio-design-design-system`, compatible with `studio-develop-design-review`.

chienchuanw Bundle

Build grandMA2 Gobo / Color / Beam / Focus preset palettes from fixture-type XML profiles, programming the correct per-fixture-type DMX value for each named function so one logical preset works across mixed fixtures. Use whenever the user wants to "build presets", "make a color palette", "set up gobo/beam/focus presets", "program a preset pool", or hands over fixture XML files and a console to populate presets on. Requires the gma2 MCP server connected (run the connect skill first). Prefer this over hand-writing preset commands — it resolves fixture-specific values from the profiles instead of guessing.

chienchuanw Skill

Use when starting or integrating work on a UI/visual project — anything that renders a screen, component, page, or layout a human looks at. Enforces a visual-first gate: for a UI project you confirm the look (a signed-off Figma frame or a throwaway preview page) BEFORE writing implementation code, and any UI change must carry a visual comparison (screenshot / preview URL / Figma frame) before it can merge. Fires when a project is flagged `ui_project: true` or the diff touches front-end files (.tsx/.jsx/.vue/.svelte/.css), and on "is the design signed off", "visual gate", "UI 專案要先確認畫面", "這個要附截圖對照嗎". Figma is the source of truth — this skill reuses the existing figma skills for design↔code sync rather than reimplementing them. The `auto-integrate` skill calls this as an extra green-light condition for UI projects.

poorgramer-zack Bundle

shadcn_flutter UI component library for building accessible, themed Flutter interfaces. Use when integrating shadcn components, configuring design system theming, or building consistent widget layouts.

poorgramer-zack Skill

Implements responsive and adaptive layouts in Flutter using flutter_screenutil v5.9.x (pixel-perfect scaling from Figma), sizer v3.1.x (percentage-based viewport), and responsive_framework v1.1.x (breakpoint-driven structure changes). Use this skill when building apps for multiple screen sizes (phones, tablets, foldables, desktop, web), fixing layout overflow or sizing issues, implementing breakpoint-based adaptive UI, creating pixel-perfect designs from Figma specs, handling orientation changes, supporting Flutter web or desktop responsive layouts, or any time the words 'responsive', 'screenutil', 'sizer', 'breakpoint', 'adaptive layout', or 'screen size' appear in the request. Includes a decision matrix for selecting the correct package per scenario.

lukaskellerstein Bundle

Design guidance and aesthetic patterns for building beautiful, distinctive frontends — websites, web apps, landing pages. Provides typography strategies, color application, motion choreography, layout composition, and component design recipes. Use when the user asks to "make this look better", "improve the design", "it looks too generic", "add visual polish", "make it look professional", "design a landing page", "hero section design", "make it beautiful", or any request about visual quality of frontend code. Prevents generic "AI slop" by providing opinionated, intentional design patterns.

luminary19 Bundle

Generate and edit raster images by driving the locally-installed OpenAI Codex CLI headlessly and invoking its FIRST-PARTY built-in `image_gen` tool (gpt-image) — using the ChatGPT Plus/Pro login Codex is already authenticated with, NO OpenAI API key, no reverse-engineered routes. Use when asked to "generate an image", "make a logo/icon/ texture/mockup", "edit this PNG", "use codex to create an image", or "/codex-imagegen". Wraps `codex exec` and parses output via a PowerShell helper so files are reliably found.

luminary19 Bundle

Forge suite — web/runtime optimization pipeline for 3D assets: compress, budget, and hand off GLB files to the browser. Takes a raw GLB exported by Blender (or another DCC) and delivers a browser-ready GLB with Draco or Meshopt geometry compression, KTX2/Basis Universal or WebP texture compression, mesh quantization, LOD generation, and spec-validation — then produces the handoff package that atelier-webgl expects (optimized GLB + poster WebP + decoder paths). Use whenever: compressing a GLB for web delivery, reducing file size, applying Draco or Meshopt, encoding KTX2 textures with UASTC or ETC1S, generating LOD levels from a GLB, setting up DRACOLoader / KTX2Loader / MeshoptDecoder in Three.js or R3F, validating a GLB against the Khronos spec, building a before/after size report, running gltf-transform or gltfpack, meeting web 3D budget targets (< 3 MB, < 100 draw calls, < 500k triangles), or preparing assets for the atelier-webgl handoff. Trigger phrases: "optimize GLB", "compress 3D model", "Draco compres

luminary19 Bundle

Atelier suite — the art-direction brain. Decide the design direction BEFORE writing any frontend code: which aesthetic, which "world" (production vs award-grade), the concept, the palette mood, type voice, motion budget, layout archetype, and signature moment. Produces a Direction Doc scaled to the task (a one-line read for small tweaks, a full one-pager for substantial builds/redesigns) that the rest of the suite (atelier-foundations, atelier-typography, atelier-layout) consumes. This is the canonical Atelier entry point — prefer it over older/general design skills. Use this FIRST whenever building a new website, landing page, web app, dashboard, portfolio, or editorial site — or deciding the look/feel/aesthetic of one — and ESPECIALLY whenever frontend output risks looking generic, templated, or "AI-made." If the user mentions design, UI, a new page, a look/vibe, an aesthetic, names a reference site, or wants to see several distinct creative directions to choose from (a moodboard of options), start here. Fo

luminary19 Bundle

Atelier suite — expensive typography. Choose and pair fonts with a point of view, build a fluid modular type scale, control tracking/leading/measure, switch on the right OpenType + variable-font features, set editorial detail (drop caps, pull quotes, hierarchy), tune font loading for zero layout shift, and animate type (kinetic / scroll-driven) tastefully. Use this whenever typography matters: picking or pairing fonts, headings that feel generic or "default Inter/Playfair," body readability, display type, variable fonts, font loading / FOUT / web-font CLS, RTL & non-Latin (CJK) type, numbers in tables, or animated/kinetic text. Run after atelier-direction (type voice) and alongside atelier-foundations (which owns the scale tokens).