Profile Reset and Document Management Commands in the AI Job Search Framework

The AI Job Search framework provides the /reset command with three distinct scopes—profile, documents, and all—to safely clear generated skill files, source documents, or both, requiring explicit textual confirmation before any deletion occurs.

The MadsLorentzen/ai-job-search repository structures candidate data across two distinct storage layers: generated profile skills under .claude/skills/job-application-assistant/ and raw source documents within the documents/ directory. Understanding the available profile reset and document management commands ensures you can safely iterate on your job application materials without accidentally deleting framework configurations or important career artifacts.

Data Architecture: Profile vs. Documents

The framework segregates candidate information into two discrete areas to separate volatile generated content from persistent source materials.

Profile Data

Profile data resides in the skill files located under .claude/skills/job-application-assistant/, including files such as 01-candidate-profile.md and 04-job-evaluation.md. These generated files are consumed by every operational command—including /scrape, /apply, and /interview—to evaluate job fit and generate CV or cover-letter drafts. Resetting this area wipes these generated skill files while preserving the underlying framework rules and configurations.

Source Documents

Source documents are stored in the documents/ directory with sub-folders for cv/, linkedin/, diplomas/, references/, and applications/. This folder holds the raw career artifacts that the /setup command reads to populate the profile. Clearing these files removes the source material, though the folder structure and its accompanying documents/README.md remain intact.

The /reset Command and Available Scopes

Defined in .claude/commands/reset.md and documented in the main README.md under the Starting over section (lines 109-119), the /reset command supports three specific scopes to target different data layers.

/reset profile

This scope deletes all generated skill files under .claude/skills/job-application-assistant/ while leaving the .claude/ configuration directory intact. Use this when you want to rebuild your candidate profile from existing documents without touching your source files.

/reset documents

This scope removes all user-provided files inside documents/ across all sub-folders. The directory structure itself persists, as does the documents/README.md file, ensuring you retain the organizational template for re-populating your career artifacts.

/reset all

This scope performs both operations sequentially, clearing both the generated profile skills and the source documents in a single command. This is useful when performing a complete fresh start of your job search preparation.

Safety Mechanisms and Confirmation Flow

As implemented in the source code, the /reset command implements a two-step confirmation process to prevent accidental data loss. When invoked, the agent first enumerates exactly which files and directories will be removed, displaying a comprehensive list of affected paths.

The user must then type the literal word RESET to confirm the operation. This requirement ensures deliberate intent before the system executes any deletions, as noted in the README.md documentation (lines 313-319).

Practical Command Examples

The following examples demonstrate the exact syntax for each reset scope:

# 1. Reset only the generated profile data

/reset profile

# → Agent lists the skill files that will be removed, then asks you to type RESET.

# After confirming, the profile files are cleared. Run `/setup` again to rebuild.

# 2. Reset only the source documents

/reset documents

# → Agent shows each sub-folder (cv/, linkedin/, …) and the files it will delete.

# Confirm with RESET, then the `documents/` folder is empty (except for README.md).

# 3. Reset everything in one command

/reset all

# → Performs both of the above steps sequentially.

Document Management Workflow

Effective document management follows a cyclical pattern of population, import, and optional reset. The workflow leverages the /setup command defined in .claude/commands/setup.md to bridge raw documents with the generated profile.

1. Populate the documents/ folder following the layout conventions described in documents/README.md, organizing files into the appropriate sub-directories (cv/, linkedin/, etc.).

2. Import the data by running /setup. This command scans the documents/**/* path pattern and merges extracted information into the profile skill files. The process is idempotent, allowing you to re-run /setup after adding new documents without overwriting existing profile content, as detailed in lines 13-25 of the setup command definition.

3. Reset when necessary using /reset documents to clear source materials, or /reset all if you need to wipe both documents and the generated profile. After resetting, rerun /setup to rebuild the profile from your fresh document set.

Indirect Document Interactions

Several commands interact with the documents folder without performing deletions:

• /apply: Stores generated CV and cover-letter PDFs within the documents structure.
• /outcome: Archives per-application files under documents/applications/.
• /expand: Adds new competencies extracted from existing documents to the profile.

These commands read from or augment the document store but never delete user data.

Summary

• The /reset command supports three scopes: profile (generated skills only), documents (source files only), and all (both areas).
• Profile data lives in .claude/skills/job-application-assistant/ while source documents reside in documents/ with specific sub-folder conventions.
• All reset operations require typing the confirmation keyword RESET to execute.
• The /setup command provides idempotent import of document contents into the profile, allowing safe re-imports after partial updates.
• Commands like /apply, /outcome, and /expand manage document output and augmentation without risking data deletion.

Frequently Asked Questions

How do I completely start over without deleting the framework itself?

Use /reset all to clear both the generated profile files and your source documents simultaneously. This preserves the .claude/ configuration directory and the documents/ folder structure, allowing you to re-run /setup immediately afterward to rebuild from new or updated career artifacts.

What happens if I run /reset profile by mistake?

The command requires you to type the literal word RESET to confirm before any files are deleted. If you do not provide this confirmation, the operation aborts and all skill files in .claude/skills/job-application-assistant/ remain intact. This safety mechanism prevents accidental deletion of your generated candidate profile.

Can I add new documents without losing my existing profile data?

Yes. The /setup command is designed to be idempotent, meaning you can add new files to the documents/ sub-folders and re-run /setup multiple times. The command merges newly extracted information with existing profile content rather than performing destructive overwrites, as implemented in .claude/commands/setup.md.

Where are the generated CVs and cover letters stored?

The /apply command stores generated PDF outputs within the documents/ directory structure, typically in the applications/ sub-folder. These outputs are separate from your source documents and are managed by the framework's application workflow commands rather than the reset functionality.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}