jobsearch-apply-mcp: Command for Claude Code

/add-template - Register a Custom CV or Cover Letter Template

You are helping the user register their own CV or cover letter template with the AI Job Search framework — LaTeX, Typst, or any other toolchain that compiles to PDF from the command line. The framework ships with moderncv (banking style) for CVs and a custom cover.cls for cover letters. This command lets the user swap in their own template: store the template files, capture usage instructions (source extension, compile command, fonts, style rules, page limits), verify the template compiles, and wire it into the /apply workflow so every future application uses it.

$ARGUMENTS may contain a subcommand, a file path, or nothing.

Follow these steps in order.

---

Step 0: Parse Arguments

• If $ARGUMENTS contains --list: run List Mode below and stop.
• If $ARGUMENTS contains --use <name>: run Switch Mode below, then continue to Step 5: Activate with the resolved template metadata. --use default deactivates any custom template and restores the stock guidance (see Step 5).
• If $ARGUMENTS contains a file path or @-mentioned file: treat it as the template source and carry it into Step 1.
• Otherwise: start the registration flow at Step 1.

List Mode

Use Glob with templates/**/TEMPLATE.md to find registered templates. For each, read the manifest and print a table:

## Registered Templates

| Name | Type | Source | Toolchain | Fonts | Active |
|------|------|--------|-----------|-------|--------|
| <name> | CV / Cover letter | .tex/.typ/... | tectonic/typst/... | <main font> | yes/no |

A template is active if 05-cv-templates.md (CV) or 06-cover-letter-templates.md (cover letter) contains an ACTIVE-TEMPLATE managed block naming it. If no custom templates exist, say so and explain that /add-template registers one. Stop here.

Switch Mode

If $ARGUMENTS contains --use <name>:

1. If <name> is default, skip template resolution and continue to Step 5 with default as the activation target.
2. Use Glob with templates/**/TEMPLATE.md and find manifests whose parent folder name exactly matches <name>.
3. If no manifest matches, stop and say the template is not registered. Suggest /add-template --list to see available names.
4. If more than one manifest matches, stop and list the matching manifest paths. Ask the user to rename one of the templates; activation must be unambiguous.
5. Read the matching TEMPLATE.md and extract:
   • Type: CV or Cover letter
   • Source extension: e.g. .tex, .typ
   • Compile command: the full declared command
   • Engine/toolchain: e.g. tectonic, typst (display label)
   • Page limit: <N> page(s)
   • Fonts: the full font summary line
6. Derive the template folder from the manifest path and verify template<source-extension> exists in the same folder. If it is missing, stop with an error; the template registration is incomplete.
7. Derive <type> for Step 5 from the manifest path:
   • templates/cv/<name>/TEMPLATE.md -> cv
   • templates/cover_letters/<name>/TEMPLATE.md -> cover_letters
8. Continue to Step 5 using the resolved <name>, <type>, <source-extension>, <compile-command>, engine/toolchain label, font summary, page limit, template skeleton path, and manifest path. Do not re-run Steps 1-4; --use switches an already-registered template.