What problem does it solve? Developers working in an elizaOS application monorepo often struggle to know which package owns a given behavior, how local versus cloud runtime routing works, and which runtime constraints must never be broken. This Skill provides the architectural map and editing heuristics needed to make correct changes without breaking the app. ## Core Features & Use Cases - Repo Navigation: Maps edit targets across packages/app-core, packages/agent, apps/app, and eliza/cloud so changes land in the right ownership boundary. - Runtime & Cloud Guidance: Explains deployment targets, service routing, onboarding flow, and when to default to Eliza Cloud 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 feature to the Eliza desktop app, use this Skill to determine whether the change belongs in app-core, the agent layer, or upstream elizaOS, then verify with the correct bun commands. ## Quick Start Ask the assistant to help you implement a new feature in the Eliza app and it will use this Skill to identify the correct package, follow the repo workflow, and respect runtime constraints.