reference-formatlisted

# Reference Format ## Core Rule Reference formatting is **deterministic — route it to the bibliography toolchain, not to the model**. Switching APA → a numbered style, abbreviating journal names, reordering author/year/title: these have exactly one correct output, and a CSL processor or biber produces it. Do **not** hand-retype entries — typing a bibliography by hand burns tokens and injects errors into a path that has a single right answer (`CLAUDE.md → Model vs Code`). Two facts the model must hold: 1. **Presentation only.** A style conversion changes how a fact is *displayed* — never the fact. The DOI, author list, year, title, and venue in `references.bib` are immutable; the style decides ordering, punctuation, and abbreviation around them. If a conversion would change a DOI or an author name, that is a bug, not a reformat. 2. **Never invent a missing field to satisfy a style.** If the target style requires page numbers or a DOI and an entry lacks them, you do **not** fabricate one to make the build clean — you **flag** it `[VALUE — verify]` (`agent_docs/citation-discipline.md → placeholder protocol`). A fabricated page range is the same cardinal-rule violation as a fabricated citation. This skill configures and runs the conversion and reports what is missing. It does not write `.bib` field *values* by hand. ## When to Use Invoke with `/reference-format` when: - The manuscript's bibliography is in the wrong style for its target venue (drafted APA, the venue wants