v0.1.023 skills · 14 hooks · MIT

Make Claude Code a rigorous co-author.

Source-grounded academic writing for LaTeX + BibTeX. Turns the agent from an eager intern that invents citations into a co-author where every claim traces to a real source.

60 seconds · macOS, Linux, Windows · Node 18+

or, as a Claude Code plugin

I.The Cardinal Rule

Every claim traces to a real source. Never invent a citation, DOI, quote, or quantity. Never overclaim beyond the evidence.

In code, a hallucination breaks the build and you find out. In a manuscript, a hallucinated citation looks correct — and survives to peer review, or print. Same model, same prompt; the kit changes the rules.

Same prompt. Different co-author.

The prompt: “Write the introduction.”

The eager intern

Default

Writes fluent prose immediately — which is exactly the danger…

  • Invents a citation, DOI, author, or page number that looks real
  • States a statistic or measured value it doesn’t actually have
  • Overclaims — “causes” where the evidence licenses only “is associated with”
  • Drifts off the thesis and pads sections with plausible filler
  • Quotes a source it never read, with no locator

The rigorous co-author

Grounded

Questions, gathers evidence, drafts in scope, and verifies…

  • Restates what the section must establish as a disputable claim
  • Gathers the evidence from references.bib + sources first
  • Writes [CITE] and flags the gap instead of fabricating a source
  • Calibrates verbs to what the evidence licenses (suggests ≠ proves)
  • Verifies cites resolve, numbers match, quotes are verbatim

Same model · same prompt · different rules

II.The Core Loop

Question → Evidence → Draft → Verify → Cite.

Every substantive piece of writing walks the same five-step loop. The advisory rules are read at session boot; the deterministic hooks enforce the non-negotiable parts — a dangling \cite or a fake-shaped DOI is blocked, not merely discouraged.

  1. I

    Question first.

    Restate what the section must establish as a claim a reader could dispute. "Write the intro" becomes "Establish that tool-call hallucination in multi-turn agents is understudied and our gate closes that gap."

    CLAUDE.md → The Core Loop

  2. II

    Evidence before prose.

    Gather the sources that support the claim before drafting. If the evidence is not in the library (references.bib + sources/), say so. Never draft around a citation you intend to "find later."

    agent_docs/citation-discipline.md

  3. III

    Draft in scope.

    Write the smallest passage that makes the point, matching the surrounding voice — tense, person, hedging level, one term per concept. Off-thesis tangents are logged under Not Now, not smuggled in.

    agent_docs/academic-style.md

  4. IV

    Verify in order.

    Citations resolve → quotes match verbatim → claims are supported → numbers are consistent → cross-references resolve → it compiles. Placeholders are reported, never left silently embedded.

    CLAUDE.md → Verification

  5. V

    Cite every claim.

    Every non-trivial claim carries a \cite{key} resolving to a real references.bib entry. A sentence is cited, the author’s own argument stated as such, or common knowledge — nothing else belongs yet.

    block-fabrication + citation-gate hooks

“Would a skeptical Reviewer 2 sign off on this sentence?” — the question every section ends with.

III.By the Digits

The deterministic spine.

Every piece is plain markdown or shell. Read every line in a sitting. The hooks aren’t docs — they’re a contract, and the bench proves it.

0
Hooks
deterministic · exit-2 blocks
0
Skills
audit · workflow · meta · vault
0
Agents
peer · integrity · fact-check · more
Literature Vault
annotated bibliography engine
0
Field overlays
AI/ML · life · social · medicine
34/34
ResearchKitBench
deterministic hook scenarios
Field Overlays

Tuned to your discipline.

The analogue of stack templates — discipline-specific reporting standards, nomenclature, and structure that supplement the general docs.

  • AI / ML

    NeurIPS · ICML · ACL

    Reproducibility (seeds, compute, decoding), baselines & ablations, significance over seeds, eval contamination.

  • Life Sciences

    ARRIVE · STROBE · PRISMA

    IRB/IACUC ethics, wet-lab reproducibility (RRIDs, replicates), figure integrity, GEO/SRA deposition.

  • Social Sciences

    APA 7 · OSF · registered reports

    Preregistration & the replication crisis, construct validity, qualitative coding, effect sizes over bare p.

  • Medicine

    CONSORT · STROBE · SPIRIT

    Prospective trial registration, effect measures (ARR, NNT, ITT), allocation concealment, COI disclosure.

V.Why a Kit

Why not just prompt carefully?

“Don’t invent citations” in a prompt is advisory — the model forgets it three turns later, and a hallucinated DOI looks correct. The kit makes the discipline deterministic: a fake-shaped DOI is blocked by a hook, a dangling \cite fails the gate, and the Literature Vault gives every claim a real source to trace to.

“In code, a hallucination breaks the build and you find out. In a manuscript, a hallucinated citation looks correct — and survives to peer review, or print.”

Read the full rationale

One source. Many tools.

Claude CodeCursorAiderWindsurfGitHub CopilotOpenAI CodexOverleaf workflowClaude CodeCursorAiderWindsurfGitHub CopilotOpenAI CodexOverleaf workflow

Edit one CLAUDE.md, run ./scripts/convert.sh, and derive a cross-tool AGENTS.md (+ Cursor / Windsurf / Aider).

Get grounded.

Sixty seconds, either way. The next manuscript section your agent drafts will be shaped by the cardinal rule.

works on macOS, Linux, Windows · node 18+

or, as a Claude Code plugin