mirror of
https://github.com/MadsLorentzen/ai-job-search.git
synced 2026-09-17 00:26:26 +00:00
/apply drafted two documents and a tracker row from the full posting, then let the text die with the session. /outcome Step 3.2 tried to recover it by re-fetching a `source` URL the spec itself expects to be dead, and a posting pasted from an email or a PDF had no `source` to re-fetch at all. Step 6b gains item 7: write the posting verbatim to documents/applications/<company>_<role>/job_posting.md, never a re-fetch or a reconstruction from memory. The folder is derived by citing /outcome Step 1.4 rather than restating the rule, so the two cannot drift. An existing file is left alone and named in the report. Step 0 and the /scrape path (job-application-assistant SKILL.md Step 1) now retain the full posting text rather than a summary, so item 7 has something verbatim to write. Pinned by tests/test_apply_records_application.py.
This commit is contained in:
+3
-3
@@ -16,7 +16,7 @@ documents/
|
||||
│ └── <Company> - <Job Title>.txt # Filename = company + job title, content = full posting text
|
||||
├── applications/ # Past job applications
|
||||
│ └── <company>_<role>/
|
||||
│ ├── job_posting.md # The original job posting (paste as text)
|
||||
│ ├── job_posting.md # The original job posting (written by /apply, or pasted)
|
||||
│ ├── cover_letter.tex # The cover letter you submitted
|
||||
│ ├── cv_draft.tex # The CV variant you submitted
|
||||
│ └── outcome.md # Result + notes (fill in after hearing back)
|
||||
@@ -113,7 +113,7 @@ A drop folder for raw job posting text when Claude can't fetch a page directly (
|
||||
|
||||
A record of past job applications. Each subfolder is one application.
|
||||
|
||||
You can maintain these folders by hand, or let the **`/outcome`** command do it: it records progress updates and final results conversationally, archives the submitted drafts and the posting text, keeps `outcome.md` in the format below, and updates `job_search_tracker.csv` in the same step.
|
||||
You can maintain these folders by hand, or let the **`/outcome`** command do it: it records progress updates and final results conversationally, archives the submitted drafts and, if `/apply` has not already written it, the posting text, keeps `outcome.md` in the format below, and updates `job_search_tracker.csv` in the same step.
|
||||
|
||||
**Subfolder naming:** `<company>_<role>` — lowercase, underscores for spaces.
|
||||
|
||||
@@ -127,7 +127,7 @@ applications/
|
||||
|
||||
### Files within each application folder
|
||||
|
||||
**`job_posting.md`** — Paste the full job posting text here. Used by `/setup` to infer which skills and role types you have targeted, and to calibrate `04-job-evaluation.md`.
|
||||
**`job_posting.md`** — The full job posting text, written by `/apply`, or paste it here. Used by `/setup` to infer which skills and role types you have targeted, and to calibrate `04-job-evaluation.md`.
|
||||
|
||||
**`cover_letter.tex`** — The cover letter you actually submitted. Used to extract writing style patterns and structure for `06-cover-letter-templates.md`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user