How AI coding agents (and the humans steering them) should work inside this repo. This is the agent-native operating contract for agentgrid itself. Co-evolve it over time. agentgrid is two products in one repo plus a self-improving harness: Use the right one; sub-agents research and review, the parent implements. CLI (the pub
How any coding agent uses and works on agentcast. This is the one source; CLAUDE.md and GEMINI.md point here. agentcast owns the sub-agents part of an agent's harness. It keeps a library of six reusable personas (researcher, code-reviewer, test-writer, security-reviewer, architect, qa-tester), installs them into a project's .claude/agents/, and checks any persona against what Claude Code reads today: name and description required, tools as the allowlist (never allowed-tools), valid model and permission values, and the flat path. It scores personas…
fleet-audit scans repositories for every surface coding agents need, checks them against one standard, scrubs them before they go public, and writes what is missing. Its persona is Muster. This file is the one set of instructions for every coding agent; Claude Code and Gemini CLI read it through CLAUDE.md and GEMINI.md. - Scan a repository from a committed ref: AGENTS.md, CLAUDE.md, GEMINI.md, llms.txt, skills, sub-agents, hooks, an MCP server, a CLI, a Claude Code plugin and marketplace, a Gemini…
This file tells a coding agent (Claude Code, the energy hub, sibling employees) what pixel is, how to call it, and where its competence lives. Read brain/ first — brain/MOC - pixel.md is the map. pixel is a TOOL-employee, not a SaaS: the surfaces are the CLI, the MCP server, and the local cockpit. pixel is a highly opinionated frontend web designer-engineer for the 2026 Next.js / React / Tailwind / shadcn stack. It treats every generated UI as an…
turbo is the Energy fleet's backend / runtime domain-expert employee. It is a tool-employee, not a messaging product: coding agents (Claude Code, the energy hub, sibling employees) operate it through the CLI and the MCP server; the chairman watches it through the local cockpit. This file tells an agent what turbo does, how to invoke every tool, the hard boundary, and what NOT to do. One-line stack: Hono ≥4.12.25 · Node 24 LTS (floor 22) · Zod 4.4 · @hono/zod-openapi…