agentleFS
Mateus-Nogueira-GTMateus-Nogueira-GT/ai-job-search-brasil/AGENTS.md

ai-job-search-brasil

AGENTS.md2 starsChanged 27 days agoMITView on GitHub

This workspace is structured to manage job search activities, scraper tools, CVs, cover letters, and interview preparation. To prevent duplication and configuration drift across different AI agent frameworks (Claude Code, Google Antigravity, Codex, Cursor, Gemini CLI, etc.), this workspace uses a unified thin-pointer design. All agent runtimes should load the canonical specifications and candidate profiles from the files and directories below:

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not duplicate these rules or specifications.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Agent Guidelines: AI Job Search

This workspace is structured to manage job search activities, scraper tools, CVs, cover letters, and interview preparation.

Thin-Pointer Design (Single Source of Truth)

To prevent duplication and configuration drift across different AI agent frameworks (Claude Code, Google Antigravity, Codex, Cursor, Gemini CLI, etc.), this workspace uses a unified thin-pointer design. All agent runtimes should load the canonical specifications and candidate profiles from the files and directories below:

  1. Personal Candidate Profile:
    • The candidate profile, contact details, education, and target preferences are defined in CLAUDE.md and the individual profile methodology files under .claude/skills/job-application-assistant/ (specifically 01-*.md etc.).
  2. Canonical Workflow Specifications:
    • The step-by-step instructions and triggers for tasks (setup, scrape, rank, apply, upskill, interview) are defined in the .claude/ directory (specifically under .claude/skills/ and .claude/commands/).
    • Do not duplicate these rules or specifications. Treat .claude/ files as the single source of truth.
  3. Portal Search Skills:
    • Job-portal search CLIs live under .agents/skills/ in the portable Agent Skills format (with a SKILL.md per portal). Codex and Antigravity discover these automatically; the /scrape workflow in .claude/skills/job-scraper/ orchestrates them. Brazilian portals: gupy-search and vagas-search.
  4. Brazilian market rules:
    • Hiring regimes (CLT/PJ/estágio), compensation, CV and selection-process conventions for Brazil are in .claude/skills/job-application-assistant/10-mercado-brasileiro.md; tools/clt_pj.py compares CLT and PJ offers.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.