agentleFS
Sign inStart free
manuelschurrmanuelschurr/professional-twin/templates/CLAUDE.md

professional-twin / templates

CLAUDE.md0 starsChanged 7 months agoMITView on GitHub

A structured reference library capturing who I am, what I've done, what I value, and what I want next. Used by the professional-twin Claude Code plugin to support job-search and career-reflection workflows. This is a pure Markdown documentation library — no code, no build, no tests, no dependencies. All "work" is reading, editing, and adding .md files. Git is the only tooling. This repository works in tandem with the professional-twin plugin for Claude Code: https://github.com/manuelschurr/c200v-marketplace The plugin provides skills that…

The file

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

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't fill in answers I haven't given: If a question is open, it's open.

    line 15
  2. Distinctive:

    Ask one question at a time: Don't overwhelm with a wall of questions.

    line 16
  3. Distinctive:

    It's okay to prompt reflection: If I'm unsure, help me think through it — offer frameworks, ask probing follow-ups, surface patterns from …

    line 17
  4. Distinctive:

    Challenge shallow answers: If an answer feels generic, push for specifics.

    line 18
  5. Distinctive:

    Capture what I say faithfully: Write things in my voice and framing, not in polished marketing language.

    line 19
  6. Distinctive:

    Flag connections across docs: If something I say about my values also answers a question in the skills doc, note it in both places.

    line 20
  7. Distinctive:

    Don't restructure without asking: If something feels wrong, propose the change — don't just do it.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with files in this repository.

Professional Twin

A structured reference library capturing who I am, what I've done, what I value, and what I want next. Used by the professional-twin Claude Code plugin to support job-search and career-reflection workflows.

Repo type

This is a pure Markdown documentation library — no code, no build, no tests, no dependencies. All "work" is reading, editing, and adding .md files. Git is the only tooling.

How to collaborate on this repo

  • Don't fill in answers I haven't given. If a question is open, it's open. Ask me rather than inferring or guessing.
  • Ask one question at a time. Don't overwhelm with a wall of questions. Pick the most important or most interesting open question.
  • It's okay to prompt reflection. If I'm unsure, help me think through it — offer frameworks, ask probing follow-ups, surface patterns from my history. But let me arrive at the answer.
  • Challenge shallow answers. If an answer feels generic, push for specifics. "What do you mean by that?" and "Can you give me an example?" are good reflexes.
  • Capture what I say faithfully. Write things in my voice and framing, not in polished marketing language. The raw honest version is more useful than a cleaned-up one.
  • Flag connections across docs. If something I say about my values also answers a question in the skills doc, note it in both places.
  • Don't restructure without asking. If something feels wrong, propose the change — don't just do it.

Structure

core-profile/          — Who I am
companies/             — Deep reference per company (raw source of truth)
direction/             — What I want next
application-materials/ — Reusable assets

The accompanying plugin

This repository works in tandem with the professional-twin plugin for Claude Code:

https://github.com/manuelschurr/c200v-marketplace

The plugin provides skills that handle the workflows below. If you (Claude) have access to these skills in the current session, prefer them over improvising a process. If they're not available, tell the user how to install the plugin from the URL above.

Use cases → skills

Use caseSkill
Add or update profile content (any file in this repo)interview
Evaluate fit between a job description and this reporeview-job-offer
Draft tailored application materials for a specific roletailor-application
Bootstrap a new twin repo (shouldn't need this — repo already exists)setup

If the plugin is not available

Tell the user:

This repository is designed to be used with the professional-twin Claude Code plugin, which is not currently installed. You can install it from https://github.com/manuelschurr/c200v-marketplace — see the README there for instructions. Without the plugin, I can still read these files and answer questions, but the structured workflows (interview, fit evaluation, tailoring) won't be as good.

Then, if the user wants to proceed without the plugin, do your best with the files as you find them. Read core-profile/, direction/, and the relevant companies/ files before answering anything substantive.

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.

Check your setup, free