agentleFS
Sign inStart free
michelabboudmichelabboud/claude-code-playbook/skills/dev-mode/SKILL.md

dev-mode

Skill1 starsChanged 41 days agoMITView on GitHub

Show or change this project's dev mode (spike, poc, mvp, production, sensitive), which sets how much code review runs and which security findings stop the line; start a hardening phase. Owner-invoked only.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. urhired-ai/system-design-workshop★ 4same name
    2. AVANT-ICONIC/gpt-webui-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill 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:

    Write Dev mode: <mode> into the project's CLAUDE.md, replacing the existing line or adding one directly under its first heading.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

/dev-mode — the project's dev mode

The rules are section 14, ~/.claude/rules/DEV_MODES.md. Read it by path first, every time. This skill only carries out what I asked for; it adds no gate and no authority of its own. Only I invoke it, which is what makes a mode change "my word" (rule 14.1).

The argument is: $ARGUMENTS

No argument, or status

  1. Find the project's CLAUDE.md (the repository root of the current working directory) and its Dev mode: line. Read-only.
  2. Report, in plain words:
    • the mode, and whether it was declared or is the rule 14.1 default (say which default and why);
    • what that mode means here: its row of the review table (rule 14.2) and what stops the line;
    • whether the data minimum applies — if the project visibly holds real personal, financial or health data while its line says less than sensitive, say so plainly;
    • from docs/security/backlog.md and docs/security/backlog.local.md, if either exists: open entries by due, and how many are due at the next mode up.
  3. Change nothing.

A mode: spike, poc, mvp, production, sensitive

  1. Reject anything else, naming the five modes.
  2. Lowering below the data minimum is refused (rule 14.1): if the project holds real personal, financial or health data, a mode below sensitive is not set — say why, and stop. If you cannot tell, ask me that one question.
  3. Write Dev mode: <mode> into the project's CLAUDE.md, replacing the existing line or adding one directly under its first heading; create the file with that line if it does not exist. Update the Dev mode: line of the running plan's header in PLAN.md (or the plan file it indexes) if there is one. Touch nothing else.
  4. Moving up (rule 14.6): this is my go for the hardening plan. Hand it to the planner (rule 8.1): every backlog entry due at the new mode, plus any I named. Then say what the move costs: the entries due, and the review row that now applies.
  5. Moving down within what the data allows: say which reviews stop running and which findings stop blocking from now on. Nothing already recorded in the backlog is removed.
  6. Report the old mode, the new mode, and the files changed. The change lands in the next commit of the normal task chain (rule 6.1); it needs no version bump of its own.

harden

Valid only in production or sensitive; otherwise say so and stop. This is my go for the extra-hardening phase (rule 14.7): hand the planner every entry due at hardening, to run as its own phase on its own line beside feature work, under the production row's reviews. Report how many entries it covers.

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