This skill addresses .astro-file styling specifically (scoping semantics unique to Astro components), not the UI framework setup itself (astro-integrations) or SOLID file-organization rules for style files (solid-astro).
Astro Styling
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Analyze existing styles, integrations, and patterns
- fuse-ai-pilot:research-expert - Verify latest Astro/Tailwind/UnoCSS docs via Context7/Exa
- mcp__context7__query-docs - Check integration compatibility with Astro 7
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
When to Use
- Styling
.astro components with component-scoped CSS
- Setting up Tailwind CSS or UnoCSS in an Astro project
- Using CSS Modules for framework-agnostic scoping
- Applying global base styles (reset, fonts, variables)
- Using
class:list for conditional class application
- Adding Sass/SCSS via Vite preprocessors
Styling Options
| Method |
Scope |
When to Use |
<style> in .astro |
Component |
Default — scoped to component |
<style is:global> |
Global |
Base styles, resets |
CSS Modules .module.css |
Component |
Framework components (React, Vue) |
| Tailwind CSS |
Utility |
Rapid UI development |
| UnoCSS |
Utility |
Lightweight, configurable atomic CSS |
| Sass/SCSS |
Component/Global |
Advanced features, variables, mixins |
Reference Guide
Concepts
| Topic |
Reference |
When to Consult |
| Scoped CSS |
scoped-css.md |
Component styling |
| CSS Modules |
css-modules.md |
Framework components |
| Global styles |
global-styles.md |
Resets, base styles |
| Tailwind |
tailwind.md |
Utility-first CSS |
| UnoCSS |
unocss.md |
Atomic CSS engine |
| Sass/SCSS |
sass.md |
Preprocessor features |
| CSS Variables |
css-variables.md |
Design tokens, themes |
Templates
| Template |
When to Use |
| scoped-component.md |
Component with scoped + conditional classes |
| tailwind-setup.md |
Full Tailwind CSS project setup |
| unocss-setup.md |
Full UnoCSS project setup |
Best Practices
- Prefer scoped styles — Use
<style> in .astro files by default
- Global styles in layouts — Apply resets and base styles in root layout
- CSS variables for themes — Define design tokens as custom properties
- Avoid
is:global in components — Reserve for layouts and global files
- class:list over ternaries — More readable conditional class logic
Forbidden
- Writing inline styles for layout/theme — use CSS classes instead
- Using
is:global inside non-layout components
- Importing CSS in multiple components without CSS Modules
- Mixing Tailwind and custom class naming without a clear convention
1---2name: astro-styling3description: Use when styling Astro components — scoped CSS, CSS Modules, Tailwind CSS, UnoCSS, Sass, the class:list directive, or global styles.4versions:5 astro: "7"6user-invocable: true7references: references/scoped-css.md, references/css-modules.md, references/global-styles.md, references/tailwind.md, references/unocss.md, references/sass.md, references/css-variables.md, references/templates/scoped-component.md, references/templates/tailwind-setup.md, references/templates/unocss-setup.md8related-skills: astro-7, astro-integrations, solid-astro9metadata:10 source: https://skillmd.com/skills/fusengine/astro-styling11---1213<objective>14Covers styling options for `.astro` components: default component-scoped `<style>`, `<style is:global>` for base styles/resets (reserved for layouts), CSS Modules (`.module.css`) for framework components (React, Vue), Tailwind CSS, UnoCSS, and Sass/SCSS via Vite preprocessors. Includes the `class:list` directive for conditional class application and CSS custom properties for design tokens/themes.1516This skill addresses `.astro`-file styling specifically (scoping semantics unique to Astro components), not the UI framework setup itself (astro-integrations) or SOLID file-organization rules for style files (solid-astro).17</objective>1819# Astro Styling2021## Agent Workflow (MANDATORY)2223Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`:24251. **fuse-ai-pilot:explore-codebase** - Analyze existing styles, integrations, and patterns262. **fuse-ai-pilot:research-expert** - Verify latest Astro/Tailwind/UnoCSS docs via Context7/Exa273. **mcp__context7__query-docs** - Check integration compatibility with Astro 72829After implementation, run **fuse-ai-pilot:sniper** for validation.3031---3233## Overview3435### When to Use3637- Styling `.astro` components with component-scoped CSS38- Setting up Tailwind CSS or UnoCSS in an Astro project39- Using CSS Modules for framework-agnostic scoping40- Applying global base styles (reset, fonts, variables)41- Using `class:list` for conditional class application42- Adding Sass/SCSS via Vite preprocessors4344### Styling Options4546| Method | Scope | When to Use |47|--------|-------|-------------|48| `<style>` in `.astro` | Component | Default — scoped to component |49| `<style is:global>` | Global | Base styles, resets |50| CSS Modules `.module.css` | Component | Framework components (React, Vue) |51| Tailwind CSS | Utility | Rapid UI development |52| UnoCSS | Utility | Lightweight, configurable atomic CSS |53| Sass/SCSS | Component/Global | Advanced features, variables, mixins |5455---5657## Reference Guide5859### Concepts6061| Topic | Reference | When to Consult |62|-------|-----------|-----------------|63| Scoped CSS | [scoped-css.md](references/scoped-css.md) | Component styling |64| CSS Modules | [css-modules.md](references/css-modules.md) | Framework components |65| Global styles | [global-styles.md](references/global-styles.md) | Resets, base styles |66| Tailwind | [tailwind.md](references/tailwind.md) | Utility-first CSS |67| UnoCSS | [unocss.md](references/unocss.md) | Atomic CSS engine |68| Sass/SCSS | [sass.md](references/sass.md) | Preprocessor features |69| CSS Variables | [css-variables.md](references/css-variables.md) | Design tokens, themes |7071### Templates7273| Template | When to Use |74|----------|-------------|75| [scoped-component.md](references/templates/scoped-component.md) | Component with scoped + conditional classes |76| [tailwind-setup.md](references/templates/tailwind-setup.md) | Full Tailwind CSS project setup |77| [unocss-setup.md](references/templates/unocss-setup.md) | Full UnoCSS project setup |7879---8081## Best Practices82831. **Prefer scoped styles** — Use `<style>` in `.astro` files by default842. **Global styles in layouts** — Apply resets and base styles in root layout853. **CSS variables for themes** — Define design tokens as custom properties864. **Avoid `is:global` in components** — Reserve for layouts and global files875. **class:list over ternaries** — More readable conditional class logic8889---9091## Forbidden9293- Writing inline styles for layout/theme — use CSS classes instead94- Using `is:global` inside non-layout components95- Importing CSS in multiple components without CSS Modules96- Mixing Tailwind and custom class naming without a clear convention