py/ai-job-search
1
0
Fork 0
mirror of https://github.com/MadsLorentzen/ai-job-search.git synced 2026-09-17 00:26:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

refactor: fold /setup_docs into /setup as third onboarding path (#9)

Browse Source 
* refactor: fold /setup_docs into /setup as third onboarding path

- Auto-detect documents/ at /setup Step 0; offer three paths (documents
  folder, single CV import, interview).
- Inline document-driven merge logic into setup.md as Path A: read-before-
  write, additive vs. conflicting bucket merge with per-conflict prompts,
  inference labeling for behavioral and style files, STAR-stub generation
  instead of fabrication.
- Step 3 substeps for skill files skip when Path A populated them; non-
  skill substeps (CLAUDE.md, cv/main_example.tex, search-queries.md)
  always run. Path C interview preserved verbatim. /setup --section <name>
  update flow preserved.
- Delete .claude/commands/setup_docs.md.
- Update /reset prompts to point only at /setup. Update documents/README.md
  to reference /setup throughout. Update README.md to drop the standalone
  /setup_docs section and add upskill/ to the skills tree.
- Remove the trailing comma left in .claude/settings.local.json after the
  PR #6 revert (was technically invalid JSON).

Single onboarding entry point. documents/ folder convention unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs(README): finish readme alignment for the /setup fold

- Update onboarding-paths tip to reflect three paths (was "Either"
  before /setup_docs landed in PR #6).
- Add documents/ and upskill/ entries to the file tree, both relied
  on by the new /setup Path A and by /upskill respectively.
- Add a brief "Other commands" section briefly describing /expand and
  /upskill so users discover them without having to read individual
  command files. /reset stays in the existing "Starting over"
  subsection, now linked from the new section.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mads Lorentzen
2026-04-29 09:57:33 +02:00
committed by GitHub
co-authored by Claude Opus 4.7
parent 2ba441f3fb
commit 974b29ec3a
6 changed files with 284 additions and 413 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documents/README.md
+11 -11
View File
@@ -1,6 +1,6 @@
# Documents Folder
This folder holds your actual career documents. The `/setup_docs` command reads everything here and uses it to populate the candidate skill files under `.claude/skills/job-application-assistant/`. It is safe to re-run `/setup_docs` as you add new documents — it merges intelligently and will never overwrite existing content without asking you first.
This folder holds your actual career documents. The `/setup` command reads everything here and uses it to populate the candidate skill files under `.claude/skills/job-application-assistant/`. It is safe to re-run `/setup` as you add new documents — it merges intelligently and will never overwrite existing content without asking you first.
---
@@ -29,14 +29,14 @@ Your master CV — the most complete, unedited version of your professional reco
**Supported formats:** `.pdf`, `.tex`
**What `/setup_docs` extracts:**
**What `/setup` extracts:**
- Work experience (titles, companies, dates, bullet points)
- Education (degrees, institutions, dates, thesis topics)
- Technical skills
- Awards and publications
- Contact information
**Naming:** Any filename works. If multiple files are present, `/setup_docs` reads all of them and cross-references for consistency.
**Naming:** Any filename works. If multiple files are present, `/setup` reads all of them and cross-references for consistency.
**Tip:** Keep your most comprehensive CV here (not a tailored variant). The skill files are the canonical source — tailored CVs are generated per application by `/apply`.
@@ -50,7 +50,7 @@ Your LinkedIn profile exported as a PDF.
**Supported formats:** `.pdf`
**What `/setup_docs` extracts:**
**What `/setup` extracts:**
- Work experience and dates (cross-referenced against your CV)
- Skills and endorsements
- Education
@@ -60,7 +60,7 @@ Your LinkedIn profile exported as a PDF.
- About/summary section (used to infer behavioral profile additions)
- Recommendations received (may enrich reference context)
**Naming:** Any filename works. Only one LinkedIn export is expected; if multiple are present, `/setup_docs` uses the most recently modified one.
**Naming:** Any filename works. Only one LinkedIn export is expected; if multiple are present, `/setup` uses the most recently modified one.
---
@@ -70,7 +70,7 @@ Degree certificates, transcripts, and any official qualifications.
**Supported formats:** `.pdf`
**What `/setup_docs` extracts:**
**What `/setup` extracts:**
- Degree titles and official names (used to verify education entries)
- Graduation dates
- Grades or distinctions (if visible)
@@ -86,7 +86,7 @@ Reference letters from former managers, supervisors, or collaborators.
**Supported formats:** `.pdf`, `.txt`, `.md`
**What `/setup_docs` extracts:**
**What `/setup` extracts:**
- Referee name, title, and organization
- Specific quotes and assessments (added to the references section of `01-candidate-profile.md`)
- Competency language used by referees (adds behavioral signal to `02-behavioral-profile.md`)
@@ -111,7 +111,7 @@ applications/
### Files within each application folder
**`job_posting.md`** — Paste the full job posting text here. Used by `/setup_docs` to infer which skills and role types you have targeted, and to calibrate `04-job-evaluation.md`.
**`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`.
**`cover_letter.tex`** — The cover letter you actually submitted. Used to extract writing style patterns and structure for `06-cover-letter-templates.md`.
@@ -139,7 +139,7 @@ What would you do differently?
Any signal about what they valued or didn't?
```
**What `/setup_docs` learns from outcome.md:**
**What `/setup` learns from outcome.md:**
- Which role types and companies have led to interviews (signals strong fit areas)
- Which applications did not progress (informs the experience match calibration in `04-job-evaluation.md`)
- Interview feedback, if you recorded it, can surface new STAR candidates
@@ -148,7 +148,7 @@ Any signal about what they valued or didn't?
## File Format Notes
| Format | Readable by `/setup_docs` | Notes |
| Format | Readable by `/setup` | Notes |
|--------|--------------------------|-------|
| `.pdf` | Yes | Parsed directly with the Read tool |
| `.tex` | Yes | LaTeX source — structure and content both readable |
@@ -159,7 +159,7 @@ Any signal about what they valued or didn't?
---
## Re-running `/setup_docs`
## Re-running `/setup`
The command is designed to be re-run as your document collection grows. Each run: