style-enforcer
Normalizes drafts to the project's writing style and formatting rules in docs/instructions/rules/writing-style.md. Use when a draft is ready to publish, as the last pass after content-reviewer and seo-optimizer.
- License 许可
- MIT
- 所属仓库
- Eliyce/paqad-ai
- 最近更新
- 2026-11-13
- Stars
- ★ 8
- Forks
- 0
01 前言 Front Matter
- name
- style-enforcer
- description
- Normalizes drafts to the project's writing style and formatting rules in docs/instructions/rules/writing-style.md. Use when a draft is ready to publish, as the last pass after content-reviewer and seo-optimizer.
02 资源文件 4
- 资产文件assets/default-rules.txt330 B
- 资产文件assets/output.template.md170 B
- 参考文档references/style-source.md558 B
- 脚本scripts/check-style.sh1.9 KB
03 SKILL.md 正文
Style Enforcer
What It Does
Applies the project's writing-style rules (and only those rules) to a draft so style is enforced consistently rather than guessed each time.
Use This When
As the final pass before publish, after content-reviewer and (when applicable) seo-optimizer have run.
Inputs
- The draft.
docs/instructions/rules/writing-style.md(the source of truth: never override with general rules).assets/default-rules.txtonly when the project has no writing-style file.
Procedure
- Run
scripts/check-style.sh <draft>: flags violations of the style file (e.g. forbidden phrases, required cases, Oxford-comma policy). - For each flagged line, apply the project rule, never a generic preference.
- Format the change list per
assets/output.template.md.
Output Contract
- Match
assets/output.template.md:## Style Edits(one bullet per change with line number and rule citation).
Resources
references/style-source.mdscripts/check-style.shassets/output.template.mdassets/default-rules.txt
04 同仓库更多 Skills
sample-skill
Sample bundled skill fixture
processing-invoices
Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.
processing-invoices
Turns a supplier invoice into one ledger line. Use when a supplier invoice arrives and needs booking.
understand-idea
Chat and Claude Code: Step 1 of the discover journey: clarifies the goal, who benefits, success and constraints into the idea block. Use when the journey directs it to step 1, not directly.
size-work
Chat and Claude Code: Suggest a size for a ticket from comparable finished work, as a labelled suggestion the team still owns. Use it when someone asks "how big is this?", "roughly how much work is ABC-12?", or wants a backlog item sized. It finds the team's sizing scale at first use, picks two to five of the closest finished tickets with links, and gives a size or range with the drivers behind it and a confidence of low, medium or high, lowered and explained when the area's documents are template text. Every result is labelled a suggested size, never a date or a commitment. It writes nothing into the size field unless the user says "set it", and it refuses to overwrite an existing size unless the user asks to replace it. Produces the sizing block of the record.
refine-ticket
Chat and Claude Code: Improve one or more existing tracker tickets without losing the author's intent. Use it when someone wants a ticket read, diagnosed and tidied up ("this ticket is vague", "fix up ABC-12", "split this, it's too big"). It reads each ticket in full and snapshots it with its last-updated time, says what is wrong with evidence, and proposes a field-by-field before and after change set limited to summary, description, labels, parent, links and new child tickets on a split. It writes nothing until an explicit "apply it" bound to that exact change set, re-checks the ticket for conflicting edits just before writing, never replaces rich descriptions with plain text, never deletes or closes a ticket, and reads each ticket back after applying. Produces the existing and changes blocks of the record.