Results for “style”

[devup-ui] Routing-first front door for Devup UI — a zero-runtime CSS-in-JS library whose Rust + WebAssembly preprocessor extracts every style at build time, so no styling JavaScript ships at runtime. Use to adopt/integrate Devup UI, wire the build-time plugin into Next.js/Vite/Rsbuild/Webpack/Bun, write styles with Box/css props or the styled-components-compatible styled() API, set up type-safe theming with devup.json, or migrate off styled-components/Emotion/Tailwind/Panda/vanilla-extract to zero runtime.

Build React interfaces with Material UI components, theming, styled engine, data grid, date pickers, and icons.

Audits UI code for compliance with the StyleSeed design system, covering design tokens, component conventions, accessibility, mobile UX, and typography.

Apply named StyleSeed motion to React components using framer-motion, with personality seeds and keyword moves from a motion library.

Convert Stitch HTML designs to React Native components or sync existing native components with updated designs using StyleSheet.

ScepticAgent UI and styles reference. Use whenever the user wants to change the side panel UI, modify highlight colours, update the markdown renderer, work with CSS architecture, add or change category colours, or understand how the sidepanel renders analysis output.

Use when writing Textual TUI CSS styles or checking valid CSS properties

Best practices for CSS development including modern layout techniques, naming conventions, theming, and maintainable stylesheet architecture

Best practices for CSS development including modern layout techniques, naming conventions, theming, and maintainable stylesheet architecture

Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.

Generate syntactically correct Claude Code configuration components (commands, subagents, skills, output styles) with optimal cross-component integration. Triggers on requests to create slash commands, agents, subagents, skills, output styles, Claude Code plugins, agentic workflows, or multi-agent pipelines. Ensures parameter validity per component type and semantic coherence across component references.

Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.

Generate a new UI component that follows StyleSeed Toss conventions for structure, tokens, accessibility, and component ergonomics.

List, add, and update StyleSeed design tokens while keeping JSON sources, CSS variables, and dark-mode values in sync.

Create beautiful, accessible user interfaces with shadcn/ui components, Tailwind CSS utility-first styling, and canvas-based visual designs.

List, add, and update StyleSeed design tokens while keeping JSON sources, CSS variables, and dark-mode values in sync.

Custom scrollbar component with consistent styling. Invoke when user needs to implement custom styled scrollbars or scrollable containers in Naive UI.

Choose and apply high-quality frontend visual direction for websites, apps, dashboards, redesigns, landing pages, portfolios, and UI polish. Use when prompts mention design taste, anti-slop UI, redesign, premium visual design, minimalist, brutalist, legacy style inheritance, design direction, or the old taste-skill/gpt-tasteskill/soft-skill/brutalist-skill/minimalist-skill/redesign-skill skills.

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

Guides choosing between Tailwind, CSS Modules, and global CSS with BEM, and implementing responsive layouts with Grid, Flexbox, and Container Queries.

Headless UI Styling

Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe.

Improve the visual design of a frontend by restyling components one at a time, with approval gates and no functional changes.

Select, pair, and implement typefaces for web projects with guidance on readability, CSS implementation, and performance optimization.

CSS Design Tokens

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

Audits an EXISTING UI/codebase for generic AI patterns and applies targeted craft fixes — layout, interactivity, content, iconography, and code quality — without discarding the project's own identity. Use when a UI looks flat, generic, or "AI-slop" and there is code to improve, not build from scratch. Triggers on: "improve the design", "looks generic", "not polished enough", "redesign this", "elevate the UI", "it looks boring", "make it better looking", "apply taste", "design review". Works with any CSS framework. For designing a NEW project's identity from a brief, use `taste-skill` instead — this skill only upgrades what's already built. Source: github.com/Leonxlnx/taste-skill (redesign-skill), restored to the full checklist + the project-identity rule the earlier port had dropped.

Anti-slop frontend design skill for building NEW landing pages, portfolios, and UI from a brief. Reads the brief and existing brand context first, infers a design direction from three configurable dials (variance, motion, density), and ships interfaces that don't look templated or default-AI. Use when starting a new page/UI with no existing identity to preserve, or when asked to design something "that doesn't look like every other AI landing page." For auditing and upgrading an EXISTING UI, use `taste-redesign` instead — this skill is for the moment before code exists. Triggers on: "build a landing page", "design a portfolio", "make this not look generic/templated/AI-generated", "anti-slop", starting UI work with a brief but no established identity yet. Also owns component-library selection (which package for toasts, dropdowns, charts, drag-and-drop, state, etc.) — use this instead of hand-rolling a component or guessing at a dependency. Source: github.com/Leonxlnx/taste-skill (taste-skill, the main v2 varian

Render the cited draft as an HTML preview styled like the brand's blog so the writer can review the article in browser before publishing.