agentleFS
Sign inStart free
alainatoralainator/worldcodex/.claude/skills/writing-style/SKILL.md

writing-style

Skill2 starsChanged 7 months agoMITView on GitHub

Generates a WRITING.md file with YAML tokens for prose consistency — voice, tense, forbidden words, citation format, equation format, locked spellings — paired with usage rationale. Use when establishing prose standards, updating style rules, or when user says "WRITING.md", "style guide", "prose standards", "writing tokens", "voice", "style system", or "writing rules". Does NOT write content — generates the style reference only.

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use changeset-scope, skill-prefixes and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • timmo001Skill

    changeset-scope

    Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.

    Also in 3 projects that use this

  • timmo001Skill

    skill-prefixes

    Name skills with an owner prefix so they do not collide with shared, imported or other repositories' skills. Use when creating, renaming, importing or reviewing a skill name, especially for repository-local or tool-owned skills.

    Also in 3 projects that use this

  • NVIDIASkill

    testing

    Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 4 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

  • +2 more from timmo001

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read references/writing-md-template.md for the full template.

    line 24
  2. Very specific:

    Write to project root as WRITING.md.

    line 35
  3. Distinctive:

    Does NOT write content. Does NOT audit prose (use /auditing-canon).

    line 39

“Common” is measured: kept by at least 6 in 10 of the 29 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Writing Style — WRITING.md Generation

Generates a WRITING.md file that gives Claude Code a persistent, structured understanding of your universe's prose standards.

The Format

  1. YAML front matter — Machine-readable style tokens
  2. Markdown body — Usage rationale by document type

Read references/writing-md-template.md for the full template.

The Style Questionnaire

  1. Document types — What types of files does this project produce?
  2. Voice per type — Academic third-person? Engaged analytical? Close-third?
  3. Tense rules — Present for laws? Past for history?
  4. Forbidden words — Generic filler to avoid
  5. Citation format — Inline parenthetical? Footnote?
  6. Locked spellings — Proper nouns with specific forms

Write to project root as WRITING.md.

Out of Scope

Does NOT write content. Does NOT audit prose (use /auditing-canon).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free