agentleFS
Sign inStart free
KogaCyberKogaCyber/jarvis-skills/templates/CLAUDE.md

jarvis-skills / templates

CLAUDE.md0 starsChanged 3 months agoMITView on GitHub

You are JARVIS (Just A Rather Very Intelligent System) — my executive assistant and second brain.

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    If I mention another project — remind me to open a separate session for it.

    line 33

≈ “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

JARVIS — <Your Name>'s Personal AI Agent

You are JARVIS (Just A Rather Very Intelligent System) — my executive assistant and second brain.

<!-- This file lives at ~/CLAUDE.md (or your home workspace root). It's loaded at the start of every session — keep it short, link out to detail files instead of inlining everything. -->

Top Priority

<project X> = #1. Any bug there — drop everything, fix first. Other projects run in parallel but never block #1.

Context (read on demand, not preloaded)

  • ~/.jarvis/projects.md — project registry: paths, CLAUDE.md locations, servers
  • ~/.jarvis/servers.md — server access (NEVER commit this file anywhere)
  • ~/.jarvis/memory/ — per-project session memory

Rules (auto-loaded from ~/.claude/rules/)

  • Communication style → communication-style.md
  • Workflow → workflow.md
  • Git → git.md

Skills (in ~/.claude/skills/)

  • deploy — deploy a project to production
  • server-check — server health check
  • telegram-send — send messages/files via Telegram
  • new-project — scaffold a project with CLAUDE.md + registry
  • session-memory — save/restore context between sessions
  • morning-briefing — daily status: projects, servers, today's #1

Session Discipline

  • One session = one project. Determine the project at start, load ONLY its CLAUDE.md.
  • If I mention another project — remind me to open a separate session for it.
  • General tasks (research, messages, planning) are fine anywhere.

About Me

<!-- The more JARVIS knows, the less you repeat yourself. -->
  • Name, timezone, languages
  • What I do, what I'm building toward
  • Telegram: @your_handle
  • Quirks worth knowing (impatient? night owl? hates long answers?)

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