aios-project-systemlisted

# AIOS Project System ## Overview Use this skill as the repository map for `aios`. It explains where state lives, how automation actually runs, and which files are authoritative before you edit tasks, workflows, or browser operations. **This skill is a map, not a router.** For task routing, use `aios-workflow-router`. For process skills, use `superpowers:*`. ## Core Topology - `CLAUDE.md` / `AGENTS.md` / `GEMINI.md`: per-client project-level behavior contract and architecture overview (each client loads its own instruction file). - `skill-sources/*/SKILL.md`: canonical skill sources (edit here, never edit generated copies). - Generated repo-local skills per client: `.codex/skills`, `.claude/skills`, `.gemini/skills` (also used by Antigravity), `.opencode/skills`, `.crush/skills`, `.agents/skills` — emitted from `skill-sources/` via `config/skills-sync-manifest.json`. - `scripts/lib/specs/*.json`: runtime specifications and limits. - `tasks/{pending,done,failed}`: task queue and outcomes. - `scripts/run-browser-use-mcp.sh`: default browser MCP launcher (bridges to `ai-browser-book/mcp-browser-use`). - `mcp-server/`: legacy Playwright MCP implementation retained for compatibility workflows. - `docs/plans/`: design, implementation, and postmortem documents. ## Runtime Truths (Do Not Skip) - The primary browser MCP server label is `mcp-browser-use`; do not add compatibility aliases for old browser MCP names. - `mcp-server/src/index.ts` still exposes Playwright `browser_*` too