Nine source-backed lessons on pattern detection, minimal editing, package validation, privacy boundaries and evidence-first review.
Latest article
Trace how the draft, mode choice and preservation constraints lead to either findings or a rewrite, and distinguish instructions from enforcement.
By publication date
01 → 09
Trace how the draft, mode choice and preservation constraints lead to either findings or a rewrite, and distinguish instructions from enforcement.
Compare explicit pattern findings with general style guidance and editorial judgment, without confusing pattern detection with authorship detection.
Distinguish a host integration from a source package build, avoid blind global installation and account for a Windows validator limitation.
Use one synthetic paragraph to test detection and minimal editing while protecting dates, technical details and deliberate uncertainty.
Design a small review aid that anchors findings to draft spans and protects facts, without turning stylistic preferences into automatic rewriting.
Learn what the writing skill edits, what its detection report should contain, and why neither mode proves whether a person or model wrote a text.
Design a clean baseline for editing quality and account for self-review, output length and human repair without inventing a benchmark score.
Separate the skills-only package from its host’s data processing and prevent stylistic edits from changing confidential or regulated meaning.
Walk through validate_source and validate_build, including seven isolated cases and the distinction between validating a directory and inspecting ZIP contents.
