Self-contained sub-project API/: a local support page where Marc pastes a client's mail; a support agent and an analyst agent stay alive for the session and produce a slide PDF that answers the client's question. Tools, detectors, knowledge and Typst brand are copied (API/PROVENANCE.md). First real case: Crissier (LENZSPITZE), workflow validated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AIMsight Typst brand
The company templates for AIMsight documents, frozen and versioned: technical documents (manuals, FAQs, reports, notes), brochures and 16:9 presentations, with the Inter fonts and the toolkit the document factories use to build, check, translate, import and illustrate documents.
Writing a document? Do not start here. Create a repository from one of
the document factories on Gitea; each carries a frozen copy of this brand in
brand/:
| Factory | For |
|---|---|
AIMsight/docfactory-technical |
user manuals, software documentation, FAQs, reports, notes; Word import and UI captures |
AIMsight/docfactory-brochure |
brochures, concept notes, datasheet-style leaflets |
AIMsight/docfactory-presentation |
slide decks |
This repository is where the brand itself changes, through pull requests and version tags.
Contents
templates/—technical.typ,brochure.typ,presentation.typ: layout and public functions.theme/— colours, geometry, typography, logos, company identity, wording per language (en, fr, de, es, it).fonts/— Inter 4.001, eight static faces, SIL Open Font License (fonts/OFL.txt).compat/legacy-conf.typ—conf(...)for documents written againstAIMsight_v2.typ/AIMsight_10pt.typ/AIMsight_11pt.typ: change the import line, nothing else.starters/— user-manual, report, note, brochure, deck.tools/— standard-library Python, run from a factory root:build.pylint, compile every document and translation, stamp revision/date/draft/history from git;--releasefor PDF/A;--watchpreview.pylive browser preview of every documentlint.pyauthoring rules, text budgets, table headers, translation structurenew.pynew document from a starter;new.py translatefor a language variantdocx2typ.pyWord document → draft technical document with its picturescapture.pyUI screenshots fromcaptures.toml(clicks, crops, hidden elements)brand.pyvendor the brand into a factory, check it, update it to a tagrelease.py,ci-setup.shused by the Gitea workflows
docs/TEMPLATE_GUIDE.md— the public API, field guidance and text budgets. Start here.docs/LLM_AUTHORING.md— compile-safe Typst rules and a prompt for generated content.docs/COLOR_SYSTEM.md,docs/ARCHITECTURE.md,docs/IMPROVEMENTS.md(review record).examples/— canonical examples per family;technical-specimen.typandbrochure-specimen.typshow every helper of their family,presentation-showcase.typevery slide type.tests/—run.py(everything),end_address.py,slide_variants.py,make_sample_docx.py, smoke and overflow fixtures.
Requirements
- Typst 0.14 or newer (tested with 0.14.2):
winget install --id Typst.Typst - Python 3.11+ for
tools/andtests/ - Chrome or Edge for
capture.py(nothing else to install) - VS Code with Tinymist for live editing (recommended by
.vscode/extensions.json)
Check and preview
python tests/run.py # all checks; PDFs per document type in build/test-pdfs/
python tests/run.py --full # with the full end-of-document address sweep
python tools/preview.py --port 8771
In VS Code, the default build task runs the tests and Tinymist previews any
example with the bundled fonts. In the Claude Code desktop app,
.claude/launch.json (brand-preview) opens the preview in the browser pane.
Changing the brand
- Branch, change
theme/ortemplates/, runpython tests/run.pyand look at the test PDFs that changed. - Add an entry to
CHANGELOG.md; bumpVERSION,typst.tomlandbrand-versioninlib.typ(patch: fixes; minor: new helpers or options; major: existing documents render differently or stop compiling). - Open a pull request on Gitea; after merge, tag
vX.Y.Zon main. - Factories and document repositories pick it up deliberately:
python brand/tools/brand.py update vX.Y.Z, rebuild, review, commit. A document repository keeps its brand until its owner updates it, so an issued document always rebuilds identically.
The rule that keeps the documents uniform: content files contain content
and semantic choices; the brand contains geometry, colours, typography,
spacing and page furniture. tools/lint.py enforces it in the factories,
and brand.py check fails a build whose brand/ copy was edited by hand.