wewrite-style

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

wewrite-style — 风格设置 / Onboard

wewrite-style — Style Settings / Onboard

运行约定

Runtime Conventions

CLI：确定性操作走
```
wewrite
```
命令（需在 PATH；缺失则引导
```
uv tool install wewrite
```
，或在仓库里
```
bash install.sh
```
）。
{home}：用户状态目录 =
```
$WEWRITE_HOME
```
或
```
~/.wewrite
```
（
```
wewrite home
```
可查）。config/style/history/playbook/output/exemplars 全在 {home}，不在仓库；references 文档中的状态路径同此约定。
读取: <路径>
= 用文件读取工具真实读完该文件再继续，不是注释。
references/：本 skill 自带
```
{skill_dir}/references/
```
；references 文档内的
```
{skill_dir}
```
即本 skill 目录。
本模块是交互式的（需要问用户问题），不受主管道"全自动"约束。

CLI: Deterministic operations use the
```
wewrite
```
command (must be in PATH; if missing, guide users to run
```
uv tool install wewrite
```
, or run
```
bash install.sh
```
in the repository).
{home}: User state directory =
```
$WEWRITE_HOME
```
or
```
~/.wewrite
```
(can be checked with
```
wewrite home
```
). All config/style/history/playbook/output/exemplars are stored in {home}, not in the repository; state paths in references documents follow the same convention.
Read: <path>
= Actually read the entire file using a file reading tool before proceeding, this is not a comment.
references/: This skill comes with
```
{skill_dir}/references/
```
;
```
{skill_dir}
```
in references documents refers to the directory of this skill.
This module is interactive (requires asking user questions) and is not bound by the "fully automatic" constraint of the main pipeline.

执行

Execution

触发场景：

主入口 Step 1 发现
```
{home}/style.yaml
```
不存在（首次使用）
用户说"重新设置风格"、"修改配置"

两种场景都执行：

读取: {skill_dir}/references/onboard.md

按 onboard.md 的 Phase 1-4 完成：交互式收集信息 → 生成

{home}/style.yaml

→ 可选 Playbook 建库 → 试跑询问。重设风格时以现有 style.yaml 为基线，只改用户要改的字段，改完展示全文让用户确认。

完成后：若由主管道激活（首次 onboard），回到主管道 Step 1 继续；若用户单独触发，告知"配置已更新，下次写作自动生效"。

Trigger Scenarios:

The main entry Step 1 detects that
```
{home}/style.yaml
```
does not exist (first-time use)
User says "reset style", "modify configuration"

Both scenarios execute the following:

Read: {skill_dir}/references/onboard.md

Follow Phase 1-4 in onboard.md to complete: interactively collect information → generate

{home}/style.yaml

→ optional Playbook library creation → trial run inquiry. When resetting the style, use the existing style.yaml as the baseline, only modify the fields that the user wants to change, and display the full content for user confirmation after modification.

After completion: If activated by the main pipeline (first-time onboard), return to main pipeline Step 1 to continue; if triggered separately by the user, inform the user that "Configuration has been updated and will take effect automatically for the next writing session".