agentleFS
gyujeongiongyujeongion/claude-life-agent/10_WORK/CLAUDE.md

claude-life-agent / 10_WORK

CLAUDE.md2 starsChanged 4 months agoMITView on GitHub

Things you're actively working on that have an end. When a project has no deadline, it's a role → 20_DOMAINS/. When it's done → 80_ARCHIVE/. 마감이 있는, 진행 중인 작업. 마감 없으면 역할 → 20_DOMAINS/. 끝나면 → 80_ARCHIVE/. Copy _PROJECT_TEMPLATE/ for each new project: Projects fade out silently — a submission goes unanswered, a client goes quiet, a plan just stops. Two rules learned the hard way: - Folder timestamps don't prove activity. Real work often happens outside this workspace…

The file

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

    Every project README.md starts with a status: line.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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

10_WORK — active projects (with deadlines)

Things you're actively working on that have an end. When a project has no deadline, it's a role → 20_DOMAINS/. When it's done → 80_ARCHIVE/.

마감이 있는, 진행 중인 작업. 마감 없으면 역할 → 20_DOMAINS/. 끝나면 → 80_ARCHIVE/.

Current projects

FolderDeadlinestatus
_PROJECT_TEMPLATE/—(template — copy me)

Standard project structure

Copy _PROJECT_TEMPLATE/ for each new project:

PROJECT/
├── README.md      # first line: status: <tag>; overview, deadline, who
├── docs/          # plans, proposals
├── decisions/     # decisions specific to this project
├── references/    # source material
└── outputs/       # deliverables

Rules

  • Every project README.md starts with a status: line.
  • Done → set status: complete, move the folder to 80_ARCHIVE/.
  • Rejected/dead → status: abandoned, reason → 00_SELF/decisions/feedback_patterns.md.
  • Deadlines that matter also belong on your calendar and/or 00_SELF/memory/todo.md.

The stale-project sweep (do this monthly)

Projects fade out silently — a submission goes unanswered, a client goes quiet, a plan just stops. Two rules learned the hard way:

  • Folder timestamps don't prove activity. Real work often happens outside this workspace (a studio, a meeting, another tool). Never judge a project dead by mtime.
  • Never auto-archive on staleness alone. List projects with no updates for 2–3 months, ask the owner one line per project, then tag on-hold / abandoned / complete accordingly. An honest "active" table is what makes this folder trustworthy — a router that points at dead projects misleads every future session.

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.