Web application starters · project planning pack

Web application starters · project planning pack

Choose a foundation for Web application starters with a platform brief, repository comparison, proposed tasks, acceptance criteria and the relevant Orqestria specialists.

This planning pack creates a project containing documents and assigns the recommended agents with their existing skills. It contains no external application code or installer and does not start an application. The task lists are proposals in files; no board tasks are created automatically.

Plan a web product around a real user journey, then compare Laravel with React or Vue, Next.js starters and SaaS-oriented bases. A starter saves initial setup; it does not prove your authorization, tenant isolation, billing or operations are ready.

First business scenario

A user signs in, creates one business record, shares it with a permitted colleague and sees a clear result; an unrelated account cannot read or change it. Add a subscription step only if paid access is part of the first release.

Records to model

Users, organizations, memberships, permissions, the first domain record and its audit events; subscription and entitlement records only when required. Decide which service owns each record and how it is exported.

Recommended team

Orion, Lara, Elara, Vera, and Yara

Documents in this pack

Read the brief, adapt the proposed tasks to your business and agree on acceptance criteria before implementation. Add the selected tasks to your board when you are ready to begin.

• Project brief: planning/en/brief.md
• Proposed initial tasks: planning/en/proposed-tasks.md
• Acceptance criteria: planning/en/acceptance.md
• Choose and validate the application foundation: planning/en/starter-selection.md

Repositories to compare

Explore the category recommendations

• Laravel React Starter Kit · Recommendation and scope
• Laravel Vue Starter Kit · Recommendation and scope
• Wave · Recommendation and scope
• Create T3 App · Recommendation and scope
• Next.js SaaS Starter · Recommendation and scope
• Next.js Boilerplate · Recommendation and scope
• Laravel Next.js Starter Kit · Recommendation and scope

Repository shortlist checked: Oct 25, 2026. Recheck current official sources before selecting a revision; inclusion is not a security audit or a guarantee of suitability.

Proposed initial tasks

These are suggested tasks to discuss and add to your board. Installation writes these documents into the project; it does not create work items, run external setup commands or contact the linked services.

Define scope and outcomes

Identify the users, the business outcome and what the first version excludes. Use this scenario as the initial acceptance journey: A user signs in, creates one business record, shares it with a permitted colleague and sees a clear result; an unrelated account cannot read or change it. Add a subscription step only if paid access is part of the first release.

Compare at least two foundations

Compare at least two linked repositories against the scenario and records. Separate shipped features from paid editions, add-ons and work you must build. Record a reasoned choice or why a custom build is preferable.

Verify the current upstream and dependencies

Review official source, licenses, edition terms, dependency requirements, maintenance activity and security advisories for the exact revision. Record unresolved findings and necessary changes before adopting it.

Model data and permissions

Define ownership, validation, relationships and allowed access for these records: Users, organizations, memberships, permissions, the first domain record and its audit events; subscription and entitlement records only when required. Decide which service owns each record and how it is exported. Include at least two roles and explicit denied-access cases.

Prototype the smallest complete scenario

Use representative sample data in an isolated test environment. Demonstrate the full scenario, including one invalid input and one failure or correction, before expanding the product.

Plan restoration and upgrades

Test a backup and restore of the prototype, define an upgrade and rollback approach and estimate hosting, migration, integration and maintenance effort. Record owners for operation and acceptance.

Acceptance criteria

These criteria define the first prototype's review, not completed work. Attach evidence and unresolved issues when the team evaluates each item.

• The agreed scenario is demonstrated end to end with representative records: A user signs in, creates one business record, shares it with a permitted colleague and sees a clear result; an unrelated account cannot read or change it. Add a subscription step only if paid access is part of the first release.
• At least two candidates have been compared, and the chosen revision, license and edition constraints, dependency fit and security findings are recorded with official source links.
• At least two roles have verified allowed and denied actions, with no access to another user's or organization's restricted records.
• Invalid input, a failure and a correction are handled with visible results and without unintended duplicate records or business actions.
• A backup has been restored in a test environment and the expected records and access rules have been verified.
• The team has documented an upgrade and rollback plan, known gaps, operating responsibilities and the remaining implementation work.
• The chosen starter or generated output runs in an isolated environment, the app root and setup steps are documented, and the first journey includes denied access and failure recovery; no SaaS-demo feature is accepted without verification.

Choose and validate the application foundation

Compare Laravel React and Laravel Vue when the team wants a PHP backend with its chosen frontend; assess Laravel Next.js separately because a split frontend/API changes authentication, deployment and data ownership. Compare the Next.js options against your actual routing, persistence and identity requirements. Evaluate Wave or a SaaS demo only against the features present in the selected edition and revision.

Create T3 App is a generator source repository. Choose its documented generator version and output options after inspection; cloning the CLI repository is not a generated product. For every candidate, record the app folder, dependency/runtime versions, license, configured external services and the explicit setup steps.

Build one complete vertical slice with sample data. Verify server-side authorization, cross-account denial, validation and error recovery; when billing is in scope, test webhook replay and access changes. Agree on deploy/rollback, backups and upstream update ownership before expanding the feature set.