agentleFS
manuelschurrmanuelschurr/professional-twin/CLAUDE.md

professional-twin

CLAUDE.md0 starsChanged 7 months agoMITView on GitHub

A standalone Claude Code plugin: professional-twin. The plugin lives here as its own repository and is installed via the c200v-marketplace catalog. The plugin's purpose: help the user build and maintain a personal repository of their professional self — identity, history, values, direction — so Claude can help them apply for jobs, prepare for interviews, and reflect on their career. Commands (commands/*.md) are thin dispatchers — they name the skill and pass through $ARGUMENTS. The real logic lives in skills/<name>/SKILL.md. When…

The file

Files
CLAUDE.md

CLAUDE.md

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

What this repo is

A standalone Claude Code plugin: professional-twin. The plugin lives here as its own repository and is installed via the c200v-marketplace catalog.

The plugin's purpose: help the user build and maintain a personal repository of their professional self — identity, history, values, direction — so Claude can help them apply for jobs, prepare for interviews, and reflect on their career.

Plugin anatomy

professional-twin/
  .claude-plugin/plugin.json  — plugin metadata, version, description
  commands/                   — slash command definitions (thin dispatchers to skills)
  skills/                     — SKILL.md files (the actual skill logic)
  templates/                  — scaffolding files copied into new twin repos by the setup skill
  README.md                   — user-facing docs

Commands and skills

Commands (commands/*.md) are thin dispatchers — they name the skill and pass through $ARGUMENTS. The real logic lives in skills/<name>/SKILL.md. When changing behavior, edit the skill; only touch the command if the dispatch metadata (description, argument handling) changes.

Skills are pure Markdown instructions, not code. They are loaded by Claude Code at runtime and followed as-is. Edit them like documentation — clarity and precision matter more than brevity.

Two CLAUDE.md files

There are two CLAUDE.md files related to this plugin:

  • This one (plugin repo root) — guides Claude when working on the plugin itself (editing skills, commands, templates).
  • templates/CLAUDE.md — a template that gets copied into the user's twin repo by the setup skill. It guides Claude when working inside a user's twin repo, not inside this plugin. Edits to one should not bleed into the other.

Conventions

  • Bump version in .claude-plugin/plugin.json on every change to the plugin's skills, commands, or templates. Claude Code checks this to decide whether the cached copy is stale.
  • The templates/ directory contains files that are copied verbatim into new twin repos by the setup skill. Edits to templates affect every new repo going forward, but not existing ones.
  • Don't add new skills or commands without discussing with the maintainer first.

Marketplace integration

This plugin is listed in the c200v-marketplace catalog by URL. When you bump the version here, also bump the corresponding entry in that marketplace's marketplace.json so users see the new version on their next refresh.

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.