The next steps, written for you and your agent
Each playbook explains how to extend a template without breaking its architecture: which files to touch, which rules to keep and how to verify the result. The same file ships in your repository, so your coding agent can follow it.
How playbooks work
Next.js + Supabase
Included in every repository created from this template.
Flutter Production App
Included in every repository created from this template.
Add a screen with a route and state
Add a feature screen reachable by name and by deep link, with Riverpod state, translated texts and a test that runs without network.
Read the playbookAdd a Supabase table with RLS
Store new user data in Supabase behind RLS and pgTAP tests, and read it in the app through a repository.
Read the playbookNext.js + Flutter Product Monorepo
Included in every repository created from this template.
Add an admin page
Add a page to the admin app that reads data of all users, authorized on the server and by an RLS policy reserved to admins.
Read the playbookAdd an endpoint to the shared contract
Add an API operation to the OpenAPI contract, serve it from a Next.js Route Handler behind RLS and call it from Flutter through the generated client.
Read the playbookConsumer Subscription App
Included in every repository created from this template.
Cover new data in account deletion
When the app stores new user data or files, extend account deletion so that nothing of the user is left behind and only the verified user can trigger it.
Read the playbookGate a feature behind Premium
Unlock a feature only with an active RevenueCat entitlement, lead free users to the paywall and enforce the same rule in Supabase when the feature has server data.
Read the playbookNative Utility
Included in every repository created from this template.
Add a job handler
Run long product work as a job in its own crate, with checkpoints for pause and cancel, progress events, stable error codes and tests through the public app-api.
Read the playbookAdd a native command
Expose a quick Rust operation to the UI through app-api, a Tauri command with its own permission and the native client, with generated types and tests on both sides.
Read the playbookBooking Platform
Included in every repository created from this template.
Add a no-refund window
Let each service define the last hours before the appointment in which a customer cancellation is no longer refunded.
Read the playbookAdd a reminder window
Send an extra reminder, for example one week before the appointment, without duplicate or late emails.
Read the playbookDeploy to production
Put the booking platform online with Vercel, Supabase, Stripe webhooks, the maintenance cron and transactional email.
Read the playbook