ss-resolve

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Resolve effective StyleSeed context

解析有效的StyleSeed上下文

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 \
  --recipe enterprise-workbench \
  --palette cobalt-instrument \
  --key-color "#175CD3" \
  --palette-character balanced \
  --palette-mode light \
  --palette-harmony auto \
  --surface-temperature cool \
  --profile swiss
Use
--list
to print supported IDs.
--recipe auto
maps the selected grammar to a maintained default;
--palette auto
maps that recipe to a contrast-verified semantic palette. Pass explicit values when the product needs a different morphology or color posture. 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.
When a key color is present in flags or the lock, the resolver uses the shared OKLCH generator and writes
.styleseed/palette.json
plus
.styleseed/palette.css
. The manifest records the generation inputs. The maintained recipe still supplies product posture and semantic restrictions; its fixed hex values become fallbacks rather than overriding the generated system.
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.
使用捆绑的
scripts/resolve-context.mjs
脚本;请勿手动组合规则栈。
  1. STYLESEED.md
    存在时读取该文件。若缺少必要选项,请向用户确认。
  2. 工作目录保持在用户项目根目录。通过已安装路径调用脚本;请勿
    cd
    到skill目录。优先使用
    --from-lock STYLESEED.md
    ;显式标志会覆盖锁定文件中的值。
  3. 构建前读取生成的
    .styleseed/effective-rules.md
    文件。
  4. 保留
    .styleseed/manifest.json
    文件。它记录了选项选择、源哈希值和包哈希值,用于更新和可复现性。
  5. 使用
    --check
    检测上下文偏移,无需重写文件。
bash
node <installed-ss-resolve>/scripts/resolve-context.mjs \
  --from-lock STYLESEED.md \
  --agent codex
无锁定文件时:
bash
node <installed-ss-resolve>/scripts/resolve-context.mjs \
  --agent claude \
  --grammar operations-console \
  --adapter product-ui \
  --domain saas \
  --page dashboard \
  --recipe enterprise-workbench \
  --palette cobalt-instrument \
  --key-color "#175CD3" \
  --palette-character balanced \
  --palette-mode light \
  --palette-harmony auto \
  --surface-temperature cool \
  --profile swiss
使用
--list
打印支持的ID。
--recipe auto
会将所选语法映射到维护的默认配置;
--palette auto
会将该配置映射到经过对比度验证的语义调色板。当产品需要不同形态或色彩风格时,请传入显式值。默认输出目录为项目根目录下的
.styleseed/
。对于项目本地的参考语法,传入
reference:<slug>
并确保
.styleseed/rulesets/<slug>/RULESET.md
存在。
当标志或锁定文件中存在关键颜色时,解析器会使用共享的OKLCH生成器,并写入
.styleseed/palette.json
.styleseed/palette.css
。清单文件会记录生成输入。维护的配置仍会提供产品风格和语义限制;其固定的十六进制值将作为回退,而非覆盖生成的系统。
成功解析包后,请勿加载
llms-full.txt
。仅当包指出存在未解决的歧义且需要该文件时,才加载更大的源文档。