gerillass 2.0.0 → 2.0.1

package/README.md

@@ -8,6 +8,8 @@
 
 [Gerillass](https://gerillass.com) is a library built on top of [Sass (Syntactically Awesome Style Sheets)](https://sass-lang.com/) to give you flexibility for your projects and accelerate your performance and creativity.
 
+It is also built to be read by coding agents. Every mixin and function ships with a machine-readable manifest, and the test suite compiles every documented example and asserts every documented refusal. So what the manifest says the library does is what the library does. The docs cannot drift away from the code, because a stale manifest fails the build.
+
 Many of the utilities that come with Gerillass are the solutions I have come up with for the challenges I have faced as a frontend developer over the years. These solutions have been shaped by the inspiration of other popular libraries and frameworks like [Bourbon](https://www.bourbon.io/), [Susy](https://www.oddbird.net/), [Scut](https://github.com/davidtheclark/scut), [Bootstrap](https://getbootstrap.com/), etc. over time and helped me create Gerillass.
 
 Hope you’ll enjoy using it!
@@ -53,7 +55,7 @@ Or with Yarn:
 
     yarn add gerillass --dev
 
-Then load it. If your setup resolves packages from **node_modules** — Vite, webpack, Next.js and most modern bundlers do — this is all you need:
+Then load it. If your setup resolves packages from **node_modules**, which Vite, webpack, Next.js and most modern bundlers do, this is all you need:
 
     @use 'gerillass' as *;
 
@@ -139,7 +141,7 @@ Then:
 
 ### Using with Grunt
 
-Use `grunt-sass` with Dart Sass as the implementation. The option here is **`loadPaths`** as well — not `loadPath`, and not `includePaths`.
+Use `grunt-sass` with Dart Sass as the implementation. The option here is **`loadPaths`** as well, not `loadPath`, and not `includePaths`.
 
     module.exports = function (grunt) {
       grunt.loadNpmTasks("grunt-sass");
@@ -188,25 +190,31 @@ Including to the project:
 
 ## Using Gerillass with an AI coding agent
 
-Gerillass ships two files that let a coding agent use the library correctly instead of guessing at it. Both are inside the installed package, so an agent working in your project can read them straight out of `node_modules/gerillass/`.
+A library this size has no training data behind it, so an agent asked to use Gerillass will guess at the argument forms and get them wrong. Two files ship with the package to stop that. Both live inside the installed package, so an agent working in your project can read them straight out of `node_modules/gerillass/`.
 
 **`gerillass.json`** describes every mixin and function: its signature, what each argument accepts, examples that compile, and inputs that are refused.
 
     const api = require("gerillass/gerillass.json");
 
-**`SKILL.md`** is a written guide generated from that manifest — how to load the library, the full catalogue, and the argument forms that are easy to get wrong. If your agent supports [Agent Skills](https://code.claude.com/docs/en/skills), copy it into your skills folder:
+**`SKILL.md`** is a written guide generated from that manifest. It covers how to load the library, the full catalogue, and the argument forms that are easy to get wrong. If your agent supports [Agent Skills](https://code.claude.com/docs/en/skills), copy it into your skills folder:
 
     mkdir -p .claude/skills/gerillass
     cp node_modules/gerillass/SKILL.md .claude/skills/gerillass/
 
 Otherwise, point your agent at the file and it will read it as plain Markdown.
 
-Neither file is generated by hand: signatures are parsed from the Sass sources, and every example and refusal in the manifest is executed by the test suite. What the manifest says the library does is what the library does.
+### Why you can trust what they say
+
+Neither file is written by hand. Signatures are parsed from the Sass sources, and the semantics come from a separate set of notes, so nobody can describe a mixin that does not exist.
+
+The part that matters is what happens next. The test suite takes every example in the manifest and compiles it. It takes every input the manifest claims is refused and checks that the library really does refuse it, with its own error message rather than an internal Sass one. It runs every example a second time under the `gls-` prefixed name and requires byte-identical CSS. And it fails the build if either generated file is out of date.
+
+So the manifest cannot claim behaviour the library does not have. That is the whole point of it. Documentation drifts away from code in most projects, quietly, and an agent reading stale docs writes code that does not work. Here it cannot happen without turning the test suite red first.
 
 
 ## Three ways to call the same mixin
 
-None of them is required — pick whichever reads best in your project, and stay with it in a given file.
+None of them is required. Pick whichever reads best in your project, and stay with it in a given file.
 
 **Bare.** The shortest, and fine unless another library defines the same name.
 

package/SKILL.md

@@ -156,8 +156,8 @@ a dropped declaration rather than an error.
 
 ## Functions
 
-Called like normal Sass functions. The two leading underscores mark them as
-functions rather than mixins; they are public API.
+Called like normal Sass functions, with no `@include`. They are public API,
+and camelCase is what tells them apart from the kebab-case mixins above.
 
 | Signature | What it does |
 |---|---|

package/gerillass.json

@@ -1,6 +1,6 @@
 {
   "name": "gerillass",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "description": "Gerillass is an open-source toolkit that contains a set of Sass mixins to help designers and developers to create better, faster and consistent user interfaces.",
   "homepage": "https://gerillass.com",
   "documentation": "https://docs.gerillass.com",

package/package.json

@@ -16,7 +16,7 @@
     }
   },
   "license": "Apache-2.0",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/selfishprimate/gerillass.git"
@@ -40,7 +40,7 @@
     "sass-tool-set"
   ],
   "scripts": {
-    "manifest": "node tools/build-manifest.js && node tools/build-skill.js",
+    "manifest": "node tools/build-manifest.js && node tools/build-skill.js && node tools/build-llms-txt.js",
     "test": "jest"
   },
   "devDependencies": {