Resolve effective StyleSeed context
Use the bundled scripts/resolve-context.mjs; do not hand-compose the rule stack.
- Read
STYLESEED.mdwhen 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
cdinto the skill directory. Prefer--from-lock STYLESEED.md; explicit flags override lock values. - Read the emitted
.styleseed/effective-rules.mdbefore building. - Preserve
.styleseed/manifest.json. It records selections, source hashes, and the bundle hash for updates and reproducibility. - Use
--checkto detect context drift without rewriting files.
node <installed-ss-resolve>/scripts/resolve-context.mjs \
--from-lock STYLESEED.md \
--agent codex
Without a lock:
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.