Eliza App Development
Developmenteliza-app-developmentEliza App Development is an Agent Skill for development published in the elizaOS/eliza repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when building or changing an elizaOS-based application in this repository. Covers eliza app architecture, monorepo layout, local versus remote versus cloud routing, where to edit features, and non-negotiable runtime constraints. Eliza is the product name of this particular eliza app checkout.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/elizaOS/eliza/blob/HEAD/packages/skills/skills/eliza-app-development/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/eliza-app-development, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
eliza app development
This repository is an elizaOS application: a local-first assistant with CLI, dashboard, Electrobun desktop shell, connectors, and Eliza Cloud integration. Eliza is this app’s product and CLI name—not a separate platform from elizaOS.
Read These References First
references/repo-map.mdfor layout, edit targets, and common commandsreferences/runtime-and-cloud.mdfor runtime flow, onboarding, service routing, skills, and Eliza Cloud behavior
Editing Heuristics
- Prefer
packages/app-core/for app shell behavior (API, CLI, onboarding, config). - Prefer
packages/agent/for agent providers, services, and runtime glue around elizaOS. - Prefer
apps/app/for UI and Electrobun work. - Treat
eliza/cloud/as the Eliza Cloud product and backend surface. - Treat
eliza/as upstream elizaOS. Edit it only when the bug or feature is genuinely upstream.
Hard Constraints
- Do not remove
NODE_PATHsetup. - Do not remove the Bun exports patch.
- Do not remove Electrobun startup error guards.
- Keep Node and Bun paths working.
Repo Workflow
bun install
bun run verify
bun run test
Narrower commands when useful:
bun run eliza ...
bun run dev
bun run dev:desktop
bun run test:e2e
Where to Look First
- Product and runtime behavior:
packages/app-core/src/ - Prompt, provider, and skill plumbing:
packages/agent/src/ - Onboarding and routing:
packages/app-core/src/onboarding/andpackages/app-core/src/runtime/ - Shipped default skills: bundled in
@elizaos/skills, seeded into the state-dir skills folder byscripts/ensure-skills.mjs - Eliza Cloud backend or monetization:
eliza/cloud/and the shippedeliza-cloudskill
Cloud Default
If the task involves building an app and Eliza Cloud is enabled, linked, or explicitly requested, treat Cloud as the default managed backend before inventing custom auth, billing, analytics, or hosting. Use the eliza-cloud skill for app, monetization, and container details.
Related Skills
elizaos— core runtime abstractions and upstream plugin patternseliza-cloud— apps, billing, monetization, auth, containers