Skill

/ss-resolve

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

One skill from styleseed.

shell

$ npx -y skills add bitjaru/styleseed --skill ss-resolve --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/ss-resolve

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

Stats

Stars857

Forks75

LanguageTypeScript

LicenseMIT

Ships with styleseed

@bitjaru Get the whole plugin, auto-invoked

More in this plugin

What is in the file

Measured from the ss-resolve.SKILL.md below.

180 words, about a 1 minute read.
Organized into 1 section.
Includes 2 worked examples.
Ships with 21 other skills in this plugin, and is the 22nd longest of them.

SKILL.md

ss-resolve.SKILL.md

---
name: ss-resolve
description: 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.
---

# Resolve effective StyleSeed context

Use the bundled `scripts/resolve-context.mjs`; do not hand-compose the rule stack.

1. Read `STYLESEED.md` when it exists. Confirm missing required selections with the user.
2. Keep the working directory at the user's project root. Invoke the script by its installed
path; do not `cd` into the skill directory. Prefer `--from-lock STYLESEED.md`; explicit flags
override lock values.
3. Read the emitted `.styleseed/effective-rules.md` before building.
4. Preserve `.styleseed/manifest.json`. It records selections, source hashes, and the bundle hash
for updates and reproducibility.
5. Use `--check` to detect context drift without rewriting files.

```bash
node <installed-ss-resolve>/scripts/resolve-context.mjs \
--from-lock STYLESEED.md \
--agent codex
```

Without a lock:

```bash
node <installed-ss-resolve>/scripts/resolve-context.mjs \
--agent claude \
--grammar operations-console \
--adapter product-ui \
--domain saas \
--page dashboard \
--profile swiss
```

Use `--list` to print supported IDs. The default output directory is `.styleseed/` in the
project root. For a project-local reference grammar, pass `reference:<slug>` and ensure
`.styleseed/rulesets/<slug>/RULESET.md` exists.

Do not load `llms-full.txt` after a bundle resolves successfully. Load a larger source document
only when the bundle names an unresolved ambiguity that requires it.