eliza-app-development

Guides development of elizaOS applications across monorepo packages, runtime routing, and Eliza Cloud integration.

1|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/Solizardking/Solana-Robotics-Kit --skill eliza-app-development-solizardking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eliza-app-development
Source: https://github.com/Solizardking/Solana-Robotics-Kit/tree/main/eliza/packages/skills/skills/eliza-app-development
Command: npx skills add https://github.com/Solizardking/Solana-Robotics-Kit --skill eliza-app-development-solizardking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about eliza-app-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which package to edit in an elizaOS app monorepo?

Choose the smallest correct ownership boundary: packages/app-core for CLI, API, onboarding, and config; packages/agent for runtime glue and providers; apps/app for UI and Electrobun; eliza/cloud for Cloud backend features. Edit upstream elizaOS only when the issue is genuinely upstream.

How do I build an app on Eliza Cloud instead of custom backend?

Create or reuse an Eliza Cloud app with its appId and API key, configure origins and redirect URIs, and use Cloud APIs for chat, media, and agent features. Enable monetization through markup and share fields, and deploy a container only when server-side code is required.

What commands verify changes in the eliza app repository?

Run bun install, bun run verify, and bun run test for full repo checks. For narrower verification use bun test on a specific package, bun run --cwd <package> test, or bun run --cwd <package> typecheck before broader checks.

What runtime constraints must not be removed in elizaOS apps?

Three invariants are non-negotiable: NODE_PATH setup required for dynamic plugin imports, the Bun exports patch required for published @elizaos packages, and Electrobun startup guards that keep the desktop UI usable when the runtime fails.

How are default skills bundled and seeded in the Eliza app?

Default skills live under packages/skills/skills/<slug>/SKILL.md and are bundled in @elizaos/skills. At runtime startup, scripts/ensure-skills.mjs seeds them into the state-dir skills folder without overwriting existing editable copies.