Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/MadsLorentzen/ai-job-search/llms.txt

Use this file to discover all available pages before exploring further.

Before you can search for jobs, apply to postings, or rank opportunities, the AI Job Search framework needs to know who you are. /setup is the first command you run inside Claude Code — it collects your professional information and populates all seven profile skill files that every other command depends on. Running /setup once gives the framework enough context to evaluate fit, tailor CVs, write cover letters, and configure your job search queries. It can also be re-run at any time to update a specific section without touching the rest of your profile.

Three Onboarding Paths

/setup detects what’s already in your documents/ folder and recommends the best starting point. All three paths converge on the same profile files — choose whichever fits your situation.
Path A is the highest-signal option when you have existing career materials. Drop any combination of files into the documents/ folder and /setup will read, cross-reference, and merge everything into your profile.Folder layout:
documents/
├── cv/              # Master CV — PDF or .tex
├── linkedin/        # LinkedIn profile export (PDF)
├── diplomas/        # Degree certificates and transcripts
├── references/      # Reference letters
└── applications/    # Past application records (<company>_<role>/)
Path A processes subfolders in order (cv/linkedin/diplomas/references/applications/) and cross-references them for consistency. If it finds a date mismatch between your CV and a diploma, or a title discrepancy between your CV and your LinkedIn export, it surfaces those conflicts for you to resolve before writing anything.Past applications in applications/ are used for calibration: if a role reached interview or offer, that role type is flagged as a confirmed strong-fit signal. If a pattern of rejections emerges, that signal is recorded too.Path A is idempotent — re-running it as you add documents will not duplicate or overwrite existing content. Conflicts between the new material and what’s already in your profile are surfaced explicitly for resolution.

What Gets Populated

After /setup completes, the following files are written or updated:
FileContent
CLAUDE.mdFull candidate profile — name, contact, education, experience, skills, goals, workflow rules, and verification checklist
01-candidate-profile.mdStructured profile: Identity, Education, Experience, Independent Projects, Technical Skills, Publications, Awards, References
02-behavioral-profile.mdBehavioral assessment or synthesized self-assessment: strongest traits, how you work best, management style preferences
04-job-evaluation.mdPersonalized scoring framework: strong/moderate/weak skill match areas, career goals, motivation filters
05-cv-templates.mdLaTeX CV profile statement templates for different role types
07-interview-prep.mdSTAR examples from your actual experience (Paths B/C) or STAR candidate stubs flagged for manual completion (Path A)
cv/main_example.texYour LaTeX CV template with actual name, contact info, education, and recent experience
.claude/skills/job-scraper/search-queries.mdJob search queries configured for your role titles, skills, and location

Updating Specific Sections

You don’t need to re-run the full onboarding to update a single part of your profile. Use the --section flag to jump directly to any section from Path C:
# Reconfigure job search queries after your priorities change
/setup --section search

# Add or update technical skills
/setup --section skills

# Update your work history with a new role
/setup --section experience
When --section is used, /setup runs only the specified section’s questions, then writes only the files that section affects. Everything else in your profile is left untouched. The --section search flag is particularly useful over time: as your job search evolves, you can re-run search configuration to add new role titles, adjust location filters, or point the scraper at different portals — without touching your CV data or behavioral profile.

Profile Depth Tips

The single biggest factor in output quality is how much detail you put into your profile. Don’t just list job titles — describe what you actually did: specific projects, tools used, responsibilities, and measurable achievements. Similarly, instead of listing “Python” as a skill, describe how and where you applied it: “Built ML pipelines for customer churn prediction using scikit-learn” gives /apply far more to work with when tailoring your CV for a specific posting.
Path A is idempotent and safe to re-run as you add materials to your documents/ folder. Content already present in your profile will not be duplicated or overwritten — only net-new material is proposed as additive changes, and any conflicts between new documents and existing profile content are surfaced explicitly for your review.

Build docs developers (and LLMs) love