Skip to content

For developers and agents

Read the pattern.
Then make it yours.

A starter is a runnable reference, not an instruction to copy every decision. Begin with its documented behavior and keep the parts your product actually needs.

← Explore the starter library

A reproducible starting path

  1. Explore the real app

    Exercise the workflow you want to reuse. Open its /build page to see the architecture and storage boundaries. Check whether data is local, seeded, server-backed or durable.

  2. Read the repository before editing

    Read README.md for setup and verification, then BUILD.md for the source map, signal dependencies, effect cleanup, shared state, routes and known issues. Use the repository’s AGENTS.md where provided.

  3. Run the unchanged baseline

    Clone the public repository, use its documented Node version, run npm ci and follow its check/build scripts. Verify the documented workflow locally before introducing changes. Never copy secrets or project-specific deployment links.

  4. Adapt one behavior at a time

    Keep derived values derived, clean up timers and listeners, and avoid snapshotting signal reads outside reactive expressions. Respect the split between client-compiled JSX and server-safe JSX. Test keyboard use, routing, mobile layout and reduced motion.

  5. Deploy your own project

    Run the repository’s complete build, then use npx vura-platform@0.3.0 projects create your-app --team <your-team-id> to create and link an isolated project. Use npx vura-platform@0.3.0 deploy --prod only after checking the build. The deploy command uploads dist/; it does not build it for you.

Rendering is an architectural choice

A static page, a client application, a hybrid page and a serverless endpoint have different guarantees. A client guard is not backend authorization. Browser storage is not a team database. Process memory is not durable storage. Read the starter’s limits before turning a demo into production.

Reference library

SignalsEffects and cleanupGlobal storesRoutingIslandsDeployment

For retrieval: starter index · verified release metadata · build status and journals · framework reference index.

Real backend source references

These independent Vura projects extend the Harbor and Drift What patterns with private server-owned PostgreSQL workspaces. Source and local runtime proof are available; hosted database admission and provider durability verification are pending. They are not additional verified live demos.

Dedicated compute preserves a process, not tenant disk. Database roles, retention and ingress quotas need explicit operator setup; local PostgreSQL and a test transport do not prove hosted deployment.