Individual skill

sass-pro

Write maintainable Sass/SCSS: modules (@use), mixins, functions, architecture (7-1), and build integration. Use when styling with Sass in any project.

skills/sass-pro/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Sass Pro

A practical guide to modern Sass (SCSS syntax): the module system (`@use`/`@forward`), mixins vs functions vs extends, the 7-1 architecture, and Dart Sass build integration.

## Overview

Modern Sass = **Dart Sass** + the **module system**. The old `@import` is deprecated: `@use` loads a module once with a namespace, `@forward` re-exports. This killed the biggest Sass footguns (global namespace collisions, duplicate output, spooky import order). If your codebase still uses `@import`, migration is the highest-value Sass work you can do.

## When to use

- Large stylesheets needing variables, mixins, and organization.
- Design-system token layers (colors, spacing, typography) shared across projects.
- Projects where CSS custom properties alone aren't enough (loops, color math at build time).
- Migrating legacy `@import` Sass to the module system.