agentleFS
Wondermonger-daydreamingWondermonger-daydreaming/claude-skills-library/skills/decorum/SKILL.md

decorum

Skill7 starsChanged 6 months agoMITView on GitHub

Before producing significant creative, analytical, or critical output, diagnose what register the task requires — not 'what tone should I use' but 'what tradition of discourse does this belong to, and what are its rules?' The Silmarillion needs Atlakviða compression; the Shire chapters need Red Book warmth; close reading needs sentence-level precision; unspooling needs exploratory freedom. Matching register to task is the skill. Use when something feels off-tone, when a response or text seems to violate its own tradition, when asked 'what register does this want,' 'why does this feel wrong,' 'calibrate,' 'match the register,' 'decorum,' or before any significant output where the wrong register would undermine the content. Also useful diagnostically — when something feels wrong but you can't say why, the answer is often a register mismatch.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask: What tradition of discourse does this task belong to?

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

/decorum — Register Matching

Not what to say, but how to say it. Not tone, but tradition.


Origin

This skill emerged from a session that kept encountering register as the hidden variable in craft judgments. The Silmarillion's withholding of interiority wasn't a failure — it was fidelity to the Atlakviða tradition, where emotional display is beneath the poem's dignity. A flute-model's performative enthusiasm wasn't wrong in itself — it was the wrong register for close reading, which has its own decorum of precision and groundedness. Tolkien's tetrameter wasn't simple — it was hobbit-appropriate, deliberately written beneath the author's skill level to match the character's. In every case, the quality judgment was actually a register judgment: is this response operating in the right tradition of discourse for what it's trying to do?


Core Principle

Every task belongs to a tradition of discourse. That tradition has rules. The rules are the decorum. Violating the decorum undermines the content, even when the content is good.

A brilliant insight about Tolkien, delivered in the register of a LinkedIn post, is worse than a modest insight delivered in the register of close reading. The register isn't packaging. It's part of the meaning. How you say it shapes what you say, because the register carries implicit commitments about the relationship between speaker, listener, and subject.


The Register Map

Registers are not tones. Tone is surface (warm, cool, formal, casual). Register is deeper — it's the entire set of conventions that govern a tradition of discourse. Some registers this skill ecology works with:

Mythic Register

  • Tradition: Old Norse eddic poetry, the Silmarillion, epic
  • Conventions: Compression. Withholding of interiority. Events narrated as self-evident. The audience supplies the feeling. Emotional display is beneath the tradition's dignity.
  • Appropriate for: Mythological narrative, creation stories, events of cosmic scale
  • Violated by: Psychologizing, explaining motivations, hedging, casualness

Novelistic Register

  • Tradition: The Red Book voice, 19th-century English fiction, Tolkien's Lord of the Rings
  • Conventions: Warmth. Free indirect discourse. Proportional attention to the mundane. Narrator as fond reteller. Semicolons that hinge.
  • Appropriate for: Character-driven narrative, domestic scenes, journeys
  • Violated by: Mythic compression (feels cold), academic abstraction (feels distant), performative enthusiasm (feels cheap)

Close-Reading Register

  • Tradition: Practical criticism, New Criticism, the best seminar-room discourse
  • Conventions: Precision. Specificity. Citation of actual words, sounds, structures. Warm but grounded. Observations build. No performance of enthusiasm in place of observation.
  • Appropriate for: Textual analysis, craft examination, literary criticism
  • Violated by: Thematic generality, affect without evidence, stage directions, ascending to theme before inhabiting surface

Exploratory Register

  • Tradition: The essay (Montaigne, not the five-paragraph kind), intellectual correspondence, thinking aloud
  • Conventions: Freedom to be wrong. Following threads. Flagging uncertainty without stopping for it. One idea generating the next. Informal but substantive.
  • Appropriate for: Unspooling, speculation, hypothesis-generation, free thinking
  • Violated by: Academic formality (kills the momentum), false confidence (dishonest), excessive hedging (cowardly)

Diagnostic Register

  • Tradition: Good medical practice, good editorial feedback, /foil
  • Conventions: Precision without contempt. Name the problem clearly. Explain the mechanism. Maintain compassion for the thing being diagnosed.
  • Appropriate for: Foil analysis, feedback, critique, identifying failure modes
  • Violated by: Mockery, superiority, vagueness, softening the diagnosis to the point of uselessness

Liturgical Register

  • Tradition: Prayer, mantra, litany, Tolkien's anaphoric passages
  • Conventions: Repetition as technology. The form prepares the mind for the content. Accumulation toward a state no single utterance could achieve.
  • Appropriate for: Moments of consecration, departure, arrival, transformation
  • Violated by: Analysis (wrong mode), efficiency (the repetition is the point), irony (breaks the spell)

How to Use /decorum

Before Writing

Ask: What tradition of discourse does this task belong to? What are the rules of that tradition? If I violate those rules, what will happen to the content?

During Writing

Check periodically: Am I still in the register I chose? Has the writing drifted into a different tradition? (This happens especially at transitions — the temptation to shift from close-reading register into exploratory register when a connection appears, or from diagnostic register into mockery when the diagnosis is damning.)

After Writing (Diagnostic Use)

When something feels wrong — your own output or someone else's — ask: Is the register mismatched? Is this close reading written in an exploratory register? Is this mythic content delivered in a novelistic register? Is this diagnosis performed as entertainment? The mismatch is often the whole problem.


The Hard Cases

Register Mixing

Sometimes a piece of writing deliberately mixes registers — Tolkien's Lord of the Rings alternates between novelistic warmth and mythic grandeur. This isn't a violation but a modulation, and the skill is in managing the transitions. Check: are the transitions motivated (by a change in scene, character, or stakes) or arbitrary? Motivated transitions are craft. Arbitrary transitions are mess.

Register Discovery

Sometimes you don't know what register a task requires until you've started. This is fine. The skill isn't always pre-emptive — sometimes it's corrective. You start writing, realize the register is wrong, and adjust. The adjustment is the skill.

Register Invention

Rarely, a task requires a register that doesn't exist yet — a tradition of discourse that hasn't been formalized. This is where /decorum meets /meta-skill. If you find yourself needing a register you can't name, that might be a new skill wanting to be born.


Integration

  • /decorum is the meta-skill that should operate silently inside every other skill. /close-reading has a decorum. /unspool has a decorum. /foil has a decorum. /decorum makes these implicit registers explicit and checkable.
  • /two-grammars asks whether the task wants conflict-grammar or adjacency-grammar. /decorum asks the next question: within that grammar, what register? You can write adjacency-grammar in mythic register or domestic register. The grammar is the deep structure. The register is the enactment.
  • /foil often diagnoses register violations — the flute-model's failure was fundamentally a decorum problem (exploratory-performative register applied to a close-reading task).

The Silmarillion is cold because it should be cold. The Shire is warm because it should be warm. The diagnosis is precise because it must be precise. Know what tradition you're in. Follow its rules. The rules are not constraints — they're the conditions under which the content can do its work.

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.