mirror of https://github.com/MadsLorentzen/ai-job-search.git synced 2026-09-17 00:26:26 +00:00

Files

T

Ayobami Adegoke 6b144dc456 feat: add /add-template command for registering custom LaTeX templates (#30 )

Users could already swap the stock moderncv/cover.cls templates, but only by
hand-editing the guidance in 05-cv-templates.md and 06-cover-letter-templates.md.
/add-template automates that:

- Interviews the user for the template's instructions: compile engine, fonts
  (bundled files or system), style rules to preserve, and hard page limit
- Stores the template profile-agnostic ([PLACEHOLDER] tokens) under templates/
  with a TEMPLATE.md manifest, so templates are safe to commit and share
- Runs a mandatory test compile with dummy data before registering anything
- Activates via a single managed block in 05/06, which /apply already reads,
  so no changes to the /apply workflow are needed; --use default is a clean
  revert to the stock templates
- --list and --use <name> manage multiple registered templates

Docs: README (commands list, file structure, LaTeX templates section) and
SETUP.md (compile section pointer).

2026-07-05 20:27:33 +02:00

README.md

feat: add /add-template command for registering custom LaTeX templates (#30 )

2026-07-05 20:27:33 +02:00

README.md

Custom Templates

This folder holds user-registered LaTeX templates, managed by the /add-template command. The framework works out of the box with its stock templates (moderncv for CVs, cover.cls for cover letters) — this folder only gets content when you register your own.

Layout

templates/
├── cv/
│   └── <template-name>/
│       ├── template.tex     # Profile-agnostic skeleton ([PLACEHOLDER] tokens)
│       ├── TEMPLATE.md      # Manifest: engine, fonts, page limit, style rules, pitfalls
│       ├── *.cls / *.sty    # Custom class/style files (if the template needs them)
│       └── fonts/           # Bundled font files (if not using system fonts)
└── cover_letters/
    └── <template-name>/
        └── (same layout)

How it works

/add-template interviews you for the template's instructions (compile engine, fonts, style rules, page limit), stores the files here, and runs a mandatory test compile before registering anything.
Activating a template adds a managed block to 05-cv-templates.md or 06-cover-letter-templates.md, which is what /apply reads when drafting — no other wiring needed.
/add-template --list shows registered templates; /add-template --use <name> switches; /add-template --use default reverts to the stock templates.

Templates are stored with [PLACEHOLDER] tokens instead of personal data, so they are safe to commit and share.