Frontend CSS Strategy
Use when the user asks which styling approach to use: CSS Modules vs CSS-in-JS vs Tailwind, styled-components, Emotion, vanilla-extract, BEM, Sass, PostCSS, cascade layers or CSS architecture. Produces a styling decision with folder and naming conventions. Not for Tailwind configuration (use frontend-tailwind-css) or dark mode (use frontend-theming).
Install
npx skills add j4flmao/agent-skills --skill frontend-css-strategygit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/frontend/universal/css-strategy ~/.claude/skills/frontend-css-strategyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Frontend CSS Strategy ## Purpose Choose and implement the right CSS approach for the project. Utility-first for rapid iteration and consistency. CSS Modules for scoped, component-encapsulated styles. CSS-in-JS for dynamic theming and colocation. Each approach solves a different problem — pick the right one. ## Agent Protocol ### Trigger Exact phrases: "CSS strategy", "CSS Modules", "CSS-in-JS", "utility-first", "Tailwind CSS", "styled-components", "Emotion", "CSS organization", "CSS architecture", "CSS approach", "styling approach", "how to style", "CSS decision". ### Input Context - Framework (React, Vue, Angular, Svelte) - Team size and CSS experience - Project type (library, app, design system) - Current styling approach (if any) - Performance requirements (runtime cost, bundle size) ### Output Artifact CSS strategy recommendation with rationale, setup code, and organization pattern. ### Response Format ``` ## Recommendation <approach> — <rationale> ## Setup <config, dependencies, file-structure> ## Usage <component-example, naming-convention> ## Organization <folder-structure, globals, utilities> — Compression footer: frontend-css/v1 | approach: <tailwind|modules|css-in-js> | perf: <runtime|zero> ``` No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick. ### Completion Criteria - [ ] CSS approach selected with documented rationale - [ ] File and folder structure created
Details
- Skill name
frontend-css-strategy- Repository
- j4flmao/agent-skills
- Path
skills/frontend/universal/css-strategy/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Frontend CSS Strategy skill do?
Use when the user asks which styling approach to use: CSS Modules vs CSS-in-JS vs Tailwind, styled-components, Emotion, vanilla-extract, BEM, Sass, PostCSS, cascade layers or CSS architecture. Produces a styling decision with folder and naming conventions. Not for Tailwind configuration (use frontend-tailwind-css) or dark mode (use frontend-theming).
How do I install the Frontend CSS Strategy skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill frontend-css-strategy. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Frontend CSS Strategy popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Frontend Data Fetching
45j4flmao/agent-skills
Use when the user asks how to cache server data on the client with TanStack Query, SWR or RTK Query, query keys, staleTime/gcTime, cache invalidation, optimistic updates, pagination or infinite scroll. Produces a typed data-fetching layer with caching and mutation patterns. Not for backend API design (use backend-api-design).
Frontend Bundler Tools
45j4flmao/agent-skills
Use when the user asks about Vite, webpack, Rspack, Turbopack, Rolldown, esbuild, bundle config, tree shaking, code splitting, chunking, build speed or migrating webpack to Vite. Produces bundler configuration and build-optimization steps. Not for Core Web Vitals field work (use web-performance) or CI pipelines (use cicd-pipeline).
Frontend Design System
45j4flmao/agent-skills
Use when the user asks to build a component library, define primitive, semantic and component design tokens as CSS variables, design component APIs with CVA variants, or wire dark mode through semantic tokens. Produces coded token layers and component library structure. Not for Figma variables and token pipeline governance (use design-systems).
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.