15 lines
1017 B
Markdown
15 lines
1017 B
Markdown
# Agent Overview
|
||
|
||
This repository splits work into two coordinated areas:
|
||
|
||
- `input/` – upstream tooling that prepares role-specific Markdown resumes.
|
||
- `output/` – the conversion pipeline that renders those Markdown files into DOCX/PDF deliverables.
|
||
|
||
Agents should treat these areas independently so changes can be reasoned about and tested in isolation.
|
||
|
||
## Working Guidelines
|
||
- Keep shared instructions in this file minimal; place deeper guidance in `input/AGENTS.md` or `output/AGENTS.md` as appropriate.
|
||
- When making automated edits, avoid touching both `input/` and `output/` in the same change set unless the work explicitly spans both pipelines.
|
||
- Resume conversion templates live under `output/templates`. Copy the `.example` files to matching names (without the suffix) when you need local overrides, and verify with a fresh conversion run.
|
||
- Use conventional commits (`<type>(scope): <message>`) to signal which side of the system a change targets, e.g., `feat(output): add failed-processing bucket`.
|