agentleFS
Zwin-uxZwin-ux/kit/AGENTS.md

kit

AGENTS.md0 starsChanged 11 days agoMITView on GitHub

Product (2.x): Kit is the control room for parallel agent work. Dispatch many agents. Watch them in one place. Nothing ships unproven. Not the product: skill marketplace, registry social, Ink TUI (archived). Skills remain local substrate — what you dispatch, not the point. Full PRD: docs/dev/PRD-1.0.md Who builds what: docs/dev/BUILD-ASSIGNMENT.md Active surface tasks: tasks/plan.md, tasks/todo.md See docs/dev/ORCHESTRATION.md. Luna storm: parallel explore/implement shards; Power synthesizes; CEO decides/merges. Workflow sketch: .grok/workflows/kit-luna-storm.rhai (local; .grok may be gitignored). Quality ladder (long-running): docs/dev/WORKFLOW-QUALITY.md + workflow…

The file

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

    Surface assumptions: before implementing.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
AGENTS.md

Kit — Agent Context

Product (2.x): Kit is the control room for parallel agent work.
Dispatch many agents. Watch them in one place. Nothing ships unproven.

Not the product: skill marketplace, registry social, Ink TUI (archived).
Skills remain local substrate — what you dispatch, not the point.

Full PRD: docs/dev/PRD-1.0.md
Who builds what: docs/dev/BUILD-ASSIGNMENT.md
Active surface tasks: tasks/plan.md, tasks/todo.md


Multi-agent roles (CEO / Power / Luna)

See docs/dev/ORCHESTRATION.md.

RoleWhoJob
CEOClaudeSequence, kill criteria, contract edits, merge, product policy
PowerGrokHeavy implementation, TUI/engine wiring, spawn Luna threads
FactoryCodexMechanical ports, fixtures, CI scaffolding
LunaMany short agentsOne-shard diagnose/design/verify (parallel token burn)

Luna storm: parallel explore/implement shards; Power synthesizes; CEO decides/merges.
Workflow sketch: .grok/workflows/kit-luna-storm.rhai (local; .grok may be gitignored).
Quality ladder (long-running): docs/dev/WORKFLOW-QUALITY.md + workflow kit-quality-cycle
(audit → skeptic → plan → implement → prove). Git copy: docs/dev/workflows/kit-quality-cycle.rhai.
Craft ladder (design | product first): workflow kit-craft-cycle before TUI/motion slices. Git copy: docs/dev/workflows/kit-craft-cycle.rhai.
CEO brief template: docs/dev/tasks/CEO-BRIEF-next.md.

Claude-grade coding practice (always): Karpathy surgical diffs and tests-as-success; addyosmani spec → plan → TDD → five-axis review; public contracts change only with a CHANGELOG entry and a test; motion is live work (RUNNING/GATING spinner) plus the resting fox's tail wag in the empty Control Room (kit-tui/src/fox.rs), all on the one clock.

Engineering skills (always)

This repo installs addyosmani/agent-skills under .agents/skills/ (24 skills).

Before non-trivial work, load using-agent-skills and route:

PhaseSkillKit use
Definespec-driven-developmentNew surface / engine milestone
Planplanning-and-task-breakdownWrite tasks/plan.md + tasks/todo.md first
Buildincremental-implementationThin slices; test after each; commit
Buildtest-driven-developmentReducer + insta snapshots for TUI
Buildfrontend-ui-engineeringTUI interaction language, a11y, fixed geometry
Buildapi-and-interface-designPublic contracts: CHANGELOG entry and a pinning test
Builddoubt-driven-developmentPTY, gate semantics, cross-crate seams
Verifycompleteness-qaAfter implement, before claiming done. Run node skills/completeness-qa/scripts/inventory.mjs --root . — stubs mean not done
Verifydebugging-and-error-recoveryRepro → localize → fix → guard
Reviewcode-review-and-qualityBefore every PR
Reviewcode-simplificationAfter green, before ship
Reviewsecurity-and-hardeningFirewall, scope, no credential custody
Reviewperformance-optimizationM0 kill: cold start <100ms, idle CPU <1%
Shipgit-workflow-and-versioningAtomic commits, ~100-line preference
Shipdocumentation-and-adrsADRs in docs/adr/ for boundary decisions

Core operating rules (from using-agent-skills)

  1. Surface assumptions before implementing.
  2. Stop on confusion — do not guess contracts.
  3. Push back on approaches that break kill criteria or crate boundaries.
  4. Simplicity first — boring over clever.
  5. Scope discipline — only touch the task's crate/files.
  6. Verify with evidence — cargo test / clippy / snapshots; "looks right" is never done.

Who may edit what

Any agent may edit any crate (kickoff spec K15, docs/superpowers/specs/2026-10-26-kit-kickoff.md). Two rules guard the public surface:

  • A change to a kit-core public type, a --json shape, KIT.toml / kit.toml, kit.lock or the receipt format needs a CHANGELOG.md entry and a test that pins the new shape.
  • The bar for every change is docs/QUALITY.md: tests at the right layer, a snapshot for every screen change, CI green on all three operating systems.

TUI non-negotiables:

  • One clock: only AppEvent::AnimationTick (no other timers)
  • Hit-testing from the same ratatui rects the renderer drew (F6)
  • Navigation mutates Screen in the reducer; engine work is Action
  • Reduced motion: NO_COLOR, KIT_MOTION=off

Commands

# Run the product
cargo run -p kitctl -- --demo    # Control Room + PRD fixture
cargo run -p kitctl              # empty Control Room
cargo run -p kitctl -- doctor

# Verify
cargo test -p kitctl-tui
cargo clippy -p kitctl -p kitctl-tui --all-targets -- -D warnings
cargo fmt --all --check
cargo test --workspace

Living status: docs/dev/CURRENT.md

Rust workspace: crates/kit-{core,agents,gate,tui,cli}
The Kit 0.1 TypeScript tree was removed from trunk in A0.0; it is kept at tag legacy-0.1-final.


Milestone map (surface focus)

DoneIn flight / next
M0 event loop (F1)F4 Dispatch + Board
F2 Control Room tableF5 Theme / motion (fox mascot back in 2.0.0)
F3 Run detailF6 Layout + hit-testing
M3 gate port (Codex)M1 engine (Codex) enables live runs

Visual / interaction language

  • Control Room is the default (kit → table of runs)
  • One interaction voice across screens (same footer grammar, Esc back)
  • Failures surface first error line in the table; detail holds full gate log
  • Attach: Esc detaches without kill; q disabled while attached

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.