design-expert

Apply NestMind design tokens and responsive CSS patterns to HTML and UI styling.

Updated Oct 4, 2025
One-click install
npx skills add https://github.com/nestmind-app/docs --skill design-expert-nestmind-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-expert
Source: https://github.com/nestmind-app/docs/tree/main/.claude/skills/design-expert
Command: npx skills add https://github.com/nestmind-app/docs --skill design-expert-nestmind-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you ensure HTML/CSS edits stay aligned with NestMind's Zed-inspired design system, preserving the editorial, light-theme aesthetic, and reusing existing patterns.

Core Features & Use Cases

  • Use tokens from css/styles.css (:root) for colors, spacing, typography, and motion.
  • Maintain typography pairing: --font-serif for headings and --font-sans for body.
  • Default theme is light; add .dark overrides only when requested or already in use.
  • Prefer existing classes and components before creating new ones.

Quick Start

  • Update the header and layout to use the existing .container, .nav, and .hero components.
  • Apply color and typography tokens from css/styles.css and ensure mobile-first breakpoints (640px, 768px, 1024px).
  • Ensure tap targets meet 44px and avoid horizontal overflow on small screens.

Frequently Asked Questions about design-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure my HTML and CSS stay aligned with a design system?

Responsive design requires reusing existing components and tokens. Use color, spacing, typography, and motion tokens from your global stylesheet; apply mobile-first breakpoints; ensure 44px tap targets; maintain semantic HTML with sufficient text contrast; and respect motion preferences to keep layouts consistent and accessible across devices.

What's the best way to implement responsive design without creating new CSS classes?

Leverage existing patterns like .container, .nav, .btn, .card, and .hero before writing new styles. Apply mobile-first breakpoints at 640px, 768px, and 1024px; use flex and grid with wrapping to avoid horizontal overflow; and pull spacing and typography values from shared tokens in your root stylesheet.

How do I add dark mode to a website while keeping light theme as default?

Define all color tokens in light theme at :root, then layer .dark overrides only when needed. This preserves the default aesthetic while allowing theme switching; reuse existing token names and avoid creating redundant color variables.

Can I use semantic HTML and maintain accessibility standards without extra markup?

Yes. Use semantic tags with visible focus states, ensure text contrast at 4.5:1 or higher, set tap targets to 44px minimum, animate only with transform and opacity while respecting prefers-reduced-motion, and avoid horizontal scroll on mobile—all without additional wrapper elements.

What happens if I add horizontal scrolling on small screens?

Horizontal overflow breaks mobile usability and accessibility. Wrap content in .container, use flex and grid with wrapping, and test at mobile-first breakpoints to prevent scroll; prioritize vertical scrolling on devices under 640px.

Does typography pairing affect how my design system scales?

Yes. Pairing serif fonts for headings and sans-serif for body text creates visual hierarchy and improves readability across breakpoints. Define both in tokens and reuse consistently across all pages and components to maintain coherent typography at every scale.