wewrite-style

Original：🇨🇳 Chinese

Translated

WeWrite Style Settings Module: First-time onboarding guide + resetting WeChat Official Account writing style configuration (style.yaml). Trigger keywords: reset style, modify style configuration, set WeChat Official Account style, first-time WeChat Official Account setup, change writing persona, modify layout theme preferences. It is also automatically activated by the main entry wewrite when style.yaml is missing. It should NOT be triggered by general "change writing style" or "polish" requests — those are editing actions, not configuration actions.

5installs

Sourceimraywang/wewrite

Added on2026-10-09

NPX Install

npx skill4agent add imraywang/wewrite wewrite-style

SKILL.md Content (Chinese)

View Translation Comparison →

wewrite-style — Style Settings / Onboard

Runtime Conventions

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

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".