Edit for Readability

Project Context

• personal config directory: !bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"
• project .han/config.md: !cat .han/config.md 2>/dev/null || echo ""

As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md probe supplies content, apply it per config-rule.md, which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.

Edit for Readability

Take a target the user already has and rewrite its prose against the shared readability standard, preserving every fact. The judgment-heavy rewrite belongs to the han-communication:readability-editor agent; this skill's job is to resolve what the target is, dispatch the editor over it, and deliver the result.

Operating principles

• This is the standalone readability pass. The readability standard applies at generation time, so synthesis skills (research, project-documentation, investigate, code-review, and the rest) already bake it into their own output. This skill exists for the gap the standard names explicitly: a file or draft that was written or hand-edited outside one of those skills, and so was never checked against the standard. Reach for it on an existing target, not as a step inside another skill.
• Fidelity outranks readability on every conflict the user did not create. Every claim, quantity, named entity, and stated condition or qualifier in the target survives the rewrite with its precision intact. The editor enforces this and returns a fact-preservation ledger; the skill's job is to pass the whole target through and surface that ledger, never to let a fact be dropped for the sake of a smoother sentence. A shape the user asked for is the one thing that moves this, and never for a fact whose loss would change what the reader does next.
• Prose only. The editor rewrites prose regions and leaves code fences, diagram bodies, rendered markup, and citation identifiers (A1, [F5], and the like) byte-for-byte unchanged. Do not ask it to touch anything else.
• The editor holds the standard. Do not restate the rubric criteria here or inline the rule text into the dispatch. The editor reads its own co-located canonical rule and applies the current standard, so this skill never drifts from readability-rule.md.

Step 1: Resolve the target and the reader

Determine which kind of target the request names, because the rest of the workflow depends on it. Read the user's request and the conversation, and classify the target into exactly one of:

| Target kind | How you know | What the target is |