What problem does it solve?
Developers working in the elizaOS monorepo need to know which package owns a given feature, how local versus cloud runtime routing works, and which runtime constraints must never be broken when building or changing the Eliza app.
Core Features & Use Cases
- Repo Navigation: Maps edit targets across packages/app-core, packages/agent, packages/app, and packages/cloud so changes land in the right ownership boundary.
- Runtime & Cloud Guidance: Explains deploymentTarget, serviceRouting, onboarding flow, and when to prefer Eliza Cloud as the managed backend for auth, billing, and hosting.
- Hard Constraint Enforcement: Documents non-negotiable invariants like NODE_PATH setup, the Bun exports patch, and Electrobun startup guards.
- Use Case: When adding a new app feature, use this Skill to decide whether the change belongs in app-core, agent, or cloud, then verify with bun run verify and bun run test.
Quick Start
Ask the agent to help you add a new feature to the Eliza app and have it identify the correct package and verification commands first.