Skip to main content

​
App patterns

Pick the smallest app shape that matches the job. Add a process, database, sync, or AI API only when the app needs that capability.
User wantsUseNotes
Landing page, report, static pageUI appOne UI component is enough.
Dashboard or internal tool with server dataUI + processKeep API routes and credentials in the process component.
Persistent app dataUI + process + databaseReuse a suitable active database before creating one.
Offline or instant multi-device dataRealtime appEnable sync and verify sync: ready before wiring the app.
Scheduled job or webhookProcess appUse triggers on a process component.
AI-powered feature inside an appProcess + Kazzle AI APIUse /ai/* with a kzl_ API key.
Tool the assistant should call laterSkillCreate a skill component with a SKILL.md entrypoint.

​
Defaults

  • Start from a template when one fits.
  • Keep frontend code free of secrets and database URLs.
  • Put server-only work in a process component.
  • Use sibling component URLs instead of hardcoded localhost addresses.
  • Verify previews in the app-dev tab before saying the app is running.