Loading...
Loading...
Found 46 Skills
Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.
Brand-first landing page designer — interviews the user to discover brand identity (adjectives, colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML output. Preferred over frontend-design for standalone landing/marketing pages where the user hasn't established visual direction yet. TRIGGER when: user asks to "create/design/build a landing page", "make a homepage for my project/product/service", "build a marketing page", or wants to promote an app/side project. Especially when they haven't defined brand colors, fonts, or visual style — the guided brand interview is the core value. DO NOT TRIGGER when: user has a specific design mockup to implement, wants a dashboard or app UI, needs component-level frontend work (buttons, forms, navbars), is building a multi-page application, or is restyling an existing page with known design tokens. Use frontend-design for those cases.
Use when: building new UI from scratch and need design workflow (layout → theme → animation → code). Don't use when: extracting design from existing code (use frontend-design-extractor) or need full production site (use frontend-design-ultimate). Routing tree: "Building new site from scratch?" → frontend-design-ultimate; "Need UX critique or design tokens?" → ui-ux-pro-max; "Redesigning existing frontend with quantified eval?" → human-optimized-frontend; "Need design workflow (wireframe → theme → code)?" → frontend-design (superdesign); "Extracting design from existing codebase?" → frontend-design-extractor
UI/UX and frontend design best practices guidelines (formerly frontend-design). This skill should be used when writing, reviewing, or designing frontend code to ensure accessibility, performance, and usability. Triggers on tasks involving HTML structure, CSS styling, responsive layouts, form design, animations, or accessibility improvements.
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design tokens, typography, status/priority systems, composition patterns, and the /design-guide showcase page. Always use this skill alongside the frontend-design skill (for visual quality) and the web-design-guidelines skill (for web best practices).
Build interfaces with design engineering craft — the intersection of design and code. Use this skill when the user asks to build UI components, interactive elements, animations, micro-interactions, or polished web experiences. Triggers on mentions of "design engineer", "interaction design", "micro-interactions", "craft", "polish", "delight", "animation", "motion design", "haptics", "toast", "command palette", "design system components", or requests for interfaces that feel alive, responsive, and meticulously detailed. This skill should also be used when the user wants to add invisible details, fine-tune interactions, or make something "feel right". Complements the frontend-design skill by focusing specifically on interaction quality, motion, and engineering craft.
Scaffold and maintain a reusable research → design → plan → orchestrate → act folder for any non-trivial work — software features, marketing campaigns, org changes. Drops a domain-agnostic spine (00-README · 01-plan · 02/03 research · 04-discussion newest-first · 05-tracking · 09-orchestration · artifact/board.html plan-board) plus stateless action-skills that augment the docs in place without clobbering hand-written prose. Composes ikenga-artifact-builder, huashu-design, frontend-design, ikenga-pkg-builder when present; degrades gracefully when not. Profile-driven: `software` (rich default, code work), `general` (lean, non-code — campaigns, org changes), and `content` (editorial/marketing with key art). TRIGGER when the user asks to start a real plan for non-trivial work ("plan a feature," "scaffold a plan folder," "set up groundwork for…"), references an existing plans/ folder by groundwork structure, or runs any of these actions: groundwork init / research / design / review / clarify / orchestrate / refresh-board / refresh-living-spec / status. DO NOT TRIGGER for one-off code changes, single-document writeups, ADRs, or content that fits in a single markdown file — those don't need a multi-doc plan folder. If the user just wants a single artifact (dashboard, mockup), route to ikenga-artifact-builder instead.
Design system generation and UI/UX planning intelligence. Use when the user needs to choose a color palette, select fonts, generate a design system, plan a visual direction, or explore UI styles before implementation. Covers 50+ styles, 97 palettes, 57 font pairings across 9 stacks. Do NOT use for building/coding UI — use frontend-design for implementation.
Build production-grade frontend interfaces with modern React, Tailwind CSS, and shadcn/ui. Five modes: scaffold projects, create components, configure themes and design tokens, refactor styles, and audit codebases. Encodes best practices for React 19 Server Components (framework-dependent), TailwindCSS v4 CSS-first config, shadcn/ui with Radix primitives, modern CSS (container queries, :has(), view transitions, scroll-driven animations), Monaspace typography, and Vite 6. Supersedes the frontend-design skill. Use when building, styling, theming, or improving any frontend project. NOT for backend APIs, database design, DevOps, testing frameworks, state management libraries, routing, or full SSR framework setup.
Guides novice PMs through a 7-step agile workflow: dialogue-based requirement gathering, drafting PRD skeleton, HTML prototype creation (via frontend-design), mermaid flowcharts, and final PRD with iframe slices.
Actionable design system complementing official frontend-design plugin. The plugin provides philosophy; this skill provides executable patterns. Invoke when: - Building web components, pages, or applications - Designing UI that needs to stand out (not generic) - Implementing visual polish and micro-interactions - Choosing typography, color palettes, or spatial layouts CRITICAL: Avoid "AI slop" aesthetics. Make creative, unexpected choices. MANDATORY: Consult Gemini before any frontend work. See also: references/dna-codes.md, references/banned-patterns.md
Casper Studios internal design system for generating consistent, production-grade SaaS UI. Use this skill whenever generating UI code for internal tools, client apps, dashboards, POCs, prototypes, or any visual interface — even quick mockups or artifacts. Apply it any time the output is a React component, page, or layout. If the user mentions "our design system", "Casper style", "match our look", or asks you to build any kind of app or interface, use this skill. Also trigger when restyling or theming existing UI to match Casper's visual language. This skill takes priority over generic frontend-design guidance.