AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Astro Styling

skill-fusengine-agents-astro-styling · by fusengine

Use when styling Astro components with scoped CSS, CSS Modules, Tailwind CSS, UnoCSS, or Sass. Covers class:list directive, global styles, CSS custom properties, and Vite-powered preprocessors.

No reviews yet
0 installs
34 views
0.0% view→install

Install

$ agentstack add skill-fusengine-agents-astro-styling

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-fusengine-agents-astro-styling)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Astro Styling? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Astro Styling

Agent Workflow (MANDATORY)

Before ANY implementation, use TeamCreate to spawn 3 agents:

  1. fuse-ai-pilot:explore-codebase - Analyze existing styles, integrations, and patterns
  2. fuse-ai-pilot:research-expert - Verify latest Astro/Tailwind/UnoCSS docs via Context7/Exa
  3. mcp__context7__query-docs - Check integration compatibility with Astro 6

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 | |--------|-------|-------------| | ` in .astro | Component | Default — scoped to component | | | 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](references/scoped-css.md) | Component styling | | CSS Modules | [css-modules.md](references/css-modules.md) | Framework components | | Global styles | [global-styles.md](references/global-styles.md) | Resets, base styles | | Tailwind | [tailwind.md](references/tailwind.md) | Utility-first CSS | | UnoCSS | [unocss.md](references/unocss.md) | Atomic CSS engine | | Sass/SCSS | [sass.md](references/sass.md) | Preprocessor features | | CSS Variables | [css-variables.md](references/css-variables.md) | Design tokens, themes |

Templates

| Template | When to Use | |----------|-------------| | [scoped-component.md](references/templates/scoped-component.md) | Component with scoped + conditional classes | | [tailwind-setup.md](references/templates/tailwind-setup.md) | Full Tailwind CSS project setup | | [unocss-setup.md](references/templates/unocss-setup.md) | Full UnoCSS project setup |


Best Practices

  1. Prefer scoped styles — Use ` in .astro` files by default
  2. Global styles in layouts — Apply resets and base styles in root layout
  3. CSS variables for themes — Define design tokens as custom properties
  4. Avoid is:global in components — Reserve for layouts and global files
  5. 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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.