css-creative-expert
/css-creative-expert
Use when CSS-specific composition, cascade behavior, responsive layout, theming, or motion requires design or diagnostic judgment.
- Author
- vosslab ↗
- Repository
- vosslab-skills ↗
- Licence
- MIT
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when CSS-specific composition, cascade behavior, responsive layout, theming, or motion requires design or diagnostic judgment.
Original author description
Use when CSS-specific composition, cascade behavior, responsive layout, theming, or motion requires design or diagnostic judgment.
How it works
- Overview
- Workflow
- Implementation defaults
- Quality bar
- Output expectations
SKILL.md preview
--- name: css-creative-expert description: Use when CSS-specific composition, cascade behavior, responsive layout, theming, or motion requires design or diagnostic judgment. --- # CSS creative expert ## Overview Turn an imprecise request to improve a page into a small, rendered, maintainable CSS change. Own visual craft, layout, responsive behavior, theming, motion, and accessible color design. Route measured contrast audits and palette repair to `color-accessibility-expert`; route interaction, task flow, and usability judgment to `ui-ux-engineer`. ## Workflow 1. Classify the request and choose a visible outcome. - Sort it into visual craft, layout, theming, or motion; name the audience, page state, viewport range, color scheme, and observable improvement. - Read [references/task_selection.md](references/task_selection.md), then use [references/topic_index.md](references/topic_index.md) for the focused route. 2. Detect the target project shape and map its cascade surface. - Existing stylesheet: inventory entry points, layers, custom properties, specificity hot spots, component boundaries, responsive breakpoints, and existing visual tests before editing. - Greenfield page: establish content hierarchy, semantic HTML, a token system, baseline layout, narrow-screen behavior, and one coherent visual direction. - Read [references/project_workflow.md](references/project_workflow.md). 3. Establish the visual and structural contract. - State the content hierarchy, layout primitive, width and overflow behavior, color-role intent, motion purpose, reduced-motion behavior, and target viewports. Keep design tokens and component rules legible in the cascade. - Prefer a focused change that preserves the page's purpose over a generic restyle. Select the relevant source and verification move from [references/topic_index.md](references/topic_index.md). 4. Route local evidence by outcome and source type. - When the local corpus exists, use [references/local_books.md](references/local_books.md) to select `css-creative/` for visual craft or `css-technical/` for mechanics. - Search one verified term from [references/reference_survey.md](references/reference_survey.md). Use a focused guide for an exact feature, a broad book for its surrounding model, or secondary examples as idea sources. - Read the full surrounding section, then confirm evolving syntax, browser support, and implementation details in MDN and the relevant CSS specification. 5. Implement one coherent CSS slice. - Use grid or flexbox for page geometry, intrinsic sizing and logical properties where appropriate, and custom properties for repeated values and themes. - Keep selectors scoped, specificity intentional, fallbacks explicit, and transitions purposeful. Respect `prefers-reduced-motion`; use motion to clarify content and essential controls. - Keep color roles distinguishable and readable; send numerical contrast measurement and any resulting repair workflow to `color-accessibility-expert`. 6. Validate the rendered behavior and refine. - Compare screenshots across required viewport sizes and light/dark schemes; run a focused Playwright pass when the target serves HTML. - Inspect computed styles for the contract's critical rules and use the appropriate oracle in [references/testing_and_oracles.md](references/testing_and_oracles.md). ## Implementation defaults - Start from semantic document structure and content hierarchy; let CSS express layout and presentation instead of compensating for missing structure. - Use a small token vocabulary for color, spacing, type, radius, and elevation; define themes through custom properties and consolidate repeated overrides. - Prefer fluid constraints (`minmax()`, `clamp()`, intrinsic sizing, container queries) before accumulating viewport-specific exceptions. - Use cascade layers to make reset, base, component, utility, and override precedence visible when the target's scale warrants them. - Make dark mode an intentional color-role design, then delegate measured contrast verification to `color-accessibility-expert`. - Use animation to explain state change or spatial continuity, honor reduced motion, and validate performance on representative content. ## Quality bar - Preserve content meaning, keyboard reachability, source order, and readable zoom behavior while improving the rendered result. - Make responsive behavior work at intermediate and named device widths. - Keep cascade priority explicit, content height fluid, and decorative effects subordinate to readability. - Compare light and dark schemes, normal and reduced motion, empty and long content, and the layout's narrowest supported viewport. - Use current primary documentation for browser support and new CSS features. ## Output expectations When using this skill, produce: - A concise visual contract, target files, cascade-surface inventory, and route. - A file- and selector-specific CSS implementation or recommendation. - Screenshot, computed-style, and browser-test evidence for the changed states. - A handoff to `color-accessibility-expert` for measured contrast repair or to `ui-ux-engineer` for interaction and usability decisions when applicable. - A clear next step if browser support, brand direction, or target viewports require user confirmation.
Files in this package (8)
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
- references/local_books.md 5 KB
- references/project_workflow.md 1 KB
- references/reference_survey.md 6 KB
- references/task_selection.md 1 KB
- references/testing_and_oracles.md 2 KB
- references/topic_index.md 5 KB
Versions
The database has no other skills named css-creative-expert.
Database snapshot: 13.11.2026 · package version 818b5b1f102e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100frontend-design
Use this skill when specifying, designing, or documenting UI components, layouts, and design systems for frontend implementation. Trigger phrases: ''design this UI component'', ''create a responsive layout'', ''spec the CSS for'', ''design system for''. Do NOT use for backend… - 100design-tokens
Design tokens and CSS custom properties: theme systems, dark mode, component libraries. Use when implementing design systems or user mentions tokens, CSS variables, or theming. - 100daisyui
Guide for daisyUI component library with Tailwind CSS. Use when building UI components, implementing themes, or creating responsive designs with daisyUI. - 100obsidian-app-css
Use when writing, debugging, auditing, or reorganizing CSS snippets or app themes for Obsidian desktop/mobile, including DOM selectors, CSS variables, platform classes, plugin/theme compatibility, specificity, or cascade conflicts. Excludes hosted Publish, publish.css, and publish.js. - 95frontend-theming
Use this skill when the user says 'theming', 'dark mode', 'light mode', 'theme switching', 'CSS variables', 'custom properties', 'theme provider', 'theme context', 'color scheme', 'prefers-color-scheme', 'theme toggle', 'design tokens'. Implement theme systems with CSS… - 100css
CSS conventions, layout systems, and modern patterns: predictable styles through low specificity and explicit cascade control. Invoke whenever task involves any interaction with CSS code — writing, reviewing, refactoring, debugging, or understanding stylesheets, SCSS, layout, or responsive design.