A clearer brief.
A better first build.

108 authored engineering prompts across 12 categories. Start from a real visitor task, a route plan, typed data and a check you can perform. Then make the requirements yours.

These are curated starting briefs, not 108 production-tested apps. Copying or preparing one makes no model request. Name your project, review the prompt and send it explicitly to begin generation. Normal usage and the $4.99 source entitlement apply.

Looking for a smaller starting point? Use the free prompt architect, or inspect interactive blueprint concepts.

Category

108 of 108 authored prompts. Preparing a brief does not start generation.

SaaS dashboards & CRMs

Sales pipeline CRM

Help an independent consultant move a qualified lead from first contact to a won or lost opportunity.

Pages: 6 route roles
Collections: deals, contacts
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build sales pipeline crm. Help an independent consultant move a qualified lead from first contact to a won or lost opportunity. Build stage filters, a keyboard-operable deal drawer, editable value and a pipeline total derived from saved deals.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, deals workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"deals","fields":{"title":{"type":"string","required":true},"value":{"type":"number"},"stage":{"type":"string","required":true}},"label":"deals","access":"private","seed":[]},{"name":"contacts","fields":{"name":{"type":"string","required":true},"email":{"type":"string","required":true}},"label":"contacts","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm graphite surfaces, compact Geist type, restrained copper status accents, a useful persistent sidebar and legible dense tables. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Create and move a deal, reload, and verify both the stage and recalculated pipeline total. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

SaaS dashboards & CRMs

Client follow-up tracker

Keep the next promised action visible for each active client without inventing email delivery.

Pages: 6 route roles
Collections: clients, followups
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build client follow-up tracker. Keep the next promised action visible for each active client without inventing email delivery. Provide an overdue filter, due-date editor and a completion action with reversible feedback.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, clients workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"clients","fields":{"name":{"type":"string","required":true},"company":{"type":"string","required":true}},"label":"clients","access":"private","seed":[]},{"name":"followups","fields":{"title":{"type":"string","required":true},"due":{"type":"date"},"status":{"type":"string","required":true}},"label":"followups","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm graphite surfaces, compact Geist type, restrained copper status accents, a useful persistent sidebar and legible dense tables. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Complete a follow-up, navigate away and confirm the saved status on return. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

SaaS dashboards & CRMs

Creative agency project CRM

Give a small agency an honest view of project status, scope and pending decisions.

Pages: 6 route roles
Collections: projects, decisions
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build creative agency project crm. Give a small agency an honest view of project status, scope and pending decisions. Add project search, stage tabs and a decision drawer; calculate budget summaries from returned records.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, projects workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"projects","fields":{"name":{"type":"string","required":true},"stage":{"type":"string","required":true},"budget":{"type":"number"}},"label":"projects","access":"private","seed":[]},{"name":"decisions","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"decisions","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm graphite surfaces, compact Geist type, restrained copper status accents, a useful persistent sidebar and legible dense tables. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Edit a budget and verify the same amount in the detail route and summary. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

SaaS dashboards & CRMs

Freelance proposal manager

Organize proposal drafts and decisions without pretending to send documents or collect signatures.

Pages: 6 route roles
Collections: proposals, clients
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build freelance proposal manager. Organize proposal drafts and decisions without pretending to send documents or collect signatures. Implement draft editing, status filters and a printable proposal view labelled as a draft.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, proposals workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"proposals","fields":{"title":{"type":"string","required":true},"amount":{"type":"number"},"status":{"type":"string","required":true}},"label":"proposals","access":"private","seed":[]},{"name":"clients","fields":{"name":{"type":"string","required":true},"company":{"type":"string","required":true}},"label":"clients","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm graphite surfaces, compact Geist type, restrained copper status accents, a useful persistent sidebar and legible dense tables. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Save a proposal, reload its detail route and verify content and status remain. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

SaaS dashboards & CRMs

Customer onboarding workspace

Track a consultant's own onboarding checklists for new clients, with completion tied to actual task records.

Pages: 6 route roles
Collections: onboarding_cases, checklist_items
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build customer onboarding workspace. Track a consultant's own onboarding checklists for new clients, with completion tied to actual task records. Use editable checklists, a pending-items filter and a progress count computed from persisted items.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, onboarding cases workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"onboarding_cases","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"onboarding cases","access":"private","seed":[]},{"name":"checklist_items","fields":{"title":{"type":"string","required":true},"done":{"type":"boolean"}},"label":"checklist items","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm graphite surfaces, compact Geist type, restrained copper status accents, a useful persistent sidebar and legible dense tables. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Toggle a checklist item and verify the counter and state after reload. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

SaaS dashboards & CRMs

Account renewal calendar

Help a service operator see upcoming contract reviews without claiming automated renewals or live billing.

Pages: 6 route roles
Collections: accounts, reviews
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build account renewal calendar. Help a service operator see upcoming contract reviews without claiming automated renewals or live billing. Switch between a chronological list and month view; edit review dates and filter by review state.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, accounts workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"accounts","fields":{"name":{"type":"string","required":true},"renewal":{"type":"date"},"value":{"type":"number"}},"label":"accounts","access":"private","seed":[]},{"name":"reviews","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"reviews","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm graphite surfaces, compact Geist type, restrained copper status accents, a useful persistent sidebar and legible dense tables. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Change a renewal date and confirm it moves to the correct chronological position. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

SaaS dashboards & CRMs

Service request CRM

Collect and manage private service requests with a clear distinction between requested and completed work.

Pages: 6 route roles
Collections: requests, notes
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build service request crm. Collect and manage private service requests with a clear distinction between requested and completed work. Add priority filters, a create form and a detail timeline backed by saved notes.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, requests workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"requests","fields":{"title":{"type":"string","required":true},"priority":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"requests","access":"private","seed":[]},{"name":"notes","fields":{"body":{"type":"string","required":true},"created":{"type":"date"}},"label":"notes","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm graphite surfaces, compact Geist type, restrained copper status accents, a useful persistent sidebar and legible dense tables. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Reject a blank request, then save a valid request and see it in the correct filter. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

SaaS dashboards & CRMs

Recruiting candidate tracker

Let an individual recruiter organize permission-cleared fictional candidate records without automated hiring decisions.

Pages: 6 route roles
Collections: candidates, interviews
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build recruiting candidate tracker. Let an individual recruiter organize permission-cleared fictional candidate records without automated hiring decisions. Implement role search, stage filters and an interview-date editor; keep sensitive data out of examples.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, candidates workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"candidates","fields":{"name":{"type":"string","required":true},"role":{"type":"string","required":true},"stage":{"type":"string","required":true}},"label":"candidates","access":"private","seed":[]},{"name":"interviews","fields":{"title":{"type":"string","required":true},"date":{"type":"date"}},"label":"interviews","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm graphite surfaces, compact Geist type, restrained copper status accents, a useful persistent sidebar and legible dense tables. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Move a disposable candidate and verify unrelated candidates and interview dates remain unchanged. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

SaaS dashboards & CRMs

Partnership deal room

Track a business owner's partnership discussions, obligations and next decisions.

Pages: 6 route roles
Collections: partners, obligations
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build partnership deal room. Track a business owner's partnership discussions, obligations and next decisions. Provide a partner index, category filter and obligation checklist with an actionable empty state.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, partners workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"partners","fields":{"name":{"type":"string","required":true},"category":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"partners","access":"private","seed":[]},{"name":"obligations","fields":{"title":{"type":"string","required":true},"due":{"type":"date"},"done":{"type":"boolean"}},"label":"obligations","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm graphite surfaces, compact Geist type, restrained copper status accents, a useful persistent sidebar and legible dense tables. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Add an obligation, mark it complete and recover the same saved state after reload. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

AI micro-SaaS & assistants

AI resume reviewer

Help a job seeker identify specific improvements in text they supply, without inventing qualifications or making hiring decisions.

Pages: 6 route roles
Collections: reviews, roles
Connectors: Database · Visitor auth · In-app AI

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build ai resume reviewer. Help a job seeker identify specific improvements in text they supply, without inventing qualifications or making hiring decisions. Run actual bounded AI review, validate structured feedback and let the user save a selected recommendation.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, reviews workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"reviews","fields":{"title":{"type":"string","required":true},"input":{"type":"string","required":true},"result":{"type":"string","required":true}},"label":"reviews","access":"private","seed":[]},{"name":"roles","fields":{"title":{"type":"string","required":true},"requirements":{"type":"string","required":true}},"label":"roles","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Use actual Uvilno.ai.ask/json for the requested AI feature, with a 600-output-token ceiling. Validate result fields, show pending/retry states and never use canned text as successful inference. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A calm split workspace with readable input, a clearly separated result pane, restrained accent color and provenance beside every generated suggestion. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Submit fictional resume text, distinguish pending/error/success, save a real response and reopen it. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

AI micro-SaaS & assistants

AI study plan builder

Turn a learner's topic and available time into a short, editable study plan using actual model output.

Pages: 6 route roles
Collections: study_plans, sessions
Connectors: Database · Visitor auth · In-app AI

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build ai study plan builder. Turn a learner's topic and available time into a short, editable study plan using actual model output. Provide topic and time inputs, a real generation state and a saved session checklist.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, study plans workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"study_plans","fields":{"title":{"type":"string","required":true},"topic":{"type":"string","required":true},"result":{"type":"string","required":true}},"label":"study plans","access":"private","seed":[]},{"name":"sessions","fields":{"title":{"type":"string","required":true},"done":{"type":"boolean"}},"label":"sessions","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Use actual Uvilno.ai.ask/json for the requested AI feature, with a 600-output-token ceiling. Validate result fields, show pending/retry states and never use canned text as successful inference. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A calm split workspace with readable input, a clearly separated result pane, restrained accent color and provenance beside every generated suggestion. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Generate and validate a plan, save it, then check a session without rerunning inference. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

AI micro-SaaS & assistants

AI meeting action extractor

Extract proposed actions only from supplied meeting notes and require user review before saving.

Pages: 6 route roles
Collections: meetings, actions
Connectors: Database · Visitor auth · In-app AI

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build ai meeting action extractor. Extract proposed actions only from supplied meeting notes and require user review before saving. Show source notes alongside actual AI suggestions and an explicit approve-to-save action.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, meetings workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"meetings","fields":{"title":{"type":"string","required":true},"notes":{"type":"string","required":true}},"label":"meetings","access":"private","seed":[]},{"name":"actions","fields":{"title":{"type":"string","required":true},"approved":{"type":"boolean"}},"label":"actions","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Use actual Uvilno.ai.ask/json for the requested AI feature, with a 600-output-token ceiling. Validate result fields, show pending/retry states and never use canned text as successful inference. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A calm split workspace with readable input, a clearly separated result pane, restrained accent color and provenance beside every generated suggestion. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm unapproved suggestions are not silently stored as assigned work. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

AI micro-SaaS & assistants

AI recipe notebook

Help a home cook draft recipes from supplied ingredients while stating that allergy and safety checks remain the user's responsibility.

Pages: 6 route roles
Collections: recipes, saved_meals
Connectors: Database · Visitor auth · In-app AI

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build ai recipe notebook. Help a home cook draft recipes from supplied ingredients while stating that allergy and safety checks remain the user's responsibility. Use actual structured AI suggestions, editable ingredient lists and a saved-recipe filter.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, recipes workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"recipes","fields":{"title":{"type":"string","required":true},"ingredients":{"type":"string","required":true},"instructions":{"type":"string","required":true}},"label":"recipes","access":"private","seed":[]},{"name":"saved_meals","fields":{"title":{"type":"string","required":true},"planned":{"type":"date"}},"label":"saved meals","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Use actual Uvilno.ai.ask/json for the requested AI feature, with a 600-output-token ceiling. Validate result fields, show pending/retry states and never use canned text as successful inference. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A calm split workspace with readable input, a clearly separated result pane, restrained accent color and provenance beside every generated suggestion. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Save an edited suggestion and reopen the edited version rather than the original response. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

AI micro-SaaS & assistants

AI product copy workbench

Draft concise product copy from supplied facts without fabricating reviews, metrics, endorsements or availability.

Pages: 6 route roles
Collections: products, drafts
Connectors: Database · Visitor auth · In-app AI

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build ai product copy workbench. Draft concise product copy from supplied facts without fabricating reviews, metrics, endorsements or availability. Provide tone and length inputs, actual inference, a fact-review checklist and an explicit draft approval.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, products workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"products","fields":{"name":{"type":"string","required":true},"facts":{"type":"string","required":true}},"label":"products","access":"private","seed":[]},{"name":"drafts","fields":{"title":{"type":"string","required":true},"copy":{"type":"string","required":true},"approved":{"type":"boolean"}},"label":"drafts","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Use actual Uvilno.ai.ask/json for the requested AI feature, with a 600-output-token ceiling. Validate result fields, show pending/retry states and never use canned text as successful inference. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A calm split workspace with readable input, a clearly separated result pane, restrained accent color and provenance beside every generated suggestion. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify unknown product facts remain absent and the approved copy survives reload. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

AI micro-SaaS & assistants

AI language practice journal

Give a learner short feedback on their own writing, with transparent AI limitations and editable corrections.

Pages: 6 route roles
Collections: entries, feedback
Connectors: Database · Visitor auth · In-app AI

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build ai language practice journal. Give a learner short feedback on their own writing, with transparent AI limitations and editable corrections. Offer a language selector, real feedback request and a comparison view of original versus user-approved text.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, entries workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"entries","fields":{"title":{"type":"string","required":true},"text":{"type":"string","required":true},"language":{"type":"string","required":true}},"label":"entries","access":"private","seed":[]},{"name":"feedback","fields":{"title":{"type":"string","required":true},"result":{"type":"string","required":true}},"label":"feedback","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Use actual Uvilno.ai.ask/json for the requested AI feature, with a 600-output-token ceiling. Validate result fields, show pending/retry states and never use canned text as successful inference. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A calm split workspace with readable input, a clearly separated result pane, restrained accent color and provenance beside every generated suggestion. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Save original writing and reviewed feedback separately without overwriting the original. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

AI micro-SaaS & assistants

AI support reply drafter

Draft support responses from supplied issue details without claiming access to customer accounts or sending messages.

Pages: 6 route roles
Collections: cases, replies
Connectors: Database · Visitor auth · In-app AI

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build ai support reply drafter. Draft support responses from supplied issue details without claiming access to customer accounts or sending messages. Show actual model suggestions, a fact-check checklist and copy-to-clipboard; label every response as an unsent draft.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, cases workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"cases","fields":{"title":{"type":"string","required":true},"issue":{"type":"string","required":true}},"label":"cases","access":"private","seed":[]},{"name":"replies","fields":{"title":{"type":"string","required":true},"draft":{"type":"string","required":true},"approved":{"type":"boolean"}},"label":"replies","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Use actual Uvilno.ai.ask/json for the requested AI feature, with a 600-output-token ceiling. Validate result fields, show pending/retry states and never use canned text as successful inference. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A calm split workspace with readable input, a clearly separated result pane, restrained accent color and provenance beside every generated suggestion. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Copy a reviewed draft and confirm no send or account-mutation action is represented as completed. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

AI micro-SaaS & assistants

AI workout planning notebook

Help an adult organize general fitness ideas from supplied preferences without medical advice, diagnosis or injury guarantees.

Pages: 6 route roles
Collections: plans, workouts
Connectors: Database · Visitor auth · In-app AI

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build ai workout planning notebook. Help an adult organize general fitness ideas from supplied preferences without medical advice, diagnosis or injury guarantees. Generate bounded suggestions with real AI, make every item editable and persist the user's chosen plan.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, plans workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"plans","fields":{"title":{"type":"string","required":true},"preferences":{"type":"string","required":true},"result":{"type":"string","required":true}},"label":"plans","access":"private","seed":[]},{"name":"workouts","fields":{"title":{"type":"string","required":true},"done":{"type":"boolean"}},"label":"workouts","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Use actual Uvilno.ai.ask/json for the requested AI feature, with a 600-output-token ceiling. Validate result fields, show pending/retry states and never use canned text as successful inference. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A calm split workspace with readable input, a clearly separated result pane, restrained accent color and provenance beside every generated suggestion. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Handle model failure while preserving preferences and never substitute a fabricated AI success. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

AI micro-SaaS & assistants

AI research question organizer

Turn supplied research notes into proposed questions, preserving the distinction between evidence and model suggestions.

Pages: 6 route roles
Collections: notes, questions
Connectors: Database · Visitor auth · In-app AI

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build ai research question organizer. Turn supplied research notes into proposed questions, preserving the distinction between evidence and model suggestions. Provide actual suggestion generation, manual source fields and explicit promotion of a suggestion into the saved question list.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, notes workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"notes","fields":{"title":{"type":"string","required":true},"body":{"type":"string","required":true}},"label":"notes","access":"private","seed":[]},{"name":"questions","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"questions","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Use actual Uvilno.ai.ask/json for the requested AI feature, with a 600-output-token ceiling. Validate result fields, show pending/retry states and never use canned text as successful inference. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A calm split workspace with readable input, a clearly separated result pane, restrained accent color and provenance beside every generated suggestion. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify AI output does not fabricate cited papers or silently mark a question as answered. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Stripe stores & product catalogs

Ceramics test-checkout store

Let visitors explore a small studio's supplied ceramic pieces and test an explicitly non-live purchase journey.

Pages: 6 route roles
Collections: products, cart_items
Connectors: Database · Visitor auth · Stripe test Checkout

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build ceramics test-checkout store. Let visitors explore a small studio's supplied ceramic pieces and test an explicitly non-live purchase journey. Build category filters, product routes, quantity controls and a test-checkout handoff; do not invent stock or shipping promises.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, products workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"products","fields":{"name":{"type":"string","required":true},"price":{"type":"number"},"available":{"type":"boolean"}},"label":"products","access":"private","seed":[]},{"name":"cart_items","fields":{"title":{"type":"string","required":true},"quantity":{"type":"number"}},"label":"cart items","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Use only the configured Stripe TEST Checkout workflow; a test receipt is not a live charge, fulfilled order or purchased entitlement. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
An image-led editorial storefront with disciplined product typography, quiet surfaces and a compact accessible cart drawer; use only supplied product imagery. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Change quantity and verify totals before completing only the configured test workflow. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Stripe stores & product catalogs

Coffee subscription planner

Help a roastery customer compare supplied beans and plan a delivery cadence without claiming active recurring charges.

Pages: 6 route roles
Collections: coffees, preferences
Connectors: Database · Visitor auth · Stripe test Checkout

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build coffee subscription planner. Help a roastery customer compare supplied beans and plan a delivery cadence without claiming active recurring charges. Provide roast filters and a cadence/quantity estimate; label subscription selection as a draft until real billing exists.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, coffees workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"coffees","fields":{"name":{"type":"string","required":true},"price":{"type":"number"},"roast":{"type":"string","required":true}},"label":"coffees","access":"private","seed":[]},{"name":"preferences","fields":{"title":{"type":"string","required":true},"cadence":{"type":"string","required":true},"quantity":{"type":"number"}},"label":"preferences","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Use only the configured Stripe TEST Checkout workflow; a test receipt is not a live charge, fulfilled order or purchased entitlement. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
An image-led editorial storefront with disciplined product typography, quiet surfaces and a compact accessible cart drawer; use only supplied product imagery. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Save a cadence choice and confirm no recurring live subscription is claimed. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Stripe stores & product catalogs

Independent bookshop catalog

Make a supplied catalog easy to search, shortlist and evaluate before a test checkout.

Pages: 6 route roles
Collections: books, cart_items
Connectors: Database · Visitor auth · Stripe test Checkout

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build independent bookshop catalog. Make a supplied catalog easy to search, shortlist and evaluate before a test checkout. Add author/category search, accessible book detail pages and an honest unavailable-item state.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, books workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"books","fields":{"title":{"type":"string","required":true},"author":{"type":"string","required":true},"price":{"type":"number"}},"label":"books","access":"private","seed":[]},{"name":"cart_items","fields":{"title":{"type":"string","required":true},"quantity":{"type":"number"}},"label":"cart items","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Use only the configured Stripe TEST Checkout workflow; a test receipt is not a live charge, fulfilled order or purchased entitlement. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
An image-led editorial storefront with disciplined product typography, quiet surfaces and a compact accessible cart drawer; use only supplied product imagery. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Filter by author, add a known item and verify the cart total after changing quantity. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Stripe stores & product catalogs

Design object store

Present supplied furniture and objects with useful dimensions, finish selections and clear test-mode commerce.

Pages: 6 route roles
Collections: objects, cart_items
Connectors: Database · Visitor auth · Stripe test Checkout

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build design object store. Present supplied furniture and objects with useful dimensions, finish selections and clear test-mode commerce. Use finish selectors that update the selected variant, comparison notes and a persistent cart.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, objects workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"objects","fields":{"name":{"type":"string","required":true},"price":{"type":"number"},"finish":{"type":"string","required":true}},"label":"objects","access":"private","seed":[]},{"name":"cart_items","fields":{"title":{"type":"string","required":true},"quantity":{"type":"number"}},"label":"cart items","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Use only the configured Stripe TEST Checkout workflow; a test receipt is not a live charge, fulfilled order or purchased entitlement. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
An image-led editorial storefront with disciplined product typography, quiet surfaces and a compact accessible cart drawer; use only supplied product imagery. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Keep the selected finish and quantity consistent between product detail and cart. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Stripe stores & product catalogs

Digital resource test store

Show original digital resources with license descriptions without fabricating download entitlements after test payment.

Pages: 6 route roles
Collections: resources, cart_items
Connectors: Database · Visitor auth · Stripe test Checkout

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build digital resource test store. Show original digital resources with license descriptions without fabricating download entitlements after test payment. Provide category filters, a license accordion and test checkout; exclude delivery unless a verified real entitlement exists.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, resources workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"resources","fields":{"name":{"type":"string","required":true},"price":{"type":"number"},"license":{"type":"string","required":true}},"label":"resources","access":"private","seed":[]},{"name":"cart_items","fields":{"title":{"type":"string","required":true},"quantity":{"type":"number"}},"label":"cart items","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Use only the configured Stripe TEST Checkout workflow; a test receipt is not a live charge, fulfilled order or purchased entitlement. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
An image-led editorial storefront with disciplined product typography, quiet surfaces and a compact accessible cart drawer; use only supplied product imagery. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm a test receipt is labelled and cannot unlock a claimed purchased file. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Stripe stores & product catalogs

Skincare product information store

Organize supplied cosmetic products and ingredient facts without medical claims or invented clinical results.

Pages: 6 route roles
Collections: products, cart_items
Connectors: Database · Visitor auth · Stripe test Checkout

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build skincare product information store. Organize supplied cosmetic products and ingredient facts without medical claims or invented clinical results. Add ingredient search, supplied usage notes and a test-only cart; no diagnosis or efficacy scoring.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, products workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"products","fields":{"name":{"type":"string","required":true},"price":{"type":"number"},"ingredients":{"type":"string","required":true}},"label":"products","access":"private","seed":[]},{"name":"cart_items","fields":{"title":{"type":"string","required":true},"quantity":{"type":"number"}},"label":"cart items","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Use only the configured Stripe TEST Checkout workflow; a test receipt is not a live charge, fulfilled order or purchased entitlement. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
An image-led editorial storefront with disciplined product typography, quiet surfaces and a compact accessible cart drawer; use only supplied product imagery. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify missing clinical claims remain absent and product filters match stored facts. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Stripe stores & product catalogs

Art print edition store

Help an artist present supplied works, available sizes and edition information without inventing scarcity.

Pages: 6 route roles
Collections: prints, cart_items
Connectors: Database · Visitor auth · Stripe test Checkout

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build art print edition store. Help an artist present supplied works, available sizes and edition information without inventing scarcity. Use size choices, a zoomable supplied image and an explicitly test-only purchase summary.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, prints workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"prints","fields":{"title":{"type":"string","required":true},"size":{"type":"string","required":true},"price":{"type":"number"}},"label":"prints","access":"private","seed":[]},{"name":"cart_items","fields":{"title":{"type":"string","required":true},"quantity":{"type":"number"}},"label":"cart items","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Use only the configured Stripe TEST Checkout workflow; a test receipt is not a live charge, fulfilled order or purchased entitlement. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
An image-led editorial storefront with disciplined product typography, quiet surfaces and a compact accessible cart drawer; use only supplied product imagery. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Choose a size and confirm the same variant and entered price in the cart summary. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Stripe stores & product catalogs

Local florist order request

Prepare a bouquet request from supplied options, with a test payment demonstration rather than confirmed fulfillment.

Pages: 6 route roles
Collections: bouquets, requests
Connectors: Database · Visitor auth · Stripe test Checkout

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build local florist order request. Prepare a bouquet request from supplied options, with a test payment demonstration rather than confirmed fulfillment. Offer occasion filters and a request form; state that availability and delivery require human confirmation.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, bouquets workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"bouquets","fields":{"name":{"type":"string","required":true},"price":{"type":"number"},"category":{"type":"string","required":true}},"label":"bouquets","access":"private","seed":[]},{"name":"requests","fields":{"title":{"type":"string","required":true},"date":{"type":"date"},"status":{"type":"string","required":true}},"label":"requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Use only the configured Stripe TEST Checkout workflow; a test receipt is not a live charge, fulfilled order or purchased entitlement. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
An image-led editorial storefront with disciplined product typography, quiet surfaces and a compact accessible cart drawer; use only supplied product imagery. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Persist a request and show its actual pending state without claiming delivery or acceptance. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Stripe stores & product catalogs

Storefront with inventory review

Give a creator a product catalog plus a reviewed management view, keeping actual authorization separate from a preview role.

Pages: 6 route roles
Collections: products, stock_movements
Connectors: Database · Visitor auth · Stripe test Checkout

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build storefront with inventory review. Give a creator a product catalog plus a reviewed management view, keeping actual authorization separate from a preview role. Add catalog filtering and a private inventory form; use server-authorized operations, never a client role label as permission.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, products workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"products","fields":{"name":{"type":"string","required":true},"price":{"type":"number"},"stock":{"type":"number"}},"label":"products","access":"private","seed":[]},{"name":"stock_movements","fields":{"title":{"type":"string","required":true},"quantity":{"type":"number"}},"label":"stock movements","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Use only the configured Stripe TEST Checkout workflow; a test receipt is not a live charge, fulfilled order or purchased entitlement. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
An image-led editorial storefront with disciplined product typography, quiet surfaces and a compact accessible cart drawer; use only supplied product imagery. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check stock updates through actual allowed writes and show denied access honestly to another visitor. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Browser games & score systems

Orbital survival arcade

Create a playable dodge-and-collect loop with keyboard and touch controls rather than a decorative game mockup.

Pages: 6 route roles
Collections: runs, settings
Connectors: Database · Visitor auth · Canvas game

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build orbital survival arcade. Create a playable dodge-and-collect loop with keyboard and touch controls rather than a decorative game mockup. Implement collision, a rising challenge, pause/restart and local practice scores; make any shared leaderboard explicitly scoped and abuse-aware.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, runs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"runs","fields":{"title":{"type":"string","required":true},"score":{"type":"number"},"duration":{"type":"number"}},"label":"runs","access":"private","seed":[]},{"name":"settings","fields":{"title":{"type":"string","required":true},"sound":{"type":"boolean"}},"label":"settings","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Use a clear game arena, high-contrast readable HUD, original vector or geometric assets, deliberate hit feedback and separate simulation/render modules. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Play a full round, restart, pause and measure frame time on the stated target device without a universal FPS promise. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Browser games & score systems

Paddle breaker challenge

Build a ball-and-paddle challenge whose win and loss conditions follow real collisions.

Pages: 6 route roles
Collections: runs, preferences
Connectors: Database · Visitor auth · Canvas game

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build paddle breaker challenge. Build a ball-and-paddle challenge whose win and loss conditions follow real collisions. Implement paddle control, brick durability, a bounded difficulty curve and accessible pause/restart controls.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, runs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"runs","fields":{"title":{"type":"string","required":true},"score":{"type":"number"},"level":{"type":"number"}},"label":"runs","access":"private","seed":[]},{"name":"preferences","fields":{"title":{"type":"string","required":true},"sound":{"type":"boolean"}},"label":"preferences","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Use a clear game arena, high-contrast readable HUD, original vector or geometric assets, deliberate hit feedback and separate simulation/render modules. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify every brick clears through actual collision and the score persists only after a completed round. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Browser games & score systems

Top-down delivery racer

Create an original route-and-time game without real logistics or delivery claims.

Pages: 6 route roles
Collections: runs, routes
Connectors: Database · Visitor auth · Canvas game

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build top-down delivery racer. Create an original route-and-time game without real logistics or delivery claims. Build acceleration/braking, obstacle collision, checkpoints and a finish state with both keyboard and touch input.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, runs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"runs","fields":{"title":{"type":"string","required":true},"score":{"type":"number"},"time":{"type":"number"}},"label":"runs","access":"private","seed":[]},{"name":"routes","fields":{"title":{"type":"string","required":true},"difficulty":{"type":"string","required":true}},"label":"routes","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Use a clear game arena, high-contrast readable HUD, original vector or geometric assets, deliberate hit feedback and separate simulation/render modules. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Finish the route, verify checkpoints are required and confirm time resets on a new run. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Browser games & score systems

Memory card garden

Make an original matching game with deterministic pair logic and an understandable completion state.

Pages: 6 route roles
Collections: runs, preferences
Connectors: Database · Visitor auth · Canvas game

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build memory card garden. Make an original matching game with deterministic pair logic and an understandable completion state. Implement shuffled pairs, mismatch delay, move count, reset and a reduced-motion mode.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, runs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"runs","fields":{"title":{"type":"string","required":true},"moves":{"type":"number"},"time":{"type":"number"}},"label":"runs","access":"private","seed":[]},{"name":"preferences","fields":{"title":{"type":"string","required":true},"difficulty":{"type":"string","required":true}},"label":"preferences","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Use a clear game arena, high-contrast readable HUD, original vector or geometric assets, deliberate hit feedback and separate simulation/render modules. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Complete all pairs and verify rapid clicks cannot expose more than two unresolved cards. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Browser games & score systems

Rhythm timing practice

Create a visual timing challenge using original or permission-cleared sound, with explicit user-enabled audio.

Pages: 6 route roles
Collections: runs, preferences
Connectors: Database · Visitor auth · Canvas game

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build rhythm timing practice. Create a visual timing challenge using original or permission-cleared sound, with explicit user-enabled audio. Implement an actual timing window, keyboard/touch input, mute and practice-speed selection.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, runs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"runs","fields":{"title":{"type":"string","required":true},"score":{"type":"number"},"accuracy":{"type":"number"}},"label":"runs","access":"private","seed":[]},{"name":"preferences","fields":{"title":{"type":"string","required":true},"sound":{"type":"boolean"}},"label":"preferences","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Use a clear game arena, high-contrast readable HUD, original vector or geometric assets, deliberate hit feedback and separate simulation/render modules. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify scoring depends on input timing and audio never starts before explicit user interaction. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Browser games & score systems

Grid puzzle expedition

Build a grid-based puzzle with meaningful legal moves and a replayable level sequence.

Pages: 6 route roles
Collections: runs, preferences
Connectors: Database · Visitor auth · Canvas game

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build grid puzzle expedition. Build a grid-based puzzle with meaningful legal moves and a replayable level sequence. Implement move validation, undo, restart and a finite set of solvable levels rather than random impossible boards.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, runs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"runs","fields":{"title":{"type":"string","required":true},"moves":{"type":"number"},"level":{"type":"number"}},"label":"runs","access":"private","seed":[]},{"name":"preferences","fields":{"title":{"type":"string","required":true},"hints":{"type":"boolean"}},"label":"preferences","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Use a clear game arena, high-contrast readable HUD, original vector or geometric assets, deliberate hit feedback and separate simulation/render modules. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Solve a known level and confirm illegal moves preserve the puzzle state. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Browser games & score systems

Tower defense sketch

Create a bounded original strategy game with enemies, a path and actual resource spending.

Pages: 6 route roles
Collections: runs, loadouts
Connectors: Database · Visitor auth · Canvas game

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build tower defense sketch. Create a bounded original strategy game with enemies, a path and actual resource spending. Implement path-following enemies, placement rules, tower cooldowns, upgrade cost and explicit game-over/restart.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, runs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"runs","fields":{"title":{"type":"string","required":true},"wave":{"type":"number"},"score":{"type":"number"}},"label":"runs","access":"private","seed":[]},{"name":"loadouts","fields":{"title":{"type":"string","required":true},"tower":{"type":"string","required":true}},"label":"loadouts","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Use a clear game arena, high-contrast readable HUD, original vector or geometric assets, deliberate hit feedback and separate simulation/render modules. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify an upgrade deducts the displayed resource and enemies cannot skip the defined path. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Browser games & score systems

Typing focus arcade

Build a practice game that scores the supplied text accurately without collecting sensitive keystrokes.

Pages: 6 route roles
Collections: runs, preferences
Connectors: Database · Visitor auth · Canvas game

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build typing focus arcade. Build a practice game that scores the supplied text accurately without collecting sensitive keystrokes. Use original practice passages, real character matching, restart and an optional untimed mode.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, runs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"runs","fields":{"title":{"type":"string","required":true},"accuracy":{"type":"number"},"duration":{"type":"number"}},"label":"runs","access":"private","seed":[]},{"name":"preferences","fields":{"title":{"type":"string","required":true},"length":{"type":"number"}},"label":"preferences","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Use a clear game arena, high-contrast readable HUD, original vector or geometric assets, deliberate hit feedback and separate simulation/render modules. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check mistakes reduce accuracy correctly and no typed content is sent outside the declared score workflow. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Browser games & score systems

Mini-golf physics lab

Create a small original physics challenge with aim, power and understandable stroke counting.

Pages: 6 route roles
Collections: runs, preferences
Connectors: Database · Visitor auth · Canvas game

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build mini-golf physics lab. Create a small original physics challenge with aim, power and understandable stroke counting. Implement wall collision, friction, a finite course, aim preview and a reset for stuck states.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, runs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"runs","fields":{"title":{"type":"string","required":true},"strokes":{"type":"number"},"course":{"type":"string","required":true}},"label":"runs","access":"private","seed":[]},{"name":"preferences","fields":{"title":{"type":"string","required":true},"assist":{"type":"boolean"}},"label":"preferences","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Use a clear game arena, high-contrast readable HUD, original vector or geometric assets, deliberate hit feedback and separate simulation/render modules. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Complete a hole and verify strokes count releases rather than every drag movement. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Booking & service portals

Dental appointment request portal

Let a visitor request a consultation without collecting medical history or implying confirmed clinical availability.

Pages: 6 route roles
Collections: services, appointment_requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build dental appointment request portal. Let a visitor request a consultation without collecting medical history or implying confirmed clinical availability. Provide service details and preferred-date requests; keep the status pending until a real clinic workflow confirms it.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, services workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"services","fields":{"name":{"type":"string","required":true},"duration":{"type":"number"}},"label":"services","access":"private","seed":[]},{"name":"appointment_requests","fields":{"title":{"type":"string","required":true},"date":{"type":"date"},"status":{"type":"string","required":true}},"label":"appointment requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Light stone surfaces, calm readable hierarchy, a prominent service selector and direct request status; avoid urgency badges or medical imagery as decoration. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Save a request and verify it is neither a medical record nor an automatically confirmed appointment. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Booking & service portals

Wellness class reservation planner

Organize supplied classes and visitor interest without representing unverified capacity as live.

Pages: 6 route roles
Collections: classes, requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build wellness class reservation planner. Organize supplied classes and visitor interest without representing unverified capacity as live. Add date/category filters and a persisted request form with duplicate-submission feedback.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, classes workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"classes","fields":{"title":{"type":"string","required":true},"date":{"type":"date"},"capacity":{"type":"number"}},"label":"classes","access":"private","seed":[]},{"name":"requests","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Light stone surfaces, calm readable hierarchy, a prominent service selector and direct request status; avoid urgency badges or medical imagery as decoration. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Submit once and confirm repeating the action cannot display an invented reservation confirmation. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Booking & service portals

Home repair service portal

Help homeowners describe a non-emergency repair and track the request state.

Pages: 6 route roles
Collections: services, requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build home repair service portal. Help homeowners describe a non-emergency repair and track the request state. Build service search, a short request form and an account history with actual saved statuses.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, services workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"services","fields":{"name":{"type":"string","required":true},"category":{"type":"string","required":true}},"label":"services","access":"private","seed":[]},{"name":"requests","fields":{"title":{"type":"string","required":true},"location":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Light stone surfaces, calm readable hierarchy, a prominent service selector and direct request status; avoid urgency badges or medical imagery as decoration. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Refresh after submission and recover the same request while retaining a pending-review explanation. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Booking & service portals

Barber appointment request

Show supplied services and allow a preferred date and time request without claiming an active scheduling integration.

Pages: 6 route roles
Collections: services, requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build barber appointment request. Show supplied services and allow a preferred date and time request without claiming an active scheduling integration. Use a duration/price summary, clearly labelled preference inputs and a saved-request history.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, services workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"services","fields":{"name":{"type":"string","required":true},"price":{"type":"number"}},"label":"services","access":"private","seed":[]},{"name":"requests","fields":{"title":{"type":"string","required":true},"preferred":{"type":"date"},"status":{"type":"string","required":true}},"label":"requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Light stone surfaces, calm readable hierarchy, a prominent service selector and direct request status; avoid urgency badges or medical imagery as decoration. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify the chosen service and date persist without a fabricated calendar slot lock. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Booking & service portals

Photography session inquiries

Let a photographer collect session preferences and review inquiries as actual saved records.

Pages: 6 route roles
Collections: sessions, inquiries
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build photography session inquiries. Let a photographer collect session preferences and review inquiries as actual saved records. Provide category browsing, permission-cleared portfolio references and a date-preference form.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, sessions workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"sessions","fields":{"name":{"type":"string","required":true},"category":{"type":"string","required":true}},"label":"sessions","access":"private","seed":[]},{"name":"inquiries","fields":{"title":{"type":"string","required":true},"date":{"type":"date"},"status":{"type":"string","required":true}},"label":"inquiries","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Light stone surfaces, calm readable hierarchy, a prominent service selector and direct request status; avoid urgency badges or medical imagery as decoration. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Save an inquiry and verify it is not described as a paid or confirmed booking. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Booking & service portals

Equipment rental request portal

Help visitors shortlist equipment and request a rental period while keeping availability subject to review.

Pages: 6 route roles
Collections: equipment, requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build equipment rental request portal. Help visitors shortlist equipment and request a rental period while keeping availability subject to review. Implement filters, a date-range validator and an itemized request summary.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, equipment workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"equipment","fields":{"name":{"type":"string","required":true},"category":{"type":"string","required":true},"rate":{"type":"number"}},"label":"equipment","access":"private","seed":[]},{"name":"requests","fields":{"title":{"type":"string","required":true},"start":{"type":"date"},"end":{"type":"date"}},"label":"requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Light stone surfaces, calm readable hierarchy, a prominent service selector and direct request status; avoid urgency badges or medical imagery as decoration. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Reject an end date before the start date and persist a valid request accurately. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Booking & service portals

Pet grooming request hub

Collect a grooming service preference without veterinary advice or invented scheduling availability.

Pages: 6 route roles
Collections: services, requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build pet grooming request hub. Collect a grooming service preference without veterinary advice or invented scheduling availability. Provide supplied service facts, a short preference form and editable request notes.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, services workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"services","fields":{"name":{"type":"string","required":true},"duration":{"type":"number"}},"label":"services","access":"private","seed":[]},{"name":"requests","fields":{"title":{"type":"string","required":true},"date":{"type":"date"},"notes":{"type":"string","required":true}},"label":"requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Light stone surfaces, calm readable hierarchy, a prominent service selector and direct request status; avoid urgency badges or medical imagery as decoration. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Retain entered notes when a save fails and recover saved notes after a successful retry. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Booking & service portals

Tutoring session planner

Let a learner request help by subject and review the planned sessions they own.

Pages: 6 route roles
Collections: subjects, requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build tutoring session planner. Let a learner request help by subject and review the planned sessions they own. Use subject filters, a preferred-date form and a private request dashboard without automated acceptance.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, subjects workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"subjects","fields":{"name":{"type":"string","required":true},"level":{"type":"string","required":true}},"label":"subjects","access":"private","seed":[]},{"name":"requests","fields":{"title":{"type":"string","required":true},"date":{"type":"date"},"status":{"type":"string","required":true}},"label":"requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Light stone surfaces, calm readable hierarchy, a prominent service selector and direct request status; avoid urgency badges or medical imagery as decoration. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm another visitor cannot access the first visitor's request notes. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Booking & service portals

Event venue inquiry portal

Support a venue shortlist and date inquiry without claiming actual venue inventory or a reservation.

Pages: 6 route roles
Collections: venues, inquiries
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build event venue inquiry portal. Support a venue shortlist and date inquiry without claiming actual venue inventory or a reservation. Implement capacity/location filters and an inquiry summary with accurate pending state.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, venues workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"venues","fields":{"name":{"type":"string","required":true},"capacity":{"type":"number"},"location":{"type":"string","required":true}},"label":"venues","access":"private","seed":[]},{"name":"inquiries","fields":{"title":{"type":"string","required":true},"date":{"type":"date"},"status":{"type":"string","required":true}},"label":"inquiries","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Light stone surfaces, calm readable hierarchy, a prominent service selector and direct request status; avoid urgency badges or medical imagery as decoration. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Change filters, save an inquiry and verify the selected venue remains consistent. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Architecture & design portfolios

Architecture monograph library

Present supplied architectural projects through a readable index and original project stories.

Pages: 6 route roles
Collections: projects, saved_projects
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build architecture monograph library. Present supplied architectural projects through a readable index and original project stories. Build project categories, detail routes and a visitor-private saved-project notebook.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, projects workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"projects","fields":{"title":{"type":"string","required":true},"location":{"type":"string","required":true},"year":{"type":"number"}},"label":"projects","access":"private","seed":[]},{"name":"saved_projects","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved projects","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Editorial warm ivory, a distinctive licensed serif for display, neutral sans body, asymmetrical supplied imagery and generous but consistent project spacing. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Filter a project, open its real detail route and recover a saved note after reload. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Architecture & design portfolios

Industrial design process portfolio

Explain a designer's supplied research, prototypes and final objects without fabricated clients or awards.

Pages: 6 route roles
Collections: projects, saved_references
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build industrial design process portfolio. Explain a designer's supplied research, prototypes and final objects without fabricated clients or awards. Use process-stage filters and an accessible image sequence with supplied captions.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, projects workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"projects","fields":{"title":{"type":"string","required":true},"material":{"type":"string","required":true},"stage":{"type":"string","required":true}},"label":"projects","access":"private","seed":[]},{"name":"saved_references","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved references","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Editorial warm ivory, a distinctive licensed serif for display, neutral sans body, asymmetrical supplied imagery and generous but consistent project spacing. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Navigate the sequence by keyboard and verify project details match supplied content. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Architecture & design portfolios

Interior materials journal

Let visitors explore actual supplied interior studies and collect a private material shortlist.

Pages: 6 route roles
Collections: studies, saved_materials
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build interior materials journal. Let visitors explore actual supplied interior studies and collect a private material shortlist. Create room/material filters and a shortlist drawer that stores only the visitor's selections.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, studies workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"studies","fields":{"title":{"type":"string","required":true},"material":{"type":"string","required":true},"room":{"type":"string","required":true}},"label":"studies","access":"private","seed":[]},{"name":"saved_materials","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved materials","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Editorial warm ivory, a distinctive licensed serif for display, neutral sans body, asymmetrical supplied imagery and generous but consistent project spacing. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Save a material note, reload and verify another visitor receives no private shortlist. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Architecture & design portfolios

Landscape studio project index

Show place, season and design intent using supplied landscape projects rather than generic scenery.

Pages: 6 route roles
Collections: projects, inquiries
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build landscape studio project index. Show place, season and design intent using supplied landscape projects rather than generic scenery. Provide season/location filtering, true project routes and an inquiry record with no delivery claim.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, projects workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"projects","fields":{"title":{"type":"string","required":true},"season":{"type":"string","required":true},"location":{"type":"string","required":true}},"label":"projects","access":"private","seed":[]},{"name":"inquiries","fields":{"title":{"type":"string","required":true},"message":{"type":"string","required":true}},"label":"inquiries","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Editorial warm ivory, a distinctive licensed serif for display, neutral sans body, asymmetrical supplied imagery and generous but consistent project spacing. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify filters combine correctly and an inquiry is labelled submitted for review only. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Architecture & design portfolios

Brand studio case-study system

Present supplied brand work with a clear brief, decision and result story without inventing performance metrics.

Pages: 6 route roles
Collections: cases, saved_cases
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build brand studio case-study system. Present supplied brand work with a clear brief, decision and result story without inventing performance metrics. Build sector filters, long-form case routes and an actual private reference notebook.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, cases workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"cases","fields":{"title":{"type":"string","required":true},"sector":{"type":"string","required":true},"year":{"type":"number"}},"label":"cases","access":"private","seed":[]},{"name":"saved_cases","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved cases","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Editorial warm ivory, a distinctive licensed serif for display, neutral sans body, asymmetrical supplied imagery and generous but consistent project spacing. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check a deep-linked case opens independently and all quoted business facts are supplied. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Architecture & design portfolios

Furniture design collection

Explain original furniture pieces through material, dimension and process details, with no fake purchasing flow.

Pages: 6 route roles
Collections: pieces, inquiries
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build furniture design collection. Explain original furniture pieces through material, dimension and process details, with no fake purchasing flow. Use material filters, dimension disclosures and a commission inquiry form backed by saved requests.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, pieces workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"pieces","fields":{"name":{"type":"string","required":true},"material":{"type":"string","required":true},"width":{"type":"number"}},"label":"pieces","access":"private","seed":[]},{"name":"inquiries","fields":{"title":{"type":"string","required":true},"message":{"type":"string","required":true}},"label":"inquiries","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Editorial warm ivory, a distinctive licensed serif for display, neutral sans body, asymmetrical supplied imagery and generous but consistent project spacing. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Submit a disposable inquiry and verify it does not claim an order or payment. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Architecture & design portfolios

Photographic editorial archive

Organize permission-cleared image series and meaningful captions without copying another photographer's work.

Pages: 6 route roles
Collections: series, saved_series
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build photographic editorial archive. Organize permission-cleared image series and meaningful captions without copying another photographer's work. Implement a series index, keyboard-operable lightbox and a private saved-series list.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, series workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"series","fields":{"title":{"type":"string","required":true},"location":{"type":"string","required":true},"year":{"type":"number"}},"label":"series","access":"private","seed":[]},{"name":"saved_series","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved series","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Editorial warm ivory, a distinctive licensed serif for display, neutral sans body, asymmetrical supplied imagery and generous but consistent project spacing. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify image alt text and keyboard focus return when the lightbox closes. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Architecture & design portfolios

Motion designer reel library

Make supplied reels and process notes easy to explore without autoplaying audible media.

Pages: 6 route roles
Collections: reels, saved_reels
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build motion designer reel library. Make supplied reels and process notes easy to explore without autoplaying audible media. Add discipline filtering, explicit playback controls and transcripts or descriptions where supplied.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, reels workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"reels","fields":{"title":{"type":"string","required":true},"discipline":{"type":"string","required":true},"year":{"type":"number"}},"label":"reels","access":"private","seed":[]},{"name":"saved_reels","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved reels","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Editorial warm ivory, a distinctive licensed serif for display, neutral sans body, asymmetrical supplied imagery and generous but consistent project spacing. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm videos start muted or only by user action and all controls are keyboard reachable. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Architecture & design portfolios

Craft studio commission portfolio

Connect supplied craft projects to a concise commission inquiry without promising availability or lead times.

Pages: 6 route roles
Collections: works, requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build craft studio commission portfolio. Connect supplied craft projects to a concise commission inquiry without promising availability or lead times. Build a material index, work detail and a request form with an honest pending-review state.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, works workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"works","fields":{"title":{"type":"string","required":true},"material":{"type":"string","required":true}},"label":"works","access":"private","seed":[]},{"name":"requests","fields":{"title":{"type":"string","required":true},"scope":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Editorial warm ivory, a distinctive licensed serif for display, neutral sans body, asymmetrical supplied imagery and generous but consistent project spacing. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Persist request scope and verify missing prices or production dates are not invented. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Directories & marketplaces

Real estate shortlist app

Help a buyer compare permission-cleared fictional properties and save private notes, without brokerage or valuation claims.

Pages: 6 route roles
Collections: properties, saved_listings
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build real estate shortlist app. Help a buyer compare permission-cleared fictional properties and save private notes, without brokerage or valuation claims. Build price/location filters and a mortgage estimate with explicit rate, term and fee exclusions.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, properties workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"properties","fields":{"title":{"type":"string","required":true},"location":{"type":"string","required":true},"price":{"type":"number"}},"label":"properties","access":"private","seed":[]},{"name":"saved_listings","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved listings","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Structured neutral surfaces, map-free location discovery unless a real map integration exists, useful filters and compact comparison details. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Recalculate the estimate from entered assumptions and recover a saved shortlist after reload. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Directories & marketplaces

Local maker directory

Help visitors discover supplied maker profiles and save a private set of references.

Pages: 6 route roles
Collections: makers, saved_makers
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build local maker directory. Help visitors discover supplied maker profiles and save a private set of references. Add discipline and location search, real profile routes and an explicit contact destination.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, makers workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"makers","fields":{"name":{"type":"string","required":true},"discipline":{"type":"string","required":true},"location":{"type":"string","required":true}},"label":"makers","access":"private","seed":[]},{"name":"saved_makers","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved makers","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Structured neutral surfaces, map-free location discovery unless a real map integration exists, useful filters and compact comparison details. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify every contact action has a supplied destination and does not claim an introduction was sent. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Directories & marketplaces

Remote job board workspace

Organize supplied job information and the visitor's own application tracker without claiming employer integrations.

Pages: 6 route roles
Collections: jobs, applications
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build remote job board workspace. Organize supplied job information and the visitor's own application tracker without claiming employer integrations. Provide location/role filters, genuine external application links and a private saved application state.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, jobs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"jobs","fields":{"title":{"type":"string","required":true},"company":{"type":"string","required":true},"location":{"type":"string","required":true}},"label":"jobs","access":"private","seed":[]},{"name":"applications","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"applications","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Structured neutral surfaces, map-free location discovery unless a real map integration exists, useful filters and compact comparison details. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Change one application status and confirm shared job data is not silently modified. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Directories & marketplaces

Specialist consultant directory

Present approved consultant information and allow visitors to compare fields of expertise.

Pages: 6 route roles
Collections: consultants, saved_profiles
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build specialist consultant directory. Present approved consultant information and allow visitors to compare fields of expertise. Implement specialty filters and a private comparison shortlist; do not imply verification or endorsements.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, consultants workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"consultants","fields":{"name":{"type":"string","required":true},"specialty":{"type":"string","required":true},"location":{"type":"string","required":true}},"label":"consultants","access":"private","seed":[]},{"name":"saved_profiles","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved profiles","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Structured neutral surfaces, map-free location discovery unless a real map integration exists, useful filters and compact comparison details. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify only supplied qualifications appear and shortlist changes survive refresh. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Directories & marketplaces

Accessible venue directory

Help visitors compare supplied access information while avoiding unverified accessibility certification.

Pages: 6 route roles
Collections: venues, saved_venues
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build accessible venue directory. Help visitors compare supplied access information while avoiding unverified accessibility certification. Use access-feature filters only for known supplied facts and display the source/review date.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, venues workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"venues","fields":{"name":{"type":"string","required":true},"location":{"type":"string","required":true},"access_notes":{"type":"string","required":true}},"label":"venues","access":"private","seed":[]},{"name":"saved_venues","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved venues","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Structured neutral surfaces, map-free location discovery unless a real map integration exists, useful filters and compact comparison details. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm unknown access fields remain unknown rather than being presented as available. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Directories & marketplaces

Rental workspace directory

Compare supplied desk and studio options without claiming live availability or a lease transaction.

Pages: 6 route roles
Collections: spaces, inquiries
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build rental workspace directory. Compare supplied desk and studio options without claiming live availability or a lease transaction. Add location/rate filters, a shortlist and a persisted inquiry request.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, spaces workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"spaces","fields":{"name":{"type":"string","required":true},"location":{"type":"string","required":true},"monthly_rate":{"type":"number"}},"label":"spaces","access":"private","seed":[]},{"name":"inquiries","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"inquiries","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Structured neutral surfaces, map-free location discovery unless a real map integration exists, useful filters and compact comparison details. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify selected rate assumptions are labelled and inquiries do not become confirmed leases. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Directories & marketplaces

Independent course directory

Let learners compare supplied course descriptions and maintain their own learning shortlist.

Pages: 6 route roles
Collections: courses, saved_courses
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build independent course directory. Let learners compare supplied course descriptions and maintain their own learning shortlist. Build provider/level filters and real external enrollment links without inventing certification.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, courses workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"courses","fields":{"title":{"type":"string","required":true},"provider":{"type":"string","required":true},"level":{"type":"string","required":true}},"label":"courses","access":"private","seed":[]},{"name":"saved_courses","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved courses","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Structured neutral surfaces, map-free location discovery unless a real map integration exists, useful filters and compact comparison details. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check the shortlist is private and unknown fees or certificates are not fabricated. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Directories & marketplaces

Used equipment listing board

Offer a clearly scoped listing catalog and private inquiry tracker without acting as a payment intermediary.

Pages: 6 route roles
Collections: listings, inquiries
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build used equipment listing board. Offer a clearly scoped listing catalog and private inquiry tracker without acting as a payment intermediary. Implement condition/price filters, detail routes and inquiry persistence; no fake escrow or verified seller badge.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, listings workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"listings","fields":{"title":{"type":"string","required":true},"condition":{"type":"string","required":true},"price":{"type":"number"}},"label":"listings","access":"private","seed":[]},{"name":"inquiries","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"inquiries","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Structured neutral surfaces, map-free location discovery unless a real map integration exists, useful filters and compact comparison details. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check price filters use stored numeric values and no purchase is implied by an inquiry. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Directories & marketplaces

Community resource index

Organize reviewed local resources by category without pretending a location graphic is a connected map.

Pages: 6 route roles
Collections: resources, saved_resources
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build community resource index. Organize reviewed local resources by category without pretending a location graphic is a connected map. Provide category/location search, reviewed contact links and a private saved-resource list.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, resources workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"resources","fields":{"title":{"type":"string","required":true},"category":{"type":"string","required":true},"location":{"type":"string","required":true}},"label":"resources","access":"private","seed":[]},{"name":"saved_resources","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved resources","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Structured neutral surfaces, map-free location discovery unless a real map integration exists, useful filters and compact comparison details. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify the page works without a map provider and every listed fact has supplied provenance. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Finance & analytics tools

Personal budget scenario tool

Help a person explore their entered income and spending assumptions without account access or financial advice.

Pages: 6 route roles
Collections: budgets, expenses
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build personal budget scenario tool. Help a person explore their entered income and spending assumptions without account access or financial advice. Implement category totals, editable scenarios and an honest estimate chart based solely on saved inputs.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, budgets workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"budgets","fields":{"title":{"type":"string","required":true},"income":{"type":"number"}},"label":"budgets","access":"private","seed":[]},{"name":"expenses","fields":{"title":{"type":"string","required":true},"amount":{"type":"number"},"category":{"type":"string","required":true}},"label":"expenses","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A quiet dark technical workspace with tabular numerals, clear units, restrained color semantics and charts derived from actual entered or stored values. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Change an expense and verify both the balance and chart update from the same records. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Finance & analytics tools

SaaS revenue scenario calculator

Model subscription assumptions without representing projections as actual revenue or connected billing.

Pages: 6 route roles
Collections: scenarios, costs
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build saas revenue scenario calculator. Model subscription assumptions without representing projections as actual revenue or connected billing. Build price/customer sliders, explicit time units and a saved scenario comparison.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, scenarios workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"scenarios","fields":{"title":{"type":"string","required":true},"customers":{"type":"number"},"price":{"type":"number"}},"label":"scenarios","access":"private","seed":[]},{"name":"costs","fields":{"title":{"type":"string","required":true},"amount":{"type":"number"}},"label":"costs","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A quiet dark technical workspace with tabular numerals, clear units, restrained color semantics and charts derived from actual entered or stored values. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check zero customers and high costs produce sensible output without fabricated profit claims. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Finance & analytics tools

Freelance cash-flow planner

Let a freelancer organize expected receipts and expenses without pretending to access bank accounts.

Pages: 6 route roles
Collections: receipts, expenses
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build freelance cash-flow planner. Let a freelancer organize expected receipts and expenses without pretending to access bank accounts. Provide a date-range view, paid/planned distinction and a cash-flow chart derived from actual records.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, receipts workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"receipts","fields":{"title":{"type":"string","required":true},"amount":{"type":"number"},"due":{"type":"date"}},"label":"receipts","access":"private","seed":[]},{"name":"expenses","fields":{"title":{"type":"string","required":true},"amount":{"type":"number"},"due":{"type":"date"}},"label":"expenses","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A quiet dark technical workspace with tabular numerals, clear units, restrained color semantics and charts derived from actual entered or stored values. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify moving a due date changes the relevant period total without changing the amount. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Finance & analytics tools

Invoice register dashboard

Track supplied invoice records as an organizational tool without claiming issuance, tax compliance or payment collection.

Pages: 6 route roles
Collections: invoices, clients
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build invoice register dashboard. Track supplied invoice records as an organizational tool without claiming issuance, tax compliance or payment collection. Create status filters, due-date review and a print-friendly draft summary.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, invoices workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"invoices","fields":{"title":{"type":"string","required":true},"amount":{"type":"number"},"status":{"type":"string","required":true}},"label":"invoices","access":"private","seed":[]},{"name":"clients","fields":{"name":{"type":"string","required":true},"company":{"type":"string","required":true}},"label":"clients","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A quiet dark technical workspace with tabular numerals, clear units, restrained color semantics and charts derived from actual entered or stored values. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify marked-paid state is a user-entered record rather than provider-confirmed payment. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Finance & analytics tools

Mortgage assumption calculator

Compute principal-and-interest estimates from entered assumptions with transparent exclusions.

Pages: 6 route roles
Collections: scenarios, notes
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build mortgage assumption calculator. Compute principal-and-interest estimates from entered assumptions with transparent exclusions. Implement rate/term/deposit controls, zero-rate handling and a saved comparison table.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, scenarios workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"scenarios","fields":{"title":{"type":"string","required":true},"principal":{"type":"number"},"rate":{"type":"number"}},"label":"scenarios","access":"private","seed":[]},{"name":"notes","fields":{"title":{"type":"string","required":true},"body":{"type":"string","required":true}},"label":"notes","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A quiet dark technical workspace with tabular numerals, clear units, restrained color semantics and charts derived from actual entered or stored values. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check a zero-rate loan divides principal by payment count and fees remain explicitly excluded. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Finance & analytics tools

Project margin planner

Help a studio estimate margin from its own project fee and cost entries.

Pages: 6 route roles
Collections: projects, cost_items
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build project margin planner. Help a studio estimate margin from its own project fee and cost entries. Build an itemized cost editor, scenario totals and an explicit estimate label rather than a success metric.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, projects workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"projects","fields":{"title":{"type":"string","required":true},"fee":{"type":"number"}},"label":"projects","access":"private","seed":[]},{"name":"cost_items","fields":{"title":{"type":"string","required":true},"amount":{"type":"number"},"category":{"type":"string","required":true}},"label":"cost items","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A quiet dark technical workspace with tabular numerals, clear units, restrained color semantics and charts derived from actual entered or stored values. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Add a cost and verify the estimate recomputes with the correct currency and units. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Finance & analytics tools

Subscription spend auditor

Let an individual record recurring tool costs and renewal dates without reading bank or email accounts.

Pages: 6 route roles
Collections: subscriptions, decisions
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build subscription spend auditor. Let an individual record recurring tool costs and renewal dates without reading bank or email accounts. Provide monthly/annual cost normalization, category filters and a user-maintained cancellation checklist.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, subscriptions workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"subscriptions","fields":{"name":{"type":"string","required":true},"monthly_cost":{"type":"number"},"renewal":{"type":"date"}},"label":"subscriptions","access":"private","seed":[]},{"name":"decisions","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"decisions","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A quiet dark technical workspace with tabular numerals, clear units, restrained color semantics and charts derived from actual entered or stored values. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify annual totals use the entered billing term and never claim a service was canceled. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Finance & analytics tools

Crypto watchlist notebook

Organize a user's manually entered asset notes without pretending to stream market prices or execute trades.

Pages: 6 route roles
Collections: assets, notes
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build crypto watchlist notebook. Organize a user's manually entered asset notes without pretending to stream market prices or execute trades. Build asset search and a clearly labelled manually entered reference-price view; no trading or return projections.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, assets workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"assets","fields":{"symbol":{"type":"string","required":true},"reference_price":{"type":"number"}},"label":"assets","access":"private","seed":[]},{"name":"notes","fields":{"title":{"type":"string","required":true},"thesis":{"type":"string","required":true}},"label":"notes","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A quiet dark technical workspace with tabular numerals, clear units, restrained color semantics and charts derived from actual entered or stored values. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm no stale/manual price is labelled live and no action simulates trade execution. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Finance & analytics tools

Business KPI input dashboard

Visualize actual user-entered business measurements with definitions and reporting periods.

Pages: 6 route roles
Collections: measurements, definitions
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build business kpi input dashboard. Visualize actual user-entered business measurements with definitions and reporting periods. Add period selection, unit-aware comparisons and editable metric definitions without invented growth.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, measurements workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"measurements","fields":{"name":{"type":"string","required":true},"value":{"type":"number"},"period":{"type":"date"}},"label":"measurements","access":"private","seed":[]},{"name":"definitions","fields":{"title":{"type":"string","required":true},"unit":{"type":"string","required":true}},"label":"definitions","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A quiet dark technical workspace with tabular numerals, clear units, restrained color semantics and charts derived from actual entered or stored values. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify missing periods show an honest empty state instead of fabricated values. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Learning & course workspaces

Self-paced course workspace

Help a learner work through supplied lessons and record their own progress without unsupported certification.

Pages: 6 route roles
Collections: lessons, progress
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build self-paced course workspace. Help a learner work through supplied lessons and record their own progress without unsupported certification. Provide module navigation, a searchable syllabus and an explicit mark-complete action.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, lessons workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"lessons","fields":{"title":{"type":"string","required":true},"module":{"type":"string","required":true}},"label":"lessons","access":"private","seed":[]},{"name":"progress","fields":{"title":{"type":"string","required":true},"complete":{"type":"boolean"}},"label":"progress","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm paper-like reading surfaces, clear lesson hierarchy, comfortable line length and progress that corresponds to actual learner actions. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Complete a lesson and verify the same progress after navigating and reloading. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Learning & course workspaces

Flashcard review notebook

Let a learner create and review cards from supplied material without pretending the content is professionally verified.

Pages: 6 route roles
Collections: cards, reviews
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build flashcard review notebook. Let a learner create and review cards from supplied material without pretending the content is professionally verified. Implement reveal, self-rating, deck filters and editable cards with separate practice history.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, cards workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"cards","fields":{"front":{"type":"string","required":true},"back":{"type":"string","required":true},"deck":{"type":"string","required":true}},"label":"cards","access":"private","seed":[]},{"name":"reviews","fields":{"title":{"type":"string","required":true},"correct":{"type":"boolean"}},"label":"reviews","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm paper-like reading surfaces, clear lesson hierarchy, comfortable line length and progress that corresponds to actual learner actions. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Ensure answers remain hidden until reveal and review history does not overwrite card content. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Learning & course workspaces

Language vocabulary shelf

Organize a learner's words, examples and review decisions in private saved records.

Pages: 6 route roles
Collections: words, reviews
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build language vocabulary shelf. Organize a learner's words, examples and review decisions in private saved records. Build language/category search and a reveal-based practice view with actual completion tracking.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, words workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"words","fields":{"term":{"type":"string","required":true},"meaning":{"type":"string","required":true},"language":{"type":"string","required":true}},"label":"words","access":"private","seed":[]},{"name":"reviews","fields":{"title":{"type":"string","required":true},"done":{"type":"boolean"}},"label":"reviews","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm paper-like reading surfaces, clear lesson hierarchy, comfortable line length and progress that corresponds to actual learner actions. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Edit a meaning, reopen practice and verify the updated saved text appears. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Learning & course workspaces

Research reading planner

Help a student prioritize permission-cleared readings and keep notes separate from completion state.

Pages: 6 route roles
Collections: readings, notes
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build research reading planner. Help a student prioritize permission-cleared readings and keep notes separate from completion state. Provide status filters, real supplied source links and a private note editor.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, readings workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"readings","fields":{"title":{"type":"string","required":true},"source":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"readings","access":"private","seed":[]},{"name":"notes","fields":{"title":{"type":"string","required":true},"body":{"type":"string","required":true}},"label":"notes","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm paper-like reading surfaces, clear lesson hierarchy, comfortable line length and progress that corresponds to actual learner actions. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm unsupplied citations never appear and note changes survive a page reload. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Learning & course workspaces

Teacher resource organizer

Allow one educator to maintain their own resource library without exposing student records.

Pages: 6 route roles
Collections: resources, collections
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build teacher resource organizer. Allow one educator to maintain their own resource library without exposing student records. Build subject/level search and a saved collection organizer; exclude real learner names or grades.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, resources workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"resources","fields":{"title":{"type":"string","required":true},"subject":{"type":"string","required":true},"level":{"type":"string","required":true}},"label":"resources","access":"private","seed":[]},{"name":"collections","fields":{"title":{"type":"string","required":true},"description":{"type":"string","required":true}},"label":"collections","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm paper-like reading surfaces, clear lesson hierarchy, comfortable line length and progress that corresponds to actual learner actions. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify search handles long titles and another app visitor cannot read private resources. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Learning & course workspaces

Practice quiz runner

Run supplied practice questions with deterministic answer checking and no fabricated grading authority.

Pages: 6 route roles
Collections: questions, attempts
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build practice quiz runner. Run supplied practice questions with deterministic answer checking and no fabricated grading authority. Implement one-question-at-a-time navigation, explanation reveal and a restartable practice attempt.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, questions workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"questions","fields":{"title":{"type":"string","required":true},"answer":{"type":"string","required":true},"topic":{"type":"string","required":true}},"label":"questions","access":"private","seed":[]},{"name":"attempts","fields":{"title":{"type":"string","required":true},"score":{"type":"number"}},"label":"attempts","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm paper-like reading surfaces, clear lesson hierarchy, comfortable line length and progress that corresponds to actual learner actions. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check a known incorrect answer affects the computed score and restart clears attempt state. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Learning & course workspaces

Workshop materials portal

Make a supplied workshop agenda and materials easy to navigate without claiming access control beyond the actual app identity.

Pages: 6 route roles
Collections: sessions, resources
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build workshop materials portal. Make a supplied workshop agenda and materials easy to navigate without claiming access control beyond the actual app identity. Provide agenda filtering, real resource links and a private personal checklist.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, sessions workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"sessions","fields":{"title":{"type":"string","required":true},"start":{"type":"date"}},"label":"sessions","access":"private","seed":[]},{"name":"resources","fields":{"title":{"type":"string","required":true},"url":{"type":"string","required":true}},"label":"resources","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm paper-like reading surfaces, clear lesson hierarchy, comfortable line length and progress that corresponds to actual learner actions. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check every download/resource destination exists and completed checklist items remain private. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Learning & course workspaces

Portfolio learning journal

Help a learner document completed work and reflections without inventing credentials or publishing private entries.

Pages: 6 route roles
Collections: entries, goals
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build portfolio learning journal. Help a learner document completed work and reflections without inventing credentials or publishing private entries. Offer chronological browsing, goal tracking and an editable reflection form.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, entries workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"entries","fields":{"title":{"type":"string","required":true},"reflection":{"type":"string","required":true},"date":{"type":"date"}},"label":"entries","access":"private","seed":[]},{"name":"goals","fields":{"title":{"type":"string","required":true},"done":{"type":"boolean"}},"label":"goals","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm paper-like reading surfaces, clear lesson hierarchy, comfortable line length and progress that corresponds to actual learner actions. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Save a long reflection, reload and confirm it remains scoped to the current visitor. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Learning & course workspaces

Exam revision calendar

Organize a learner's entered topics and dates into a realistic private revision plan.

Pages: 6 route roles
Collections: topics, sessions
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build exam revision calendar. Organize a learner's entered topics and dates into a realistic private revision plan. Add a weekly list/calendar switch, topic filtering and completed-session tracking.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, topics workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"topics","fields":{"title":{"type":"string","required":true},"priority":{"type":"string","required":true}},"label":"topics","access":"private","seed":[]},{"name":"sessions","fields":{"title":{"type":"string","required":true},"date":{"type":"date"},"done":{"type":"boolean"}},"label":"sessions","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Warm paper-like reading surfaces, clear lesson hierarchy, comfortable line length and progress that corresponds to actual learner actions. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Move a session to another date and verify no duplicate record appears. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Community & membership workflows

Club interest portal

Collect real membership interest without presenting submission as approved membership.

Pages: 6 route roles
Collections: events, interest_requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build club interest portal. Collect real membership interest without presenting submission as approved membership. Provide event browsing, a private interest form and a clear pending-review explanation.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, events workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"events","fields":{"title":{"type":"string","required":true},"date":{"type":"date"}},"label":"events","access":"private","seed":[]},{"name":"interest_requests","fields":{"title":{"type":"string","required":true},"message":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"interest requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A welcoming typographic system with explicit content ownership, readable activity lists and restrained identity surfaces; never fake member counts. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify a submitted interest record does not grant membership or expose other requests. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Community & membership workflows

Volunteer opportunity board

Help visitors discover supplied opportunities and maintain their own expression of interest.

Pages: 6 route roles
Collections: opportunities, interests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build volunteer opportunity board. Help visitors discover supplied opportunities and maintain their own expression of interest. Build location/category filters and a saved interest history without claimed placement.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, opportunities workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"opportunities","fields":{"title":{"type":"string","required":true},"location":{"type":"string","required":true}},"label":"opportunities","access":"private","seed":[]},{"name":"interests","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"interests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A welcoming typographic system with explicit content ownership, readable activity lists and restrained identity surfaces; never fake member counts. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Save an interest and confirm no organizer message or approval is falsely reported. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Community & membership workflows

Creator membership outline

Describe supplied membership content and test an account journey without pretending subscriptions are activated.

Pages: 6 route roles
Collections: resources, interests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build creator membership outline. Describe supplied membership content and test an account journey without pretending subscriptions are activated. Implement previewable resources, real sign-in and a membership-interest state; omit live billing until configured.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, resources workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"resources","fields":{"title":{"type":"string","required":true},"category":{"type":"string","required":true}},"label":"resources","access":"private","seed":[]},{"name":"interests","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"interests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A welcoming typographic system with explicit content ownership, readable activity lists and restrained identity surfaces; never fake member counts. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check account creation alone never unlocks a claimed purchased entitlement. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Community & membership workflows

Neighborhood event calendar

Publish reviewed event details and let visitors save a private attendance plan.

Pages: 6 route roles
Collections: events, saved_events
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build neighborhood event calendar. Publish reviewed event details and let visitors save a private attendance plan. Offer date/location filters, detail routes and an add-to-personal-plan action without issuing tickets.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, events workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"events","fields":{"title":{"type":"string","required":true},"date":{"type":"date"},"location":{"type":"string","required":true}},"label":"events","access":"private","seed":[]},{"name":"saved_events","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved events","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A welcoming typographic system with explicit content ownership, readable activity lists and restrained identity surfaces; never fake member counts. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify saved plans survive reload and the event date comes from supplied data. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Community & membership workflows

Professional resource circle

Organize permission-cleared professional resources without implying credentials or endorsement.

Pages: 6 route roles
Collections: resources, saved_resources
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build professional resource circle. Organize permission-cleared professional resources without implying credentials or endorsement. Build discipline filters and a private reference notebook with genuine external links.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, resources workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"resources","fields":{"title":{"type":"string","required":true},"discipline":{"type":"string","required":true},"url":{"type":"string","required":true}},"label":"resources","access":"private","seed":[]},{"name":"saved_resources","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved resources","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A welcoming typographic system with explicit content ownership, readable activity lists and restrained identity surfaces; never fake member counts. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check no resource link is a placeholder and no visitor-private notes become public. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Community & membership workflows

Donation interest information hub

Explain a supplied organization's work and collect inquiries without fabricating donations or charity status.

Pages: 6 route roles
Collections: programs, inquiries
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build donation interest information hub. Explain a supplied organization's work and collect inquiries without fabricating donations or charity status. Provide program routes and an interest form; show only supplied registration and contact facts.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, programs workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"programs","fields":{"title":{"type":"string","required":true},"description":{"type":"string","required":true}},"label":"programs","access":"private","seed":[]},{"name":"inquiries","fields":{"title":{"type":"string","required":true},"message":{"type":"string","required":true}},"label":"inquiries","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A welcoming typographic system with explicit content ownership, readable activity lists and restrained identity surfaces; never fake member counts. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm no request is represented as a donation, tax receipt or verified beneficiary outcome. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Community & membership workflows

Community proposal workspace

Let an individual maintain project proposals and review notes without pretending there is a connected voting system.

Pages: 6 route roles
Collections: proposals, notes
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build community proposal workspace. Let an individual maintain project proposals and review notes without pretending there is a connected voting system. Implement proposal editing, status filters and a private review checklist.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, proposals workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"proposals","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"proposals","access":"private","seed":[]},{"name":"notes","fields":{"title":{"type":"string","required":true},"body":{"type":"string","required":true}},"label":"notes","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A welcoming typographic system with explicit content ownership, readable activity lists and restrained identity surfaces; never fake member counts. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify a local approval label cannot change another user's permissions or claim a public vote. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Community & membership workflows

Peer mentoring interest board

Collect a visitor's mentoring interests without exposing a public member directory by default.

Pages: 6 route roles
Collections: topics, requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build peer mentoring interest board. Collect a visitor's mentoring interests without exposing a public member directory by default. Offer topic search and a private request tracker; exclude automatic matching or message delivery.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, topics workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"topics","fields":{"title":{"type":"string","required":true},"discipline":{"type":"string","required":true}},"label":"topics","access":"private","seed":[]},{"name":"requests","fields":{"title":{"type":"string","required":true},"message":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A welcoming typographic system with explicit content ownership, readable activity lists and restrained identity surfaces; never fake member counts. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Persist a request and clearly explain the real next review step. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Community & membership workflows

Creative collective project hub

Present approved collective work while keeping contributor claims and project ownership accurate.

Pages: 6 route roles
Collections: projects, inquiries
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build creative collective project hub. Present approved collective work while keeping contributor claims and project ownership accurate. Build a project index and supplied contributor references, plus a saved inquiry flow.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, projects workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"projects","fields":{"title":{"type":"string","required":true},"discipline":{"type":"string","required":true}},"label":"projects","access":"private","seed":[]},{"name":"inquiries","fields":{"title":{"type":"string","required":true},"message":{"type":"string","required":true}},"label":"inquiries","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A welcoming typographic system with explicit content ownership, readable activity lists and restrained identity surfaces; never fake member counts. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify names and credits are permission-cleared and inquiry submission does not imply collaboration approval. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Editorial & publishing systems

Independent magazine index

Make supplied articles discoverable through topic, author and meaningful summaries.

Pages: 6 route roles
Collections: articles, saved_articles
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build independent magazine index. Make supplied articles discoverable through topic, author and meaningful summaries. Provide topic search, article routes and a private reading list without fabricating publication history.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, articles workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"articles","fields":{"title":{"type":"string","required":true},"topic":{"type":"string","required":true},"author":{"type":"string","required":true}},"label":"articles","access":"private","seed":[]},{"name":"saved_articles","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved articles","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Content-led layouts with a distinctive display face, neutral body typography, measured reading width and a fast text-first index rather than decorative feature tiles. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Open an article by direct URL and recover a saved reading-list note. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Editorial & publishing systems

Newsletter archive browser

Present a supplied newsletter archive and collect real interest without claiming email delivery.

Pages: 6 route roles
Collections: issues, interests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build newsletter archive browser. Present a supplied newsletter archive and collect real interest without claiming email delivery. Build date/topic search and a collector-backed interest form with a clear consent explanation.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, issues workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"issues","fields":{"title":{"type":"string","required":true},"date":{"type":"date"}},"label":"issues","access":"private","seed":[]},{"name":"interests","fields":{"title":{"type":"string","required":true},"email":{"type":"string","required":true}},"label":"interests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Content-led layouts with a distinctive display face, neutral body typography, measured reading width and a fast text-first index rather than decorative feature tiles. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Save interest once and show actual acknowledgment without claiming a welcome email was sent. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Editorial & publishing systems

Podcast episode library

Organize supplied episodes, transcripts and listening notes with accessible playback controls.

Pages: 6 route roles
Collections: episodes, notes
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build podcast episode library. Organize supplied episodes, transcripts and listening notes with accessible playback controls. Use episode filters, real supplied media links and a private note form; no audible autoplay.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, episodes workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"episodes","fields":{"title":{"type":"string","required":true},"topic":{"type":"string","required":true},"duration":{"type":"number"}},"label":"episodes","access":"private","seed":[]},{"name":"notes","fields":{"title":{"type":"string","required":true},"body":{"type":"string","required":true}},"label":"notes","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Content-led layouts with a distinctive display face, neutral body typography, measured reading width and a fast text-first index rather than decorative feature tiles. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check playback controls and transcript navigation work without inventing unavailable audio. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Editorial & publishing systems

Technical documentation library

Publish supplied technical explanations with useful navigation and no fabricated supported API methods.

Pages: 6 route roles
Collections: documents, saved_pages
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build technical documentation library. Publish supplied technical explanations with useful navigation and no fabricated supported API methods. Build section search, deep-linkable headings and a private notes layer separate from public reference content.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, documents workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"documents","fields":{"title":{"type":"string","required":true},"section":{"type":"string","required":true}},"label":"documents","access":"private","seed":[]},{"name":"saved_pages","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved pages","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Content-led layouts with a distinctive display face, neutral body typography, measured reading width and a fast text-first index rather than decorative feature tiles. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify links point to real headings and all code examples match supplied contracts. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Editorial & publishing systems

Travel field-notes archive

Present an author's supplied place notes without inventing safety claims, prices or current opening hours.

Pages: 6 route roles
Collections: notes, saved_places
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build travel field-notes archive. Present an author's supplied place notes without inventing safety claims, prices or current opening hours. Provide location/date filters and an editable private itinerary list labelled as planning only.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, notes workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"notes","fields":{"title":{"type":"string","required":true},"location":{"type":"string","required":true},"date":{"type":"date"}},"label":"notes","access":"private","seed":[]},{"name":"saved_places","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved places","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Content-led layouts with a distinctive display face, neutral body typography, measured reading width and a fast text-first index rather than decorative feature tiles. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm time-sensitive facts have supplied dates and saved plans do not claim bookings. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Editorial & publishing systems

Recipe editorial collection

Organize original supplied recipes with practical ingredient and serving controls.

Pages: 6 route roles
Collections: recipes, saved_recipes
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build recipe editorial collection. Organize original supplied recipes with practical ingredient and serving controls. Add category search and a serving multiplier that preserves clear units; no dietary safety certification.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, recipes workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"recipes","fields":{"title":{"type":"string","required":true},"category":{"type":"string","required":true},"servings":{"type":"number"}},"label":"recipes","access":"private","seed":[]},{"name":"saved_recipes","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved recipes","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Content-led layouts with a distinctive display face, neutral body typography, measured reading width and a fast text-first index rather than decorative feature tiles. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check doubled servings scale known quantities correctly and a saved note persists. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Editorial & publishing systems

Oral history listening room

Make consented recordings and transcripts browsable without exposing restricted personal information.

Pages: 6 route roles
Collections: stories, saved_stories
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build oral history listening room. Make consented recordings and transcripts browsable without exposing restricted personal information. Provide theme filters, explicit audio playback and readable transcript sections.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, stories workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"stories","fields":{"title":{"type":"string","required":true},"theme":{"type":"string","required":true},"date":{"type":"date"}},"label":"stories","access":"private","seed":[]},{"name":"saved_stories","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved stories","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Content-led layouts with a distinctive display face, neutral body typography, measured reading width and a fast text-first index rather than decorative feature tiles. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify all published voices and names are permission-cleared and media has an honest unavailable state. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Editorial & publishing systems

Book review reading shelf

Publish original supplied reviews and let visitors maintain a separate private reading shelf.

Pages: 6 route roles
Collections: reviews, reading_list
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build book review reading shelf. Publish original supplied reviews and let visitors maintain a separate private reading shelf. Implement genre/author filters and a saved to-read/finished state without inventing star ratings.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, reviews workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"reviews","fields":{"title":{"type":"string","required":true},"author":{"type":"string","required":true},"genre":{"type":"string","required":true}},"label":"reviews","access":"private","seed":[]},{"name":"reading_list","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"reading list","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Content-led layouts with a distinctive display face, neutral body typography, measured reading width and a fast text-first index rather than decorative feature tiles. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Move a book to finished and verify that public review content does not change. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Editorial & publishing systems

Design research publication index

Explain supplied research projects and sources without treating editorial conclusions as independent benchmark wins.

Pages: 6 route roles
Collections: publications, saved_sources
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build design research publication index. Explain supplied research projects and sources without treating editorial conclusions as independent benchmark wins. Build discipline/year filtering and genuine source links with a private annotation view.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, publications workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"publications","fields":{"title":{"type":"string","required":true},"discipline":{"type":"string","required":true},"year":{"type":"number"}},"label":"publications","access":"private","seed":[]},{"name":"saved_sources","fields":{"title":{"type":"string","required":true},"note":{"type":"string","required":true}},"label":"saved sources","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Content-led layouts with a distinctive display face, neutral body typography, measured reading width and a fast text-first index rather than decorative feature tiles. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check every citation exists and missing measurements are not replaced with invented scores. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Operations & developer workspaces

Inventory reorder workspace

Track a small operator's entered stock and reorder decisions without claiming a connected warehouse.

Pages: 6 route roles
Collections: items, movements
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build inventory reorder workspace. Track a small operator's entered stock and reorder decisions without claiming a connected warehouse. Provide low-stock filters, validated movements and a user-reviewed reorder list.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, items workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"items","fields":{"name":{"type":"string","required":true},"stock":{"type":"number"},"threshold":{"type":"number"}},"label":"items","access":"private","seed":[]},{"name":"movements","fields":{"title":{"type":"string","required":true},"quantity":{"type":"number"}},"label":"movements","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Record a movement once and verify count changes do not duplicate on refresh. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Operations & developer workspaces

Maintenance request dashboard

Let a facility manager organize their own maintenance requests and actual review states.

Pages: 6 route roles
Collections: assets, requests
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build maintenance request dashboard. Let a facility manager organize their own maintenance requests and actual review states. Build location/priority search, editable request details and a completion checklist.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, assets workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"assets","fields":{"name":{"type":"string","required":true},"location":{"type":"string","required":true}},"label":"assets","access":"private","seed":[]},{"name":"requests","fields":{"title":{"type":"string","required":true},"priority":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"requests","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify a closed request retains its history and no external technician notification is invented. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Operations & developer workspaces

Release checklist manager

Track release preparation without pretending the app can deploy code or access production systems.

Pages: 6 route roles
Collections: releases, checks
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build release checklist manager. Track release preparation without pretending the app can deploy code or access production systems. Use release filters, a checklist drawer and a readiness count derived from saved checks.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, releases workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"releases","fields":{"title":{"type":"string","required":true},"date":{"type":"date"},"status":{"type":"string","required":true}},"label":"releases","access":"private","seed":[]},{"name":"checks","fields":{"title":{"type":"string","required":true},"done":{"type":"boolean"}},"label":"checks","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Mark a check complete and ensure the app does not claim the actual release was deployed. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Operations & developer workspaces

API incident notebook

Record manually supplied incidents and investigation notes without fabricated live observability.

Pages: 6 route roles
Collections: incidents, notes
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build api incident notebook. Record manually supplied incidents and investigation notes without fabricated live observability. Provide severity/status filtering and a chronological note editor; label all inputs as operator-maintained.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, incidents workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"incidents","fields":{"title":{"type":"string","required":true},"severity":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"incidents","access":"private","seed":[]},{"name":"notes","fields":{"title":{"type":"string","required":true},"body":{"type":"string","required":true}},"label":"notes","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Confirm no chart or status claims a connected monitoring feed when none exists. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Operations & developer workspaces

Equipment checkout register

Let an individual organize equipment loans and returns without a false multi-user permission model.

Pages: 6 route roles
Collections: equipment, loans
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build equipment checkout register. Let an individual organize equipment loans and returns without a false multi-user permission model. Build availability derived from actual loan records, a due-date view and an explicit return action.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, equipment workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"equipment","fields":{"name":{"type":"string","required":true},"condition":{"type":"string","required":true}},"label":"equipment","access":"private","seed":[]},{"name":"loans","fields":{"title":{"type":"string","required":true},"due":{"type":"date"},"returned":{"type":"boolean"}},"label":"loans","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Return an item and verify its availability updates from the same acknowledged write. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Operations & developer workspaces

Supplier review workspace

Help a buyer compare supplied supplier notes without claiming verified ratings or automated procurement.

Pages: 6 route roles
Collections: suppliers, reviews
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build supplier review workspace. Help a buyer compare supplied supplier notes without claiming verified ratings or automated procurement. Add category filters, a private evaluation form and an exportable text summary of entered facts.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, suppliers workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"suppliers","fields":{"name":{"type":"string","required":true},"category":{"type":"string","required":true}},"label":"suppliers","access":"private","seed":[]},{"name":"reviews","fields":{"title":{"type":"string","required":true},"status":{"type":"string","required":true},"notes":{"type":"string","required":true}},"label":"reviews","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify a draft review is never published as an independent rating or purchase order. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Operations & developer workspaces

Bug triage workbench

Organize reproducible issues, severity and next action without pretending to modify a remote repository.

Pages: 6 route roles
Collections: issues, reproductions
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build bug triage workbench. Organize reproducible issues, severity and next action without pretending to modify a remote repository. Build severity/status filters, an issue drawer and actual saved reproduction steps.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, issues workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"issues","fields":{"title":{"type":"string","required":true},"severity":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"issues","access":"private","seed":[]},{"name":"reproductions","fields":{"title":{"type":"string","required":true},"steps":{"type":"string","required":true}},"label":"reproductions","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Edit one issue and confirm unrelated issues and reproduction notes remain intact. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Operations & developer workspaces

Content approval queue

Let one editor review their own content drafts with a clear distinction between approval records and actual publishing.

Pages: 6 route roles
Collections: drafts, reviews
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build content approval queue. Let one editor review their own content drafts with a clear distinction between approval records and actual publishing. Provide status tabs, an editing drawer and a review history without fake CMS deployment.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, drafts workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"drafts","fields":{"title":{"type":"string","required":true},"body":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"drafts","access":"private","seed":[]},{"name":"reviews","fields":{"title":{"type":"string","required":true},"notes":{"type":"string","required":true}},"label":"reviews","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Approve a draft and confirm the UI does not claim it was published to an external site. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Operations & developer workspaces

Lab sample organization tool

Organize fictional non-clinical sample labels and review notes without regulated diagnostic or chain-of-custody claims.

Pages: 6 route roles
Collections: samples, observations
Connectors: Database · Visitor auth

Read the complete engineering prompt

PRODUCT AND OUTCOME
Build lab sample organization tool. Organize fictional non-clinical sample labels and review notes without regulated diagnostic or chain-of-custody claims. Build batch/status filters and a private observation form; no patient identifiers or diagnostic interpretation.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, samples workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"samples","fields":{"title":{"type":"string","required":true},"batch":{"type":"string","required":true},"status":{"type":"string","required":true}},"label":"samples","access":"private","seed":[]},{"name":"observations","fields":{"title":{"type":"string","required":true},"notes":{"type":"string","required":true}},"label":"observations","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
Precise neutral interfaces with compact controls, tabular data, clear units and a deliberate distinction between actual stored status and unconnected infrastructure. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Verify sample notes persist and the interface never claims clinical validation or certified custody. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Check the architecture. Compare the tradeoffs.

Follow the data model, account boundary and source handoff before choosing a builder.