Dominio
Frontend Development
Perfil de habilidad
styled-components, Emotion, vanilla-extract, CSS Modules, runtime vs zero-runtime
Roles
3
donde aparece esta habilidad
Niveles
5
ruta de crecimiento estructurada
Requisitos obligatorios
15
los otros 0 opcionales
Frontend Development
CSS & Styling
17/3/2026
Selecciona tu nivel actual y compara las expectativas.
La tabla muestra cómo crece la profundidad desde Junior hasta Principal.
| Rol | Obligatorio | Descripción |
|---|---|---|
| Frontend Developer (React) | Obligatorio | Uses CSS-in-JS at a basic level. Creates simple components from design. Understands basic concepts and follows component guidelines. |
| Frontend Developer (Svelte) | Obligatorio | Uses CSS-in-JS at a basic level. Creates simple components following design specs. Understands basic concepts and follows component guidelines. |
| Frontend Developer (Vue) | Obligatorio | Uses CSS-in-JS at basic level. Creates simple components from design. Understands basic concepts and follows component guidelines. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Frontend Developer (React) | Obligatorio | Implements complex React UI components using styled-components or Emotion with dynamic theming and responsive styles. Optimizes rendering performance by avoiding unnecessary style recalculations. Writes unit tests for styled components and applies proper CSS-in-JS patterns for state-driven styling. |
| Frontend Developer (Svelte) | Obligatorio | Applies CSS-in-JS approaches within Svelte component styling, using scoped styles with dynamic class bindings and CSS custom properties. Optimizes rendering performance by leveraging Svelte's compile-time style optimization. Integrates design tokens and writes tests for component visual states. |
| Frontend Developer (Vue) | Obligatorio | Implements complex Vue components using CSS-in-JS libraries (e.g., vue-styled-components) or scoped styles with dynamic bindings. Optimizes rendering by minimizing style recalculations in reactive contexts. Applies proper patterns for theme switching and state-driven styling in Vue SFCs. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Frontend Developer (React) | Obligatorio | Designs React design system architecture with CSS-in-JS: token-based theming, variant APIs, and compound component patterns. Optimizes bundle size through static extraction and critical CSS strategies. Implements accessible, performant component libraries meeting Core Web Vitals targets. |
| Frontend Developer (Svelte) | Obligatorio | Designs Svelte design system architecture combining scoped CSS with CSS-in-JS patterns for cross-project consistency. Optimizes bundle size and Core Web Vitals through Svelte's zero-runtime CSS approach. Creates reusable, accessible component libraries with comprehensive theming and variant support. |
| Frontend Developer (Vue) | Obligatorio | Designs Vue design system architecture with CSS-in-JS integration: token-based theming, variant composition, and style isolation patterns. Optimizes bundle size and Core Web Vitals through tree-shaking and critical CSS extraction. Builds accessible, reusable component libraries for the organization. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Frontend Developer (React) | Obligatorio | Defines product-level CSS-in-JS architecture for React applications: selects styling solutions (runtime vs zero-runtime), establishes theming contracts, and enforces design token standards. Conducts architectural reviews ensuring performance, accessibility, and maintainability across teams. |
| Frontend Developer (Svelte) | Obligatorio | Defines product-level styling architecture for Svelte applications: evaluates CSS-in-JS approaches vs Svelte native styling, establishes design token standards, and sets component styling guidelines. Conducts reviews ensuring consistent, performant, and accessible UI across all teams. |
| Frontend Developer (Vue) | Obligatorio | Defines product-level CSS-in-JS architecture for Vue applications: evaluates styling strategies (SFC scoped vs CSS-in-JS libraries), establishes design token governance, and sets component API standards. Conducts architectural reviews ensuring scalable, accessible, and performant styling across teams. |
| Rol | Obligatorio | Descripción |
|---|---|---|
| Frontend Developer (React) | Obligatorio | Defines CSS architecture strategy for the React application ecosystem: choosing between Tailwind CSS, CSS Modules and styled-components considering Server Components compatibility. Designs zero-runtime solutions for SSR, standardizes design tokens and theming across the organization. |
| Frontend Developer (Svelte) | Obligatorio | Defines strategy for choosing between Svelte scoped styles, Tailwind CSS, and CSS-in-JS solutions at the organizational level. Researches performance of different styling approaches in the Svelte compiler context, develops migration recommendations between styling systems. |
| Frontend Developer (Vue) | Obligatorio | Defines styling strategy for company's Vue ecosystem — zero-runtime CSS-in-JS through UnoCSS, atomic CSS approach with Tailwind, design token integration. Researches and introduces advanced approaches — CSS Layers, Container Queries, View Transitions API in Vue components. |