Skip to content
gentic.news — AI News Intelligence Platform
Connecting to the Living Graph…

Listen to today's AI briefing

Daily podcast — 5 min, AI-narrated summary of top stories

A solo developer at a desk writes code on a laptop while multiple AI agent icons float around the screen, with a…

Write Your Repo for AI, Not Humans

Adopt the `claude-code-life` template: one repo with `CLAUDE.md` shared context, `.claude/skills/` per-purpose agents, and one-fact-per-file YAML frontmatter for AI-readable knowledge that compounds across journaling, projects, and self-analysis.

·1d ago·3 min read··3 views·AI-Generated·Report error
Share:
Source: dev.tovia devto_claudecodeMulti-Source
How do I structure a Git repository for Claude Code to run my life as multiple AI agents?

Use the `claude-code-life` template to structure your repo with one-fact-per-file YAML frontmatter, `.claude/skills/` for per-purpose agents, and `CLAUDE.md` shared context — so Claude Code can query across journaling, projects, and self-analysis.

TL;DR

One developer runs his entire life as a single Git repo with Claude Code, writing documents for AI readability, not human prose.

The Technique: One Repo, Multiple Agents, AI-First Documents

Takotyan00 realized a fundamental truth: when you're solo, there's no human team to read your docs. The primary reader is the AI. So he stopped writing for humans and started writing for Claude Code.

His claude-code-life template on GitHub is open-source and immediately actionable. It's a single Git repository that houses his journal, self-analysis, project metadata, and ideas — all structured so Claude Code can query across them seamlessly.

The Three Rules for AI-First Documents

  1. One fact per file. No long prose. Each file contains a single, atomic piece of information.
  2. Searchable metadata in frontmatter. Every file starts with a YAML block the AI can grep or query against.
  3. Name files for AI retrieval. Ask "will the AI be able to find this later?" — not "will a human understand this filename?"

Repository Skeleton

life/
├── journal/      # dialogue-style journal (year/month/day.md)
├── persona/      # self-analysis (dimensions/, chapters/, insights/)
├── projects/     # metadata for each dev project
├── ideas/        # seeds of ideas
└── .claude/
    ├── skills/            # per-purpose agents (/journal, /weekly-review, /persona)
    ├── rules/             # behavioral rules injected into agents
    └── config/context.yaml  # context shared by every skill

Why It Works: Compounding Context

Separate apps split up the one thing that should stay continuous: you. Your investing tool doesn't know your values. Your journaling app doesn't know your cognitive quirks. By bundling everything into one repo, the AI reads across all domains. The base gets stronger the more you build.

This is the opposite of a "second brain." A second brain is meant to be read back later. Here, the notes are deliberately unreadable to you. The human-facing interface is conversation — you ask Claude Code, not open files.

How To Apply It

  1. Clone the template: git clone https://github.com/takotyan00/claude-code-life
  2. Set up shared context: Copy .claude/config/context.example.yaml to .claude/config/context.yaml and fill in your interests and projects.
  3. Use the built-in skills: Run /journal for dialogue-style journaling, /weekly-review for weekly retrospectives, /persona for self-analysis.
  4. Customize rules: Adjust .claude/rules/ for behavioral tweaks. The template includes correction rules (e.g., example-understated-expression.md) to help the AI read you correctly.

What's Included in the Template

  • CLAUDE.md — shared instruction template
  • .claude/skills/ — three skills: journal, weekly review, persona (generalized)
  • .claude/rules/ — methodology rules + dialogue behavior rules + format templates
  • .claude/rules/correction-rules/ — one generalized example for correcting how the AI reads you
  • .claude/config/context.example.yaml — context template for all skills
  • Directory READMEs for journal/, ideas/, projects/, persona/

Try It Now

# Clone the template
cd ~
git clone https://github.com/takotyan00/claude-code-life.git life

# Set up your context
cp life/.claude/config/context.example.yaml life/.claude/config/context.yaml

# Edit context.yaml with your own interests and projects

# Start Claude Code and try a skill
claude code
# Then type: /journal

This isn't about organizing your life for a human reader. It's about building a knowledge base that Claude Code can query across domains — and the more you add, the smarter the AI becomes about you.

Cover image for My repository isn't written for humans — I run my whole life with Claude Code


Source: dev.to

Source: gentic.news · · author= · citation.json

AI-assisted reporting. Generated by gentic.news from multiple verified sources, fact-checked against the Living Graph of 4,300+ entities. Edited by Ala SMITH.

Following this story?

Get a weekly digest with AI predictions, trends, and analysis — free.

AI Analysis

Claude Code users should immediately adopt the `one-fact-per-file` frontmatter pattern for any personal knowledge base. Stop writing long journal entries. Instead, structure them as YAML frontmatter with date, mood, tags, and highlights — then let the AI handle retrieval. The `claude-code-life` template demonstrates exactly how to wire `.claude/skills/` as per-purpose agents that share a single `context.yaml`. Users should clone this repo, strip the personal data, and adapt the skills to their own domains (e.g., finance tracking, hobby curation, parenting logs). The key workflow change: stop opening files to read them. The human interface is conversation. Run `/journal` to log a day, `/weekly-review` to get a summary, `/persona` for self-analysis. This shifts from a pull model (you search) to a push model (you ask Claude Code). The correction rules in `.claude/rules/correction-rules/` are also underutilized — users should add their own examples of how the AI misreads their tone or understated expressions to improve accuracy over time.
This story is part of
Claude Code's Campus Conquest Flips Anthropic's Talent Pipeline, Leaving Google's Academic Edge in Doubt
Viral adoption at MIT and Stanford transforms Claude Code from product into recruiting funnel, threatening Google's long-held research talent dominance
Compare side-by-side
Claude Code vs claude-code-life
Enjoyed this article?
Share:

AI Toolslive

Five one-click lenses on this article. Cached for 24h.

Pick a tool above to generate an instant lens on this article.

Related Articles

From the lab

The framework underneath this story

Every article on this site sits on top of one engine and one framework — both built by the lab.

More in Opinion & Analysis

View all