Installation
Both plugins are distributed through the Claude Code plugin marketplace under the shawn-sandy namespace.
Install both plugins
Section titled “Install both plugins”-
Add the marketplace to your Claude Code session:
/plugin marketplace add shawn-sandy/agentic-acss-plugins -
Install acss-kit (components + themes):
/plugin install acss-kit@shawn-sandy-agentic-acss-plugins -
Install acss-utilities (atomic CSS + token bridge):
/plugin install acss-utilities@shawn-sandy-agentic-acss-plugins -
Verify the install — list available components to confirm acss-kit is active:
/kit-listYou should see the full component catalogue grouped by category.
Install only acss-kit
Section titled “Install only acss-kit”If you don’t need utility classes:
/plugin marketplace add shawn-sandy/agentic-acss-plugins/plugin install acss-kit@shawn-sandy-agentic-acss-pluginsInstall only acss-utilities
Section titled “Install only acss-utilities”If you have an existing component system and just want the utility classes:
/plugin marketplace add shawn-sandy/agentic-acss-plugins/plugin install acss-utilities@shawn-sandy-agentic-acss-pluginsVerify installation
Section titled “Verify installation”After installing, confirm the slash commands are available:
/kit-list # lists all available components/utility-list # lists all utility families and classesBoth commands are read-only and make no changes to your project — they’re safe to run at any time to explore what’s available.
Updating the plugins
Section titled “Updating the plugins”To get the latest version of a plugin:
/plugin update acss-kit@shawn-sandy-agentic-acss-plugins/plugin update acss-utilities@shawn-sandy-agentic-acss-pluginsLocal development install
Section titled “Local development install”If you’ve cloned the plugin repo and want to test local changes without publishing:
# From the acss-plugins repo rootclaude --plugin-dir ./plugins/acss-kitThis loads acss-kit directly from the local directory, bypassing the marketplace.