agentleFS
Sign inStart free
Mark-LifeMark-Life/peektrace/CLAUDE.md

peektrace

CLAUDE.md4 starsChanged 3 months agoMITView on GitHub

Use these to explore APIs, find usage examples, and understand implementation details when the documentation isn't enough. Check the version that matches the code you're touching; when in doubt, consult both.

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

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When writing or reviewing TypeScript/full-stack code, follow the quality-code skill (.agents/skills/quality-code/SKILL.md).

    line 2
  2. Distinctive:

    Use these to explore APIs, find usage examples, and understand implementation details when the documentation isn't enough.

    line 14

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

Code Quality

When writing or reviewing TypeScript/full-stack code, follow the quality-code skill (.agents/skills/quality-code/SKILL.md). It loads on demand — invoke it for the full standards.

Typecheck

Typecheck with bun run typecheck (per-package tsc --noEmit). Never run tsc -b or bare tsc — build/emit mode writes .js/.d.ts/.d.ts.map next to sources and pollutes the tree; stale emitted *.test.js then get double-run by bun test. The base tsconfig sets noEmit, but build mode (-b) bypasses it. This repo never builds via tsc (Bun runs TS directly; the inspector builds with Vite; web with Next).

Local Effect Source

Two Effect checkouts are cloned locally for reference (we're mid-transition, so both matter):

  • v3 (current stable): ~/.local/share/effect-solutions/effect — effect@3.21.0, the main Effect-TS/effect repo.
  • v4 (smol / next): ~/.local/share/effect-solutions/effect-smol — effect@4.0.0-beta.x, the Effect-TS/effect-smol repo.

Use these to explore APIs, find usage examples, and understand implementation details when the documentation isn't enough. Check the version that matches the code you're touching; when in doubt, consult both.

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