Eve Fullstack App Design

Load this when you're drawing up a new Eve app or moving one over. It walks through the manifest as architectural blueprint: how to lay out services (API plus worker plus managed DB is the common pattern), when to mark things external, how ingress and stable egress work, and where object storage and Cloud FS mounts fit. The reference architecture section shows the nginx SPA proxy pattern that keeps your API internal and kills CORS. It's design thinking for Eve's PaaS layer, not CLI mechanics. If you need to know whether your current setup uses the platform well or you're planning service topology from scratch, this gives you the mental model.

skills.sh installs: 274
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add incept5/eve-skillpacks --skill eve-fullstack-app-design --agent claude-code

Installs into .claude/skills of the current project.

Files

Full-Stack App Design on Eve Horizon

Architect applications where the manifest is the blueprint, the platform handles infrastructure, and every design decision is intentional.

When to Use

Load this skill when:

Designing a new application from scratch on Eve
Migrating an existing app onto the platform
Evaluating whether your current architecture uses Eve's capabilities well
Planning service topology, database strategy, or deployment pipelines
Deciding between managed and external services

This skill teaches design thinking for Eve's PaaS layer. For CLI usage and operational detail, load the corresponding eve-se skills (eve-manifest-authoring, eve-deploy-debugging, eve-auth-and-secrets, eve-pipelines-workflows).

The Manifest as Blueprint

The manifest (.eve/manifest.yaml) is the single source of truth for your application's shape. Treat it as an architectural document, not just configuration.