css
Best practices for CSS development including modern layout techniques, naming conventions, theming, and maintainable stylesheet architecture
What this skill does
# CSS Development Guidelines ## Core Principles - Write semantic HTML to improve accessibility and SEO - Use CSS for styling, avoiding inline styles - Ensure responsive design using media queries and flexible layouts - Prioritize external stylesheets over inline or embedded styles ## Layout Techniques ### Flexbox - Use Flexbox for one-dimensional layouts (rows or columns) - Leverage `justify-content` and `align-items` for alignment - Use `flex-wrap` for responsive wrapping behavior - Prefer `gap` property over margins for consistent spacing ### Grid - Use CSS Grid for two-dimensional layouts - Define grid templates with `grid-template-columns` and `grid-template-rows` - Use `grid-area` for named template areas - Leverage `auto-fit` and `auto-fill` for responsive grids ## Units and Typography - Use `rem` units for typography to respect user preferences - Use `em` units for component-relative sizing - Avoid `px` for font sizes; reserve for borders and fixed elements - Implement fluid typography with `clamp()` when appropriate - Use viewport units (`vw`, `vh`) thoughtfully for full-screen layouts ## CSS Variables (Custom Properties) - Define design tokens as CSS variables on `:root` - Use variables for colors, spacing, typography, and shadows - Implement theming by overriding variables in different contexts - Name variables semantically (e.g., `--color-primary`, `--spacing-md`) ## Naming Conventions ### BEM Methodology - Block: Standalone component (e.g., `.card`) - Element: Part of a block (e.g., `.card__title`) - Modifier: Variation of block or element (e.g., `.card--featured`) ### Best Practices - Use lowercase with hyphens for class names - Avoid IDs for styling; reserve for JavaScript hooks - Keep specificity low by using single class selectors - Scope styles to components to prevent conflicts ## Specificity Management - Maintain specificity at 0-1-0 (single class) when possible - Avoid `!important` declarations - Use cascading intentionally, not accidentally - Consider CSS Layers (`@layer`) for specificity control ## Responsive Design - Implement mobile-first media queries - Use relative units for flexible layouts - Test across multiple viewport sizes - Consider container queries for component-level responsiveness ## Performance - Minimize selector complexity - Avoid deeply nested selectors - Use efficient selectors (class over element) - Leverage CSS containment for isolated components - Consider critical CSS for above-the-fold content ## Modern CSS Features - Use `aspect-ratio` for maintaining proportions - Leverage `gap` in Flexbox and Grid - Use logical properties (`margin-inline`, `padding-block`) - Implement smooth transitions with `transition` property - Use `@supports` for feature detection ## Organization - Structure stylesheets logically (base, layout, components, utilities) - Keep files modular and focused - Document complex styles with comments - Use a consistent property order within declarations ## Browser Compatibility - Use vendor prefixes when necessary (consider Autoprefixer) - Test across target browsers - Provide fallbacks for newer features - Use progressive enhancement approach ## Accessibility - Ensure sufficient color contrast (WCAG AA minimum) - Provide visible focus styles for keyboard navigation - Avoid hiding content in ways that affect screen readers - Use `prefers-reduced-motion` media query for animations
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.