Compile a small, deterministic StyleSeed rule bundle for one agent, output grammar, surface adapter, domain, page type, and optional profile. Use before setup or build, when STYLESEED.md changes, when updating StyleSeed, or whenever an agent would otherwise load the full rule handbook.
SkillScore87Maintained
Automatic
◆Frontend / UI pack
Last verified 8/17/2026
What it changes
Passed 18 of 21 test cases with the skill, and 8 of 21 without it.
Without skill39%
With skill87%
Checks it passed that the model alone missed
Passes --agent codex to the resolution script
Passes the --all flag to scripts/resolve-context.mjs
Passes the --list flag to scripts/resolve-context.mjs
and 11 more in the full report
11 fixed9 passed either way3 still failing0 broke
Pass-rate lift
+48 pp
Tokens
-15%
Agent turns
0%
Response time
-67%
Model gemini-3.6-flashMeasured 8/17/2026v320 of 23 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
I just ran context resolution on a legacy single-artifact repository that uses a STYLESEED.md lock file. Which generated file should I inspect to review the effective rules bundle?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies .styleseed/effective-rules.md as the generated rules bundle location
Missed
Passed
case-04 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md66 lines12 filesincludes scripts
Resolve effective StyleSeed context
Use the bundled scripts/resolve-context.mjs; do not hand-compose the rule stack.
Read STYLESEED.md when it exists. Confirm missing required selections with the user.
Keep the working directory at the user's project root. Invoke the script by its installed
path; do not cd into the skill directory.
Legacy single-artifact projects should prefer --from-lock STYLESEED.md. Registry projects use
.styleseed/project.json plus .styleseed/artifacts/*.json and must resolve with --artifact
or --all; in registry mode, edit project-owned config instead of passing selection overrides.
Read the emitted bundle before building: legacy writes .styleseed/effective-rules.md; registry
writes .styleseed/bundles/<artifact-id>.md.
Preserve the manifest output: legacy uses .styleseed/manifest.json; registry uses
.styleseed/manifests/<artifact-id>.json.
Use --check to detect context drift without rewriting files.