Where to Find Structured Mode Files in CareerOps: A Complete Directory Guide

CareerOps stores all structured mode files in the top-level modes/ directory, with global configuration in modes/_shared.md, user preferences in modes/_profile.md, and workflow-specific prompts like modes/oferta.md and modes/pipeline.md alongside localized subdirectories for international markets.

The open-source santifer/career-ops repository organizes its prompt-driven automation system through a centralized modes/ directory. Understanding the location and purpose of these structured mode files is essential for customizing evaluation workflows, localization, and user-specific archetype configurations.

Top-Level Mode Directory Layout

All structured mode files reside in the repository root under modes/. This directory serves as the single source of truth for prompt templates that drive the application's evaluation, application generation, and interview-prep workflows. The architecture separates global shared context from user-specific overrides and market-specific localizations.

Global Configuration Files

Two critical files sit at the root of modes/ and provide the foundation for all operations:

• modes/_shared.md – Contains the system-wide context including archetype taxonomy, scoring rules, spend-tier mapping, and market overrides that every mode inherits.
• modes/_profile.md – Stores user-specific customizations such as preferred archetypes, narrative style preferences, and personal configuration (complemented by config/profile.yml).

Workflow-Specific Mode Files

Individual workflow prompts are stored as standalone Markdown files in the modes/ root for the default English market:

• modes/oferta.md – Powers the evaluation workflow, implementing the A-F scoring system for job classification and opportunity assessment.
• modes/pipeline.md – Orchestrates sub-agents to process pending URL lists and manage batch evaluation operations.
• modes/scan.md – Implements the zero-token portal scanner for detecting job platforms like Greenhouse and Lever without API costs.
• modes/apply.md – Generates draft application emails and LinkedIn messages based on evaluated job criteria.
• modes/interview/practice.md – Provides structured interview preparation, planning frameworks, and debriefing capabilities.

Localization and Market-Specific Modes

For international users, structured mode files are organized into language-specific subdirectories that mirror the root layout. Each market folder contains a localized _shared.md plus translated workflow files adapted to local job markets.

Common market directories include:

• modes/de/ – German language versions including modes/de/_shared.md and modes/de/offert.md (the localized evaluation prompt).
• modes/zh/ – Chinese localization with corresponding workflow files.
• modes/ja/ – Japanese localization using files like modes/ja/kyujin.md for job evaluation.
• modes/fr/ – French versions with modes/fr/_shared.md and modes/fr/oferta.md, including README documentation mapping local files to global contexts.

When operating in a specific market, CareerOps loads the localized _shared.md (e.g., modes/fr/_shared.md) alongside the translated workflow files (e.g., modes/fr/oferta.md). The system maintains the core logic defined in the English source files while applying cultural and linguistic context through the subdirectory structure.

Executing Different Modes

To invoke these structured mode files, use the CLI with the appropriate command. Set environment variables to switch between market-specific directories without changing file references in your commands.

Run the default English evaluation on a job posting:

node codex exec "career-ops evaluate https://example.com/job"

Switch to German market modes by setting the modes directory:

export LANG_OUTPUT=en
export LANG_MODES_DIR=modes/de
node codex exec "career-ops evaluate https://example.com/job-de"

Execute the pipeline mode for batch URL processing:

node codex exec "career-ops pipeline"

Trigger the zero-token scanner for portal detection:

node codex exec "career-ops scan"

Draft an application using the apply mode:

node codex exec "career-ops apply https://example.com/job"

Summary

• CareerOps structured mode files are centralized in the modes/ directory at the repository root.
• Global system configuration lives in modes/_shared.md, while personal settings reside in modes/_profile.md (supported by config/profile.yml).
• Workflow-specific prompts—including evaluation (oferta.md), pipeline processing (pipeline.md), portal scanning (scan.md), and application drafting (apply.md)—are stored in the root for English defaults.
• International markets use subdirectories like modes/de/, modes/ja/, and modes/fr/ containing localized _shared.md files and translated workflow prompts such as modes/de/offert.md and modes/ja/kyujin.md.
• The system loads market-specific contexts dynamically based on the LANG_MODES_DIR environment variable.

Frequently Asked Questions

What is the difference between modes/_shared.md and modes/_profile.md?

According to the santifer/career-ops source code, modes/_shared.md contains the global system context including archetype definitions, scoring rules, and spend-tier mappings that apply universally across all workflows. In contrast, modes/_profile.md stores individualized preferences such as your preferred archetypes and narrative style settings, allowing you to customize outputs without modifying the core system logic.

How do I add support for a new language market in CareerOps?

Create a new subdirectory under modes/ using the appropriate ISO language code (e.g., modes/es/ for Spanish), then copy the English root files including _shared.md and the workflow files like oferta.md. Translate the prompt content while preserving the structural markers and archetype references. As implemented in the repository, the system automatically detects and loads these files when you set LANG_MODES_DIR=modes/es.

Can I override specific archetype definitions without modifying modes/_shared.md?

Yes. Place your customized archetype definitions or scoring rules in modes/_profile.md or config/profile.yml. The CareerOps engine loads _profile.md after _shared.md, allowing your user-specific settings to override the global defaults while maintaining compatibility with upstream updates to the core structured mode files.

Where are the interview preparation prompts stored in the CareerOps repository?

The interview preparation workflow is located at modes/interview/practice.md. This file contains the structured prompts for practice sessions, planning frameworks, and debriefing questions, separate from the job evaluation and application drafting modes stored in the root modes/ directory.

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