Elysia Architecture

Portable house style for Elysia HTTP apps. Use this skill alone — it does not depend on other skills.

Job: where code lives, how folders/files are named, and ownership boundaries.

Not this skill: Elysia API quirks, plugin lifecycle details, Eden, adapters, or latest framework docs. Prefer current Elysia docs for those.

If the target repo already documents architecture (e.g. AGENTS.md) and it conflicts, repo wins unless the user asks to migrate toward this skill.

Stack defaults (core)