This file is the single source of truth for agents entering this repository. Read this file first; after entering apps/, packages/, tools/, or e2e/, read that layer's AGENTS.md for module-level details. Do not copy module details back into the root file; root stays focused on cross-repository boundaries, workflow, and commands.
This directory holds design templates — packaged "shapes" the agent renders into a project artifact (decks, prototypes, image/video/audio templates, …). Each entry is a folder with a SKILL.md (same shape as functional skills) plus rendering side files (example.html, assets/, references/, …). If the entry primarily does work on user input — utilities, briefs, asset packagers, fidelity audits — it belongs under ../skills/ instead. See specs/current/skills-and-design-templates.md for the full split. - Listed under /api/design-templates. The shape mirrors /api/skills (same SkillSummary/SkillDetail types)…
Follow the root AGENTS.md first. This package owns user-level end-to-end smoke tests and Playwright UI automation only. For the current coverage posture, recent hardening work, grouped-run status, and known intentional gaps, see docs/testing/e2e-coverage/status.md.
This directory is still only partially standardized. Several historical workflows and helper locations do not yet follow one uniform shape. Do not copy old patterns blindly. For new work, bug fixes, and cleanup, use the ci.yml + comment.atom.yml + autofix.atom.yml + report.atom.yml + .github/scripts/handoff.py system as the reference topology unless a maintainer explicitly chooses a different boundary. Before changing GitHub automation, read the current versions of: If the change affects cross-workflow behavior, update the topology tests instead of relying only…
This directory owns MonoField plugin content and plugin authoring material. For plugin content changes, run: When the daemon CLI is built and available, also validate runnable plugin folders with:
This directory holds functional skills — capabilities the agent invokes mid-task to do work on user input. Each skill is a folder with a SKILL.md (frontmatter + body) and any side files (assets/, references/, scripts, …) the workflow needs. If the entry primarily renders a design artifact (deck, prototype, image/video/audio template) it belongs under ../design-templates/ instead. See specs/current/skills-and-design-templates.md for the full split. - Listed under /api/skills (functional only). User-imported skills shadow built-in entries with the same frontmatter name. - Asset…