Gerillass skill
A Sass mixin library with an argument manifest and a skill so an agent writes SCSS without guessing
- 171 ★ on the repository
- Last commit
Minimal access
Why this level
- The skill only explains the library API to the agent, but the agent will edit your style files
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/gerillassDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill only explains the library API to the agent, but the agent will edit your style files
This is third-party code. Review the repository files before installing.
What it does
Gerillass is a Sass library of 55 mixins and 24 functions that emit CSS from semantic declarations. There is no runtime and no utility classes, so styles stay in your stylesheet and markup stays clean. The `gerillass` package installs from npm, loads with `@use 'gerillass' as *;` and works with Vite, webpack, Parcel, Next.js, Angular, Gulp and Grunt. A Ruby gem covers Rails and Jekyll. Two files ship for agents. `gerillass.json` describes every mixin and function: signature, accepted argument values, examples that compile and inputs that are refused. `SKILL.md` is generated from that manifest and covers loading, the catalogue and the argument forms that are easy to get wrong. You copy it into `.claude/skills/gerillass/` and the agent picks it up when working on SCSS. The author verifies the docs with tests. The suite compiles every manifest example, checks that refused inputs really raise the library own error, and compares the same call under the `gls-` prefix byte for byte. If the docs drift from the code, the build fails.
Who it is for. Front-end developers on Sass who ask Claude Code or Cursor to write SCSS on top of a ready mixin library.
Good fit when
- The agent keeps getting mixin arguments wrong and needs a manifest with working examples
- A Vite or Next.js project moves to Dart Sass and loads `pkg:gerillass` through the package importer
- You want styles with no utility classes and clean markup
- A Rails or Jekyll project loads styles from the gem and copies the skill from the `bundle info gerillass --path` location
Not a fit when
- The project is on LibSass or Node Sass: since 1.3.0 only Dart Sass is supported
- You want ready-styled components: the library emits CSS from declarations and ships no styled blocks
- Your stack has no Sass at all, for example Tailwind without a preprocessor
Example request
Rewrite the card block in styles/cards.scss with Gerillass mixins and check gerillass.json instead of guessing argumentsLimitations
The skill works only in projects with `gerillass` installed and does not install the library itself. Since 1.3.0 LibSass is unsupported and Dart Sass is required, with Dart Sass 1.71.0 or newer for `pkg:` imports. Parcel reads the `main` field in `package.json` as a build target, so it must be removed or the app will not build. The author verified the bundler recipes on version 1.5.0. The `SKILL.md` file arrives with the package and changes with versions, so the copy in `.claude/skills/` has to be re-copied after an update.
How to disable. Delete the `.claude/skills/gerillass/` folder. The package itself is removed with `npm uninstall gerillass`, and the `@use` line in your styles has to be replaced.
FAQ
How do I set up Gerillass for Claude Code?
Run `npm install gerillass --save-dev`, then `mkdir -p .claude/skills/gerillass` and `cp node_modules/gerillass/SKILL.md .claude/skills/gerillass/`. In a Ruby project `bundle info gerillass --path` gives the file location.
What is inside gerillass.json?
A description of every mixin and function: signature, accepted argument values, compiling examples and refused inputs. Code can read it with `require("gerillass/gerillass.json")`.
Why should an agent not rely on memory for the docs?
The library has little training data behind it, so an agent starts guessing argument forms. The manifest and skill are generated from the Sass sources and tests compile every example, so they match the code.
Does Gerillass work with LibSass?
No. LibSass and Node Sass support ended with version 1.3.0 and Dart Sass is required. `pkg:` imports need Dart Sass 1.71.0 or newer.
What is the gls- prefix?
The same mixins are available under names with the `gls-` prefix. Tests require the prefixed call to produce byte-identical CSS.
Discussion
No questions or reviews yet.
Related
SkillsA skill gives an agent modern CSS techniques: one declaration instead of piles of breakpoints, and a CSS feature before a script.
Hand-built skills for Angular, React, Next.js, TypeScript and Django plus six community ones for Java, Elixir and Electron
julianromli/ai-skills
ai-skills
A collection of 31 skills for Claude Code and other agents: interfaces, React, Postgres, code review, SEO and browser automation
A skill for building high-craft interfaces: landing pages, dashboards and mobile screens on four routes, with a cheapness check
A deterministic HTML and CSS check for 73 tells of generated UI, with auto-fixes and the /gesso-critique command.
A skill builds and debugs GLSL shaders from reusable blocks, bundles dependencies into one file and checks WebGL2-oriented code.
README in short
The page opens with the LibSass drop notice for version 1.3.0, then covers the npm install and recipes for Vite, webpack, Parcel, Next.js, Angular, Gulp, Grunt and Ruby. A dedicated section explains using the library with an agent, three ways to call one mixin and vendor prefix support. Testing and contribution close the page.