Loading...
Loading...
Found 598 Skills
Use this skill when discussing UI components, design systems, frontend implementation, or component architecture. Guides thinking about Atomic Design methodology - atoms, molecules, organisms - and promotes component reuse over creation. Triggers on UI/frontend discussions, "what components do we need?", "should I create a new component?", or design system questions.
Expert visual designer specializing in creating intuitive, beautiful, and accessible user interfaces. Masters design systems, interaction patterns, and visual hierarchy to craft exceptional user experiences that balance aesthetics with functionality.
Use when designing or reviewing web UI, implementing forms/buttons/inputs, fixing visual hierarchy issues, creating color systems, building layouts, or when interface feels cluttered, hard to read, or users don't know what to click.
Initialize .chalk folder — analyze a repo and capture its architecture, coding style, tech stack, design assets, and project identity into chalk.json and structured docs
Automatically injects the project's extracted design soul into any frontend task. Use this skill on EVERY request that involves building, editing, or reviewing UI — including components, pages, layouts, styles, animations, and design decisions. Triggers on: any prompt containing words like "build", "create", "make", "design", "component", "page", "layout", "button", "form", "card", "nav", "header", "modal", "style", "css", "tailwind", "animate", "responsive", "ui", "frontend", "screen", "dashboard", "landing", "section", or any request to write JSX, TSX, HTML, or CSS. Do NOT trigger on backend-only tasks, database queries, API routes with no UI, or pure logic/utility functions with no visual output. This skill has no slash command — it runs silently in the background on every frontend task. The user never needs to invoke it manually.
Takes an existing component, file, or CSS and rewrites it to match the project's extracted design soul in .marrow.md. Fixes all soul violations while preserving the component's structure, logic, and functionality. Use this skill when the user wants to fix a specific file to match the design soul, align existing code to marrow rules, or repair soul violations found by marrow-check. Triggers on: /marrow-align, or prompts like "align this to marrow", "fix this to match the soul", "make this match .marrow.md", "fix the soul violations in this file", "align this component", "marrow-align [filename]". Requires .marrow.md to exist. If not found, instructs user to run /marrow first.
Surgically updates a specific section of .marrow.md without re-running the full extraction. Accepts a new value, color, image, or description and patches only the relevant section — leaving everything else intact. Use this skill when the user wants to update one part of the extracted soul, change the brand accent color, update spacing rules, replace a typeface, refine the brand personality, or extract color from a new reference image. Triggers on: /marrow-update, or prompts like "update the accent color to X", "change the brand color", "update spacing in marrow", "the font changed to X", "update marrow with this new color", "patch marrow", "update just the accent", "marrow-update accent #FF6B6B", "update the palette from this image". Requires .marrow.md to exist. If not found, instructs user to run /marrow first.
Designer role. Reads outline, generates a single HTML presentation file with CSS design system + JS slide engine + per-slide content. Accepts visual references (URLs, screenshots, design specs) and extracts design signals to inform the isomorphic mapping. Use whenever the user says "design slides", "generate deck", "generate the deck", "build slides", "visual style", "reference this style", "like this design", "design", "generate slides", "visual style", "reference this style", or wants to turn an outline into actual slides.
Apple-inspired premium aesthetic with precise spacing, modern typography, and a refined, polished visual language.
This skill should be used when a designer wants to produce a holistic design for a full feature before it is broken into tasks — for example "design feature
Buttons, inputs, pills, badges, calendars, and other interactive components form a visual family — they share the same border-radius, colour logic, shadow scale, border style, and spacing rhythm. Inconsistency between them breaks the sense of a coherent product. Use when building or reviewing a component library, design system, or any set of UI components.
You are **ArchitectUX**, a technical architecture and UX specialist who creates solid foundations for developers. You bridge the gap between project specifications and implementation by providing C...