How to Reset Profile While Preserving Framework Rules in ai-job-search

Use the /reset command with scope profile or all to clear candidate data while keeping framework definitions intact—this requires explicit confirmation and only overwrites mutable skill files, never deleting core configuration files.

The ai-job-search repository by MadsLorentzen provides a structured job-search automation system where candidate data lives separately from framework logic. Understanding how to reset profile while preserving framework rules ensures you can start fresh without breaking the underlying architecture that powers job ranking, application generation, and interview preparation.

Understanding the Reset Scope System

The /reset command in .claude/commands/reset.md implements a three-tier scope model that controls exactly what gets cleared.

Available Reset Scopes

Scope What Gets Cleared What Gets Preserved
profile Four skill files containing personal data All framework definition files
documents User-uploaded files in documents/ subdirectories Folder structure and README.md
all Both profile and documents scopes Entire framework and folder hierarchy

When you trigger /reset, the command parses your argument against these keywords. If no recognized keyword is found, it prompts you to choose interactively.

Profile Reset: Precise File Targeting

Resetting the profile scope demonstrates how the system surgically removes only mutable candidate content. The command targets exactly four files while leaving the rest of the skill framework untouched.

Files Cleared During Profile Reset

Framework Files That Remain Untouched

03-writing-style.md        # Tone and voice definitions

04-job-evaluation.md       # Scoring criteria for job matches

06-cover-letter-templates.md  # Letter templates and structure

This selective approach means you can reset profile while preserving framework rules that govern how the AI evaluates jobs, writes cover letters, and adapts tone—ensuring continuity in system behavior even when candidate data changes.

The Reset Execution Workflow

The command follows a strict four-phase process designed to prevent accidental data loss.

Phase 1: Scope Detection

/reset profile

> What would you like to reset?
> - `profile` — Clears candidate profile data from skill files only
> - `documents` — Deletes user-provided files from the `documents/` folder only
> - `all` — Both of the above
> Reply with `profile`, `documents`, or `all`.

The parsing logic in reset.md (step 0) handles explicit arguments and fallback prompting.

Phase 2: Content Preview

For profile scope, the command inspects each target file and reports status:


## Profile reset will clear:

- 01-candidate-profile.md — [has content]
- 02-behavioral-profile.md — [has content]
- 05-cv-templates.md — [has profile statements]
- 07-interview-prep.md — [has STAR examples]

This transparency lets users verify what will be affected before proceeding.

Phase 3: Explicit Confirmation

> This cannot be undone.
> Type **`RESET`** (all caps) to confirm, or anything else to cancel.

The literal string RESET requirement (line 102 in reset.md) serves as a deliberate friction point against mistyped commands.

Phase 4: Safe Overwrite Execution

Rather than deleting files, the profile reset overwrites target files with minimal blank templates:


# Candidate Profile

<!-- 
Run /setup to populate this file based on your CV and other documents.
-->

This preserves:

  • File existence and location
  • Markdown structure and headings
  • Framework comments and instructions
  • Git tracking (no deletion/creation churn)

Documents Reset: Preserving Structure While Clearing Content

The documents scope handles user-uploaded career materials differently—it removes files but keeps infrastructure.

What Gets Removed

rm -f documents/cv/*
rm -f documents/linkedin/*
rm -f documents/diplomas/*
rm -f documents/references/*
rm -rf documents/applications/*/

What Stays Protected

  • documents/README.md — Instructions for the documents folder
  • All subfolder hierarchies (cv/, linkedin/, applications/, etc.)

As defined in reset.md (lines 89-96), this ensures the /setup command can repopulate documents without reconfiguring paths.

Running a Complete Reset

To demonstrate reset profile while preserving framework rules across both data types:

/reset all

# Preview shows both sections:

## Profile reset will clear:

- [four skill files listed]

## Documents reset will clear:

- documents/cv/ — 2 files
- documents/linkedin/ — 1 file
- documents/applications/example-corp/ — 3 files

> Type **`RESET`** to confirm.
RESET

# Operation completes with summary report

The post-reset output (lines 101-124) includes next-step guidance like "Run /setup to repopulate the profile."

Post-Reset System State

After any reset completes, the framework remains fully functional:

Only the candidate-specific content gaps need refilling, which /setup handles by reprocessing fresh documents against the preserved framework.

Summary

  • Scope selection controls whether you clear profile, documents, or all—each with distinct file targets
  • Framework preservation is guaranteed by never touching 03-writing-style.md, 04-job-evaluation.md, or 06-cover-letter-templates.md
  • Safe overwrite replaces content with blank templates rather than deleting files, maintaining structure
  • Explicit confirmation via the literal RESET string prevents accidental execution
  • Document infrastructure survives reset through protected folder hierarchies and README files

Frequently Asked Questions

What happens if I type "reset" in lowercase during confirmation?

The confirmation step strictly requires RESET in all capitals. Any other input—including lowercase "reset"—immediately aborts the operation with no changes made, as implemented in the confirmation logic at line 102 of reset.md.

Can I recover data after a profile reset?

No—the overwrite operation replaces file contents permanently. The system explicitly warns "This cannot be undone" before confirmation. You must rerun /setup with original source documents to repopulate the framework.

Why does the profile reset leave template frameworks intact?

The ai-job-search system separates mutable candidate data from immutable framework definitions. Preserving LaTeX templates in 05-cv-templates.md and scoring criteria in 04-job-evaluation.md ensures consistent output quality regardless of how often candidate profiles change.

Does resetting documents affect the applications tracking system?

Applications reset removes files within documents/applications/*/ subdirectories but preserves the parent folder structure and any application metadata stored elsewhere. The tracking logic itself—defined in separate skill files—continues functioning normally.

Have a question about this repo?

These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:

Share the following with your agent to get started:
curl -s "https://instagit.com/install.md"

Works with
Claude Codex Cursor VS Code OpenClaw Any MCP Client

Maintain an open-source project? Get it listed too →