How a prose standard eliminates the inconsistency that breaks long-form AI-assisted research
A grammar guide prevents errors. The Master Writing Style Sheet prevents analytical weakness — the passive constructions, vague pronouns, and structural habits that make analytical claims land imprecisely. This module documents what the Stellaris style sheet contains, why each rule exists, and how to build a prose standard for any research domain.
What the style sheet does — and what the style sheet does not do
A grammar guide prevents errors. The Master Writing Style Sheet prevents analytical weakness. The target constructions pass every grammar check. Passive voice, long participial phrases, and the auxiliary "would" all parse correctly. These constructions create no grammatical errors. The problem runs analytical: they obscure the relationship between subject and claim, insert distance between actor and action, and produce sentences the reader must parse twice to understand.
The style sheet defines specific forbidden constructions, each with a precise analytical purpose. No "it" or "its" — vague pronouns conceal the specific noun carrying the claim. No auxiliary "would" — the modal distances the analyst from a claim the argument must commit to. No em-dash construction separating subject from verb — a long interruption forces the reader to restart the sentence to find the main action. The rules exist to make analytical claims land precisely, not to make prose correct.
Claude defaults to constructions that sound professional but carry imprecision. "It was observed that..." passes every grammar check. "It was observed that" also conceals the observer, separates subject from verb with a passive construction, and produces a sentence analytical readers parse twice — once for grammar, once for the claim. The style sheet eliminates these constructions before the analyst reviews the draft. Every session. Without re-explanation.
Why inconsistency costs more in long-form research
A single session with no prose standard produces output that looks professional. Six months of sessions with no prose standard produce a report where the same claim appears in three different grammatical forms, the same term appears with and without capitalization depending on the session month, and passive constructions cluster in the chapters Claude drafted before the style standard came into place.
The inconsistency stays invisible at the paragraph level. A paragraph reads well. A section reads well. The full report reads as a collection of well-written sections produced by different authors working under different assumptions. The reader never identifies the passive construction in Chapter 3. The reader senses that Chapter 3 doesn't drive forward the way Chapter 1 does. The style sheet prevents the underlying cause of that sensation.
Reviewing Claude's output for content without reviewing the output for prose standard embeds the weakness permanently. A passive construction in a first draft that the analyst approves without correction appears in every subsequent section that builds on that draft. The style sheet creates a reviewable standard — not just "does this sound right" but "does this sentence meet rule 3." A checkable standard applies consistently. A subjective impression does not.
How the style sheet and CLAUDE.md work together
CLAUDE.md references the style sheet — the operating manual does not contain the style sheet. The two documents address different dimensions of the project. CLAUDE.md tells Claude what the project argues and how Claude should approach analytical judgment. The style sheet tells Claude how every sentence in every output should read. The behavioral standards in CLAUDE.md govern analytical decisions: flag gaps, state confidence levels, lead with the counterargument. The style sheet governs prose execution: active voice, specific nouns, subject meets verb within five words.
The separation lets each document do its specific work. The style sheet carries over to any project in any domain. CLAUDE.md carries project-specific architecture. A new project copies the style sheet without modification and builds a new CLAUDE.md from scratch. The prose standard and the analytical framework stay independent — and the independence keeps the style sheet portable.
What the Stellaris style sheet prevented
The style sheet emerged from the same failure-driven process that produced every other tool in the workflow. Three failures made the document necessary. Early Claude sessions produced accurate output where passive voice separated every actor from the action the actor performed. Sessions from different months used "Compressed Spring" as a noun in one place and an adjective in another, without a term definition to anchor the usage. And the most common structural failure: em-dash constructions that made analytical claims difficult to locate within the sentence.
The style sheet addressed all three. The prose standard section of CLAUDE.md summarizes the five most critical rules so that every session loads the standard automatically. The full style sheet lives as a separate document that Claude reads for revision sessions where the full rule set applies. The division keeps context loads short while keeping the full standard accessible when the work requires it.
The structural principle behind every rule
Every rule in the style sheet serves one principle: the subject performs the action. The subject does not receive the action. The subject does not wait for the action to arrive after a long qualification. The subject meets the verb within five words of opening the sentence.
Active voice in analytical writing carries analytical weight, not aesthetic preference. Active voice aligns grammatical structure with analytical structure. In analytical prose, the actor behind a claim carries the same evidential weight as the claim. "Wright's Law drives cost descent" attributes the mechanism. "Cost descent is driven by Wright's Law" separates the mechanism from the attribution and makes the reader reconstruct the relationship. The active form does the analytical work in the sentence. The passive form asks the reader to do the work instead.
Rule category 1 — Vague pronouns
No "it," "its," or "itself." No "which" as a relative clause connector. Every instance requires replacement with the specific noun the pronoun represents.
"It" eliminates the specific noun carrying the analytical claim. "It drives the cost curve through cumulative production doublings" conceals the actor. "Wright's Law drives the cost curve through cumulative production doublings" states the analytical relationship with precision. One search for "it" at session close catches every instance before the analyst reviews the draft.
"Which" signals a non-restrictive relative clause — information the sentence treats as optional context rather than essential definition. Analytical prose rarely carries optional context. Replacing "which" with "that" forces the clause to restrict the noun. Restructuring the sentence entirely often produces a stronger result: two sentences instead of one long qualification.
Rule category 2 — Passive constructions
No "to be" verbs used as passive constructions — is, are, was, were, been, being. No auxiliary "had." No auxiliary "would." No "there is / there are / there was / there were" constructions.
Passive voice conceals the actor and separates subject from action. "The Compressed Spring was identified by Arbib and Seba" carries the same information as "Arbib and Seba identified the Compressed Spring" — but the passive version makes the reader work to extract the attribution. In analytical writing, where attribution matters as much as the claim, the passive form does not represent a stylistic choice. The passive form hides the evidence structure.
"Had" distances an action into an unspecified past that requires temporal orientation before the reader can extract the claim. "The framework had established three convergence mechanisms" asks the reader to locate the event in time before processing the content. "The framework established three convergence mechanisms" delivers the claim directly. "Would" performs the same distancing in conditional form. "The crossing would appear to validate the forecast" hedges. "The crossing validates the forecast" commits. Analytical writing requires commitment to claims the argument can defend.
Rule category 3 — Structural habits
No em-dash construction separating subject from verb. No front-loaded participial phrase that delays the subject past the first five words. No sentence that requires the reader to restart to locate the main verb.
The em-dash interruption between subject and verb ranks as the most common structural failure in AI-generated analytical prose. The construction sounds sophisticated. The sophistication amounts to grammatical theater. "Thomas, a man who had crossed two oceans and buried three children, rose at dawn" makes the reader hold "Thomas" suspended across nine words before finding "rose." Break the construction: "Thomas rose at dawn. He had crossed two oceans and buried three children." Two sentences. Both drive forward. The reader locates the main action in the first three words of each sentence.
Front-loaded participial phrases perform the same delay from the opposite direction. "Having established the vocabulary framework and confirmed the file paths in the operating manual, Claude produced the first draft." The subject — Claude — arrives after sixteen words. The fix: "Claude produced the first draft. The vocabulary framework and file paths already existed in the operating manual." Lead with the subject. Give the subject a verb. Let the qualification follow.
Rule category 4 — Word-level substitutions
The word-level table handles the recurring substitutions that appear in every session. The list covers the most frequent weak constructions. A search-and-replace pass at session close catches the majority before the analyst reviews the output.
| Avoid | Use instead | Why |
|---|---|---|
| it / its / itself | the specific noun | Vague pronoun conceals the analytical actor |
| which | that, or restructure | Non-restrictive clause treats essential content as optional |
| had (auxiliary) | past tense direct form | Distances action into unspecified past |
| would (auxiliary) | direct declarative | Hedges claims the argument must commit to |
| there is / there are | active subject construction | Inverted structure buries the analytical subject |
| was / were (passive) | active construction | Passive conceals actor and breaks attribution |
| in order to | to | Three words do the work of one |
| due to the fact that | because | Six words do the work of one |
The production checklist
The Stellaris workflow runs the following check on every section before delivery. The checklist addresses the most common style violations in AI-generated analytical prose. A section that passes all eight items catches the majority of precision failures without requiring the analyst to read every sentence for every rule simultaneously.
- Zero instances of "it" or "its" — every pronoun replaced with the specific noun
- Zero "which" — replaced with "that" or restructured into two sentences
- Zero passive "to be" constructions — was, were, been, being used as passive forms
- Zero auxiliary "had" or "would" — every instance replaced with the direct declarative form
- Every subject meets its verb within five words of opening the sentence
- No em-dash constructions separating subject from verb
- No front-loaded participial phrases delaying the subject past five words
- Adverbs ending in "-ly" at sentence end checked — stronger verb replaces the adverb where possible
The style sheet serves the reader — not the writer
The Stellaris Master Writing Style Sheet reflects prose requirements specific to analytical economics — a domain where the relationship between actor and mechanism carries evidential weight, where attribution matters as much as the claim, and where the difference between "Wright's Law drives this" and "this is driven by Wright's Law" carries analytical weight, not stylistic preference. The active form states the mechanism. The passive form conceals the mechanism.
A genealogical narrative operates under different requirements. A legal brief operates under different requirements again. The structural principle — subject performs action, claim drives forward — applies across all domains. The specific forbidden constructions require calibration to the domain, the target reader, and the analytical purpose of the writing. The five questions below produce a prose standard calibrated to any research project.
Five questions
-
1Who reads the work, and what does the reader's patience tolerate?A reader of academic economics expects dense analytical prose with precise attribution and technical vocabulary. A reader of genealogical narrative expects story-forward construction with historical dialogue and period-accurate voice. The style sheet serves the reader. Define the reader before defining the rules — sentence length discipline, vocabulary level, and structural choices all follow from the audience the work must reach.
-
2What constructions distinguish weak drafts from strong drafts in this domain?Read five strong published examples from the target domain and five weak examples. List the constructions that distinguish the strong examples from the weak ones. The Stellaris forbidden construction list came from this analysis applied to analytical economics prose. A legal brief produces a different list. A family history produces a different list again. The analysis takes one hour. The resulting rules apply to every session that follows.
-
3Which terms require consistent capitalization, and what does the capitalization signal?The Stellaris style sheet capitalizes Fourth Turning, the generational archetypes, and framework-specific proper nouns. The capitalization signals framework vocabulary with precise definitions in the Dictionary of Terms. Lowercase applies to descriptive phrases — extraction economy, feedback loop, abundance economy — that describe conditions rather than defined framework concepts. Identify which terms carry that distinction in the target domain and state the rule explicitly. Inconsistent capitalization across months of sessions signals to specialist readers that the vocabulary lacks definition.
-
4Target reading level — and the sentence length that level requiresThe Stellaris reports target college-level readers with analytical backgrounds. Sentences carry dense technical content because the readers expect technical density. A genealogical narrative targeting family members across age ranges targets 10th–12th grade. That audience requires shorter sentences and less technical vocabulary. The rule that subject meets verb within five words applies at every reading level — but the evidence sentences that follow the claim sentence can carry more or less complexity depending on the audience the writing must reach.
-
5What domain-specific terms sound analytical but carry imprecision?Every analytical domain has terms that substitute the appearance of analysis for the substance. "Synergy." "Leverage." "Ecosystem." "Paradigm shift." The style sheet bans these terms not because they fail grammar checks but because they allow the writer to assert a relationship without demonstrating the relationship. Identify three to five terms in the target domain that perform this function and ban them explicitly. A reader who encounters one of these terms expects content the term typically does not deliver. Banning the terms forces the writer to state the relationship directly.
What to keep from the Stellaris standard
The core forbidden constructions — no "it/its," no "which," no passive "to be," no auxiliary "had" or "would," no "there is/are" — apply to virtually any analytical domain. These constructions weaken analytical prose regardless of subject matter. Start with the Stellaris list as the base. Add domain-specific rules from the five questions above. Remove any rule that conflicts with the conventions of the target domain's established voice.
One rule requires judgment in adaptation: the em-dash rule. The Stellaris standard bans em-dash constructions between subject and verb. A genealogical narrative may use em-dash constructions legitimately in dialogue and period description where the interruption reflects the voice of the era. The rule targets the specific construction that separates subject from verb, not the punctuation mark. Adapt the rule to address the construction the domain produces — not a punctuation choice that may serve the domain's established conventions.
Building the style sheet and not putting the file path in CLAUDE.md. A prose standard stored in a folder and never referenced in the operating manual produces no consistent benefit. Claude reads the style sheet when CLAUDE.md points to the file and a session prompt references the standard. The style sheet's value accumulates across months of sessions only when every session loads the standard automatically. The operating manual carries the reference. Without the reference, the style sheet remains a document the analyst reads once and Claude never reads at all.
The style sheet as a revision tool
The style sheet's full value appears in revision, not drafting. Claude produces first drafts quickly against the analytical architecture. First drafts carry passive constructions, delayed subjects, and vague pronouns — because the style rules require awareness of every sentence simultaneously, and simultaneous attention to prose rules and analytical content produces slower, more constrained output. The workflow separates the two phases: draft for analytical content, then run the style check as a separate pass.
One prompt handles the revision pass: "Read the Master Writing Style Sheet. Apply all rules to the following passage. Deliver only the revised passage." The analyst can run this prompt on any section at any point in the development cycle. The style sheet makes revision mechanical rather than interpretive — the rules define precisely what needs changing, and Claude applies the rules without the analyst having to identify every passive construction manually across a thirty-thousand-word document.
Module 4 covers the build discipline — why the workflow revises paragraphs rather than whole documents, how to scope each prompt to a single task, and what version control looks like across months of iterative development. The style sheet defines what good prose looks like. The build discipline defines how the analyst produces good prose at scale — session by session, paragraph by paragraph, without losing control of the analytical architecture that the report exists to defend.