eliza-app-development

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

19.2k|5.7k|Updated Jul 9, 2024
One-click install
npx skills add https://github.com/elizaOS/eliza --skill eliza-app-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eliza-app-development
Source: https://github.com/elizaOS/eliza/tree/main/packages/skills/skills/eliza-app-development
Command: npx skills add https://github.com/elizaOS/eliza --skill eliza-app-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

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 the elizaOS monorepo?

Use packages/app-core for CLI, API, onboarding, and runtime startup; packages/agent for providers and runtime glue; packages/app for UI; and packages/cloud for Eliza Cloud backend. Pick the smallest ownership boundary that already owns the behavior.

How do I add a default skill to the Eliza app?

Add a SKILL.md with concise frontmatter under packages/skills/skills/<slug>/ and put long details in references/*.md. The ensure-skills.mjs script seeds bundled skills into the state-dir skills folder without overwriting existing copies.

When should I use Eliza Cloud instead of custom backend code?

Prefer Eliza Cloud when it is enabled, linked, or explicitly requested, since it provides auth, billing, analytics, domains, and hosting. Only deploy a custom container when server-side code is actually required.

What runtime constraints must not be removed in the Eliza app?

Do not remove NODE_PATH setup, the Bun exports patch, or Electrobun startup error guards. These are required for dynamic plugin imports, published @elizaos/* package compatibility, and keeping the desktop UI usable when the runtime fails.

How do I verify changes in the elizaOS repository?

Start with the narrowest check such as bun test <package> or bun run --cwd <package> typecheck. For cross-package changes, run bun run verify and bun run test from the repository root.