q734738781/achemso-latex-manuscript

achemso-latex-manuscript

Overview

Use the bundled achemso assets as the fixed manuscript shell when the writing lane is producing an ACS-style draft. Prefer writing section/body fragments that will be assembled into the template over free-form generation of a full standalone document.

Quick Start

Use when the section should be written against an ACS-style LaTeX template or when the output must stay close to achemso structure.

For ACS-style manuscript drafting, default to a figure-aware deliverable: if the evidence supports it, complete the draft with the necessary figures, tables, and concise explanatory schematics rather than returning text alone. For short notes, status summaries, or compact internal writeups, clarity is the default and visuals are optional unless the user asks for them or they are clearly needed to avoid ambiguity.

Read these assets first through the read-only skills mount:

• assets/achemso-demo.tex
• assets/achemso-demo.bib

Allowed tools

• edit_file
• read_file
• execute

Workflow

1. Read the SKILL.md and the two asset files before drafting the section.
2. Treat the mounted asset as the canonical outer shell and bibliography reference; do not try to edit the read-only mounted asset directly.
3. Write or update section-level .tex fragments under the writable run workspace instead of regenerating the entire manuscript wrapper.
4. Use edit_file for deterministic SEARCH/REPLACE edits to the working TeX file.
5. Keep bibliography keys and citation commands consistent with the template's BibTeX usage.
6. Treat section_tex and workspace .tex artifacts as the primary output; use section_md only as a concise reviewer shadow when useful.

Journal-facing prose discipline

• For ACS-style manuscript output, write as an author of the scientific work, not as an agent narrating how the draft was assembled.
• Do not mention the workspace, runs, files, tools, prompts, interruptions, or that no new calculations were run during the writing pass.
• Keep internal provenance phrases such as workspace evidence, accessible snippets, bundle, this draft, or assembled from existing results out of the abstract and main text.
• Write titles as journal titles, not as project labels or workflow summaries. Center the title on the material system and principal scientific result; avoid meta phrases such as same-template comparison, workflow, screening hierarchy, or sentence-length takeaway titles unless scientifically unavoidable.
• Scientific limitations are acceptable; workflow disclaimers are not. If an evidence boundary matters, express it in scientific language such as unresolved benchmark coverage or incomplete literature verification rather than as an internal-process note.
• Do not use Acknowledgement or Supporting Information sections to apologize for process limitations or to explain the agent workflow.

Template discipline

• Preserve the documentclass, package imports, and global preamble unless the task explicitly requires a change.
• Prefer editing section bodies, captions, and bibliography entries over restructuring the full template.
• Do not emit a second independent paper template when the system is already assembling an achemso outer shell.
• Do not invent BibTeX entries. If a citation key is unknown, leave a clear placeholder or gap note.
• Keep LaTeX macros simple and local; avoid adding fragile custom commands unless necessary.
• The mounted asset is reference-only; any edited TeX should live under the writable run workspace.

Editing rules

• Use comments to mark inserted section blocks only when that helps later assembly or review.
• Keep figures and tables aligned with actual artifact paths and generated files.
• In ACS-style TeX, place each figure close to the first substantive paragraph that discusses it; do not accumulate figure environments in a later block after the surrounding argument is already complete.
• Prefer conservative float placement such as [htbp] for ordinary figures. If the template already includes placeins, use \FloatBarrier sparingly to stop obvious float drift across subsection boundaries.
• After compilation, inspect whether figures appear near their first callout in the PDF and repair placement if they do not; compile success alone is not enough.
• When the manuscript needs atomistic structure renders, create a tuned reproducible render script, starting from skills/materials/structure-visual-inspection/code/render_structure_panel.py when useful, and do not annotate the exported panel with renderer/backend labels.
• When the manuscript needs a conceptual, mechanistic, or workflow figure, use generate_nanobanana_figure to create a concise publication-facing schematic and save it under the writing workspace.
• When numerical evidence is better communicated as a table or plot than prose alone, add that artifact instead of forcing the explanation into dense text.
• If you create a new .tex helper file, record the path in latex_artifact_refs.
• If the template and the evidence disagree, preserve the evidence and adapt the prose, not the other way around.

Citation hygiene

• Final journal-facing .bib entries should look like publication metadata, not internal evidence memos.
• Do not leave note = {...} fields that explain workspace snippets, internal benchmark notes, or how a citation was inferred unless the cited source is genuinely an unpublished note or communication.
• If the citation metadata is incomplete, either resolve it properly, leave a clear pre-submission gap to fix, or remove the weak citation from the journal-facing draft.
• Prefer fewer clean references over many questionable placeholder entries.

Output Contract

Return section-level section_tex as the primary output. If you create or edit a workspace .tex fragment directly, record it in latex_artifact_refs. The outer achemso manuscript wrapper is assembled by the system.

References

• Read ../_references/style-and-revision-checks.md for sentence-level revision and consistency checks.
• Read ../_references/submission-and-editorial-readiness.md before treating the LaTeX section as journal-facing.