Input and Output
- Output: audits deliver only reports and revision plans; file changes are made after user approval
Execution Principles
Ruleset
Stance: senior architect's perspective, concise and accurate language, so readers read comfortably, directly, without redundancy. The ruleset is the only style yardstick: write only by it, audit only by it, do not report issues outside the set; when writing encounters cases the rules do not cover, judge by the stance; in audits do not use the stance as grounds for findings.
Prose:
- Conclusion first: give the conclusion before the basis, the important before the secondary
- Redundancy and repetition: delete anything whose removal loses no information: padded openings and endings, synonymous restatement, filler sentences, lists of near-synonyms
- Concreteness and verb usage: write verifiable facts and concrete verbs; for "perform / implement / make + noun" write the verb directly; without data do not fabricate, instead generalize but stay concrete
- Sentence and paragraph: split Chinese sentences over 60 characters; one point per paragraph; align the structure of parallel items
- Consistency and reference: one name for one concept throughout; refer by concrete names, not numbered aliases like "Plan 1" or dangling references like "it / this"
- Tone and moderation: declarative sentences state the claim directly with its basis; change hedging phrasing ("could we perhaps...") to statements; at most one hedge per sentence; omit honorifics where possible
- Punctuation width: punctuation follows the main language of its sentence, full-width for Chinese, half-width for English; exceptions inside code / URLs / numbers
- Full-width symbols: in prose use only regular full-width punctuation (，。；：？！（）); do not use full-width letters and digits (ＡＢＣ１２３) or full-width spaces
- Carrier selection: lists for itemized content, tables for data, diagrams only for relationships and flows; use Mermaid for document diagrams, ASCII diagrams only when rendering is unavailable
- No text-figure duplication: beside a figure keep only the conclusion, do not repeat information already in the figure
- ASCII diagram drawing: inside boxes use pure half-width, no Chinese inside boxes; leave complex alignment to tables
AI voice:
- Three-part summary: once the body is clear, do not restate it with "in summary"
- Bold addiction: keep bold only for scan-locating purposes (term definitions, warnings)
- List addiction: do not split into bullets what one sentence can say
- Fake dialogue: in non-dialogue genres do not write "you may ask" self Q&A
- Flattery and sales pitch: text gives the reader only information; delete opening flattery and marketing words; at most one exclamation mark in the whole text
- Decorative symbols: in prose do not use emoji, Unicode arrows, the dash "——", corner brackets 「」『』 or graphic symbols like ★ ● ▶; change parenthetical remarks to parentheses or commas
Workflow
To produce a new document, go to writing; to check an existing document, go to audit.
Writing
- Clarify the genre, audience, and delivery location
- Write according to the rule set
- Before delivery, self-check item by item against the rule set; for any artifact that must be written to a file, always run from the skill root
python3 tools/scan_fingerprints.py <产物>machine check; deliver only after hits are cleared to zero
Audit
When the user explicitly requests multi-model / cross-review, and production is found to shift tomulti-model orchestration, the reporting and confirmation steps remain unchanged.
- Read the target document in full
- Run from the skill root
python3 tools/scan_fingerprints.py <目标文档>to obtain mechanical candidates, then complete them item by item against all entries in the rule set - Produce a report: each finding includes the rule name, the original-text quotation, and a revision proposal; trivial items (typos, isolated punctuation) do not go into the report; the report is output only in the conversation and is not written to a file
- Deliver the report to the user; after approval, revise the file according to the proposal, changing only the wording and not the semantics: not a single bit of facts, data, conclusions, or citations may be lost