Run any Skill in Manus with one click

boss-css-authoring

Stars4

Forks0

UpdatedFebruary 22, 2026 at 05:42

Boss CSS authoring conventions and style guidelines. Use when writing or reviewing $$ props, tokens, pseudos, @at, or className usage.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

wintercounter

wintercounter/boss

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web DevelopersComputer and Mathematical Occupations·SOC 15-1254

SKILL.md

readonly

name	boss-css-authoring
description	Boss CSS authoring conventions and style guidelines. Use when writing or reviewing $$ props, tokens, pseudos, @at, or className usage.
license	MIT
metadata	{"author":"boss-css","version":"0.1.0"}

Goal

Apply Boss CSS props cleanly with tokens and selectors.

Guidance

Prefer $$ props for structured styles over raw className strings.
Use token keys (for example color="primary") when tokens exist.
Use pseudos and @at for state and breakpoints instead of ad-hoc selectors.
In classname-first, pass dynamic values as functions (prop={() => value}).
In classname-first, return $$.token.* from dynamic functions when using tokens.
Use child for nested selectors instead of manual selector strings.
Prefer unitless values (padding:12). Use _ for spaces (padding:10_20).
Avoid hardcoded default unit suffixes in class tokens (border:1_solid, not border:1px_solid).
Prefer arrays for shorthands (padding={[0, 10]}).

References

See .bo$$/LLMS.md for live tokens, pseudos, and breakpoints.

More from this repository

same repository

boss-css-bosswind

wintercounter/boss

Bosswind shorthand preferences. Use when Bosswind is enabled and you want concise, Tailwind-like tokens.

2026-02-224

boss-css-boundaries

wintercounter/boss

CSS boundary rules and .boss.css behavior. Use when adjusting CSS scoping or boundary outputs.

2026-02-224

boss-css-breakpoints

wintercounter/boss

Breakpoint and media shorthand guidance. Use when picking responsive keys or authoring at/mobile styles.

2026-02-224

boss-css-classname-only

wintercounter/boss

Classname-only mode guidance. Use when running classname-only strategy or migrating from utility classes.

2026-02-224

boss-css-classname

wintercounter/boss

Classname syntax and shorthands. Use when writing className strings or converting from CSS.

2026-02-224

boss-css-compile-pruning

wintercounter/boss

How to keep compile output runtime-free. Use when you want compile to prune Boss runtime imports.

2026-02-224

name	boss-css-authoring
description	Boss CSS authoring conventions and style guidelines. Use when writing or reviewing $$ props, tokens, pseudos, @at, or className usage.
license	MIT
metadata	{"author":"boss-css","version":"0.1.0"}

Goal

Apply Boss CSS props cleanly with tokens and selectors.

Guidance

Prefer $$ props for structured styles over raw className strings.
Use token keys (for example color="primary") when tokens exist.
Use pseudos and @at for state and breakpoints instead of ad-hoc selectors.
In classname-first, pass dynamic values as functions (prop={() => value}).
In classname-first, return $$.token.* from dynamic functions when using tokens.
Use child for nested selectors instead of manual selector strings.
Prefer unitless values (padding:12). Use _ for spaces (padding:10_20).
Avoid hardcoded default unit suffixes in class tokens (border:1_solid, not border:1px_solid).
Prefer arrays for shorthands (padding={[0, 10]}).

References

See .bo$$/LLMS.md for live tokens, pseudos, and breakpoints.