agentleFS
DahunHanDahunHan/lattice/CLAUDE.md

lattice

CLAUDE.md8 starsChanged 7 months agoMITView on GitHub

Workflow: Architect -> Frontend Dev -> (Design Reviewer + Code Reviewer in parallel) -> QA Tester Workflow: Dogfood Tester -> (Docs Writer + Community Manager in parallel) -> Content Creator -> Growth Tracker

The file

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:

    All files .ts or .tsx. No .js.

    line 41
  2. Distinctive:

    Design is KING: Every pixel matters.

    line 49

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

Lattice — Agent Workflow Visualizer

1. Goal

Open-source Next.js dashboard that auto-reads project folders or uploaded MD files and renders an interactive, stunning visualization of agent workflows. Replaces the FlowSight Streamlit prototype.

2. Orchestration

Built by a 5-agent harness:

AgentRole
architectComponent structure, data models, API design
frontend-devReact components, styling, animations
design-reviewerVisual quality gate (>= 7/10 to pass)
code-reviewerCode quality, performance, security
qa-testerParsing validation, edge cases, browser compat

Workflow: Architect -> Frontend Dev -> (Design Reviewer + Code Reviewer in parallel) -> QA Tester

Growth Harness (open source ops)

AgentRole
dogfood-testerTests Lattice against real open source agent projects, reports bugs
docs-writerMaintains README, guides, changelogs, onboarding content
content-creatorWrites launch posts, Twitter threads, Reddit posts, dev.to articles
community-managerTriages GitHub issues, manages PRs, tracks community health
growth-trackerMonitors npm downloads, GitHub stars, generates weekly growth reports

Workflow: Dogfood Tester -> (Docs Writer + Community Manager in parallel) -> Content Creator -> Growth Tracker

3. Technical Stack

  • Framework: Next.js 16 (App Router)
  • Language: TypeScript (strict, no any)
  • Styling: Tailwind CSS
  • Graph: React Flow (@xyflow/react)
  • State: Zustand
  • Animation: Framer Motion
  • Layout: Dagre (@dagrejs/dagre)

4. Coding Standards

  • All files .ts or .tsx. No .js.
  • Named exports only (except page defaults).
  • One component per file, PascalCase filenames.
  • Tailwind classes only — no CSS modules, no styled-components.
  • Parsers are pure functions with explicit types.
  • Dark theme: bg #0A0A1B, surface #12122A, border #1E1E3A, text #E0E0F0, accent #F5A623.

5. Design Principles

  • Design is KING. Every pixel matters.
  • Dark theme with glassmorphism, glows, smooth animations.
  • Information density over whitespace — developer tool, not marketing site.
  • Hover reveals detail. Click opens panels.
  • 200ms transitions. Framer Motion for enter/exit.
  • Desktop-first, min 1024px viewport.

6. Input Modes

  1. Upload: Drag & drop MD files
  2. Scan: Provide folder path, API route reads all .md files recursively

7. What Gets Parsed

  • AGENT_MAP.md — CSV tables of agents
  • SYSTEM-ARCHITECTURE.MD — Pipeline phases, data flow
  • CLAUDE.md — Project goals, model allocation
  • .agents/skills/*/SKILL.md — Agent instructions
  • Any .md with agent-related content (heuristic detection)

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.