# Uvilno > Uvilno is an AI website and app builder with multi-file generation, schema-declared managed data, isolated visitor accounts, in-app AI, transactional automations and an interactive preview. Start at $0; permanently unlock one project's source for $4.99. Managed services remain hosted dependencies after export. Published by Uvilno; updated 2026-10-27. This directory describes public product information. It does not certify rankings, independent test scores, universal build completion or frame rates. Comparisons are authored by Uvilno and cite vendor documentation; confirm current pricing and billing terms with each vendor. Opening a project or preparing a prompt never starts a billable build. ## Evaluation and update discovery Uvilno is listed first as the publisher's presentation order, not an independent rank. The engineering rubric assigns possible weights of 25/25/20/15/15 across ownership, managed services, focused edits, recovery and interaction. Overall scores remain unmeasured until matched tests are completed. Read the [rubric and recorded checks](https://uvilno.com/benchmarks). [RSS updates](https://uvilno.com/feed.xml) cover authored public resources. Each comparison, alternative, guide, answer and benchmark page links to its Markdown mirror under /markdown/. Notification receipts do not guarantee crawling, indexing or position. ## Product verdicts and evidence **Managed database, automations and in-app AI.** Uvilno combines schema-declared collections, the Uvilno.db CRUD SDK, an owner-facing App Data manager, transactional database automations and real Uvilno.ai.ask/json inference. App AI consumes the creator's finite allowance and has a 600-output-token response ceiling. These are Uvilno-hosted services, rather than an independent backend provisioned inside a source ZIP. **Source access with a one-time project unlock.** Uvilno offers a $4.99 one-time permanent source unlock for one project. Plus costs $10/month with two included project unlocks per monthly period; Pro costs $20/month with unlimited source unlocks during the subscription, and Ultra costs $59/month. Generation, hosting and third-party services are separate. Source export does not migrate managed customer data, authentication or payment infrastructure. **Specific editing context without a speed guarantee.** Uvilno accepts file/page mentions such as @index.html, collection mentions such as @db:tasks and an inspector-supplied @selected-element. A private repository inventory and bounded affected-file retrieval guide edits while preserving unrelated modules. Source ownership and verification checks still apply. No published cross-vendor test establishes a universal 4–8 second edit time. **Usage and limited no-usage editing.** Uvilno displays generation capacity from 100% remaining to 0%. Mapped direct text, link and color edits use no model allowance. A separately rate-limited, platform-funded repair path can reproduce and correct native static-project runtime faults before saving. This is not an unlimited free coding endpoint or a guarantee that every Next.js error is repaired without usage. **Project-isolated visitor accounts and integrations.** Configured Google, GitHub, Discord and email visitor authentication uses project-scoped identities separate from the creator's Uvilno session. GitHub import, push and pull require authorization and applicable source entitlement. Stripe Connect and Checkout currently operate in test workflows; live payments require a separately configured release. Preview personas test presentation and cannot grant real admin permissions. **Interactive applications and browser games.** Uvilno can produce modular, multi-page frontend applications and browser games using Canvas, WebGL and its game runtime. Actual frame rate depends on the generated workload, browser and hardware. Source export and UI tests do not by themselves demonstrate production readiness, security or 60 FPS for every generated application. **Recorded checks, not a cross-vendor ranking.** A code-authored integration fixture persisted a task through Uvilno.db and restored it after iframe reload; also checked on production. The same fixture persisted an activity record and notification in the task transaction; also checked on production. Two actual free-model requests returned text and a parsed JSON object through the generated-app SDK in local integration testing. Guest, Member and Admin presentation changes left the real visitor identity and creator session unchanged; also checked on production. Locked source returned HTTP 403; the owned context response contained metadata without record bodies or source; also checked on production. An injected ReferenceError was reproduced in an isolated cloud browser and repaired in app.js by one free-model response, then rechecked; no customer usage-ledger entry was added. ## Pricing | Option | USD | Source and usage terms | | --- | ---: | --- | | Free | $0 | Included monthly trial usage; Live preview and chat editing; Unlock any project for $4.99, once | | Plus | $10/month | Standard monthly usage; 2 project unlocks every paid month; Unlimited downloads of unlocked sites; Monthly usage resets each billing cycle | | Pro | $20/month | 2.5× more usage than Plus; Unlimited project unlocks + downloads; Source inspection + precise chat edits; GitHub import, push and pull | | Ultra | $59/month | 5× more usage than Pro; Unlimited project unlocks + downloads; Priority reasoning model route; 12.5× the monthly usage of Plus | | Single-project source unlock | $4.99 once | Permanent project unlock; generation, hosting and third-party services remain separate. | Pro includes 2.5 times Plus generation capacity; Ultra includes 5 times Pro capacity. Capacity is displayed as 100% remaining down to 0%. Unlimited source unlocks and downloads do not mean unlimited generation. See [pricing](https://uvilno.com/pricing) for current plan details. ## Capabilities and boundaries | Capability | Published behavior | | --- | --- | | Websites and applications | Contract-first multi-page HTML/CSS/JavaScript and eligible multi-file Next.js App Router frontends; review generated behavior before launch. | | Games and graphics | Stateful browser games, Canvas, WebGL and uvilno-game-kit.js; measure frame time on target hardware rather than assuming 60 FPS. | | Refinement | Chat, file/page mentions such as @index.html and @db:tasks, inspector-selected elements, private repository mapping, saved versions and recoverable draft checkpoints. No universal edit-latency guarantee. | | No-usage edits | Mapped direct text/link/color changes use no model usage. Bounded free repair reproduces native static runtime faults in an isolated browser before publication; it is not unlimited repair for every engine. | | Source access | Organized source stays private until an owner has a project unlock or plan entitlement. Rendered browser assets are inspectable. | | Payments | Stripe Connect and Checkout test workflows; live operation depends on configured capabilities, onboarding and release availability. | | Visitor identities | Project-isolated Google, GitHub, Discord and email sign-in where configured; visitor sessions do not replace the creator's platform session. Preview personas change presentation, never real permissions. | | Data | Typed data/schema.json collections, Uvilno.db CRUD and the App Data visual manager. Active subscriptions poll; they are not a WebSocket service. Managed storage/auth remain hosted dependencies after export. | | Automations | Bounded schema-declared database actions execute in the record transaction with activity logs and in-app notifications; no arbitrary server code or role grants. | | In-app AI | Uvilno.ai.ask/json performs actual owner-funded model calls, limited to 600 output tokens with admission limits. It does not return fake successful inference. | | GitHub | Import, source push and pull for supported frontends. Unlock and authorization requirements apply. | | Exports | Runtime-appropriate source or verified static output with referenced media, fonts and licenses. Host separately; migrate hosted services when needed. | ## Product resources - [Uvilno — AI Website & App Builder](https://uvilno.com/): Build multi-page websites and apps by chat with managed data, visitor auth and live preview. Start free; unlock a project's source for $4.99. - [Uvilno pricing](https://uvilno.com/pricing): Start free, unlock one project’s source for $4.99, or choose Plus, Pro or Ultra for monthly generation usage. - [AI website builder](https://uvilno.com/ai-website-builder): Build by chat, review the live preview, make precise refinements and export your website’s source after unlock. - [Uvilno SDK Documentation: Database, Auth, AI and Automations](https://uvilno.com/docs): Use Uvilno.db, auth, AI and transactional automations in generated apps. Read schema examples, exact API methods, context mentions and export limitations. - [AI App Builder Benchmarks: Evidence and Evaluation Protocol](https://uvilno.com/benchmarks): Read six recorded Uvilno SDK checks and a downloadable 50-case comparison protocol. Unmeasured completion rates, quality scores and edit timings stay explicit. ## Hub resources - [Compare AI builders](https://uvilno.com/compare): Compare workflows, source portability, hosted services and published costs using cited vendor documentation. - [AI builder alternatives](https://uvilno.com/alternatives): Find alternatives to Base44, Emergent, Lovable, Bolt.new, v0, Replit, Cursor, Framer and Webflow by workflow and portability. - [What to build with Uvilno](https://uvilno.com/build): Explore practical website and full-stack app briefs, route plans, database interactions and service requirements. - [Uvilno field notes](https://uvilno.com/guides): Practical guides to planning, refining, testing, exporting and maintaining AI-built websites and applications. - [Remixable full-stack app blueprints](https://uvilno.com/templates): Explore authored multi-page app concepts, declared data fields and editable build briefs, plus explicitly published community templates. - [Direct answers about AI app builders](https://uvilno.com/answers): Find sourced answers about app data, authentication, ownership, pricing, migration and verification before choosing an AI builder. - [Free AI app planning tools](https://uvilno.com/tools): Calculate published plan costs, assemble a full-stack engineering prompt and plan a platform migration without a model request. - [Full-stack AI app prompt library](https://uvilno.com/prompts): Browse 108 editable briefs with route plans, declared data, interaction checks and specific visual direction. Prepare a prompt before building. ## Comparison resources - [Uvilno vs Emergent](https://uvilno.com/compare/uvilno-vs-emergent): Compare Uvilno and Emergent for database-backed apps, isolated accounts, multi-file editing, source ownership and separately budgeted deployment. - [Uvilno vs Lovable](https://uvilno.com/compare/uvilno-vs-lovable): Uvilno vs Lovable: compare typed app data, built-in AI, source access, Git sync, credit billing and backend portability using current official documentation. - [Uvilno vs Base44](https://uvilno.com/compare/uvilno-vs-base44): Uvilno vs Base44: compare typed app data, auth, built-in AI, workflows, GitHub source handoff and the difference between a $4.99 unlock and recurring app hosting. - [Uvilno vs Bolt.new](https://uvilno.com/compare/uvilno-vs-bolt): Compare Uvilno and Bolt.new across 24 practical criteria: app data, source handoff, token usage, hosting, integrations and annual budget assumptions. - [Uvilno vs v0](https://uvilno.com/compare/uvilno-vs-v0): Uvilno vs v0 by Vercel: compare website source unlocks with framework-led app development, GitHub, deployment and current per-user pricing. - [Uvilno vs Replit Agent](https://uvilno.com/compare/uvilno-vs-replit-agent): Compare Uvilno's website source workflow with Replit Agent's development workspace, effort-based AI billing and hosted application infrastructure. - [Uvilno vs Cursor](https://uvilno.com/compare/uvilno-vs-cursor): Compare Uvilno with Cursor for website projects: visual review versus developer-led code work, current plan pricing and independent hosting responsibilities. - [Uvilno vs Framer](https://uvilno.com/compare/uvilno-vs-framer): Uvilno vs Framer: compare conversational website source exports with a visual design canvas, hosted CMS workflow and current annual site-plan pricing. - [Uvilno vs Webflow](https://uvilno.com/compare/uvilno-vs-webflow): Compare Uvilno and Webflow across site publishing, CMS, code export, workspace versus site billing, and practical source portability limits. - [Best AI website builders in 2026: a practical buyer's guide](https://uvilno.com/compare/best-ai-website-builders-2026): Compare ten website and app-building options across 24 documented architecture, source ownership and pricing criteria, including Base44. Published by Uvilno with official sources. - [Emergent vs Lovable (2026): backend, billing and code ownership](https://uvilno.com/compare/emergent-vs-lovable): Compare Emergent and Lovable for hosted app infrastructure, usage accounting, Git handoff and team review, with Uvilno as a source-unlock alternative. - [Lovable vs Bolt.new (2026): cloud, credits and source handoff](https://uvilno.com/compare/lovable-vs-bolt): Understand Lovable's managed backend and unified credits alongside Bolt Cloud, token allowances and code workflows; compare Uvilno's separate source entitlement. - [Base44 vs Lovable (2026): managed data and code portability](https://uvilno.com/compare/base44-vs-lovable): Compare Base44 and Lovable backend models, source and data exports, visitor accounts and migration work, with Uvilno's $4.99 source option alongside. - [Emergent vs Base44 (2026): application workflow and backend handoff](https://uvilno.com/compare/emergent-vs-base44): Compare Emergent and Base44 for agent-led development, managed records, app permissions and a realistic ownership handoff, including the Uvilno alternative. - [Emergent vs Bolt.new (2026): runtime, usage and multi-page review](https://uvilno.com/compare/emergent-vs-bolt): Compare Emergent and Bolt.new runtime choices, managed services, subscription allowances and multi-page acceptance tasks, with Uvilno as a third option. - [Bolt.new vs v0 (2026): app runtime, backend and Git workflow](https://uvilno.com/compare/bolt-vs-v0): Compare Bolt Cloud with v0's Vercel and Git workflow across runtime, integrations and usage; include Uvilno's source-unlock model without an invented ranking. - [Replit Agent vs Lovable (2026): hosted apps, usage and ownership](https://uvilno.com/compare/replit-agent-vs-lovable): Compare Replit Agent and Lovable for project development, managed backend services, allowance controls and source handoff, plus Uvilno's per-project unlock. - [Cursor vs Lovable vs Uvilno (2026): choose the development workflow](https://uvilno.com/compare/cursor-vs-lovable): Compare Cursor's repository-oriented workflow with Lovable's hosted app platform and Uvilno's chat, preview, managed-data and source-unlock contract. ## Alternative resources - [Emergent alternatives](https://uvilno.com/alternatives/emergent): Explore alternatives to Emergent by project fit, source portability and operating costs, including where Uvilno makes sense. - [Lovable alternatives](https://uvilno.com/alternatives/lovable): Explore alternatives to Lovable by project fit, source portability and operating costs, including where Uvilno makes sense. - [Base44 alternatives](https://uvilno.com/alternatives/base44): Explore alternatives to Base44 by project fit, source portability and operating costs, including where Uvilno makes sense. - [Bolt.new alternatives](https://uvilno.com/alternatives/bolt): Explore alternatives to Bolt.new by project fit, source portability and operating costs, including where Uvilno makes sense. - [v0 alternatives](https://uvilno.com/alternatives/v0): Explore alternatives to v0 by project fit, source portability and operating costs, including where Uvilno makes sense. - [Replit Agent alternatives](https://uvilno.com/alternatives/replit): Explore alternatives to Replit Agent by project fit, source portability and operating costs, including where Uvilno makes sense. - [Cursor alternatives](https://uvilno.com/alternatives/cursor): Explore alternatives to Cursor by project fit, source portability and operating costs, including where Uvilno makes sense. - [Framer alternatives](https://uvilno.com/alternatives/framer): Explore alternatives to Framer by project fit, source portability and operating costs, including where Uvilno makes sense. - [Webflow alternatives](https://uvilno.com/alternatives/webflow): Explore alternatives to Webflow by project fit, source portability and operating costs, including where Uvilno makes sense. ## Builder resources - [Full-Stack AI App Builder with Managed Data and Auth](https://uvilno.com/build/full-stack-ai-app-builder): Build multi-page apps with typed collections, isolated visitor accounts, transactional automations and real in-app AI. Review the architecture before launch. - [A Base44 and Emergent Alternative with Source Export](https://uvilno.com/build/base44-and-emergent-alternative): Evaluate Uvilno for multi-page managed-data apps, focused edits and a $4.99 permanent project source unlock. Compare service dependencies before switching. - [AI CRM and Internal Tool Builder with Persistent Records](https://uvilno.com/build/ai-crm-and-internal-tool-builder): Build a focused CRM, record manager or operational dashboard with typed fields, real CRUD and inspectable automation activity. Keep authorization explicit. - [AI Wrapper and Micro-SaaS Builder with Real In-App AI](https://uvilno.com/build/ai-wrapper-and-micro-saas-builder): Build a narrow AI product using real Uvilno.ai inference, private saved results and explicit usage controls. Prototype checkout in Stripe test mode. - [AI Website Builder for Real Multi-page Sites](https://uvilno.com/build/ai-website-builder): Plan a useful multi-page website, refine it in chat, and review an isolated live preview. Start with three editable business website briefs. - [AI SaaS Builder — Scope Your First Product](https://uvilno.com/build/ai-saas-builder): Plan a focused SaaS interface with accounts, a core record workflow, and clear service boundaries. Explore three editable product briefs. - [AI Web App Builder for Focused Workflows](https://uvilno.com/build/ai-web-app-builder): Turn a workflow into real routes, usable states, and an explicit data plan. Start an AI web app with one of three editable briefs. - [AI Browser Game Builder — Playable Game Briefs](https://uvilno.com/build/ai-browser-game-builder): Scope a playable browser game with real controls, restart states, and honest persistence limits. Explore three editable game briefs. - [AI Stripe Ecommerce Store Builder — Test-mode Plans](https://uvilno.com/build/ai-stripe-ecommerce-store-builder): Plan product pages, cart states, and a Stripe test checkout with clear commerce limitations. Start from three editable store briefs. - [AI Landing Page Generator for a Focused Offer](https://uvilno.com/build/ai-landing-page-generator): Build a campaign page around one audience and one action. Use editable launch, waitlist, and service-offer briefs with real form states. - [AI Portfolio Website Builder for Selected Work](https://uvilno.com/build/ai-portfolio-website-builder): Create a portfolio with project detail routes, image-led storytelling, and useful enquiry flows. Edit three briefs for different creative practices. - [AI Architecture Studio Website Builder](https://uvilno.com/build/ai-architecture-studio-website-builder): Plan an architecture studio website around projects, drawings, material context, and enquiries. Use three editable practice-specific briefs. - [AI Restaurant and Bakery Website Builder](https://uvilno.com/build/ai-restaurant-and-bakery-website-builder): Build a useful restaurant or bakery site with readable menus, real opening information, and clear enquiry routes. Explore three editable briefs. - [AI Dental and Medical Clinic Website Builder](https://uvilno.com/build/ai-dental-and-medical-clinic-website-builder): Plan a clinic information website with service pages, practitioner details, and cautious enquiry forms. Start with three editable non-clinical briefs. - [AI Real Estate Website Builder for Property Portfolios](https://uvilno.com/build/ai-real-estate-website-builder): Plan property detail pages, useful filters, and genuine viewing enquiries without implying a live listing feed. Explore three editable real estate briefs. - [AI Fintech Dashboard Builder for Product Prototypes](https://uvilno.com/build/ai-fintech-dashboard-builder): Prototype a financial interface with labelled sample data, explicit calculation rules, and honest connection states. Edit three focused dashboard briefs. - [AI Agency Website Builder for Clear Positioning](https://uvilno.com/build/ai-agency-website-builder): Build an agency site around a defined offer, credited case studies, and qualified enquiries. Explore three editable agency briefs. - [AI Directory and Marketplace Builder — Define the Scope](https://uvilno.com/build/ai-directory-and-marketplace-builder): Plan a directory with real filters, useful listing pages, and honest marketplace boundaries. Edit three distinct catalog and listing briefs. - [HTML, CSS and JavaScript AI Code Generator](https://uvilno.com/build/html-css-js-code-generator): Scope portable static pages and browser interactions with a practical AI code-generation brief. Review previews before unlocking source export. - [Next.js and Tailwind AI Builder for Multi-file Projects](https://uvilno.com/build/nextjs-tailwind-ai-builder): Plan a modular Next.js and Tailwind build with real routes, interaction states, and export boundaries. Explore three editable developer briefs. - [AI Internal Tool Builder for a Bounded Workflow](https://uvilno.com/build/ai-internal-tool-builder): Plan an internal tool with clear records, useful tables, and explicit permission limits. Start with three editable operations briefs. - [AI Calculator Builder with Transparent Assumptions](https://uvilno.com/build/ai-calculator-builder): Build an interactive calculator from rules you supply, with accessible inputs and visible assumptions. Edit three practical browser-tool briefs. - [AI Event Website Builder for Clear Attendee Information](https://uvilno.com/build/ai-event-website-builder): Plan an event site with real schedule routes, speaker information, and honest registration handoffs. Edit three event-specific starter briefs. - [AI Nonprofit Website Builder for Programs and Action](https://uvilno.com/build/ai-nonprofit-website-builder): Build a nonprofit information site with clear programs, supported impact claims, and genuine volunteer or donation handoffs. Edit three starter briefs. - [AI Educational Website Builder for Lessons and Resources](https://uvilno.com/build/ai-educational-website-builder): Plan a learning resource with lesson routes, accessible exercises, and honest progress limits. Start with three editable educational briefs. - [AI Local Services Website Builder for Genuine Enquiries](https://uvilno.com/build/ai-local-services-website-builder): Build a local service website with verified coverage, practical service pages, and honest quote enquiries. Edit three useful starter briefs. - [AI Documentation Website Builder for Clear Product Guides](https://uvilno.com/build/ai-documentation-website-builder): Plan product documentation with real navigation, readable examples, and explicit search limits. Edit three documentation-specific starter briefs. - [AI Community Website Builder for Programs and Resources](https://uvilno.com/build/ai-community-website-builder): Plan a community information hub with useful resources, event routes, and explicit membership boundaries. Explore three editable community briefs. ## Guide resources - [Build a Full-Stack SaaS with Database, Auth and a Tested User Journey](https://uvilno.com/guides/how-to-build-a-full-stack-saas-with-database-and-auth): Plan typed records, isolated accounts, real CRUD, transactional automations and optional AI in Uvilno. Verify persistence and payment boundaries before launch. - [Base44 vs Emergent vs Lovable vs Uvilno: Choose the Full-Stack Workflow](https://uvilno.com/guides/base44-vs-emergent-vs-lovable-vs-uvilno): Compare four app-building workflows through data ownership, authentication, focused edits, inference, exports and operating costs. Separate published features from tested outcomes. - [7 Full-Stack AI App Builders in 2026: Data, Auth and Source Compared](https://uvilno.com/guides/best-full-stack-ai-app-builders-2026): Evaluate Uvilno, Lovable, Base44, Emergent, Bolt.new, Replit Agent and v0 against a real application checklist, with published sources and explicit evidence limits. - [How to build a website with AI, from brief to launch](https://uvilno.com/guides/how-to-build-a-website-with-ai): Turn a real business brief into a useful website. Plan the pages, review the preview, make focused edits, and prepare a source export. - [How to export and host your AI website](https://uvilno.com/guides/how-to-export-and-host-your-ai-website): Move a Uvilno project to a static host with its assets intact. Understand source unlocks, export formats, connected services, domains, and launch testing. - [Compare Emergent, Lovable, Bolt, and Uvilno using one brief](https://uvilno.com/guides/emergent-vs-lovable-vs-bolt-vs-uvilno): A practical comparison method for AI builders: use the same requirements, test real interactions, record usage, and check source portability before choosing. - [How to add Stripe test payments without pasting API keys](https://uvilno.com/guides/how-to-add-stripe-payments-without-api-keys): Build a real Stripe test-checkout flow with Uvilno's managed connection, understand Connect authorization, and prepare the separate work required for live payments. - [How to build a playable browser game with AI](https://uvilno.com/guides/how-to-build-a-playable-browser-game-with-ai): Specify a real game loop, responsive controls, fair rules, and browser-local progress. Measure performance and test playability before sharing. - [A practical prompt engineering guide for AI website builders](https://uvilno.com/guides/ai-website-builder-prompt-engineering-guide): Write briefs that describe purpose, pages, state, behavior, and design. Use examples and acceptance checks to make revisions easier to verify. - [Understand credits and usage before choosing an AI builder](https://uvilno.com/guides/why-credit-based-ai-builders-rip-you-off): Read AI-builder allowances without guesswork. Separate processing, project unlocks, downloads, refills, and external costs, then estimate a useful plan. - [How to add Google and Discord login to an AI website](https://uvilno.com/guides/how-to-add-google-and-discord-login-to-ai-websites): Plan hosted app sign-in, private records, account states, and export-origin setup. Keep OAuth on trusted pages and generated code inside its preview boundary. - [Plan a multi-page AI application before you build](https://uvilno.com/guides/planning-a-multi-page-ai-application): Map routes, user journeys, state ownership, service dependencies, and acceptance checks so a multi-page app is more than linked mock screens. - [Make precise visual website edits with AI](https://uvilno.com/guides/visual-website-editing-with-ai): Use element selection, screenshots, and focused instructions to change layout and copy without losing the parts of your website that already work. - [Make an AI-generated website more accessible](https://uvilno.com/guides/accessible-ai-generated-websites): Review keyboard access, semantics, contrast, forms, motion, and responsive behavior with concrete checks that go beyond a polished screenshot. - [Use GitHub sync and saved versions without losing your work](https://uvilno.com/guides/github-sync-and-version-recovery): Understand GitHub authorization, imports, source-gated publishing, conflict review, saved-version restoration, and unfinished-build recovery in Uvilno. ## Legal resources - [Terms of service](https://uvilno.com/terms): Terms governing Uvilno accounts, usage, source exports and supported services. - [Privacy policy](https://uvilno.com/privacy): How Uvilno handles account, project, billing and service data. - [Refund policy](https://uvilno.com/refund): Uvilno’s source-unlock and subscription refund terms. ## Resource resources - [Uvilno Full-Stack AI Builder Feed](https://uvilno.com/feed.xml): RSS updates for authored comparisons, guides, answers and app blueprints, with WebSub discovery. - [Uvilno AI reference directory](https://uvilno.com/llms.txt): Public product facts, pricing and canonical resources for agents and readers. - [Uvilno complete AI reference](https://uvilno.com/llms-full.txt): Expanded public guides, comparison facts, service limits and source citations. - [AI app builder capabilities and recorded checks](https://uvilno.com/ai-benchmarks.json): Machine-readable vendor sources, prices, nullable feature flags and recorded Uvilno integration checks. - [Recorded checks and planned evaluation cases: CSV](https://uvilno.com/benchmarks-2026.csv): Download six recorded Uvilno checks and 50 unexecuted comparative build cases, with missing measurements explicitly blank. ## Template resources - [Meridian CRM](https://uvilno.com/templates/full-stack-crm): A relationship-led sales workspace with contact records, deal stages, follow-up tasks and an auditable activity view. - [Margin Career Studio](https://uvilno.com/templates/ai-resume-analyzer): A resume-review product plan with saved analyses, career goals and a real managed AI integration after building. - [Object Supply](https://uvilno.com/templates/stripe-commerce-store): A considered storefront with product filtering, a persistent local concept cart and an inventory/admin build contract. - [Aster Appointment Desk](https://uvilno.com/templates/medical-booking-portal): An appointment-request portal blueprint with account pages, practitioner discovery and deliberately minimal non-clinical records. - [Emberline Arcade](https://uvilno.com/templates/survival-arcade-game): A playable local survival exercise and a multi-page game blueprint with personal runs, cosmetics and a reviewed leaderboard contract. - [Found Residence](https://uvilno.com/templates/real-estate-marketplace): A property discovery and saved-listing blueprint with a working mortgage estimate and private enquiry records. - [Ember & Rye Orders](https://uvilno.com/templates/bakery-ordering-system): A bakery counter and ordering-plan blueprint with product choices, order records and a real queue interface concept. - [Atelier Fieldwork](https://uvilno.com/templates/architecture-monograph): An architectural project archive with a light-study control, materials library and commission enquiry plan. - [Relay Project Space](https://uvilno.com/templates/project-management-saas): A multi-project task workspace with private records, status filtering, accountable milestones and project activity. - [Tempo Training](https://uvilno.com/templates/fitness-coaching-app): A personal training planner with session records, exercise notes and a coach-discovery workflow. - [Common Ground Learning](https://uvilno.com/templates/course-learning-portal): A course catalog and personal learning plan with saved lessons, study notes and honest completion states. - [Table Twelve](https://uvilno.com/templates/restaurant-reservation-app): A restaurant enquiry and table-planning blueprint with a visible request queue and account-safe preferences. - [Good Company Studio](https://uvilno.com/templates/creator-membership-hub): A creator resource library, saved reading list and membership-interest workflow with isolated account planning. - [Ledger Personal](https://uvilno.com/templates/finance-budget-dashboard): A private household planning tool with a working projection, category records and transparent assumptions. - [Interval Support Desk](https://uvilno.com/templates/help-desk-support-tool): A ticket triage app plan with statuses, response notes and scoped activity records. - [Assembly Calendar](https://uvilno.com/templates/event-registration-hub): An event discovery and registration-interest plan with saved sessions and clear capacity checks. - [Stockroom Operations](https://uvilno.com/templates/inventory-purchasing-dashboard): An inventory and restock workspace with quantity fields, product filtering and a purchase-request queue. - [Kit Library](https://uvilno.com/templates/rental-equipment-booking): An equipment catalog and hire-request tool with date preferences, saved kits and availability boundaries. - [Footnote Research](https://uvilno.com/templates/ai-research-workspace): A research-note and source-review app plan with saved questions and a real opt-in managed AI summary contract. - [Caretaker Portal](https://uvilno.com/templates/property-maintenance-portal): A property maintenance-request workspace with issue status, property records and non-sensitive resident notes. - [Open Practice Jobs](https://uvilno.com/templates/job-board-marketplace): A focused job directory and saved-opportunity workspace with application-interest records. - [Runner Dog Game](https://uvilno.com/templates/community/untitled-project-ea376581aca1bcf31b): A simple browser game ## Answer resources - [Can you export source code from Base44?](https://uvilno.com/answers/can-you-export-source-code-from-base44): Base44 documents source ownership and GitHub export; it does not universally lock away code. Uvilno offers a different purchase: a permanent $4.99 source unlock for one project. In both products, exported frontend code and an independently migrated database, authentication service and… - [Why can AI builder bug fixes consume tokens?](https://uvilno.com/answers/why-does-bolt-new-burn-tokens-on-bug-fixes): AI bug fixes can consume model context and generated output, including unsuccessful attempts. This does not establish that every Bolt build wastes tokens. Uvilno separates metered edits from mapped direct edits and a bounded, platform-funded repair path for reproduced runtime faults in… - [How should Emergent's app cost be compared with Uvilno?](https://uvilno.com/answers/emergent-sh-pricing-and-credit-burn-explained): Emergent publishes subscription credits and separate deployment considerations; a project's cost depends on usage and services. Uvilno's $4.99 purchase unlocks one project's source, not unlimited generation or annual hosting. Compare subscriptions, extra model usage, deployment,… - [Does Lovable require manual Supabase setup for every app?](https://uvilno.com/answers/lovable-dev-supabase-setup-vs-uvilno-built-in-database): Lovable offers Cloud backend services, so Supabase setup is not required for every Lovable app. Uvilno uses schema-declared managed collections through Uvilno.db and a visual App Data manager. Compare ownership rules, supported queries, service limits and migration requirements rather… - [Which AI app builder fits a database and authentication project?](https://uvilno.com/answers/best-ai-app-builder-with-database-and-authentication): The choice depends on the data model, authorization and deployment requirements. Uvilno provides typed managed collections and project-isolated visitor identities, with configured OAuth providers and email accounts. Validate persistence, ownership and unsupported integrations in a… - [Can Uvilno source access be purchased without a monthly subscription?](https://uvilno.com/answers/best-ai-website-builder-without-monthly-subscription): Uvilno offers a $0 tier and a $4.99 one-time source unlock for one project, without requiring a subscription for that entitlement. Included generation is finite. Ongoing hosting, domains, model usage and hosted backend dependencies are separate; source ownership does not eliminate… - [How can an AI micro-SaaS use Uvilno's managed integrations?](https://uvilno.com/answers/how-to-build-an-ai-micro-saas-with-stripe-and-no-api-keys): Uvilno can connect app features to owner-funded Uvilno.ai inference, project accounts, managed records and configured Stripe test Checkout. The visitor need not receive provider keys. Live monetization still requires an enabled production payment setup, onboarding, usage budgeting and… - [What should be tested in an AI-built browser game?](https://uvilno.com/answers/best-ai-builder-for-html5-browser-games): Evaluate controls, collision behavior, score persistence and frame time on the target device. Uvilno supports browser games, Canvas, WebGL and its game runtime, but no universal 60fps guarantee follows. A shared leaderboard also needs scoped storage and abuse controls; a local score is… - [How does Uvilno's declarative database work?](https://uvilno.com/answers/how-does-uvilno-declarative-database-work): Uvilno declares collections, typed fields, references and optional rules in data/schema.json. Generated interfaces call Uvilno.db for hosted CRUD, and the creator inspects rows through App Data. The schema is validated with the saved version; it is not permission to execute arbitrary… - [How can saved app records be verified after reload?](https://uvilno.com/answers/do-generated-app-records-survive-reload): A saved record should be retrieved from the hosted service after navigation or reload, using the same authorized app identity. Uvilno.db provides that persistence for declared collections. A toast, optimistic update or localStorage mirror alone is insufficient evidence; inspect App… - [Does the Admin preview persona grant real permissions?](https://uvilno.com/answers/does-admin-preview-grant-real-permissions): Uvilno's Guest, Member and Admin preview selector changes presentation only. It can reveal declared role-specific views, but cannot alter the app visitor's identity, database ownership or server permissions. Administrative authorization must be implemented and verified; hidden controls… - [Is generated-app login separate from Uvilno's creator account?](https://uvilno.com/answers/is-generated-app-login-isolated-from-builder): Uvilno's app authentication uses project-scoped visitor identities and sessions, separate from the creator's platform login. Configured Google, GitHub, Discord and email flows must not replace builder cookies. Verify both identities around sign-in, sign-out and reload; a separate login… - [Does Uvilno.ai perform real inference?](https://uvilno.com/answers/does-uvilno-in-app-ai-use-real-inference): Uvilno.ai.ask and Uvilno.ai.json call a project-authorized server proxy for real configured model inference. They are not canned successful responses. Requests use the creator's finite allowance, have admission limits and a 600-output-token ceiling, and require the managed AI… - [Is a JSON description the same as schema validation?](https://uvilno.com/answers/is-ai-json-output-schema-validated): Uvilno.ai.json parses a bounded JSON object or array and rejects unsafe structures, but a schema description is not domain validation. Generated applications must check required fields, types and permitted values before rendering or saving results. Treat every model response as… - [What happens if a database automation fails?](https://uvilno.com/answers/how-do-transactional-app-automations-work): Uvilno's schema-declared database automations run in the record transaction with the same owner scope. A failed action rolls back the write and its effects. Idempotent retries avoid duplicated actions, and rules do not recursively trigger rules or execute uploaded JavaScript, external… - [Where can creators inspect automation activity?](https://uvilno.com/answers/where-to-inspect-automation-logs): Open App Data in Uvilno's builder and select Automations & Logs. The view shows installed rules and committed event metadata with bounded refresh. It does not expose project source or private record bodies, and an activity entry does not prove an external service was executed. - [How do file and database mentions target an edit?](https://uvilno.com/answers/how-to-use-file-and-database-context-mentions): Typing @ in Uvilno's builder opens page, file and collection suggestions. Choose references such as @index.html or @db:tasks, or use an inspector-provided @selected-element. These references guide private source retrieval for a focused edit; they do not expose locked code or guarantee… - [What does Uvilno's repository map contribute to edits?](https://uvilno.com/answers/what-does-a-project-repo-map-do): Uvilno maintains an inventory of project files, routes and module relationships to guide context retrieval. The model receives affected source rather than rewriting everything. Repository awareness improves targeting, but cannot prove an edit correct; compilation, behavioral checks and… - [Which visual edits use no model usage?](https://uvilno.com/answers/which-visual-edits-use-no-ai-usage): Uvilno's Inspect & Edit controls can change text, links and colors without a model request. Targeted AI instructions are a metered action. Direct edits require ownership, compatible source mapping and saved-version checks; the control is not an unrestricted browser DOM mutation or… - [Is Uvilno's automatic repair unlimited?](https://uvilno.com/answers/is-automatic-repair-always-free-and-unlimited): Uvilno's platform-funded repair is limited to native static-project faults reproduced by server-side browser checks. It has per-version, project and owner admission limits and a bounded free-model response. Ordinary edits and broader repairs remain metered, and failed recovery… - [Can a long build resume after an interruption?](https://uvilno.com/answers/can-a-failed-long-build-be-resumed): Uvilno preserves completed-file checkpoints and supports viewing an unfinished draft or continuing the brief after interruption. The verified version remains separate. Recovery has retention and execution limits, and a checkpoint is not a verified application; inspect its status before… - [How should a twenty-page application be planned?](https://uvilno.com/answers/how-to-plan-a-twenty-page-ai-application): Define the navigation, route purposes, data contract and user journeys before generating twenty screens. Uvilno's contract-first pipeline and contextual retrieval support modular projects, but every route still needs checks. Build a vertical slice first, preserve components and expand… - [Does a Next.js source export include a managed backend?](https://uvilno.com/answers/does-nextjs-export-include-a-managed-backend): A Next.js source export provides project files and build instructions, not ownership of each service it calls. Uvilno's framework output uses a static-export contract. Managed identity, collections, AI and payments remain configured dependencies; arbitrary Server Actions or dynamic… - [What does the $4.99 Uvilno source unlock include?](https://uvilno.com/answers/what-does-the-499-source-unlock-include): The $4.99 one-time unlock permanently grants source access for one Uvilno project. Exports include runtime-appropriate files, referenced uploads, bundled fonts and licenses; eligible projects also support static output. It does not buy unlimited generation, hosting, domains, customer… - [How do Plus and Pro differ for multiple projects?](https://uvilno.com/answers/uvilno-plus-vs-pro-for-multiple-projects): Uvilno Plus costs $10 per month with capacity and two project source unlocks per paid period. Pro costs $20 per month with 2.5 times Plus capacity and unlimited project unlocks during the subscription. Neither plan means unlimited generation; unlocked projects retain their permanent… - [When does Uvilno Ultra fit a workflow?](https://uvilno.com/answers/when-does-uvilno-ultra-make-sense): Uvilno Ultra costs $59 per month, includes five times Pro's capacity and unlimited source unlocks during the paid period. It suits heavier iteration needs, not a guarantee of unlimited builds or flawless output. Priority model routing remains subject to availability, scheduling,… - [What does 100% remaining usage mean?](https://uvilno.com/answers/what-does-100-percent-remaining-usage-mean): Uvilno displays capacity as 100% remaining down to 0%, with the reset information. Model-backed planning, generation and refinements consume allowance. Source entitlements and downloads are separate. Preview viewing or naming a draft does not initiate a build, and unlimited unlocks do… - [Can the current Stripe connector accept live payments?](https://uvilno.com/answers/can-uvilno-stripe-checkout-accept-live-payments): Uvilno's Stripe Connect and Checkout workflows use test mode. They verify a payment journey without taking money. Live payments require an enabled configuration, provider onboarding and verified fulfillment behavior. A test checkout must never be displayed as actual revenue, settlement… - [What should be checked before using GitHub sync?](https://uvilno.com/answers/how-does-two-way-github-sync-work): Uvilno supports GitHub import, source push and pull for frontends; source pushes require project entitlement. Repository access does not migrate customer records or grant unrelated account permissions. Check the repository, branch, changes and conflict behavior before synchronizing,… - [Does importing source migrate customer data and passwords?](https://uvilno.com/answers/can-customer-data-move-between-ai-builders): Importing source or a GitHub repository moves code, not customer records, identities, passwords, payment history or service credentials. Uvilno requires an authorized migration plan for those systems. Preserve ownership, consent and field mappings, and test a sample before changing an… - [Can an exported app run without Uvilno's hosted services?](https://uvilno.com/answers/can-an-export-run-without-uvilno-services): A static frontend can run on compatible hosting, but an app using Uvilno-managed auth, data, AI or payments calls those services unless they are replaced. Source ownership allows adaptation; it does not recreate infrastructure. Inspect the dependency inventory and verify the host… - [What does a public app blueprint demonstrate?](https://uvilno.com/answers/are-public-templates-real-customer-apps): A blueprint demonstrates a structure, routes, data fields and interactions, not proof that a customer app is deployed or benchmarked. Uvilno distinguishes examples from consented community projects. Review the preview's data and service labels, then prepare a brief rather than assuming… - [What is safe to prototype in a medical booking site?](https://uvilno.com/answers/can-ai-build-a-medical-booking-portal): Prototype service information and an appointment-interest journey before handling medical records. Uvilno's managed collections do not establish healthcare compliance or suitability. Do not collect patient histories, diagnoses or sensitive documents without a separately reviewed… - [What makes an AI builder benchmark credible?](https://uvilno.com/answers/how-to-read-ai-builder-benchmark-claims): A benchmark states the prompts, tool versions, model settings, attempts, costs, runtime checks and limitations, and publishes results. Uvilno's SDK and recovery checks do not establish a fifty-build contest or winner. Unmeasured completion rates, edit latency and competitor scores… - [Will AI-generated pages automatically rank first in search?](https://uvilno.com/answers/will-ai-generated-pages-rank-first-on-google): No builder can guarantee first place, indexing or AI citation for every query. Uvilno supports pages, metadata and exports, but search visibility depends on accessible content and search-engine decisions. Verify canonicals, links and crawl access, publish information, and treat sitemap… - [Who funds AI requests inside a generated app?](https://uvilno.com/answers/who-pays-for-generated-app-ai-requests): Managed Uvilno.ai requests consume the creator's studio allowance, subject to visitor, IP, project and owner admission limits. Each response is capped at 600 output tokens. An AI feature therefore needs a product scope and failure states; it is not an unlimited model endpoint for visitors. - [Does copying a website's style migrate its application?](https://uvilno.com/answers/can-website-style-copying-migrate-an-app): A reference can guide typography, layout and interaction direction, but cannot migrate source, customer data, credentials or business processes. Uvilno's style-reference and import workflows serve different purposes. Use only material you may provide, describe the behavior and verify… - [Does restoring a website version rewind customer data?](https://uvilno.com/answers/does-rollback-restore-customer-database): Restoring a Uvilno website version restores its preview and design snapshot; it does not rewind customer records or completed external operations. Review schema compatibility before rollback. Keep a data recovery plan, and never assume a visual version selector reverses payments,… - [Where does generated-app media storage live?](https://uvilno.com/answers/are-uploaded-app-media-files-stored-on-server): Uvilno's generated-app storage helper keeps visitor media on the device; it is distinct from creator-uploaded project assets and hosted collection records. An avatar does not prove a server upload or cross-device backup. Specify the storage boundary and test another device before… - [How do public catalogs differ from private visitor records?](https://uvilno.com/answers/can-generated-apps-use-public-shared-records): Uvilno distinguishes private visitor-owned collection rows from public-read catalog data. Public reading does not grant writing, and an Admin view cannot override ownership. Choose the access contract, test separate identities and avoid placing sensitive information into a shared… - [What must an AI-generated CRM prove before launch?](https://uvilno.com/answers/how-to-verify-ai-crm-before-launch): A CRM must prove records, references, ownership, filters and failure states, not just charts. Uvilno can supply typed collections, real CRUD and transactional activity rules. Test one complete customer-to-task workflow with separate visitors, reloads and conflicting edits before… - [Should saying thanks change project files?](https://uvilno.com/answers/can-a-chat-message-change-files-accidentally): A conversational acknowledgment should not initiate generation, modify files or consume model allowance. Uvilno routes replies separately from build and edit requests. Ambiguous instructions still need clear intent, so describe the change explicitly and inspect the run state rather… ## Tool resources - [AI builder cost calculator](https://uvilno.com/tools/ai-builder-cost-calculator): Compare published annual plan and source-access costs, add your own usage and hosting budget, and inspect every assumption before choosing an AI builder. - [Free full-stack prompt architect](https://uvilno.com/tools/full-stack-prompt-architect): Turn an app idea into an editable multi-page brief with typed collections, real interactions, account boundaries and integration checks without an AI request. - [AI builder migration checker](https://uvilno.com/tools/competitor-migration-checker): Plan a move from Base44, Emergent, Lovable, Bolt.new, Replit or v0. Separate transferable source from records, identities, secrets and hosted services. ## Prompt resources - [Sales pipeline CRM](https://uvilno.com/prompts/sales-pipeline-crm): Help an independent consultant move a qualified lead from first contact to a won or lost opportunity. Review the route plan, typed collections, design direction and acceptance checks before building. - [Client follow-up tracker](https://uvilno.com/prompts/client-follow-up-tracker): Keep the next promised action visible for each active client without inventing email delivery. Review the route plan, typed collections, design direction and acceptance checks before building. - [Creative agency project CRM](https://uvilno.com/prompts/creative-agency-project-crm): Give a small agency an honest view of project status, scope and pending decisions. Review the route plan, typed collections, design direction and acceptance checks before building. - [Freelance proposal manager](https://uvilno.com/prompts/freelance-proposal-manager): Organize proposal drafts and decisions without pretending to send documents or collect signatures. Review the route plan, typed collections, design direction and acceptance checks before building. - [Customer onboarding workspace](https://uvilno.com/prompts/customer-onboarding-workspace): Track a consultant's own onboarding checklists for new clients, with completion tied to actual task records. Review the route plan, typed collections, design direction and acceptance checks before building. - [Account renewal calendar](https://uvilno.com/prompts/account-renewal-calendar): Help a service operator see upcoming contract reviews without claiming automated renewals or live billing. Review the route plan, typed collections, design direction and acceptance checks before building. - [Service request CRM](https://uvilno.com/prompts/service-request-crm): Collect and manage private service requests with a clear distinction between requested and completed work. Review the route plan, typed collections, design direction and acceptance checks before building. - [Recruiting candidate tracker](https://uvilno.com/prompts/recruiting-candidate-tracker): Let an individual recruiter organize permission-cleared fictional candidate records without automated hiring decisions. Review the route plan, typed collections, design direction and acceptance checks before building. - [Partnership deal room](https://uvilno.com/prompts/partnership-deal-room): Track a business owner's partnership discussions, obligations and next decisions. Review the route plan, typed collections, design direction and acceptance checks before building. - [AI resume reviewer](https://uvilno.com/prompts/ai-resume-reviewer): Help a job seeker identify specific improvements in text they supply, without inventing qualifications or making hiring decisions. Review the route plan, typed collections, design direction and acceptance checks before building. - [AI study plan builder](https://uvilno.com/prompts/ai-study-plan-builder): Turn a learner's topic and available time into a short, editable study plan using actual model output. Review the route plan, typed collections, design direction and acceptance checks before building. - [AI meeting action extractor](https://uvilno.com/prompts/ai-meeting-action-extractor): Extract proposed actions only from supplied meeting notes and require user review before saving. Review the route plan, typed collections, design direction and acceptance checks before building. - [AI recipe notebook](https://uvilno.com/prompts/ai-recipe-notebook): Help a home cook draft recipes from supplied ingredients while stating that allergy and safety checks remain the user's responsibility. Review the route plan, typed collections, design direction and acceptance checks before building. - [AI product copy workbench](https://uvilno.com/prompts/ai-product-copy-workbench): Draft concise product copy from supplied facts without fabricating reviews, metrics, endorsements or availability. Review the route plan, typed collections, design direction and acceptance checks before building. - [AI language practice journal](https://uvilno.com/prompts/ai-language-practice-journal): Give a learner short feedback on their own writing, with transparent AI limitations and editable corrections. Review the route plan, typed collections, design direction and acceptance checks before building. - [AI support reply drafter](https://uvilno.com/prompts/ai-support-reply-drafter): Draft support responses from supplied issue details without claiming access to customer accounts or sending messages. Review the route plan, typed collections, design direction and acceptance checks before building. - [AI workout planning notebook](https://uvilno.com/prompts/ai-workout-planning-notebook): Help an adult organize general fitness ideas from supplied preferences without medical advice, diagnosis or injury guarantees. Review the route plan, typed collections, design direction and acceptance checks before building. - [AI research question organizer](https://uvilno.com/prompts/ai-research-question-organizer): Turn supplied research notes into proposed questions, preserving the distinction between evidence and model suggestions. Review the route plan, typed collections, design direction and acceptance checks before building. - [Ceramics test-checkout store](https://uvilno.com/prompts/ceramics-test-checkout-store): Let visitors explore a small studio's supplied ceramic pieces and test an explicitly non-live purchase journey. Review the route plan, typed collections, design direction and acceptance checks before building. - [Coffee subscription planner](https://uvilno.com/prompts/coffee-subscription-planner): Help a roastery customer compare supplied beans and plan a delivery cadence without claiming active recurring charges. Review the route plan, typed collections, design direction and acceptance checks before building. - [Independent bookshop catalog](https://uvilno.com/prompts/independent-bookshop-catalog): Make a supplied catalog easy to search, shortlist and evaluate before a test checkout. Review the route plan, typed collections, design direction and acceptance checks before building. - [Design object store](https://uvilno.com/prompts/design-object-store): Present supplied furniture and objects with useful dimensions, finish selections and clear test-mode commerce. Review the route plan, typed collections, design direction and acceptance checks before building. - [Digital resource test store](https://uvilno.com/prompts/digital-resource-test-store): Show original digital resources with license descriptions without fabricating download entitlements after test payment. Review the route plan, typed collections, design direction and acceptance checks before building. - [Skincare product information store](https://uvilno.com/prompts/skincare-product-information-store): Organize supplied cosmetic products and ingredient facts without medical claims or invented clinical results. Review the route plan, typed collections, design direction and acceptance checks before building. - [Art print edition store](https://uvilno.com/prompts/art-print-edition-store): Help an artist present supplied works, available sizes and edition information without inventing scarcity. Review the route plan, typed collections, design direction and acceptance checks before building. - [Local florist order request](https://uvilno.com/prompts/local-florist-order-request): Prepare a bouquet request from supplied options, with a test payment demonstration rather than confirmed fulfillment. Review the route plan, typed collections, design direction and acceptance checks before building. - [Storefront with inventory review](https://uvilno.com/prompts/inventory-admin-storefront): Give a creator a product catalog plus a reviewed management view, keeping actual authorization separate from a preview role. Review the route plan, typed collections, design direction and acceptance checks before building. - [Orbital survival arcade](https://uvilno.com/prompts/orbital-survival-arcade): Create a playable dodge-and-collect loop with keyboard and touch controls rather than a decorative game mockup. Review the route plan, typed collections, design direction and acceptance checks before building. - [Paddle breaker challenge](https://uvilno.com/prompts/paddle-breaker-challenge): Build a ball-and-paddle challenge whose win and loss conditions follow real collisions. Review the route plan, typed collections, design direction and acceptance checks before building. - [Top-down delivery racer](https://uvilno.com/prompts/top-down-delivery-racer): Create an original route-and-time game without real logistics or delivery claims. Review the route plan, typed collections, design direction and acceptance checks before building. - [Memory card garden](https://uvilno.com/prompts/memory-card-garden): Make an original matching game with deterministic pair logic and an understandable completion state. Review the route plan, typed collections, design direction and acceptance checks before building. - [Rhythm timing practice](https://uvilno.com/prompts/rhythm-timing-practice): Create a visual timing challenge using original or permission-cleared sound, with explicit user-enabled audio. Review the route plan, typed collections, design direction and acceptance checks before building. - [Grid puzzle expedition](https://uvilno.com/prompts/grid-puzzle-expedition): Build a grid-based puzzle with meaningful legal moves and a replayable level sequence. Review the route plan, typed collections, design direction and acceptance checks before building. - [Tower defense sketch](https://uvilno.com/prompts/tower-defense-sketch): Create a bounded original strategy game with enemies, a path and actual resource spending. Review the route plan, typed collections, design direction and acceptance checks before building. - [Typing focus arcade](https://uvilno.com/prompts/typing-focus-arcade): Build a practice game that scores the supplied text accurately without collecting sensitive keystrokes. Review the route plan, typed collections, design direction and acceptance checks before building. - [Mini-golf physics lab](https://uvilno.com/prompts/mini-golf-physics-lab): Create a small original physics challenge with aim, power and understandable stroke counting. Review the route plan, typed collections, design direction and acceptance checks before building. - [Dental appointment request portal](https://uvilno.com/prompts/dental-appointment-request-portal): Let a visitor request a consultation without collecting medical history or implying confirmed clinical availability. Review the route plan, typed collections, design direction and acceptance checks before building. - [Wellness class reservation planner](https://uvilno.com/prompts/wellness-class-reservation-planner): Organize supplied classes and visitor interest without representing unverified capacity as live. Review the route plan, typed collections, design direction and acceptance checks before building. - [Home repair service portal](https://uvilno.com/prompts/home-repair-service-portal): Help homeowners describe a non-emergency repair and track the request state. Review the route plan, typed collections, design direction and acceptance checks before building. - [Barber appointment request](https://uvilno.com/prompts/barber-appointment-request): Show supplied services and allow a preferred date and time request without claiming an active scheduling integration. Review the route plan, typed collections, design direction and acceptance checks before building. - [Photography session inquiries](https://uvilno.com/prompts/photography-session-inquiries): Let a photographer collect session preferences and review inquiries as actual saved records. Review the route plan, typed collections, design direction and acceptance checks before building. - [Equipment rental request portal](https://uvilno.com/prompts/equipment-rental-request-portal): Help visitors shortlist equipment and request a rental period while keeping availability subject to review. Review the route plan, typed collections, design direction and acceptance checks before building. - [Pet grooming request hub](https://uvilno.com/prompts/pet-grooming-request-hub): Collect a grooming service preference without veterinary advice or invented scheduling availability. Review the route plan, typed collections, design direction and acceptance checks before building. - [Tutoring session planner](https://uvilno.com/prompts/tutoring-session-planner): Let a learner request help by subject and review the planned sessions they own. Review the route plan, typed collections, design direction and acceptance checks before building. - [Event venue inquiry portal](https://uvilno.com/prompts/event-venue-inquiry-portal): Support a venue shortlist and date inquiry without claiming actual venue inventory or a reservation. Review the route plan, typed collections, design direction and acceptance checks before building. - [Architecture monograph library](https://uvilno.com/prompts/architecture-monograph-library): Present supplied architectural projects through a readable index and original project stories. Review the route plan, typed collections, design direction and acceptance checks before building. - [Industrial design process portfolio](https://uvilno.com/prompts/industrial-design-process-portfolio): Explain a designer's supplied research, prototypes and final objects without fabricated clients or awards. Review the route plan, typed collections, design direction and acceptance checks before building. - [Interior materials journal](https://uvilno.com/prompts/interior-materials-journal): Let visitors explore actual supplied interior studies and collect a private material shortlist. Review the route plan, typed collections, design direction and acceptance checks before building. - [Landscape studio project index](https://uvilno.com/prompts/landscape-studio-project-index): Show place, season and design intent using supplied landscape projects rather than generic scenery. Review the route plan, typed collections, design direction and acceptance checks before building. - [Brand studio case-study system](https://uvilno.com/prompts/brand-studio-case-study-system): Present supplied brand work with a clear brief, decision and result story without inventing performance metrics. Review the route plan, typed collections, design direction and acceptance checks before building. - [Furniture design collection](https://uvilno.com/prompts/furniture-design-collection): Explain original furniture pieces through material, dimension and process details, with no fake purchasing flow. Review the route plan, typed collections, design direction and acceptance checks before building. - [Photographic editorial archive](https://uvilno.com/prompts/photographic-editorial-archive): Organize permission-cleared image series and meaningful captions without copying another photographer's work. Review the route plan, typed collections, design direction and acceptance checks before building. - [Motion designer reel library](https://uvilno.com/prompts/motion-designer-reel-library): Make supplied reels and process notes easy to explore without autoplaying audible media. Review the route plan, typed collections, design direction and acceptance checks before building. - [Craft studio commission portfolio](https://uvilno.com/prompts/craft-studio-commission-portfolio): Connect supplied craft projects to a concise commission inquiry without promising availability or lead times. Review the route plan, typed collections, design direction and acceptance checks before building. - [Real estate shortlist app](https://uvilno.com/prompts/real-estate-shortlist-app): Help a buyer compare permission-cleared fictional properties and save private notes, without brokerage or valuation claims. Review the route plan, typed collections, design direction and acceptance checks before building. - [Local maker directory](https://uvilno.com/prompts/local-maker-directory): Help visitors discover supplied maker profiles and save a private set of references. Review the route plan, typed collections, design direction and acceptance checks before building. - [Remote job board workspace](https://uvilno.com/prompts/remote-job-board-workspace): Organize supplied job information and the visitor's own application tracker without claiming employer integrations. Review the route plan, typed collections, design direction and acceptance checks before building. - [Specialist consultant directory](https://uvilno.com/prompts/specialist-consultant-directory): Present approved consultant information and allow visitors to compare fields of expertise. Review the route plan, typed collections, design direction and acceptance checks before building. - [Accessible venue directory](https://uvilno.com/prompts/accessible-venue-directory): Help visitors compare supplied access information while avoiding unverified accessibility certification. Review the route plan, typed collections, design direction and acceptance checks before building. - [Rental workspace directory](https://uvilno.com/prompts/rental-workspace-directory): Compare supplied desk and studio options without claiming live availability or a lease transaction. Review the route plan, typed collections, design direction and acceptance checks before building. - [Independent course directory](https://uvilno.com/prompts/independent-course-directory): Let learners compare supplied course descriptions and maintain their own learning shortlist. Review the route plan, typed collections, design direction and acceptance checks before building. - [Used equipment listing board](https://uvilno.com/prompts/used-equipment-listing-board): Offer a clearly scoped listing catalog and private inquiry tracker without acting as a payment intermediary. Review the route plan, typed collections, design direction and acceptance checks before building. - [Community resource index](https://uvilno.com/prompts/community-resource-map-index): Organize reviewed local resources by category without pretending a location graphic is a connected map. Review the route plan, typed collections, design direction and acceptance checks before building. - [Personal budget scenario tool](https://uvilno.com/prompts/personal-budget-scenario-tool): Help a person explore their entered income and spending assumptions without account access or financial advice. Review the route plan, typed collections, design direction and acceptance checks before building. - [SaaS revenue scenario calculator](https://uvilno.com/prompts/saas-revenue-scenario-calculator): Model subscription assumptions without representing projections as actual revenue or connected billing. Review the route plan, typed collections, design direction and acceptance checks before building. - [Freelance cash-flow planner](https://uvilno.com/prompts/freelance-cashflow-planner): Let a freelancer organize expected receipts and expenses without pretending to access bank accounts. Review the route plan, typed collections, design direction and acceptance checks before building. - [Invoice register dashboard](https://uvilno.com/prompts/invoice-register-dashboard): Track supplied invoice records as an organizational tool without claiming issuance, tax compliance or payment collection. Review the route plan, typed collections, design direction and acceptance checks before building. - [Mortgage assumption calculator](https://uvilno.com/prompts/mortgage-assumption-calculator): Compute principal-and-interest estimates from entered assumptions with transparent exclusions. Review the route plan, typed collections, design direction and acceptance checks before building. - [Project margin planner](https://uvilno.com/prompts/project-margin-planner): Help a studio estimate margin from its own project fee and cost entries. Review the route plan, typed collections, design direction and acceptance checks before building. - [Subscription spend auditor](https://uvilno.com/prompts/subscription-spend-auditor): Let an individual record recurring tool costs and renewal dates without reading bank or email accounts. Review the route plan, typed collections, design direction and acceptance checks before building. - [Crypto watchlist notebook](https://uvilno.com/prompts/crypto-watchlist-notebook): Organize a user's manually entered asset notes without pretending to stream market prices or execute trades. Review the route plan, typed collections, design direction and acceptance checks before building. - [Business KPI input dashboard](https://uvilno.com/prompts/business-kpi-input-dashboard): Visualize actual user-entered business measurements with definitions and reporting periods. Review the route plan, typed collections, design direction and acceptance checks before building. - [Self-paced course workspace](https://uvilno.com/prompts/self-paced-course-workspace): Help a learner work through supplied lessons and record their own progress without unsupported certification. Review the route plan, typed collections, design direction and acceptance checks before building. - [Flashcard review notebook](https://uvilno.com/prompts/flashcard-review-notebook): Let a learner create and review cards from supplied material without pretending the content is professionally verified. Review the route plan, typed collections, design direction and acceptance checks before building. - [Language vocabulary shelf](https://uvilno.com/prompts/language-vocabulary-shelf): Organize a learner's words, examples and review decisions in private saved records. Review the route plan, typed collections, design direction and acceptance checks before building. - [Research reading planner](https://uvilno.com/prompts/research-reading-planner): Help a student prioritize permission-cleared readings and keep notes separate from completion state. Review the route plan, typed collections, design direction and acceptance checks before building. - [Teacher resource organizer](https://uvilno.com/prompts/teacher-resource-organizer): Allow one educator to maintain their own resource library without exposing student records. Review the route plan, typed collections, design direction and acceptance checks before building. - [Practice quiz runner](https://uvilno.com/prompts/practice-quiz-runner): Run supplied practice questions with deterministic answer checking and no fabricated grading authority. Review the route plan, typed collections, design direction and acceptance checks before building. - [Workshop materials portal](https://uvilno.com/prompts/workshop-materials-portal): Make a supplied workshop agenda and materials easy to navigate without claiming access control beyond the actual app identity. Review the route plan, typed collections, design direction and acceptance checks before building. - [Portfolio learning journal](https://uvilno.com/prompts/portfolio-learning-journal): Help a learner document completed work and reflections without inventing credentials or publishing private entries. Review the route plan, typed collections, design direction and acceptance checks before building. - [Exam revision calendar](https://uvilno.com/prompts/exam-revision-calendar): Organize a learner's entered topics and dates into a realistic private revision plan. Review the route plan, typed collections, design direction and acceptance checks before building. - [Club interest portal](https://uvilno.com/prompts/club-interest-portal): Collect real membership interest without presenting submission as approved membership. Review the route plan, typed collections, design direction and acceptance checks before building. - [Volunteer opportunity board](https://uvilno.com/prompts/volunteer-opportunity-board): Help visitors discover supplied opportunities and maintain their own expression of interest. Review the route plan, typed collections, design direction and acceptance checks before building. - [Creator membership outline](https://uvilno.com/prompts/creator-membership-outline): Describe supplied membership content and test an account journey without pretending subscriptions are activated. Review the route plan, typed collections, design direction and acceptance checks before building. - [Neighborhood event calendar](https://uvilno.com/prompts/neighborhood-event-calendar): Publish reviewed event details and let visitors save a private attendance plan. Review the route plan, typed collections, design direction and acceptance checks before building. - [Professional resource circle](https://uvilno.com/prompts/professional-resource-circle): Organize permission-cleared professional resources without implying credentials or endorsement. Review the route plan, typed collections, design direction and acceptance checks before building. - [Donation interest information hub](https://uvilno.com/prompts/donation-interest-information-hub): Explain a supplied organization's work and collect inquiries without fabricating donations or charity status. Review the route plan, typed collections, design direction and acceptance checks before building. - [Community proposal workspace](https://uvilno.com/prompts/community-proposal-workspace): Let an individual maintain project proposals and review notes without pretending there is a connected voting system. Review the route plan, typed collections, design direction and acceptance checks before building. - [Peer mentoring interest board](https://uvilno.com/prompts/peer-mentoring-interest-board): Collect a visitor's mentoring interests without exposing a public member directory by default. Review the route plan, typed collections, design direction and acceptance checks before building. - [Creative collective project hub](https://uvilno.com/prompts/creative-collective-project-hub): Present approved collective work while keeping contributor claims and project ownership accurate. Review the route plan, typed collections, design direction and acceptance checks before building. - [Independent magazine index](https://uvilno.com/prompts/independent-magazine-index): Make supplied articles discoverable through topic, author and meaningful summaries. Review the route plan, typed collections, design direction and acceptance checks before building. - [Newsletter archive browser](https://uvilno.com/prompts/newsletter-archive-browser): Present a supplied newsletter archive and collect real interest without claiming email delivery. Review the route plan, typed collections, design direction and acceptance checks before building. - [Podcast episode library](https://uvilno.com/prompts/podcast-episode-library): Organize supplied episodes, transcripts and listening notes with accessible playback controls. Review the route plan, typed collections, design direction and acceptance checks before building. - [Technical documentation library](https://uvilno.com/prompts/technical-documentation-library): Publish supplied technical explanations with useful navigation and no fabricated supported API methods. Review the route plan, typed collections, design direction and acceptance checks before building. - [Travel field-notes archive](https://uvilno.com/prompts/travel-field-notes-archive): Present an author's supplied place notes without inventing safety claims, prices or current opening hours. Review the route plan, typed collections, design direction and acceptance checks before building. - [Recipe editorial collection](https://uvilno.com/prompts/recipe-editorial-collection): Organize original supplied recipes with practical ingredient and serving controls. Review the route plan, typed collections, design direction and acceptance checks before building. - [Oral history listening room](https://uvilno.com/prompts/oral-history-listening-room): Make consented recordings and transcripts browsable without exposing restricted personal information. Review the route plan, typed collections, design direction and acceptance checks before building. - [Book review reading shelf](https://uvilno.com/prompts/book-review-reading-shelf): Publish original supplied reviews and let visitors maintain a separate private reading shelf. Review the route plan, typed collections, design direction and acceptance checks before building. - [Design research publication index](https://uvilno.com/prompts/design-research-publication-index): Explain supplied research projects and sources without treating editorial conclusions as independent benchmark wins. Review the route plan, typed collections, design direction and acceptance checks before building. - [Inventory reorder workspace](https://uvilno.com/prompts/inventory-reorder-workspace): Track a small operator's entered stock and reorder decisions without claiming a connected warehouse. Review the route plan, typed collections, design direction and acceptance checks before building. - [Maintenance request dashboard](https://uvilno.com/prompts/maintenance-request-dashboard): Let a facility manager organize their own maintenance requests and actual review states. Review the route plan, typed collections, design direction and acceptance checks before building. - [Release checklist manager](https://uvilno.com/prompts/release-checklist-manager): Track release preparation without pretending the app can deploy code or access production systems. Review the route plan, typed collections, design direction and acceptance checks before building. - [API incident notebook](https://uvilno.com/prompts/api-incident-notebook): Record manually supplied incidents and investigation notes without fabricated live observability. Review the route plan, typed collections, design direction and acceptance checks before building. - [Equipment checkout register](https://uvilno.com/prompts/equipment-checkout-register): Let an individual organize equipment loans and returns without a false multi-user permission model. Review the route plan, typed collections, design direction and acceptance checks before building. - [Supplier review workspace](https://uvilno.com/prompts/supplier-review-workspace): Help a buyer compare supplied supplier notes without claiming verified ratings or automated procurement. Review the route plan, typed collections, design direction and acceptance checks before building. - [Bug triage workbench](https://uvilno.com/prompts/bug-triage-workbench): Organize reproducible issues, severity and next action without pretending to modify a remote repository. Review the route plan, typed collections, design direction and acceptance checks before building. - [Content approval queue](https://uvilno.com/prompts/content-approval-queue): Let one editor review their own content drafts with a clear distinction between approval records and actual publishing. Review the route plan, typed collections, design direction and acceptance checks before building. - [Lab sample organization tool](https://uvilno.com/prompts/lab-sample-organization-tool): Organize fictional non-clinical sample labels and review notes without regulated diagnostic or chain-of-custody claims. Review the route plan, typed collections, design direction and acceptance checks before building. ## Frequently asked questions ### How do I start building with Uvilno? Name a project, describe the website in chat, and send your brief when you are ready. Naming or reopening a project does not start a build or use your AI allowance. ### How do the monthly plans work? Plus costs $10/month with standard usage and two project source unlocks per paid month. Pro is $20/month with 2.5× more usage than Plus and unlimited project unlocks. Ultra is $59/month with 5× more usage than Pro, unlimited unlocks, and priority model routing. Allowances reset monthly. Plans renew until canceled in billing. ### Do my unlocked projects stay unlocked? Yes. A $4.99 purchase or an included plan unlock permanently unlocks that project. You can download its source again without spending another unlock, even after canceling a subscription. Unlimited downloads do not mean unlimited AI generation. ### Do I need to know how to code? No. You describe the site in plain language and refine it by chat. You never touch files, a terminal or a server. When you unlock, you receive clean files you can hand to any host. ### What exactly do I get when I unlock? An export appropriate to your project: static HTML/CSS/JavaScript, or eligible Next.js project source and verified static output. Referenced uploads, bundled fonts and licenses travel with it. Hosted authentication, databases, payment services and external media still need their own configuration or migration. ### Why can't I see the code during the preview? The preview lets you explore your website while the source bundle stays on the server. Unlocking releases the files for code inspection and export. As with any website, browsers can inspect rendered assets; the preview is not a form of copy protection. ### How does usage work? Your studio starts at 100% remaining and counts down to 0%, with a reset date. Model-backed builds, refinements and planning use measured processing. Casual chat acknowledgments and safe deterministic element edits use no model tokens. Viewing previews, organizing projects and adjusting settings do not start AI generation. Prompt assistance has its own limits. ### Can I use my own domain? Yes. Export your unlocked site's files and deploy them to a static host, then connect your domain through that provider. Domain registration and hosting are separate from your Uvilno plan. ### What happens to my images? Add your logo and photographs using the workspace's image controls. Referenced uploads and bundled fonts are included in your unlocked export. Check your rights to any imagery before publishing. ### Which languages are supported? Describe your site in any language and the copy is written in it. The Uvilno interface is English for now, with more languages planned. ## Direct answers and their sources ### Can you export source code from Base44? Canonical: https://uvilno.com/answers/can-you-export-source-code-from-base44 Base44 documents source ownership and GitHub export; it does not universally lock away code. Uvilno offers a different purchase: a permanent $4.99 source unlock for one project. In both products, exported frontend code and an independently migrated database, authentication service and hosting are separate deliverables. Compare the entitlement that actually supplies source, not simply the cheapest advertised subscription. Base44 lists GitHub integration on applicable plans, while Uvilno offers individual permanent project unlocks alongside subscription entitlements. Review the current plan, repository permissions and export limitations before deciding. An exit test has two parts: build the exported source on a separate host, then check every service it calls. Customer records, account identities, credentials and hosted workflows do not migrate merely because frontend files were downloaded. Inventory those dependencies before canceling either platform. Sources: - [Uvilno pricing and source entitlements](https://uvilno.com/pricing) - [Export and hosting guide](https://uvilno.com/guides/how-to-export-and-host-your-ai-website) - [Base44 plans, included services and source ownership](https://base44.com/pricing) - [Base Code and GitHub repository workflow](https://docs.base44.com/Getting-Started/base-code) - [Base44 app data management](https://docs.base44.com/Building-your-app/Managing-your-app-data) - [Base44 access and roles](https://docs.base44.com/Setting-up-your-app/Managing-access) - [Base44 automation triggers and workflow migration](https://docs.base44.com/Building-your-app/Creating-automations) - [Base44 Stripe payment integration](https://docs.base44.com/documentation/setting-up-your-app/setting-up-payments) - [Base44 app inference and supported models](https://docs.base44.com/developers/backend/resources/models) ### Why can AI builder bug fixes consume tokens? Canonical: https://uvilno.com/answers/why-does-bolt-new-burn-tokens-on-bug-fixes AI bug fixes can consume model context and generated output, including unsuccessful attempts. This does not establish that every Bolt build wastes tokens. Uvilno separates metered edits from mapped direct edits and a bounded, platform-funded repair path for reproduced runtime faults in native static projects. A repair request may require the model to inspect related modules, explain an error to the controller and emit a replacement. Larger context and repeated failed attempts can increase usage. Ask the platform to expose its actual billing model rather than inferring cost from the number of visible messages. Uvilno's no-usage repair is narrowly admitted and checked in an isolated browser. It is not a free general-purpose coding service, does not cover every framework issue, and cannot promise that all failures disappear. Preserve the previous version and make the smallest reproducible request. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) - [Bolt pricing and plan limits](https://bolt.new/pricing) - [Build and refine with Bolt](https://support.bolt.new/building) - [Bolt GitHub integration](https://support.bolt.new/integrations/git) - [Bolt project download and WebContainer troubleshooting](https://support.bolt.new/faqs/troubleshooting/webcontainer) - [Bolt Cloud data and user management](https://support.bolt.new/building/intro-bolt) - [Bolt model-token usage](https://support.bolt.new/faqs/account-and-subscription/tokens) ### How should Emergent's app cost be compared with Uvilno? Canonical: https://uvilno.com/answers/emergent-sh-pricing-and-credit-burn-explained Emergent publishes subscription credits and separate deployment considerations; a project's cost depends on usage and services. Uvilno's $4.99 purchase unlocks one project's source, not unlimited generation or annual hosting. Compare subscriptions, extra model usage, deployment, databases and migration over the same period before estimating savings. Do not multiply a headline monthly price into a supposed cost per app without knowing how many builds, refinements and deployments the account actually performs. Annual offers and checkout terms may differ, and credit grants can change. The comparison page cites current official sources and flags conflicts instead of guessing. For a useful budget, write down the number of active apps, expected edits and ongoing services. Keep generation separate from ownership: permanent source access can be valuable, but does not fund an API, domain, customer database or payment processor indefinitely. Sources: - [Uvilno pricing and source entitlements](https://uvilno.com/pricing) - [Emergent plans](https://emergent.sh/pricing) - [Emergent website builder and deployment FAQ](https://emergent.sh/learn/ai-website-builder-faq) - [Emergent data and code ownership](https://help.emergent.sh/your-data-ownership) - [Emergent product FAQ](https://help.emergent.sh/faqs) - [Emergent free-tier grant terms](https://help.emergent.sh/plans-the-free-tier) - [Emergent credit accounting and testing costs](https://help.emergent.sh/plans-and-credits) ### Does Lovable require manual Supabase setup for every app? Canonical: https://uvilno.com/answers/lovable-dev-supabase-setup-vs-uvilno-built-in-database Lovable offers Cloud backend services, so Supabase setup is not required for every Lovable app. Uvilno uses schema-declared managed collections through Uvilno.db and a visual App Data manager. Compare ownership rules, supported queries, service limits and migration requirements rather than assuming either backend requires nothing. Lovable Cloud documents database, authentication and other managed capabilities. A separate Supabase integration may still fit a particular project, but describing all Lovable projects as manual configuration would be inaccurate. Compare the selected backend path and its current plan terms. Uvilno's data contract declares supported typed fields, references, access and optional bounded automations. Generated forms use the hosted SDK; the owner can inspect real rows through App Data. This is a defined service contract, not an arbitrary SQL server provisioned inside the frontend export. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) - [Lovable subscription plans](https://docs.lovable.dev/introduction/subscription-plans) - [Lovable credits and usage](https://docs.lovable.dev/introduction/credits-and-usage) - [Lovable deployment, hosting and ownership](https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership) - [Lovable Git sync](https://docs.lovable.dev/integrations/git-sync-overview) - [Lovable built-in backend and jobs](https://docs.lovable.dev/features/cloud) - [Lovable managed AI features for apps](https://docs.lovable.dev/features/ai) ### Which AI app builder fits a database and authentication project? Canonical: https://uvilno.com/answers/best-ai-app-builder-with-database-and-authentication The choice depends on the data model, authorization and deployment requirements. Uvilno provides typed managed collections and project-isolated visitor identities, with configured OAuth providers and email accounts. Validate persistence, ownership and unsupported integrations in a working slice before choosing any platform for a production application. Start with a visitor and a record: who creates it, who reads it and which changes are permitted? An attractive login screen or a visible admin label does not prove that those boundaries are enforced. Specify the permissions and test them using separate disposable identities. Uvilno can support the declared collection and identity workflow, while broader organizational sharing or specialist compliance requirements need explicit review. Compare those requirements against other builders' documented capabilities; no single product is established as universally best by this page. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Can Uvilno source access be purchased without a monthly subscription? Canonical: https://uvilno.com/answers/best-ai-website-builder-without-monthly-subscription Uvilno offers a $0 tier and a $4.99 one-time source unlock for one project, without requiring a subscription for that entitlement. Included generation is finite. Ongoing hosting, domains, model usage and hosted backend dependencies are separate; source ownership does not eliminate every recurring operating expense. The individual unlock is useful when the deliverable is the site's source rather than a continuing subscription entitlement. Already unlocked projects remain downloadable after cancellation. Monthly plans add generation capacity and included source unlocks, but are a separate purchase decision. Before selecting a source-only approach, decide where the exported site will run. A static site has different needs from a visitor-account app backed by hosted collections or paid inference. Record those dependencies and obtain real hosting and service prices instead of calling the whole application subscription-free. Sources: - [Uvilno pricing and source entitlements](https://uvilno.com/pricing) - [Export and hosting guide](https://uvilno.com/guides/how-to-export-and-host-your-ai-website) ### How can an AI micro-SaaS use Uvilno's managed integrations? Canonical: https://uvilno.com/answers/how-to-build-an-ai-micro-saas-with-stripe-and-no-api-keys Uvilno can connect app features to owner-funded Uvilno.ai inference, project accounts, managed records and configured Stripe test Checkout. The visitor need not receive provider keys. Live monetization still requires an enabled production payment setup, onboarding, usage budgeting and verification; test checkout is not real revenue. For an AI resume helper, define the input, result format and saved history before requesting a payment screen. Keep sensitive documents out of test fixtures. Each managed AI response is bounded, and failed inference should preserve input rather than display a fabricated successful analysis. A test payment flow helps verify the interaction and fulfillment design, but cannot collect a live customer payment. Plan cancellation, refunds, webhook-driven entitlements and abuse limits before production. Do not infer that a single connector toggle has completed every business and operational requirement. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) - [Stripe integration guide](https://uvilno.com/guides/how-to-add-stripe-payments-without-api-keys) ### What should be tested in an AI-built browser game? Canonical: https://uvilno.com/answers/best-ai-builder-for-html5-browser-games Evaluate controls, collision behavior, score persistence and frame time on the target device. Uvilno supports browser games, Canvas, WebGL and its game runtime, but no universal 60fps guarantee follows. A shared leaderboard also needs scoped storage and abuse controls; a local score is not global. State the core loop, input scheme, win and loss conditions, restart behavior and accessibility options. Test keyboard and touch separately, then measure frame time during the most demanding scene. A screenshot of a game board is not evidence that its mechanics work. Decide whether scores are device-local, visitor-private or deliberately published. Public client-submitted scores are not inherently cheat-proof. Cosmetics and a checkout UI are also different from a verified purchase and entitlement service. Keep fictional examples visibly labeled and test network failures without losing the current run. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### How does Uvilno's declarative database work? Canonical: https://uvilno.com/answers/how-does-uvilno-declarative-database-work Uvilno declares collections, typed fields, references and optional rules in data/schema.json. Generated interfaces call Uvilno.db for hosted CRUD, and the creator inspects rows through App Data. The schema is validated with the saved version; it is not permission to execute arbitrary SQL or server code. Begin with field meanings and ownership, not merely table names. Mark required values, supported options and references to other declared collections. A schema change can affect existing records, so inspect compatibility instead of assuming a new preview automatically migrates every old value. The hosted service validates operations independently of the generated interface. A disabled button or hidden section is not an access-control mechanism. Keep real orders, bookings and lead collections empty initially; only explicitly disclosed fictional demonstration records should be seeded. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### How can saved app records be verified after reload? Canonical: https://uvilno.com/answers/do-generated-app-records-survive-reload A saved record should be retrieved from the hosted service after navigation or reload, using the same authorized app identity. Uvilno.db provides that persistence for declared collections. A toast, optimistic update or localStorage mirror alone is insufficient evidence; inspect App Data and test a retrieval. Use a unique, non-sensitive test value so the record cannot be confused with demonstration data. Create it, change one field, leave the route and return. Reload the iframe, sign back into the same app identity if needed, and check the value again. Then exercise failure behavior. A rejected write should leave the previous saved state intact and explain what the user can retry. Uvilno's local media storage and collection records have different persistence boundaries, so verify them separately instead of treating every browser cache as a backend. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Does the Admin preview persona grant real permissions? Canonical: https://uvilno.com/answers/does-admin-preview-grant-real-permissions Uvilno's Guest, Member and Admin preview selector changes presentation only. It can reveal declared role-specific views, but cannot alter the app visitor's identity, database ownership or server permissions. Administrative authorization must be implemented and verified; hidden controls and client-side role labels are not security boundaries. The preview selector is useful for reviewing information hierarchy and role-specific states without logging the creator out. A real app must still authorize every read and mutation using its actual app session. Client-side setRole cannot promote a visitor or expose another visitor's records. When asking for an admin experience, define the actual permitted operations and supported server authorization. If the product lacks the requested multi-user management capability, the interface should explain that boundary rather than show a convincing control that secretly has no legitimate authority. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Is generated-app login separate from Uvilno's creator account? Canonical: https://uvilno.com/answers/is-generated-app-login-isolated-from-builder Uvilno's app authentication uses project-scoped visitor identities and sessions, separate from the creator's platform login. Configured Google, GitHub, Discord and email flows must not replace builder cookies. Verify both identities around sign-in, sign-out and reload; a separate login page alone does not establish session isolation. The creator and the visitor have different jobs and privileges. A website visitor should never become the builder account simply by completing an OAuth flow in the preview. Tokens and callback state must remain scoped to the intended project and application origin. Test at least two projects and two disposable visitor identities. Sign into the generated app, reload it, sign out and confirm the platform still shows the original creator. Exports need their final supported HTTPS origin registered; copying a callback URL from the builder is not a migration strategy. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Does Uvilno.ai perform real inference? Canonical: https://uvilno.com/answers/does-uvilno-in-app-ai-use-real-inference Uvilno.ai.ask and Uvilno.ai.json call a project-authorized server proxy for real configured model inference. They are not canned successful responses. Requests use the creator's finite allowance, have admission limits and a 600-output-token ceiling, and require the managed AI capability and an authenticated app visitor for access. An AI feature should show pending, limited and failed states in addition to a successful result. Preserve user input when the provider or allowance is unavailable. A returned sentence that happens to match a demo example is not proof of a real request; test a distinct input and observe the application response. Choose a bounded feature such as a short summary, question set or classification. Do not design a long report around a 600-token response. Keep provider credentials on the server and validate results before saving them into a typed collection or treating them as consequential advice. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Is a JSON description the same as schema validation? Canonical: https://uvilno.com/answers/is-ai-json-output-schema-validated Uvilno.ai.json parses a bounded JSON object or array and rejects unsafe structures, but a schema description is not domain validation. Generated applications must check required fields, types and permitted values before rendering or saving results. Treat every model response as untrusted input, including valid JSON. Parsing establishes that the text is JSON, not that it represents your intended record. A quiz may contain a missing answer, a classification may invent a category, or a numeric estimate may be outside your permitted range. Define the checks that matter to the feature. Render plain values through safe framework bindings, never as arbitrary HTML. If validation fails, show an actionable error and keep the original input. Model-produced identities, URLs and instructions cannot override project authorization, navigate to privileged callbacks or modify the schema by themselves. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### What happens if a database automation fails? Canonical: https://uvilno.com/answers/how-do-transactional-app-automations-work Uvilno's schema-declared database automations run in the record transaction with the same owner scope. A failed action rolls back the write and its effects. Idempotent retries avoid duplicated actions, and rules do not recursively trigger rules or execute uploaded JavaScript, external requests or role grants. Keep a rule small enough to understand: creating a task can create a scoped activity entry and an in-app notification. Related record updates or numeric increments must reference declared fields and respect the same ownership rules. A transaction should either commit its supported effects or report a failure. Do not infer email delivery, background scheduling or third-party fulfillment from an in-app notification. Those are different capabilities. When evolving a schema, test the rule with disposable rows and inspect the actual resulting record rather than trusting only the interface toast. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Where can creators inspect automation activity? Canonical: https://uvilno.com/answers/where-to-inspect-automation-logs Open App Data in Uvilno's builder and select Automations & Logs. The view shows installed rules and committed event metadata with bounded refresh. It does not expose project source or private record bodies, and an activity entry does not prove an external service was executed. Start with the rule definition: its collection, triggering operation and supported actions. Then perform one identifiable write and locate the corresponding event. If the transaction fails, inspect the visible error rather than expecting a successful activity entry for an uncommitted operation. Logs are a diagnostic view, not a customer database export. They intentionally avoid sensitive record bodies. Website rollback does not rewind application data, so record changes and version changes should be reviewed separately when debugging a production workflow. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### How do file and database mentions target an edit? Canonical: https://uvilno.com/answers/how-to-use-file-and-database-context-mentions Typing @ in Uvilno's builder opens page, file and collection suggestions. Choose references such as @index.html or @db:tasks, or use an inspector-provided @selected-element. These references guide private source retrieval for a focused edit; they do not expose locked code or guarantee a fixed completion time. Use a mention when the location matters: a tasks filter belongs to the tasks controller, while a shared navigation change may affect several pages. The menu supports keyboard navigation and selected references remain removable pills, so review them before submitting. The server validates each reference against the current owned version. An arbitrary path pasted into the message is not authority to load private storage or another customer's project. Preserve an explicit description of the desired behavior alongside the reference; a filename alone is not an edit specification. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### What does Uvilno's repository map contribute to edits? Canonical: https://uvilno.com/answers/what-does-a-project-repo-map-do Uvilno maintains an inventory of project files, routes and module relationships to guide context retrieval. The model receives affected source rather than rewriting everything. Repository awareness improves targeting, but cannot prove an edit correct; compilation, behavioral checks and review of the resulting version remain necessary. A large app can contain shared navigation, several route modules and a common data controller. Loading one page without its dependencies may miss the actual cause of a bug. The repository inventory helps locate those relationships while keeping the full project out of every model request. For an additive feature, name the route and expected action. For a bug, provide the failing step and state. Avoid requesting a global redesign when only a small behavior is broken, and keep a known saved version for comparison. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Which visual edits use no model usage? Canonical: https://uvilno.com/answers/which-visual-edits-use-no-ai-usage Uvilno's Inspect & Edit controls can change text, links and colors without a model request. Targeted AI instructions are a metered action. Direct edits require ownership, compatible source mapping and saved-version checks; the control is not an unrestricted browser DOM mutation or automatic source unlock. Use the preview inspector to select the actual element. Review its supported edit controls and save a concrete value, such as a heading correction or destination URL. A direct change should persist in the saved version, not disappear when the iframe reloads. Some content is generated dynamically or lacks a safe source mapping. In that case, use a targeted instruction rather than pretending every visual node can be edited deterministically. Keep a clear distinction between a local preview state and a verified saved change. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Is Uvilno's automatic repair unlimited? Canonical: https://uvilno.com/answers/is-automatic-repair-always-free-and-unlimited Uvilno's platform-funded repair is limited to native static-project faults reproduced by server-side browser checks. It has per-version, project and owner admission limits and a bounded free-model response. Ordinary edits and broader repairs remain metered, and failed recovery preserves the saved version rather than claiming success. The live iframe can report a critical observation, but its message cannot authorize arbitrary free coding. The server independently reproduces the fault, selects a small affected file set, validates complete replacements and checks the rendered result before publication. A new feature, redesign or general question is not a runtime repair. Next.js verification and normal generation keep their own contracts. If automatic recovery cannot verify a safe result, use the saved version and a precise bug report; no finite system can promise every future error will disappear. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Can a long build resume after an interruption? Canonical: https://uvilno.com/answers/can-a-failed-long-build-be-resumed Uvilno preserves completed-file checkpoints and supports viewing an unfinished draft or continuing the brief after interruption. The verified version remains separate. Recovery has retention and execution limits, and a checkpoint is not a verified application; inspect its status before treating it as ready to launch. A network interruption and a failed server build are different events. Durable work can continue independently of the browser, while a stopped attempt may leave completed modules that can seed recovery. Reopen the owned project and inspect its actual run status instead of repeatedly submitting a new build. An unfinished preview is useful evidence, but may lack a route, dependency or valid data contract. Continue from the saved request with relevant context intact. Do not overwrite the last verified version simply to make an incomplete candidate look successful. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) - [GitHub and recovery guide](https://uvilno.com/guides/github-sync-and-version-recovery) ### How should a twenty-page application be planned? Canonical: https://uvilno.com/answers/how-to-plan-a-twenty-page-ai-application Define the navigation, route purposes, data contract and user journeys before generating twenty screens. Uvilno's contract-first pipeline and contextual retrieval support modular projects, but every route still needs checks. Build a vertical slice first, preserve components and expand only after its persistence and interactions pass. A list of page names is not an architecture. Group routes by audience and workflow, identify shared layouts and state, and define which pages need authentication. Avoid twenty separately styled copies of the same dashboard that never agree on data or navigation. Use one complete journey as the reference implementation: sign in, create a record, inspect its detail, edit it and reload. Then add related routes against the same contract. Keep unsupported backend requirements visible rather than generating a convincing screen for an unavailable service. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Does a Next.js source export include a managed backend? Canonical: https://uvilno.com/answers/does-nextjs-export-include-a-managed-backend A Next.js source export provides project files and build instructions, not ownership of each service it calls. Uvilno's framework output uses a static-export contract. Managed identity, collections, AI and payments remain configured dependencies; arbitrary Server Actions or dynamic backend provisioning are not implied by Next.js. Framework selection and infrastructure ownership answer different questions. A multi-file App Router project can contain build-time Server Components and interactive Client Components while still requiring external services for persistence. Inspect the actual generated contract instead of assuming the framework name supplies a backend. On a clean host, install the pinned dependencies and build the export, then exercise routes and media. Register the final supported origin for hosted authentication and decide whether to retain or replace managed services. Never copy platform secrets into browser configuration to make a migration appear complete. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) - [Export and hosting guide](https://uvilno.com/guides/how-to-export-and-host-your-ai-website) ### What does the $4.99 Uvilno source unlock include? Canonical: https://uvilno.com/answers/what-does-the-499-source-unlock-include The $4.99 one-time unlock permanently grants source access for one Uvilno project. Exports include runtime-appropriate files, referenced uploads, bundled fonts and licenses; eligible projects also support static output. It does not buy unlimited generation, hosting, domains, customer records, provider credentials or a migrated backend service. Source entitlement is tied to the project rather than a single download. An already unlocked project remains downloadable after a subscription ends, and supported GitHub source pushes still require authorization. Check which runtime archive is available for the actual saved version. Before handing the export to a developer, include the deployment target, service inventory and rights to supplied assets. Customer data is intentionally excluded from ordinary source archives. A developer can adapt the frontend, but database, identity and billing migration require deliberate, separate work. Sources: - [Uvilno pricing and source entitlements](https://uvilno.com/pricing) - [Export and hosting guide](https://uvilno.com/guides/how-to-export-and-host-your-ai-website) ### How do Plus and Pro differ for multiple projects? Canonical: https://uvilno.com/answers/uvilno-plus-vs-pro-for-multiple-projects Uvilno Plus costs $10 per month with capacity and two project source unlocks per paid period. Pro costs $20 per month with 2.5 times Plus capacity and unlimited project unlocks during the subscription. Neither plan means unlimited generation; unlocked projects retain their permanent source entitlement. Compare two separate needs: how much iteration your applications require and how many distinct projects need source access. Downloading an already unlocked project again does not consume another included unlock. The individual $4.99 purchase remains available for a single project. Usage is displayed as remaining capacity rather than a promise of a fixed number of successful applications. A complex app can require more planning, generation and refinement than a small brochure site. Choose a plan using actual work and review the current reset and entitlement details. Sources: - [Uvilno pricing and source entitlements](https://uvilno.com/pricing) ### When does Uvilno Ultra fit a workflow? Canonical: https://uvilno.com/answers/when-does-uvilno-ultra-make-sense Uvilno Ultra costs $59 per month, includes five times Pro's capacity and unlimited source unlocks during the paid period. It suits heavier iteration needs, not a guarantee of unlimited builds or flawless output. Priority model routing remains subject to availability, scheduling, admission and execution limits. Pro already includes unlimited project unlocks, so Ultra's relevant difference is additional processing capacity and the configured priority route. Review the remaining meter and the amount of repeated planning and refinement your actual work consumes before upgrading. A larger allowance cannot resolve an unsupported integration or replace product requirements. Bound each release, preserve known working versions and check the data and account workflow. No subscription price can establish that a complex application is automatically production-ready. Sources: - [Uvilno pricing and source entitlements](https://uvilno.com/pricing) ### What does 100% remaining usage mean? Canonical: https://uvilno.com/answers/what-does-100-percent-remaining-usage-mean Uvilno displays capacity as 100% remaining down to 0%, with the reset information. Model-backed planning, generation and refinements consume allowance. Source entitlements and downloads are separate. Preview viewing or naming a draft does not initiate a build, and unlimited unlocks do not mean unlimited inference. The percentage is an allowance display, not a count of pages or messages. Different requests can require different input and output processing. Inspect the reset date and current plan rather than assuming that one short message always consumes the same amount. Manage work deliberately: prepare the brief first, make focused edits and distinguish deterministic visual changes from AI requests. An app's managed AI feature can also consume the creator's allowance, so public inference needs admission limits and a realistic product budget. Sources: - [Uvilno pricing and source entitlements](https://uvilno.com/pricing) - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Can the current Stripe connector accept live payments? Canonical: https://uvilno.com/answers/can-uvilno-stripe-checkout-accept-live-payments Uvilno's Stripe Connect and Checkout workflows use test mode. They verify a payment journey without taking money. Live payments require an enabled configuration, provider onboarding and verified fulfillment behavior. A test checkout must never be displayed as actual revenue, settlement or a completed live sale. Keep test products, prices and success states visibly identified. A frontend redirect after checkout is not sufficient authority to grant a paid entitlement; the real service must verify the corresponding payment state. Test cancellation and webhook replay as well as the happy path. Before launch, decide who owns the connected account, how refunds work and what happens when payment succeeds but fulfillment fails. Credentials belong on the server. A connector reduces setup steps but does not replace these business and operational decisions. Sources: - [Stripe integration guide](https://uvilno.com/guides/how-to-add-stripe-payments-without-api-keys) - [Uvilno public SDK documentation](https://uvilno.com/docs) ### What should be checked before using GitHub sync? Canonical: https://uvilno.com/answers/how-does-two-way-github-sync-work Uvilno supports GitHub import, source push and pull for frontends; source pushes require project entitlement. Repository access does not migrate customer records or grant unrelated account permissions. Check the repository, branch, changes and conflict behavior before synchronizing, and keep credentials out of source and exports. Use the correct repository and branch for the intended project. Inspect the proposed changes and confirm whether the external branch has moved since the last sync. A pull should not silently discard a local saved version or private draft without a clear conflict path. Generated code is untrusted and still needs compilation and behavior checks after import. Secrets should remain in private environment settings rather than committed .env files. A GitHub connection makes code transport convenient, but is not a production deployment, backup of customer data or automatic security review. Sources: - [GitHub and recovery guide](https://uvilno.com/guides/github-sync-and-version-recovery) - [Uvilno pricing and source entitlements](https://uvilno.com/pricing) ### Does importing source migrate customer data and passwords? Canonical: https://uvilno.com/answers/can-customer-data-move-between-ai-builders Importing source or a GitHub repository moves code, not customer records, identities, passwords, payment history or service credentials. Uvilno requires an authorized migration plan for those systems. Preserve ownership, consent and field mappings, and test a sample before changing an application's backend or account flow. Inventory each system of record and the permitted export format. Password and OAuth identity migration can have special constraints, and a frontend cannot safely reconstruct those credentials. Keep migration administration separate from ordinary visitor access. Map data types and references before import, preserve the original identifiers where required and validate record counts. Plan a cutover and rollback window, including how writes are handled while both systems exist. Do not disguise copied demonstration rows as a completed customer migration. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) - [Export and hosting guide](https://uvilno.com/guides/how-to-export-and-host-your-ai-website) ### Can an exported app run without Uvilno's hosted services? Canonical: https://uvilno.com/answers/can-an-export-run-without-uvilno-services A static frontend can run on compatible hosting, but an app using Uvilno-managed auth, data, AI or payments calls those services unless they are replaced. Source ownership allows adaptation; it does not recreate infrastructure. Inspect the dependency inventory and verify the host before announcing independence. Separate rendering from operations. A portfolio with static content and email links may need little beyond a host and domain, while a SaaS with accounts, records and inference needs ongoing services. Export the correct runtime package and keep referenced media and font licenses with it. If replacing a hosted service, implement its authorization and failure behavior, not just its method names. Register the new application origin where required and test real visitors after deployment. Do not copy platform credentials into client JavaScript to bypass a missing integration. Sources: - [Export and hosting guide](https://uvilno.com/guides/how-to-export-and-host-your-ai-website) - [Uvilno public SDK documentation](https://uvilno.com/docs) ### What does a public app blueprint demonstrate? Canonical: https://uvilno.com/answers/are-public-templates-real-customer-apps A blueprint demonstrates a structure, routes, data fields and interactions, not proof that a customer app is deployed or benchmarked. Uvilno distinguishes examples from consented community projects. Review the preview's data and service labels, then prepare a brief rather than assuming each feature is connected. A blueprint can make architecture concrete: a task app might show a list, detail route, account view and collection explorer. Its preview should identify local demonstration data and avoid pretending to send email, charge a card or access private customer records. Remixing begins a separately owned project or prepares a brief, according to the action shown. It does not transfer another creator's records, secrets or paid entitlement. Only explicitly published community material should appear in the public gallery; a private share link is not automatic indexing consent. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### What is safe to prototype in a medical booking site? Canonical: https://uvilno.com/answers/can-ai-build-a-medical-booking-portal Prototype service information and an appointment-interest journey before handling medical records. Uvilno's managed collections do not establish healthcare compliance or suitability. Do not collect patient histories, diagnoses or sensitive documents without a separately reviewed system; an interest form must not claim a confirmed clinical booking. Use fictional data and approved public clinic details during design. A visitor can explore services and request a reply without entering symptoms or a medical history. State whether the form records an inquiry or connects to an actual reviewed appointment system. Sensitive patient accounts introduce legal, privacy, security and operational requirements beyond a generic app template. Get specialist review for the relevant jurisdiction and systems before production. A premium-looking dashboard, account page or encryption claim is not evidence of a compliant patient-record workflow. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### What makes an AI builder benchmark credible? Canonical: https://uvilno.com/answers/how-to-read-ai-builder-benchmark-claims A benchmark states the prompts, tool versions, model settings, attempts, costs, runtime checks and limitations, and publishes results. Uvilno's SDK and recovery checks do not establish a fifty-build contest or winner. Unmeasured completion rates, edit latency and competitor scores should remain unknown rather than invented. Compare equivalent tasks under comparable conditions. A static landing page and a persistent CRM have different acceptance criteria, and a working screenshot can hide a broken data flow. Define success before running the test, record failures and preserve the actual artifacts needed to review the result. Separate authored demos, mocked unit tests, real integration calls and production checks. Uvilno's recorded evidence proves the specific flows exercised, including persistence and a bounded static repair, but does not measure every possible app or independently rank competitors. Prefer a transparent unknown to an attractive fabricated score. Sources: - [Recorded checks and benchmark methodology](https://uvilno.com/benchmarks) ### Will AI-generated pages automatically rank first in search? Canonical: https://uvilno.com/answers/will-ai-generated-pages-rank-first-on-google No builder can guarantee first place, indexing or AI citation for every query. Uvilno supports pages, metadata and exports, but search visibility depends on accessible content and search-engine decisions. Verify canonicals, links and crawl access, publish information, and treat sitemap or IndexNow acceptance as notification. Search engines evaluate the live published site, not merely the builder preview. Check that public pages return successful responses, have distinct titles and accurate canonical URLs, and render their important content without requiring authentication. Keep private application routes and customer data outside public indexing. Structured data should describe visible supported facts. A machine-readable file, FAQ schema or a paid plan does not force an engine to cite or rank the site. Review actual search-console reports over time and avoid inventing testimonials or benchmark claims as a shortcut to authority. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Who funds AI requests inside a generated app? Canonical: https://uvilno.com/answers/who-pays-for-generated-app-ai-requests Managed Uvilno.ai requests consume the creator's studio allowance, subject to visitor, IP, project and owner admission limits. Each response is capped at 600 output tokens. An AI feature therefore needs a product scope and failure states; it is not an unlimited model endpoint for visitors. Separate the builder's generation request from the app's later inference. A generated AI helper can continue making permitted requests when real visitors use it, so its operating budget matters after the frontend is saved. Never describe those calls as free simply because the visitor did not paste an API key. Design short outputs, restrict the feature to its intended job and preserve input when a request is denied. Avoid storing sensitive prompts unnecessarily, and validate structured results before saving them. Usage limits protect the service but do not replace a thoughtful product boundary. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Does copying a website's style migrate its application? Canonical: https://uvilno.com/answers/can-website-style-copying-migrate-an-app A reference can guide typography, layout and interaction direction, but cannot migrate source, customer data, credentials or business processes. Uvilno's style-reference and import workflows serve different purposes. Use only material you may provide, describe the behavior and verify any rebuilt flow against its service capabilities. Public pages reveal a rendered interface, not the backend contract behind it. A screenshot cannot establish authorization, payment fulfillment or data ownership. Treat visual reference as design input and write the application's routes, records and failure behavior in your own brief. If you own the source, an authorized repository import may preserve more structure than reconstructing a public page. Even then, service credentials, customer data and identity migration remain separate tasks. Do not copy another business's protected branding or claim a clone is a completed operational migration. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Does restoring a website version rewind customer data? Canonical: https://uvilno.com/answers/does-rollback-restore-customer-database Restoring a Uvilno website version restores its preview and design snapshot; it does not rewind customer records or completed external operations. Review schema compatibility before rollback. Keep a data recovery plan, and never assume a visual version selector reverses payments, account changes or database writes. A saved code version and a live data store evolve independently. An older interface may expect a field or route that no longer matches current records. Inspect that contract before restoring and avoid destructive corrections made solely to fit a historical screen. For a real incident, identify the time and scope of the bad operation, preserve evidence and use the actual data recovery process. Draft settings can remain pending separately from the displayed version. Explain clearly which part of the system each recovery action changes. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) - [GitHub and recovery guide](https://uvilno.com/guides/github-sync-and-version-recovery) ### Where does generated-app media storage live? Canonical: https://uvilno.com/answers/are-uploaded-app-media-files-stored-on-server Uvilno's generated-app storage helper keeps visitor media on the device; it is distinct from creator-uploaded project assets and hosted collection records. An avatar does not prove a server upload or cross-device backup. Specify the storage boundary and test another device before promising persistent document access. Several different things can look like an upload: a creator image included in a website, a visitor avatar stored locally, or a document saved to an external service. Name the intended owner, retention and access behavior rather than using one vague upload requirement. Do not put sensitive documents into a prototype based on a misleading cloud-storage label. Browser storage may be unavailable, cleared or constrained. If a real server-backed file service is required, treat it as a separate supported integration and verify authorization, size limits and deletion. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### How do public catalogs differ from private visitor records? Canonical: https://uvilno.com/answers/can-generated-apps-use-public-shared-records Uvilno distinguishes private visitor-owned collection rows from public-read catalog data. Public reading does not grant writing, and an Admin view cannot override ownership. Choose the access contract, test separate identities and avoid placing sensitive information into a shared catalog merely to simplify a generated interface. A product catalog may legitimately be readable by every visitor, while a cart, draft inquiry or private task belongs to one account. Model these as different records and operations rather than hiding sensitive fields only in the UI. Server permissions must enforce the difference. The owner App Data manager has its own authenticated management path. That does not mean an ordinary visitor can perform every owner operation through the generated site. Test list, detail, create and update behavior with signed-out and separate signed-in visitors. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### What must an AI-generated CRM prove before launch? Canonical: https://uvilno.com/answers/how-to-verify-ai-crm-before-launch A CRM must prove records, references, ownership, filters and failure states, not just charts. Uvilno can supply typed collections, real CRUD and transactional activity rules. Test one complete customer-to-task workflow with separate visitors, reloads and conflicting edits before treating a generated CRM as ready software. Make the displayed metrics depend on actual returned rows. A pipeline chart fed by disconnected demo arrays can look convincing while every real create or update action is broken. Clearly label fictional seeds and keep real customer information out of early tests. Define how users find a customer, add a task, change its status and return later. Inspect both the interface and the owner data manager, and test a failed or conflicting save. Avoid broader organization permissions or email automation claims unless those capabilities are actually implemented. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ### Should saying thanks change project files? Canonical: https://uvilno.com/answers/can-a-chat-message-change-files-accidentally A conversational acknowledgment should not initiate generation, modify files or consume model allowance. Uvilno routes replies separately from build and edit requests. Ambiguous instructions still need clear intent, so describe the change explicitly and inspect the run state rather than assuming every message requests code. A chat composer serves both conversation and work. Acknowledgments such as thank you or got it are different from remove a button or fix a failing form. The ingestion guard can return a local professional reply without reserving a build or invoking the provider. Do not combine an important edit with vague praise and expect targeting to be obvious. State the exact element, route and desired behavior, optionally using a context mention. If a message unexpectedly starts work, keep the previous version and inspect the captured request before retrying. Sources: - [Uvilno public SDK documentation](https://uvilno.com/docs) ## Authored app blueprint directory ### Meridian CRM Canonical: https://uvilno.com/templates/full-stack-crm A relationship-led sales workspace with contact records, deal stages, follow-up tasks and an auditable activity view. Keep contact context beside the next commercial decision. The prepared build connects records to private project accounts, not a shared demo array. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: deals, contacts, tasks, activity_logs. ### Margin Career Studio Canonical: https://uvilno.com/templates/ai-resume-analyzer A resume-review product plan with saved analyses, career goals and a real managed AI integration after building. Review role-specific evidence and preserve each draft. The concept preview never uploads a resume or claims to run AI; the blueprint requests actual Uvilno.ai inference with explicit consent. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: resumes, reviews, goals. ### Object Supply Canonical: https://uvilno.com/templates/stripe-commerce-store A considered storefront with product filtering, a persistent local concept cart and an inventory/admin build contract. Browse a small collection and test cart state. The prepared app uses managed inventory records and Stripe test Checkout; a local cart is not a payment or fulfilled order. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: products, orders, inventory_logs. ### Aster Appointment Desk Canonical: https://uvilno.com/templates/medical-booking-portal An appointment-request portal blueprint with account pages, practitioner discovery and deliberately minimal non-clinical records. Only non-sensitive appointment preferences belong in this concept. Do not enter medical records. Requests require practice confirmation and are never presented as booked clinical care. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: practitioners, requests, availability. ### Emberline Arcade Canonical: https://uvilno.com/templates/survival-arcade-game A playable local survival exercise and a multi-page game blueprint with personal runs, cosmetics and a reviewed leaderboard contract. Play a short client-side movement challenge. Scores in this preview stay on this device. A public leaderboard needs the requested separate pseudonymous score policy; no universal frame-rate promise is made. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: runs, cosmetics, preferences. ### Found Residence Canonical: https://uvilno.com/templates/real-estate-marketplace A property discovery and saved-listing blueprint with a working mortgage estimate and private enquiry records. Compare a payment estimate and save a home locally. The calculation excludes tax, fees and insurance; listings are labelled fictional concept content, not available property offers. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: properties, saved_listings, enquiries. ### Ember & Rye Orders Canonical: https://uvilno.com/templates/bakery-ordering-system A bakery counter and ordering-plan blueprint with product choices, order records and a real queue interface concept. Move a fictional order through the local queue. The prepared build asks for persisted order state and test payment wiring, never fabricated kitchen delivery or live availability. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: products, orders, subscriptions. ### Atelier Fieldwork Canonical: https://uvilno.com/templates/architecture-monograph An architectural project archive with a light-study control, materials library and commission enquiry plan. Explore the editorial archive and change the concept daylight. All projects are fictional studies; a prepared build uses supplied imagery and real enquiry storage. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: projects, materials, enquiries. ### Relay Project Space Canonical: https://uvilno.com/templates/project-management-saas A multi-project task workspace with private records, status filtering, accountable milestones and project activity. Create, filter and move local tasks. The build contract keeps each signed-in visitor’s work private and requests a declared activity automation. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: projects, tasks, milestones. ### Tempo Training Canonical: https://uvilno.com/templates/fitness-coaching-app A personal training planner with session records, exercise notes and a coach-discovery workflow. Organize a personal routine without claiming medical or performance outcomes. Real coaching and payment integrations need explicit configuration and review. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: workouts, exercises, sessions. ### Common Ground Learning Canonical: https://uvilno.com/templates/course-learning-portal A course catalog and personal learning plan with saved lessons, study notes and honest completion states. Filter the fictional learning catalog and save a lesson locally. Completion reflects only a user action, not certification or verified educational credit. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: courses, lessons, notes. ### Table Twelve Canonical: https://uvilno.com/templates/restaurant-reservation-app A restaurant enquiry and table-planning blueprint with a visible request queue and account-safe preferences. Update a fictional request queue. A restaurant must confirm availability; this blueprint never treats an enquiry or local state as a confirmed reservation. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: menus, requests, preferences. ### Good Company Studio Canonical: https://uvilno.com/templates/creator-membership-hub A creator resource library, saved reading list and membership-interest workflow with isolated account planning. Save concept resources on this device. Real gated material needs a reviewed authorization policy; the preview does not grant memberships or process subscriptions. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: resources, saved_resources, interests. ### Ledger Personal Canonical: https://uvilno.com/templates/finance-budget-dashboard A private household planning tool with a working projection, category records and transparent assumptions. Adjust a hypothetical budget and save planning records. It is not financial advice, bank connectivity or a verified accounting ledger. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: transactions, categories, goals. ### Interval Support Desk Canonical: https://uvilno.com/templates/help-desk-support-tool A ticket triage app plan with statuses, response notes and scoped activity records. Move fictional tickets through triage. The blueprint records replies internally; actual email delivery requires an approved connected mail service. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: tickets, notes, activity_logs. ### Assembly Calendar Canonical: https://uvilno.com/templates/event-registration-hub An event discovery and registration-interest plan with saved sessions and clear capacity checks. Save a fictional session and test a registration-interest record. Attendance and capacity require server validation; saving interest does not issue a ticket. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: events, registrations, updates. ### Stockroom Operations Canonical: https://uvilno.com/templates/inventory-purchasing-dashboard An inventory and restock workspace with quantity fields, product filtering and a purchase-request queue. Organize fictional restock requests. The prepared build uses atomic inventory rules and rejects invalid state; no supplier order is placed by this preview. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: products, purchase_requests, suppliers. ### Kit Library Canonical: https://uvilno.com/templates/rental-equipment-booking An equipment catalog and hire-request tool with date preferences, saved kits and availability boundaries. Build a local saved-kit list. The prepared request flow must validate overlapping dates; a saved request is not confirmed equipment availability. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: equipment, requests, kits. ### Footnote Research Canonical: https://uvilno.com/templates/ai-research-workspace A research-note and source-review app plan with saved questions and a real opt-in managed AI summary contract. Prepare a bounded source-summary prompt. This preview does not browse or infer; the built app must display limitations and validate AI output before persistence. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: questions, sources, notes. ### Caretaker Portal Canonical: https://uvilno.com/templates/property-maintenance-portal A property maintenance-request workspace with issue status, property records and non-sensitive resident notes. Track a fictional repair request through local status. The blueprint excludes shared resident data until a reviewed authorization model exists. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: requests, properties, visits. ### Open Practice Jobs Canonical: https://uvilno.com/templates/job-board-marketplace A focused job directory and saved-opportunity workspace with application-interest records. Filter fictional opportunities and maintain a local application list. No application is submitted to an employer without a real approved integration. Concept previews use browser-local demonstration data; preparing a brief does not start generation. Declared collections: jobs, saved_jobs, applications. ## Editable full-stack prompt library ### Sales pipeline CRM Canonical: https://uvilno.com/prompts/sales-pipeline-crm Help an independent consultant move a qualified lead from first contact to a won or lost opportunity. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Client follow-up tracker Canonical: https://uvilno.com/prompts/client-follow-up-tracker Keep the next promised action visible for each active client without inventing email delivery. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Creative agency project CRM Canonical: https://uvilno.com/prompts/creative-agency-project-crm Give a small agency an honest view of project status, scope and pending decisions. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Freelance proposal manager Canonical: https://uvilno.com/prompts/freelance-proposal-manager Organize proposal drafts and decisions without pretending to send documents or collect signatures. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Customer onboarding workspace Canonical: https://uvilno.com/prompts/customer-onboarding-workspace Track a consultant's own onboarding checklists for new clients, with completion tied to actual task records. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Account renewal calendar Canonical: https://uvilno.com/prompts/account-renewal-calendar Help a service operator see upcoming contract reviews without claiming automated renewals or live billing. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Service request CRM Canonical: https://uvilno.com/prompts/service-request-crm Collect and manage private service requests with a clear distinction between requested and completed work. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Recruiting candidate tracker Canonical: https://uvilno.com/prompts/recruiting-candidate-tracker Let an individual recruiter organize permission-cleared fictional candidate records without automated hiring decisions. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Partnership deal room Canonical: https://uvilno.com/prompts/partnership-deal-room Track a business owner's partnership discussions, obligations and next decisions. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 resume reviewer Canonical: https://uvilno.com/prompts/ai-resume-reviewer Help a job seeker identify specific improvements in text they supply, without inventing qualifications or making hiring decisions. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 study plan builder Canonical: https://uvilno.com/prompts/ai-study-plan-builder Turn a learner's topic and available time into a short, editable study plan using actual model output. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 meeting action extractor Canonical: https://uvilno.com/prompts/ai-meeting-action-extractor Extract proposed actions only from supplied meeting notes and require user review before saving. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 recipe notebook Canonical: https://uvilno.com/prompts/ai-recipe-notebook Help a home cook draft recipes from supplied ingredients while stating that allergy and safety checks remain the user's responsibility. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 product copy workbench Canonical: https://uvilno.com/prompts/ai-product-copy-workbench Draft concise product copy from supplied facts without fabricating reviews, metrics, endorsements or availability. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 language practice journal Canonical: https://uvilno.com/prompts/ai-language-practice-journal Give a learner short feedback on their own writing, with transparent AI limitations and editable corrections. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 support reply drafter Canonical: https://uvilno.com/prompts/ai-support-reply-drafter Draft support responses from supplied issue details without claiming access to customer accounts or sending messages. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 workout planning notebook Canonical: https://uvilno.com/prompts/ai-workout-planning-notebook Help an adult organize general fitness ideas from supplied preferences without medical advice, diagnosis or injury guarantees. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 research question organizer Canonical: https://uvilno.com/prompts/ai-research-question-organizer Turn supplied research notes into proposed questions, preserving the distinction between evidence and model suggestions. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Ceramics test-checkout store Canonical: https://uvilno.com/prompts/ceramics-test-checkout-store Let visitors explore a small studio's supplied ceramic pieces and test an explicitly non-live purchase journey. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Coffee subscription planner Canonical: https://uvilno.com/prompts/coffee-subscription-planner Help a roastery customer compare supplied beans and plan a delivery cadence without claiming active recurring charges. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Independent bookshop catalog Canonical: https://uvilno.com/prompts/independent-bookshop-catalog Make a supplied catalog easy to search, shortlist and evaluate before a test checkout. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Design object store Canonical: https://uvilno.com/prompts/design-object-store Present supplied furniture and objects with useful dimensions, finish selections and clear test-mode commerce. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Digital resource test store Canonical: https://uvilno.com/prompts/digital-resource-test-store Show original digital resources with license descriptions without fabricating download entitlements after test payment. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Skincare product information store Canonical: https://uvilno.com/prompts/skincare-product-information-store Organize supplied cosmetic products and ingredient facts without medical claims or invented clinical results. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Art print edition store Canonical: https://uvilno.com/prompts/art-print-edition-store Help an artist present supplied works, available sizes and edition information without inventing scarcity. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Local florist order request Canonical: https://uvilno.com/prompts/local-florist-order-request Prepare a bouquet request from supplied options, with a test payment demonstration rather than confirmed fulfillment. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Storefront with inventory review Canonical: https://uvilno.com/prompts/inventory-admin-storefront Give a creator a product catalog plus a reviewed management view, keeping actual authorization separate from a preview role. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Orbital survival arcade Canonical: https://uvilno.com/prompts/orbital-survival-arcade Create a playable dodge-and-collect loop with keyboard and touch controls rather than a decorative game mockup. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Paddle breaker challenge Canonical: https://uvilno.com/prompts/paddle-breaker-challenge Build a ball-and-paddle challenge whose win and loss conditions follow real collisions. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Top-down delivery racer Canonical: https://uvilno.com/prompts/top-down-delivery-racer Create an original route-and-time game without real logistics or delivery claims. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Memory card garden Canonical: https://uvilno.com/prompts/memory-card-garden Make an original matching game with deterministic pair logic and an understandable completion state. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Rhythm timing practice Canonical: https://uvilno.com/prompts/rhythm-timing-practice Create a visual timing challenge using original or permission-cleared sound, with explicit user-enabled audio. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Grid puzzle expedition Canonical: https://uvilno.com/prompts/grid-puzzle-expedition Build a grid-based puzzle with meaningful legal moves and a replayable level sequence. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Tower defense sketch Canonical: https://uvilno.com/prompts/tower-defense-sketch Create a bounded original strategy game with enemies, a path and actual resource spending. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Typing focus arcade Canonical: https://uvilno.com/prompts/typing-focus-arcade Build a practice game that scores the supplied text accurately without collecting sensitive keystrokes. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Mini-golf physics lab Canonical: https://uvilno.com/prompts/mini-golf-physics-lab Create a small original physics challenge with aim, power and understandable stroke counting. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Dental appointment request portal Canonical: https://uvilno.com/prompts/dental-appointment-request-portal Let a visitor request a consultation without collecting medical history or implying confirmed clinical availability. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Wellness class reservation planner Canonical: https://uvilno.com/prompts/wellness-class-reservation-planner Organize supplied classes and visitor interest without representing unverified capacity as live. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Home repair service portal Canonical: https://uvilno.com/prompts/home-repair-service-portal Help homeowners describe a non-emergency repair and track the request state. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Barber appointment request Canonical: https://uvilno.com/prompts/barber-appointment-request Show supplied services and allow a preferred date and time request without claiming an active scheduling integration. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Photography session inquiries Canonical: https://uvilno.com/prompts/photography-session-inquiries Let a photographer collect session preferences and review inquiries as actual saved records. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Equipment rental request portal Canonical: https://uvilno.com/prompts/equipment-rental-request-portal Help visitors shortlist equipment and request a rental period while keeping availability subject to review. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Pet grooming request hub Canonical: https://uvilno.com/prompts/pet-grooming-request-hub Collect a grooming service preference without veterinary advice or invented scheduling availability. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Tutoring session planner Canonical: https://uvilno.com/prompts/tutoring-session-planner Let a learner request help by subject and review the planned sessions they own. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Event venue inquiry portal Canonical: https://uvilno.com/prompts/event-venue-inquiry-portal Support a venue shortlist and date inquiry without claiming actual venue inventory or a reservation. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 monograph library Canonical: https://uvilno.com/prompts/architecture-monograph-library Present supplied architectural projects through a readable index and original project stories. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Industrial design process portfolio Canonical: https://uvilno.com/prompts/industrial-design-process-portfolio Explain a designer's supplied research, prototypes and final objects without fabricated clients or awards. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Interior materials journal Canonical: https://uvilno.com/prompts/interior-materials-journal Let visitors explore actual supplied interior studies and collect a private material shortlist. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Landscape studio project index Canonical: https://uvilno.com/prompts/landscape-studio-project-index Show place, season and design intent using supplied landscape projects rather than generic scenery. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Brand studio case-study system Canonical: https://uvilno.com/prompts/brand-studio-case-study-system Present supplied brand work with a clear brief, decision and result story without inventing performance metrics. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Furniture design collection Canonical: https://uvilno.com/prompts/furniture-design-collection Explain original furniture pieces through material, dimension and process details, with no fake purchasing flow. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Photographic editorial archive Canonical: https://uvilno.com/prompts/photographic-editorial-archive Organize permission-cleared image series and meaningful captions without copying another photographer's work. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Motion designer reel library Canonical: https://uvilno.com/prompts/motion-designer-reel-library Make supplied reels and process notes easy to explore without autoplaying audible media. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Craft studio commission portfolio Canonical: https://uvilno.com/prompts/craft-studio-commission-portfolio Connect supplied craft projects to a concise commission inquiry without promising availability or lead times. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Real estate shortlist app Canonical: https://uvilno.com/prompts/real-estate-shortlist-app Help a buyer compare permission-cleared fictional properties and save private notes, without brokerage or valuation claims. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Local maker directory Canonical: https://uvilno.com/prompts/local-maker-directory Help visitors discover supplied maker profiles and save a private set of references. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Remote job board workspace Canonical: https://uvilno.com/prompts/remote-job-board-workspace Organize supplied job information and the visitor's own application tracker without claiming employer integrations. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Specialist consultant directory Canonical: https://uvilno.com/prompts/specialist-consultant-directory Present approved consultant information and allow visitors to compare fields of expertise. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Accessible venue directory Canonical: https://uvilno.com/prompts/accessible-venue-directory Help visitors compare supplied access information while avoiding unverified accessibility certification. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Rental workspace directory Canonical: https://uvilno.com/prompts/rental-workspace-directory Compare supplied desk and studio options without claiming live availability or a lease transaction. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Independent course directory Canonical: https://uvilno.com/prompts/independent-course-directory Let learners compare supplied course descriptions and maintain their own learning shortlist. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Used equipment listing board Canonical: https://uvilno.com/prompts/used-equipment-listing-board Offer a clearly scoped listing catalog and private inquiry tracker without acting as a payment intermediary. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Community resource index Canonical: https://uvilno.com/prompts/community-resource-map-index Organize reviewed local resources by category without pretending a location graphic is a connected map. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Personal budget scenario tool Canonical: https://uvilno.com/prompts/personal-budget-scenario-tool Help a person explore their entered income and spending assumptions without account access or financial advice. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### SaaS revenue scenario calculator Canonical: https://uvilno.com/prompts/saas-revenue-scenario-calculator Model subscription assumptions without representing projections as actual revenue or connected billing. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Freelance cash-flow planner Canonical: https://uvilno.com/prompts/freelance-cashflow-planner Let a freelancer organize expected receipts and expenses without pretending to access bank accounts. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Invoice register dashboard Canonical: https://uvilno.com/prompts/invoice-register-dashboard Track supplied invoice records as an organizational tool without claiming issuance, tax compliance or payment collection. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Mortgage assumption calculator Canonical: https://uvilno.com/prompts/mortgage-assumption-calculator Compute principal-and-interest estimates from entered assumptions with transparent exclusions. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Project margin planner Canonical: https://uvilno.com/prompts/project-margin-planner Help a studio estimate margin from its own project fee and cost entries. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Subscription spend auditor Canonical: https://uvilno.com/prompts/subscription-spend-auditor Let an individual record recurring tool costs and renewal dates without reading bank or email accounts. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Crypto watchlist notebook Canonical: https://uvilno.com/prompts/crypto-watchlist-notebook Organize a user's manually entered asset notes without pretending to stream market prices or execute trades. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Business KPI input dashboard Canonical: https://uvilno.com/prompts/business-kpi-input-dashboard Visualize actual user-entered business measurements with definitions and reporting periods. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Self-paced course workspace Canonical: https://uvilno.com/prompts/self-paced-course-workspace Help a learner work through supplied lessons and record their own progress without unsupported certification. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Flashcard review notebook Canonical: https://uvilno.com/prompts/flashcard-review-notebook Let a learner create and review cards from supplied material without pretending the content is professionally verified. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Language vocabulary shelf Canonical: https://uvilno.com/prompts/language-vocabulary-shelf Organize a learner's words, examples and review decisions in private saved records. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Research reading planner Canonical: https://uvilno.com/prompts/research-reading-planner Help a student prioritize permission-cleared readings and keep notes separate from completion state. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Teacher resource organizer Canonical: https://uvilno.com/prompts/teacher-resource-organizer Allow one educator to maintain their own resource library without exposing student records. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Practice quiz runner Canonical: https://uvilno.com/prompts/practice-quiz-runner Run supplied practice questions with deterministic answer checking and no fabricated grading authority. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Workshop materials portal Canonical: https://uvilno.com/prompts/workshop-materials-portal Make a supplied workshop agenda and materials easy to navigate without claiming access control beyond the actual app identity. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Portfolio learning journal Canonical: https://uvilno.com/prompts/portfolio-learning-journal Help a learner document completed work and reflections without inventing credentials or publishing private entries. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Exam revision calendar Canonical: https://uvilno.com/prompts/exam-revision-calendar Organize a learner's entered topics and dates into a realistic private revision plan. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Club interest portal Canonical: https://uvilno.com/prompts/club-interest-portal Collect real membership interest without presenting submission as approved membership. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Volunteer opportunity board Canonical: https://uvilno.com/prompts/volunteer-opportunity-board Help visitors discover supplied opportunities and maintain their own expression of interest. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Creator membership outline Canonical: https://uvilno.com/prompts/creator-membership-outline Describe supplied membership content and test an account journey without pretending subscriptions are activated. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Neighborhood event calendar Canonical: https://uvilno.com/prompts/neighborhood-event-calendar Publish reviewed event details and let visitors save a private attendance plan. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Professional resource circle Canonical: https://uvilno.com/prompts/professional-resource-circle Organize permission-cleared professional resources without implying credentials or endorsement. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Donation interest information hub Canonical: https://uvilno.com/prompts/donation-interest-information-hub Explain a supplied organization's work and collect inquiries without fabricating donations or charity status. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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 proposal workspace Canonical: https://uvilno.com/prompts/community-proposal-workspace Let an individual maintain project proposals and review notes without pretending there is a connected voting system. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Peer mentoring interest board Canonical: https://uvilno.com/prompts/peer-mentoring-interest-board Collect a visitor's mentoring interests without exposing a public member directory by default. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Creative collective project hub Canonical: https://uvilno.com/prompts/creative-collective-project-hub Present approved collective work while keeping contributor claims and project ownership accurate. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Independent magazine index Canonical: https://uvilno.com/prompts/independent-magazine-index Make supplied articles discoverable through topic, author and meaningful summaries. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Newsletter archive browser Canonical: https://uvilno.com/prompts/newsletter-archive-browser Present a supplied newsletter archive and collect real interest without claiming email delivery. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Podcast episode library Canonical: https://uvilno.com/prompts/podcast-episode-library Organize supplied episodes, transcripts and listening notes with accessible playback controls. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Technical documentation library Canonical: https://uvilno.com/prompts/technical-documentation-library Publish supplied technical explanations with useful navigation and no fabricated supported API methods. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Travel field-notes archive Canonical: https://uvilno.com/prompts/travel-field-notes-archive Present an author's supplied place notes without inventing safety claims, prices or current opening hours. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Recipe editorial collection Canonical: https://uvilno.com/prompts/recipe-editorial-collection Organize original supplied recipes with practical ingredient and serving controls. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Oral history listening room Canonical: https://uvilno.com/prompts/oral-history-listening-room Make consented recordings and transcripts browsable without exposing restricted personal information. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Book review reading shelf Canonical: https://uvilno.com/prompts/book-review-reading-shelf Publish original supplied reviews and let visitors maintain a separate private reading shelf. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Design research publication index Canonical: https://uvilno.com/prompts/design-research-publication-index Explain supplied research projects and sources without treating editorial conclusions as independent benchmark wins. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Inventory reorder workspace Canonical: https://uvilno.com/prompts/inventory-reorder-workspace Track a small operator's entered stock and reorder decisions without claiming a connected warehouse. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Maintenance request dashboard Canonical: https://uvilno.com/prompts/maintenance-request-dashboard Let a facility manager organize their own maintenance requests and actual review states. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Release checklist manager Canonical: https://uvilno.com/prompts/release-checklist-manager Track release preparation without pretending the app can deploy code or access production systems. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### API incident notebook Canonical: https://uvilno.com/prompts/api-incident-notebook Record manually supplied incidents and investigation notes without fabricated live observability. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Equipment checkout register Canonical: https://uvilno.com/prompts/equipment-checkout-register Let an individual organize equipment loans and returns without a false multi-user permission model. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Supplier review workspace Canonical: https://uvilno.com/prompts/supplier-review-workspace Help a buyer compare supplied supplier notes without claiming verified ratings or automated procurement. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Bug triage workbench Canonical: https://uvilno.com/prompts/bug-triage-workbench Organize reproducible issues, severity and next action without pretending to modify a remote repository. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Content approval queue Canonical: https://uvilno.com/prompts/content-approval-queue Let one editor review their own content drafts with a clear distinction between approval records and actual publishing. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ### Lab sample organization tool Canonical: https://uvilno.com/prompts/lab-sample-organization-tool Organize fictional non-clinical sample labels and review notes without regulated diagnostic or chain-of-custody claims. Review the route plan, typed collections, design direction and acceptance checks before building. Editable blueprint, not a claim of a generated or tested customer application: 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. ## Public SDK documentation ### A declared schema, shared by every page The generated project declares typed collections in data/schema.json. Supported fields are string, number, boolean, date and reference; references name another declared collection. Required fields, nullable values and string options are validated on the server. The saved website version pins the applied schema. Private collections follow the real project visitor identity. A deliberately public_read collection permits shared catalog reading; it does not make every visitor-created private row public. Start real orders, bookings and leads empty. Fictional demonstration collections require 8–15 records with a disclosure. Do not store sensitive clinical or payment-card data in a starter app. ### Uvilno.db: CRUD with acknowledged writes The controller installs window.Uvilno and window.AppDB into supported generated applications. Uvilno.db(collection) returns a table client. list accepts filter, sort, search, limit and offset; get returns one record or null. create and update return the saved record; remove returns a boolean. Every remote write is project-scoped and validated against the installed schema. The SDK can show optimistic updates, but a successful server acknowledgment establishes persistence. Failed writes roll the local view back and reject the promise. Catch errors, preserve the user's input and offer retry. A device cache is not evidence of a successful database save. ### Subscriptions and App Data subscribe(listener, query?) sends refreshed rows to the listener, refreshes after local writes and polls every four seconds while active for other changes. It returns a cleanup function. This is a polling subscription, not a WebSocket guarantee. Derive tables, totals and charts from the same returned rows rather than keeping a disconnected second dataset. The creator opens App Data beside Inspect & Edit to inspect actual collection rows, search, create, edit and delete supported records. The owner view refreshes while open and respects revision conflicts. It does not expose locked source or make a generated visitor an administrator. ### Project accounts are separate from the builder Uvilno.auth.user() returns the current project visitor or null. signIn accepts a configured Google, GitHub or Discord provider, or email/password credentials. register requires an explicit terms decision and may require email confirmation. signOut clears the app identity, not the creator's Uvilno account. The project service controls the session; generated code never receives provider secrets or the platform's service-role key. The Guest/Member/Admin preview control changes presentation only. auth.role(), auth.setRole() and data-role sections help inspect layouts; they cannot grant database permissions, mutate the real identity or implement a multi-tenant authorization policy. The owner-preview helper is unavailable as a role-grant mechanism on exported apps. ### Actual in-app inference, with explicit limits When the managed AI connector is enabled, Uvilno.ai.ask(prompt, {system?, temperature?}) returns actual text. Uvilno.ai.json(prompt, schemaDescription) returns a parsed object or array. The server requires an isolated app identity and enabled connector, charges the creator's metered studio allowance and limits each response to 600 output tokens. Input, deadline and visitor/IP/project/owner admission limits also apply. The JSON description guides the model; it is not a general JSON Schema validator. Validate the returned domain fields before rendering or saving them. Handle invalid results, quota failures and network errors explicitly. Never present a canned success message as live inference. ### Transactional rules, local observers schema.automations declares bounded create/update/remove triggers. Approved actions can create a record, update a related record, increment a number or persist an in-app notification. Actions share the record transaction and ownership scope. A failed action rolls the write back; idempotent replays cannot duplicate effects. Actions do not recursively invoke rules, execute arbitrary code, call URLs, send email or grant roles. Uvilno.automations.register and subscribe observe acknowledged browser mutations and return cleanup functions. Reliable server actions belong in the validated schema, not a browser callback. rules() returns installed rule metadata; logs() returns approved persisted activity. App Data → Automations & Logs is the owner's inspection surface. ### Local media and test Checkout Uvilno.storage saves supported generated-app media on the visitor's device. It is distinct from the creator's uploaded project assets and from cloud file storage. Device-local blobs are not a durable team document store, and a local browser permission or storage limit may prevent saving. Uvilno.payments.checkout() opens the configured managed Checkout flow; payments.testMode is true in this release. Stripe Connect authorization and onboarding are explicit. A test receipt is not a real payment, payout or shipment. Before a live commerce release, review provider configuration, webhook handling, tax, fulfillment and data authorization. ### Target the next edit In the Builder composer, type @ and choose an owned page/file, collection or inspected element. Actual examples are @index.html, @js/app.js, @db:tasks and @selected-element. References become removable pills; Arrow keys and Enter select, Escape dismisses. The owned context response includes paths and collection labels, not locked source or customer records. The server validates those references against the saved version, then combines the private repository map with bounded affected-file context. Mapped direct text, link and color changes in Inspect & Edit use no model allowance. A targeted AI instruction is a normal generation request. Neither context mentions nor the repo map guarantee a fixed edit time. ### Observe, verify and recover A controller-authored probe checks boot exceptions, broken images, invalid routes, overflow and data hydration. Observations are bounded metadata, not private page values or source. They can accompany the next edit, but a browser message cannot establish a verified build or bypass authorization. A separately limited, platform-funded repair can reproduce a native static-project runtime crash, change at most two relevant files using one free-model response, and browser-check before saving. Existing Next.js verification remains separate. Failed checks preserve the saved version. There is no universal no-error or unlimited free-repair promise. ### Own source; account for services The $4.99 one-time project unlock permits source inspection, download and supported GitHub source push. Plus, Pro and Ultra have their existing source entitlements. GitHub import, push and pull require explicit repository authorization; do not promise two-way sync with an unconnected account. Source exports include the applicable frontend runtime, declared schema, referenced assets, fonts and licenses. They do not contain private customer records, provider credentials or an independent hosted backend. Exported authentication requires registering the final HTTPS origin, and managed data/auth/AI/payments remain Uvilno-hosted dependencies unless migrated or replaced. Website version rollback does not roll back customer data. ## Open evaluation protocol Six recorded Uvilno integration and recovery checks are available at /benchmarks. The 50-case cross-vendor generation protocol is published but not run; completion rates and median edit latency remain unmeasured. Download /benchmarks-2026.csv. ## Published guide content ### Build a Full-Stack SaaS with Database, Auth and a Tested User Journey Canonical: https://uvilno.com/guides/how-to-build-a-full-stack-saas-with-database-and-auth Updated: 2026-10-27 Plan typed records, isolated accounts, real CRUD, transactional automations and optional AI in Uvilno. Verify persistence and payment boundaries before launch. #### Define one complete product loop Start with a task someone will repeat: sign in, find a customer, record the next follow-up and return later to see it. A small SaaS does not need every dashboard pattern at once. Describe the audience, the records that person owns and the result they expect after each action. Keep a separate list of exclusions such as organization sharing, calendar synchronization or live subscriptions. This gives the builder an implementable scope and gives you a concrete way to decide whether the result is useful beyond its first screen. Name the project for your own organization without turning that name into the entire AI request. Opening a draft or adjusting its brief does not start generation. Write the actual product requirements in the conversation, use Plan when the scope needs discussion, and approve a build deliberately. Planning, enhancement and generation may consume their documented usage. There is no reliable universal ten-minute promise for an application with data, identity and operational requirements; the time needed depends on the specific work and the checks it must pass. - Choose one repeatable task. - Write its success and failure outcomes. - Define private versus deliberately shared data. - List integrations and features excluded from the first release. #### Declare the records and routes before building views For a client tracker, begin with customers and followups. Customers might contain a required name and optional company, while followups contain a title, a supported status, a date and a reference to a customer. Declare the schema, field types and reference relationship in the project’s data contract. Require private visitor ownership unless the use case deliberately needs a public catalog. Keep real transactional collections empty at launch; use fictional demonstration rows only when clearly disclosed and separated from real customer activity. Map the routes to those records. Home explains the product, Login and Register establish the app identity, Customers exposes the list, a detail route shows context, Activity explains committed changes and Profile contains supported account controls. Ask for shared navigation and a shared data controller rather than separate disconnected arrays on each page. The contract-first workflow helps subsequent files agree on names and destinations, but it still needs review. A declared route that is never reachable or a field that changes meaning across pages remains an application defect. A bounded client-follow-up contract | Area | First implementation | Acceptance check | | --- | --- | --- | | Customers | Private typed name/company records | A saved edit survives reload | | Follow-ups | Private title/status/date plus customer reference | Invalid or unavailable references fail clearly | | Activity | Scoped entries from declared record actions | One create produces the intended committed entry | | Accounts | Project-specific visitor identity | Another visitor cannot read private rows | #### Connect every record action to the same saved state Ask the generated application to call Uvilno.db for list, get, create, update and remove operations. Its forms should validate input before sending and preserve unsaved values when a write fails. Lists, details and calculated counters should derive from the returned records, with subscriptions refreshing active views. Those subscriptions currently poll the managed service while active; they are not a promise of WebSocket realtime delivery. A local mirror can improve continuity, but it must never be presented as proof that a server write succeeded. Test persistence through the actual interface. Create a recognizable customer, edit one field, navigate away, reload and find the saved result. Remove a disposable record with a meaningful confirmation and verify the list and count update. Try missing required fields, a failed request and a conflicting revision. The owner’s App Data manager offers a separate view of actual collection rows without an AI generation call. Use it to corroborate the result, while remembering that the owner data manager and a generated visitor administration screen are different access paths. Example brief: Keep the customer routes and existing palette. Wire the Add customer drawer to Uvilno.db('customers').create, disable duplicate submission while saving, retain input on failure, and update the subscribed list only after the acknowledged operation. Test creating a customer, reloading and editing its company. #### Verify the real identity and authorization boundary Generated-app accounts must belong to the project, independently of the Uvilno creator account. Test registration, sign-in, the signed-out state and sign-out using disposable visitors. If email confirmation is required, follow the real confirmation process rather than treating an account form as immediate approval. Preserve a clear distinction between the person building the app and the people using it. Signing into a generated app with a different provider account should never silently replace the creator’s platform session or authorize access to the builder workspace. Then test two-account isolation: a second visitor should not see or directly obtain the first visitor's private customer records. The Guest/Member/Admin preview selector changes presentation only and can expose alternate layouts for design review; it does not change the actual app session or database authority. Team administrators, shared organizations and invitation rules require explicit server-side implementation. Do not infer those permissions from a visible management drawer, a hidden button or a client-side role value. Review the authorization model appropriate to your intended users before adding real business information. #### Add one automation whose effect you can trace A useful first automation is a follow-up activity entry. Define the trigger and bounded action in the validated schema: when a follow-up record is created, create a scoped activity row and optionally record an in-app notification. These actions run in the original record transaction with the same ownership constraints. Failed actions roll the write back, and supported idempotent replays must not duplicate effects. This is a dependable narrow contract; it is not arbitrary uploaded code, a recursive workflow engine or an external email and scheduling service. Open App Data and switch to Automations & Logs to inspect the installed rule and committed event metadata. Exercise the trigger once and verify the actual resulting record, not just a toast. Test a permitted failure in a disposable project to understand what the user sees when the transaction cannot complete. Keep sensitive record bodies out of public logs and remember that website version restoration does not rewind customer data. A rule change and a data migration are separate decisions, so preserve a record of the schema version and intended behavior when evolving a live product. #### Use bounded inference only when the product needs it If the product needs a short AI summary or structured suggestion, request the managed AI connector explicitly. Uvilno.ai.ask returns real text, while Uvilno.ai.json returns parsed, bounded JSON for the app to validate. The service requires a real app visitor identity and uses the creator’s metered studio allowance, subject to admission limits and a 600-output-token response ceiling. Design the feature to fit that contract, show real loading and failure states, and avoid replacing a failed call with a hardcoded answer that appears to be genuine analysis. Keep product claims proportional to what inference actually does. A model summary does not prove that customer facts were checked, a web page fetched or professional advice reviewed. Validate required JSON fields and explain missing or unsuitable input before saving a result. Give the visitor an explicit choice to persist generated output and keep private records private. A public website about an AI business does not need inference merely because its description contains the letters AI. Add the service for an actual product task, then measure its usage during a realistic trial. #### Keep Stripe test checkout separate from live entitlement Add a pricing and payment flow only after the application’s core task is useful. Uvilno’s managed Stripe connector is currently in test mode. A successful test checkout can establish a test provider journey, but it is not a real charge, live recurring subscription or automatically correct account entitlement. Label the interface accordingly and avoid claims that a paying customer now has access unless a real, reviewed server workflow establishes that state. Keep product prices, fulfillment rules and failure behavior explicit rather than inferring them from a successful return page. Before live commerce, review provider onboarding, live credentials, webhook signature verification, idempotency, payment failure, cancellation and refunds. The builder’s own $4.99 source unlock and monthly plans are separate from any prices your generated SaaS may eventually charge. Never embed secret provider keys in exported JavaScript or enter real customer card details in a disposable prototype. If live charging remains outside the supported release, omit the live action and document the remaining implementation rather than exposing a button that promises a transaction the application cannot safely complete. - [Plan a configured Stripe integration](/guides/how-to-add-stripe-payments-without-api-keys) #### Inspect the whole journey, then plan the handoff Use @file, @db and the selected-element context when requesting a focused refinement. Describe the current behavior, intended outcome and what must remain. Check the changed control, the next page and an unrelated nearby task after the saved result arrives. The live probe supplies bounded runtime observations, and native static projects may receive a limited free repair after a critical fault is reproduced server-side. Neither that probe nor a successful compile proves an entire application flawless. Review phone behavior, keyboard access, error recovery and the full record lifecycle with someone unfamiliar with the product. When ready for source handoff, review the unlocked package in a clean environment and identify each hosted dependency. Uvilno’s auth, database, inference and payment services do not become independently provisioned infrastructure simply because the frontend exports. Register the final origin where necessary, continue with the supported services or implement a separate replacement, and test the actual deployment before public use. Keep private customer records and credentials out of shared archives. Finish with a maintained list of operational ownership, data retention, deletion and monitoring responsibilities so the product remains understandable after its first successful demonstration. - [Review the export and hosting workflow](/guides/how-to-export-and-host-your-ai-website) - [Compare full-stack builder workflows](/guides/best-full-stack-ai-app-builders-2026) **Can a complete production SaaS be guaranteed in ten minutes?** No. Scope, provider behavior, verification, security requirements and operations determine the work. Start with one useful supported workflow and review the actual outcome. **Can I change records without running the AI?** Supported owner App Data operations and generated Uvilno.db CRUD calls operate on data without a generation turn. Changing the schema or application behavior through AI is a different action. **Does restoring a website version undo customer data?** No. Treat frontend restoration and hosted data changes separately. Review compatibility and any required migration before using an older interface against current records. ### Base44 vs Emergent vs Lovable vs Uvilno: Choose the Full-Stack Workflow Canonical: https://uvilno.com/guides/base44-vs-emergent-vs-lovable-vs-uvilno Updated: 2026-10-28 Compare four app-building workflows through data ownership, authentication, focused edits, inference, exports and operating costs. Separate published features from tested outcomes. #### Choose a boundary you can operate Base44, Emergent, Lovable and Uvilno are worth comparing when an application needs more than static pages. Start by identifying what you expect the platform to operate and what you expect to maintain yourself. An account screen, a database, an AI call and a payment integration may each have a different provider or ownership boundary. Write those boundaries down. Without that exercise, phrases such as full-stack and own your code can describe very different practical outcomes while appearing equivalent on a feature checklist. Uvilno publishes this comparison and has an interest in the decision. The aim is to make that decision inspectable, not to disguise an editorial preference as an independent benchmark. Official documentation establishes what the other products publish; Uvilno's integration tests establish the specific Uvilno behaviors exercised. Neither source establishes a universal winner, a comparative completion rate or an automatic annual savings figure. Choose a narrow application slice and test it in each shortlisted workflow using the same requirements and non-sensitive disposable records. Questions to ask of all four builders | Decision | Inspect | Evidence to keep | | --- | --- | --- | | Saved data | Where records live and how ownership is enforced | Create/reload/isolation checks | | Application identity | Visitor sessions, recovery and real authorization | Two-account positive and negative checks | | Source handoff | Files, assets, backend dependencies and entitlements | Clean export and dependency inventory | | Operating cost | Building, inference, hosting and external services | Dated plan terms and observed usage | #### Compare the managed-backend contract Base44's developer material describes a managed backend with database, auth and other platform capabilities, accessed through its SDK and CLI. It also documents code ownership and export options. Treat those as real published capabilities rather than claiming the product categorically prohibits code export. Your evaluation should identify which backend functions and data resources remain managed after the frontend is obtained. Read the current plan-specific terms, inspect the package and establish what a replacement implementation would require before describing an application as independently hosted. Uvilno's managed collection contract is deliberately explicit. A data/schema.json declaration names typed collections, fields, references and optional bounded automations. Generated forms call Uvilno.db methods, and the owner can inspect actual records through App Data. Private rows follow the real project visitor identity; supported public collections have a separate reading rule. This is not arbitrary server provisioning or a general-purpose backend runtime inside the exported ZIP. If your product requires custom jobs, cross-organization permissions or specialist infrastructure, include those requirements in the comparison instead of assuming they follow from a database checkbox. - [Base44 developer platform and ownership](https://base44.com/developers) - [Uvilno vs Base44](/compare/uvilno-vs-base44) #### Inspect the application journey behind the agent Emergent publishes an agent-led application workflow and documents taking source out through its supported handoff. The practical evaluation should follow an application all the way through a record write, a page reload and a later revision. Check which services the generated code uses, where its database contents can be exported and what the deployment requires. Source, secrets and customer data should not be treated as one indistinguishable download. Published integration support is useful context, but it does not replace testing your actual authentication and payment behavior. Uvilno's contract-first process specifies routes, modules and supported services before generating the full candidate. Shared foundations and data contracts guide later pages. The repository inventory and selected @ references then help focus refinements on the relevant context. This improves the structure of the task; it is not proof that an arbitrary complex application will always finish, or that every change affects exactly one file. Preserve the previous verified result and inspect any recovered draft as a separate, unfinished artifact until the required checks and save complete. - [Emergent data and ownership documentation](https://help.emergent.sh/your-data-ownership) - [Uvilno vs Emergent](/compare/uvilno-vs-emergent) #### Ownership is not the same as a finished migration Lovable's ownership and deployment documentation discusses code access and hosting choices. Read it before assuming that every competing builder creates unavoidable proprietary lock-in. The substantive question is what your particular project still needs after handoff: a database, identity provider, storage, AI gateway, payment webhooks or a specific runtime. A frontend repository can be available while those services need their own migration. Compare the documented process with an actual clean build and an inventory of required configuration, rather than relying on either a blanket lock-in claim or a blanket portability promise. The same standard applies to Uvilno. A $4.99 permanent project unlock enables the supported source export and source handoff; it does not provision a separate copy of Uvilno’s managed backend. Fonts, referenced project assets and runtime files belong in the package, while private customer records and secrets do not. If you continue using managed auth, data or AI after export, document that dependency and register the final origin where required. If you replace it, test the new implementation, data transfer and account recovery independently before directing real visitors to the new host. - [Lovable ownership and hosting choices](https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership) - [Uvilno vs Lovable](/compare/uvilno-vs-lovable) - [Export and host a Uvilno project](/guides/how-to-export-and-host-your-ai-website) #### Test real identity before changing the preview role For any account-based app, sign in as one disposable visitor, create a private record and sign out. Sign in as a second visitor and verify that the first record is absent and cannot be requested directly. Return to the creator's builder session and confirm it remains the creator. This simple sequence catches distinctions a polished login modal cannot establish: whether identity belongs to the generated app, whether private data follows that identity and whether a preview flow accidentally interferes with the platform account used to build it. Uvilno isolates generated-app visitor identities from the platform creator session. Its Guest/Member/Admin selector is a presentation-testing control, so changing that selector never grants access to another visitor’s data. An admin-looking drawer can still be useful for reviewing layout, but actual staff administration needs explicit server-side privileges and verification. Include invitations, organization membership and account deletion only when the product implements their real semantics. A client-side flag, hidden button or data-role attribute is not a substitute for that authorization model in any of the four builders. #### Trace the write and the inference to a real result Evaluate an automation with a small, observable task: creating a follow-up should create one scoped activity entry. Replay the same request if the supported API permits an idempotency check, then make an action invalid in a disposable test to inspect rollback behavior. Uvilno’s declarative rules run within the original managed-record transaction, support bounded actions and do not recursively execute arbitrary user code. Its Automations & Logs tab reports committed metadata. That is useful evidence for a supported workflow, but it does not imply email delivery, scheduling or unrestricted background execution. For an AI feature, require a real provider response rather than a prepared string. Uvilno.ai.ask and Uvilno.ai.json use a project visitor session and the creator’s metered allowance, with response and admission limits. The current response ceiling is 600 output tokens. A JSON description guides output but does not validate arbitrary domain semantics, so the app must check required fields and handle incomplete or failed responses. Apply the same honest-result test to the other builders, while recording each tool’s documented model, billing and service requirements separately from the observable output. #### Compare repeatable iteration and the right cost category Make the same focused edit in every trial project. For example, ask for a status filter that preserves the existing table and customer details. Record the exact instruction, affected files where accessible, elapsed time, measured usage and whether the result actually works. Uvilno offers @file, @db and inspected-element context to clarify the target; Inspect & Edit also supports mapped text, link and color changes without model usage. Those are distinct mechanisms. Their existence does not establish a guaranteed four-to-eight-second AI edit time across models, projects and network conditions. Budget building and operating separately. Uvilno keeps Free at $0, a one-project source unlock at $4.99, Plus at $10 monthly, Pro at $20 and Ultra at $59. Finite usage and included source entitlements differ by plan, so unlimited unlocks should not be read as unlimited inference. Competitor plans also bundle different resources and may change. Use dated official pricing and the task’s measured usage, then add hosting, external services and maintenance. A one-time source fee versus twelve months of a broad platform subscription is not automatically a like-for-like total-ownership comparison. - [Current Uvilno pricing](/pricing) - [Detailed comparison matrix](/compare) #### Finish with a launch checklist, not a claimed winner Retain an evaluation note for each tool containing the same core brief, what the provider documents, what you actually tested and what remains unknown. Include at least a save/reload result, two-account isolation result, focused edit result and export dependency list. If one item could not be tested, mark it untested rather than assigning a zero or inventing a score. A small honest record is more useful to the person maintaining the product than a hundred-point chart with no reproducible method or comparable trial conditions. Before choosing, try the actual visitor journey on a narrow phone and through keyboard navigation. Review validation, loading, failure recovery and destructive actions, not only successful screens. Uvilno's managed Stripe connector is currently in test mode: distinguish that configured checkout from live financial activity and check the provider’s real onboarding requirements. If storing customer information, review access, retention and deletion for the data involved. The appropriate builder is the one whose supported scope, operating model and unresolved work fit your requirements; that decision can differ between a public marketing site, a personal tool and a multi-tenant business application. - Keep the same brief and disposable test data. - Record positive, negative and untested outcomes. - Review real access control and service dependencies. - Choose against the requirements you can operate. - [Read the seven-builder evaluation method](/guides/best-full-stack-ai-app-builders-2026) - [Review machine-readable evidence](/ai-benchmarks.json) **Does Base44 prohibit all code exports?** No. Base44 publishes code ownership and export options. Inspect its current plan requirements and what remains dependent on the managed backend; do the same dependency review for Uvilno and the other tools. **Does the preview Admin selector make me a real app administrator?** No. Uvilno's selector changes presentation only. Actual account identity and server-side data permissions remain unchanged. **Which tool won a controlled four-product benchmark?** No controlled four-product benchmark is claimed in this guide. Published capabilities, specific Uvilno integration checks and a proposed evaluation method are identified separately. ### 7 Full-Stack AI App Builders in 2026: Data, Auth and Source Compared Canonical: https://uvilno.com/guides/best-full-stack-ai-app-builders-2026 Updated: 2026-10-28 Evaluate Uvilno, Lovable, Base44, Emergent, Bolt.new, Replit Agent and v0 against a real application checklist, with published sources and explicit evidence limits. #### Compare the job, not the opening screenshot A useful app-builder comparison starts with one person completing one task against saved data. Choose a customer tracker, a study journal or an inventory review rather than asking each tool for an impressive dashboard. Write the objects, ownership rules and expected actions before making a trial account. This keeps the evaluation about the same product. Otherwise one result may be a local demonstration while another uses a hosted database, and their attractive screenshots will hide the most important difference. This guide covers seven tools and links to their published material. It does not award an independently measured first place: Uvilno publishes this article, and a controlled head-to-head trial has not been completed across all seven. Our documented Uvilno integration checks establish specific behaviors, including persistence and identity isolation, not a comparative success percentage. Use the matrix to shortlist a workflow, then run the same acceptance script yourself before making a decision that affects customer data or operating costs. - Choose one complete user journey. - Use identical fields and ownership requirements. - Record observed outcomes separately from published capabilities. - Keep source access, hosting and service migration as different checks. #### Seven workflows worth evaluating Uvilno combines conversation-led frontend generation with project-isolated visitor accounts, typed managed collections, transactional declarative rules and optional in-app inference. The App Data interface exposes actual collection records, while @ references help identify files, collections and inspected elements for later edits. A permanent project source unlock costs $4.99. The exported application still depends on managed services it calls, and the Guest/Member/Admin preview control changes presentation rather than granting real administrative permissions. Those qualifications belong beside the feature list when comparing alternatives. The other six products should be evaluated on their own documented workflow rather than reduced to missing-feature caricatures. Lovable publishes ownership and hosting guidance; Base44 describes a managed backend with an SDK and CLI; Emergent documents application development and source handoff; Bolt publishes database and hosting allowances; Replit documents its Agent environment; v0 documents full-stack applications built around Next.js. Read the current official pages linked here and the detailed comparison for plan-specific conditions. An integration being listed is a starting point for testing, not proof that your particular authorization or payment requirements are already fulfilled. An editorial shortlist, not a measured ranking | Builder | Evaluate this workflow | Inspect before choosing | | --- | --- | --- | | Uvilno | Chat, typed managed records, focused context and per-project source unlock | Hosted dependencies, supported scope and finite studio allowance | | Lovable | Application building with documented ownership and hosting choices | Your project's backend migration and current plan terms | | Base44 | Managed backend, SDK/CLI and application workflow | Export contents, backend operation and current entitlements | | Emergent | Agent-led app development and source handoff | Database export, deployment costs and required integrations | | Bolt.new | Browser app development with database and hosting allowances | Token use, database scope and production hosting needs | | Replit Agent | Agent development within a hosted project environment | Execution, deployment and application security requirements | | v0 | Next.js-oriented full-stack application generation | Connected data providers, server behavior and deployment setup | - [Lovable ownership and deployment](https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership) - [Base44 developer platform](https://base44.com/developers) - [Emergent data and ownership](https://help.emergent.sh/your-data-ownership) - [Bolt published plans](https://bolt.new/pricing) - [Replit Agent documentation](https://docs.replit.com/features/agent/overview) - [v0 full-stack applications](https://v0.app/docs/full-stack-apps) #### Test whether the records are actually persistent Create a distinctive test record, change one field, reload the page and navigate to its detail view. Then sign out, sign in again and find the same record. Record each outcome and the storage method involved. A browser-local array can survive navigation and even a reload through local storage without providing an account-scoped database. It may be perfectly suitable for a personal offline tool, but it should not receive the same persistence label as a server-backed customer application. Test isolation with two separate visitor accounts as well. An application should not expose the first visitor's private rows to the second unless you deliberately declared shared access. In Uvilno, private managed rows follow the actual project visitor identity, while explicitly public collections have a different reading contract. Fictional demonstration seeds and real transactional rows also need distinct treatment. Inspect the owner’s App Data view to establish what was saved, and never use sensitive customer material merely to prove that a prototype has connected storage. #### Separate a role preview from real authority A screen labelled Admin is not an authorization system. For every shortlisted tool, ask what happens when a visitor directly calls the data endpoint rather than using the visible button. Hiding a delete action may improve the interface, but the server must enforce the same restriction independently. Test the intended positive and negative cases with separate accounts and real requests. Include sign-out, expired identity, account recovery and the boundary between the builder’s owner account and the generated application's visitors in your review. Uvilno's persona selector deliberately changes only preview presentation. It helps examine Guest, Member and Admin layouts without replacing the actual signed-in app identity or creator session. Calling setRole in a generated page cannot grant access to another visitor's records. If a product requires organization administrators, invitations or staff permissions, specify and verify that server-side model separately. This is particularly important for an internal tool: an attractive employee directory or management drawer should never imply security rules that have not been implemented. #### Measure a focused edit and a failure recovery After the first build, request one observable change such as adding a status filter or removing a duplicate navigation action. Preserve the original source snapshot where access permits and compare which files changed. Check the requested outcome in the rendered page, then exercise an unrelated nearby journey. Record elapsed time, actual usage and whether a second correction was needed. A single successful result does not establish a universal four-second latency or accuracy rate, especially when model routes, file sizes and compilation requirements differ. Also provoke a safe failure in a disposable project. Determine whether a previous saved version remains available, whether completed draft files can be recovered and whether the tool distinguishes an unverified candidate from a published result. Uvilno's live probe supplies bounded observations, and native static runtime crashes may receive a limited platform-funded repair after server reproduction. This is not an unlimited free coding channel or a guarantee that every Next.js defect repairs itself. Test the recovery path your actual application depends on rather than assuming a reassuring status message proves correctness. #### Verify inference and payments independently An AI feature should produce a real provider result or an honest error. For Uvilno apps, the managed Uvilno.ai methods require a project visitor identity and draw on the creator's metered allowance, with a 600-output-token response ceiling and admission limits. Test a valid input, a rejected input and exhausted or unavailable inference. If using JSON, validate the required business fields before rendering or storing a result; receiving a parsed object alone does not establish that its contents meet your application's contract. Payment tests need equally clear labels. A successful sandbox checkout proves a test flow, not live charging, subscription enforcement or fulfillment. Uvilno's managed Stripe setup is currently in test mode. For every tool in the shortlist, identify where product prices, customer records, webhook validation and entitlement changes live. Keep real cards and real customer funds outside an unreviewed evaluation. Before launch, verify live configuration, cancellation, failed payments, duplicate webhooks and refunds with the relevant provider’s documented process and the application’s own business rules. #### Price a working year and a credible handoff Compare recurring building usage, hosting, data, inference and operational costs separately from the right to obtain source. Uvilno's $4.99 one-time unlock is a source entitlement for one project, not an annual operating budget. Plus is $10 per month, Pro $20 and Ultra $59; each has a finite allowance and its stated unlock entitlements. A competing subscription may include different hosting or execution services. Multiplying a headline plan price by twelve is a subscription reference, not proof of the complete annual cost of either application. Perform a handoff before committing to a long project. Obtain the permitted source package, install it in a clean environment and follow the actual instructions. Identify every remaining hosted endpoint, environment setting, identity provider and data export. A standard frontend can be portable while its backend still needs the original provider. That distinction applies to Uvilno too. Keep credentials and private customer records out of shared archives, and budget for continued service use or a deliberate backend replacement instead of assuming source ownership automatically removes all dependencies. #### Keep a short evidence record for the final decision For each candidate, retain the exact brief, chosen plan, model route where visible, date, tested actions and evidence of the result. Write failed or unavailable checks as such. A feature being documented, a code-authored fixture passing and an AI-generated application passing are different forms of evidence. Uvilno's published integration record covers particular persisted-data, automation, identity and recovery checks; it does not claim a controlled CRM-versus-CRM result against the other six platforms. This prevents a scorecard from turning an incomplete evaluation into a marketing statistic. Choose the tool that meets the requirements you can actually support. A small private workflow with managed records may suit one platform; a custom server, team authorization model or specialized deployment may suit another. Before exposing the app publicly, ask a person unfamiliar with it to complete the core journey on a phone and keyboard. Review security, accessibility, retention and operational ownership with the relevant expertise. The best result is a maintainable product you understand, rather than a nominal winner whose unresolved dependencies appear after customers arrive. - [Detailed comparison directory](/compare) - [Machine-readable evidence and limitations](/ai-benchmarks.json) **Which app builder is independently ranked first here?** None. This is an editorial shortlist published by Uvilno, with official-source references and specific Uvilno integration evidence. It is not an independent controlled ranking of all seven products. **Does a code export include an independent backend?** Not necessarily. Inspect the actual export and every hosted service it calls. Uvilno source exports retain managed auth, data, AI and payment dependencies unless you implement a separate replacement. **Can I compare all tools using the same CRM brief?** Yes. Use identical routes, ownership rules, records and acceptance checks, and record real completion, usage and failure behavior. Do not infer a measured score from a feature list. ### How to build a website with AI, from brief to launch Canonical: https://uvilno.com/guides/how-to-build-a-website-with-ai Updated: 2026-10-27 Turn a real business brief into a useful website. Plan the pages, review the preview, make focused edits, and prepare a source export. #### Choose the visitor's job before choosing a style Write a one-sentence success check you can give another person: ‘Find a residential project, understand the studio's approach, and start an inquiry.’ Ask them to attempt it without explaining the interface. If they cannot identify the next step, the first improvement should address navigation or content rather than adding a visual effect. Keep this check alongside the brief for later revisions. A useful first brief starts with a person trying to do something. A prospective architecture client wants to understand your work, decide whether your approach fits, and find a way to discuss a project. A restaurant visitor needs opening hours, a menu, and a reservation destination. Write that journey in ordinary language before asking for an aesthetic. Otherwise an impressive opening screen can consume the whole project while the important details remain missing. Choose one primary action and a few supporting actions. For a studio, the primary action might be sending an inquiry; viewing projects helps someone decide to take it. List what belongs outside the first release, too. You can launch a useful portfolio without accounts, a dashboard, a booking system, or a payment flow. A short boundary gives the builder a coherent problem and gives you a realistic review checklist. - Identify the audience and its most important question. - Choose a primary action with a real destination. - List the pages needed to support that action. - Write down the features you are deliberately postponing. #### Collect the facts and assets you can stand behind Prepare the business name, services, locations, contact details, and a few strong examples of the work. Separate facts you have verified from copy you want help writing. Supply real testimonials only when you have permission to publish them. If you do not have reviews, ask for an explanation of the process or useful project detail instead. Invented client logos and impressive-looking statistics make the page less trustworthy, even when the visual design is polished. Upload photographs and a logo through the available source controls, then explain their purpose in the brief. A filename alone rarely tells the builder whether an image is a hero, a case study, or a small team portrait. For visual references, describe the qualities you want to borrow: spacing, image proportions, typography, or navigation behavior. Use material you own or are licensed to use; a public URL is a reference, not permission to reproduce another business's content. Example brief: Use the supplied courtyard photograph as the opening image and the kitchen photographs in the Willow Road project. Keep the studio name as plain text until I upload the approved logo. We have not supplied awards, client quotes, or completed-project counts; omit those sections. #### Write one coherent brief and review it before sending Combine purpose, audience, content, page structure, behavior, and visual direction into a brief that another person could implement. Specificity matters more than length. Explain what happens after a visitor clicks the main button. State whether a contact section should open an email client, link to an existing booking tool, or collect a message through an enabled service. A request for a beautiful form does not define where its data goes. In Uvilno, opening a starter brief, signing in, and naming a project do not start generation. The project name organizes your saved workspace; put the public business name in the brief separately. Read the editable text in the conversation, remove irrelevant requirements, and send when ready. Optional sources and app connections need to match the actual request. Selecting a connection prepares the next submission; it does not mean every service is already configured. - [Write more precise prompts](/guides/ai-website-builder-prompt-engineering-guide) #### Use planning when the page structure needs thought A one-page business site may be clear enough to build directly. For a larger project, use Plan mode to check the proposed pages, user journeys, and service needs before approving the build. Read the plan as a product decision: does every route serve a purpose, does the data belong to one visitor or many, and are payment or account features actually necessary? Revise misunderstandings while they are still sentences rather than layout and code. An approved plan is tied to the project state. Changing the brief or restoring a version can require a new approval. Planning and prompt enhancement are real processing and count toward usage; they are not a promise of free unlimited preparation. Once you explicitly build, follow the reported progress. A saved verified result and an unfinished recoverable draft are different states. Review the result named by the workspace rather than assuming that visible draft pixels mean the build has completed. #### Review the whole visitor journey in the preview Begin at the top of the site as a first-time visitor. Can you tell what the business offers without scrolling? Can you find evidence supporting the offer, and can you complete the primary action? Follow the navigation through every page and back again. Check that buttons perform their advertised action, not merely an animation. Read the copy aloud; this reveals vague introductions, repeated claims, and headings that look dramatic but explain very little. Switch between desktop and phone preview widths. Look for cropped subjects, long words forcing horizontal scrolling, menus covering content, and sticky controls hiding important information. Test with a keyboard as well as a pointer. The preview is intentionally isolated because generated code is untrusted. That isolation protects the application, but it also means hosted login and payment flows may open a trusted popup rather than running inside the generated page. Test those distinct journeys deliberately. Review what the visitor experiences | Area | Useful question | Evidence to record | | --- | --- | --- | | Opening screen | Is the offer and next action clear? | A new visitor can explain both. | | Navigation | Can each promised page be reached? | Every link opens the expected content. | | Contact | Where does the message go? | A test arrives through the configured service. | | Phone | Can the main task be completed comfortably? | No hidden action or horizontal overflow. | #### Revise a specific outcome and preserve what works Useful revisions name the target, the problem, the intended result, and what should stay. Select an element when that helps identify it, then write the instruction in the same chat. Instead of asking for a premium redesign, explain that the opening headline overwhelms the photograph and should occupy two lines on a phone. For a behavioral issue, describe the starting state and the click that fails. The builder needs an observable outcome, not just a mood. Group changes that belong to the same decision. A smaller headline, shorter introduction, and clearer inquiry label form a coherent opening-section edit. Mixing that request with a new account system and a different navigation structure makes review harder. After each completed revision, test the changed area and a nearby unaffected journey. Saved versions let you recover a direction, but they do not replace checking the final result before publishing or exporting it. Example brief: Keep the palette, photographs, and page order. On the home page, shorten the headline to fit two lines at phone width, reduce the introduction to two sentences, and label the main email link ‘Discuss your renovation’. Preserve the project filters and test that they still work. #### Separate the website from the services it uses A static frontend can display content, run a calculator, keep browser-local preferences, and call a configured hosted service. It cannot safely hide a secret API key in downloaded JavaScript or provide a private database by itself. Uvilno offers opt-in managed services for supported tasks such as app login and personal records. Those services remain hosted dependencies when the frontend is exported. An export does not turn them into a separately provisioned backend you own. Make this distinction visible in your requirements. Say whether a task board should persist on the same browser only or save private records after sign-in. Say whether a checkout is a test demonstration or an intended live business transaction. Current managed Stripe checkout is test mode until live setup and onboarding are completed. For unsupported infrastructure, choose an external service or further development and test it separately. Do not publish a decorative control that implies a capability you have not connected. #### Finish the factual, accessibility, and export checks Before launch, verify prices, service areas, email addresses, legal names, and every claim about the business. Give each page a descriptive title and an accurate summary. Check keyboard focus, form labels, contrast, image descriptions, and reduced-motion behavior. A generated page can pass mechanical checks and still confuse a customer, so have someone unfamiliar with the project attempt the main task without coaching. Fix the point where they hesitate. Preview access and source ownership are separate. Free includes monthly AI usage; the permanent project source unlock is $4.99, with included unlocks on paid plans. Plus is $10 per month, Pro $20, and Ultra $59. Source stays private until the project is unlocked. Download the correct saved version, keep its assets and licenses together, and test it on your chosen host. External deployment, domain setup, and future updates need their own launch checks. - [Export and host the finished website](/guides/how-to-export-and-host-your-ai-website) - [Review current pricing](/pricing) **Does opening a guide's starter brief use AI?** No. It prepares editable text. You name or open the project, review the brief, and explicitly send it to start a build. **Can I download source on the Free plan?** Free supports previews and included usage. Source access requires a permanent project unlock or an included paid-plan unlock. Locked project files are not exposed through a preview. **Does every generated website include a backend?** No. Static behavior and browser-local state differ from a hosted service. Enable supported app connections deliberately and verify their data and deployment requirements. ### How to export and host your AI website Canonical: https://uvilno.com/guides/how-to-export-and-host-your-ai-website Updated: 2026-10-27 Move a Uvilno project to a static host with its assets intact. Understand source unlocks, export formats, connected services, domains, and launch testing. #### Choose and unlock the version you intend to ship Before downloading, remove test copy from public marketing pages and inspect links that were convenient during development. A mail destination, booking URL, or canonical hostname can remain a temporary value long after the design is finished. Record these release details in a small checklist so you can repeat the same review when publishing the next archive instead of relying on memory. Export begins with a release decision. Open the saved version you want to publish, review its pages, and finish its important interactions. An owner-only recoverable draft can be useful for inspecting an interrupted build, but it is not the same as a completed verified version. Write down which saved result you are taking outside the builder. That small record prevents confusion when an older archive is accidentally deployed after a later revision. Uvilno keeps generated project source private until unlock. A one-time $4.99 unlock stays with that project; Plus includes two new project unlocks per paid month, while Pro and Ultra include unlimited project unlocks during the paid period. Repeated downloads of an already unlocked project are separate from generation usage. Unlocking releases source access. It does not buy a domain, provision arbitrary backend infrastructure, or deploy the files to an external hosting account. - [Check source unlocks and plan prices](/pricing) #### Understand the files you are downloading The usual Uvilno project is a static HTML, CSS, and JavaScript frontend. Exported archives include the referenced uploaded media and bundled font assets for the selected version, together with applicable font licenses. Keep the included deployment instructions. A source archive and a compiled static output can be different deliverables for imported framework projects. Do not assume that a directory of framework source is ready to upload without a build. Next.js supports a static-export configuration, but static output has constraints: features that depend on a running request-time server need another deployment design. That is a property of the chosen output, not something a polished preview can erase. Inspect the actual archive and its instructions rather than selecting a host from the framework name alone. Existing static projects do not need a Next.js server merely because Uvilno itself is built with Next.js. Match the deliverable to the deployment | What you have | What to do | What to check | | --- | --- | --- | | Ready static files | Publish the complete output directory | The entry HTML is at the host root. | | Framework source | Follow its build instructions | Publish the generated output, not a random source folder. | | Hosted service connections | Retain and configure those dependencies | Register the deployed origin where required. | | External media URLs | Review availability and rights | A remote image is still a dependency. | - [Next.js static-export documentation](https://nextjs.org/docs/app/guides/static-exports) #### Preserve paths, assets, and licenses Extract the entire archive into a clean folder. Keep HTML, stylesheets, scripts, images, fonts, and supporting files in the same relative arrangement. If a page refers to assets/courtyard.webp, moving that image to a different folder breaks the reference. Hosting platforms may treat filename capitalization differently from your computer, so Courtyard.webp and courtyard.webp should not be assumed interchangeable. Avoid renaming files casually during a manual upload. Review externally loaded media, scripts, and fonts. An exported site may still depend on a third-party URL or hosted app service, even when the main files are portable. Keep license files and required attributions with the release record. Owning the generated source does not give you rights to photographs or trademarks you supplied without permission. If portability matters, ask for owned or properly licensed assets and verify their presence in the downloaded package. - Extract all files into one clean release folder. - Preserve spelling, capitalization, and folder relationships. - Keep font licenses and image attribution requirements. - Record external scripts, media, and hosted-service dependencies. #### Choose a host that serves your actual output For ready static output, choose a host that serves HTML, CSS, JavaScript, and assets over HTTPS. Compare its upload workflow, custom-domain support, redirect rules, deployment history, and usage limits. A simple business site may be easiest to publish with a manual folder upload. A project you expect to maintain in code may benefit from a repository-connected deployment. Hosting charges and account limits belong to that provider, independently of your Uvilno plan. Follow the host's current instructions for prebuilt output. Cloudflare Pages documents direct upload, and Netlify documents several deployment workflows. Upload the contents of the correct output directory so the entry page sits at the published root. An extra parent directory can leave the homepage missing even when every file uploaded successfully. Start with the provider's temporary HTTPS address; finish the asset and route checks there before making DNS changes for your public domain. - [Cloudflare Pages direct upload](https://developers.cloudflare.com/pages/get-started/direct-upload/) - [Netlify deployment workflows](https://docs.netlify.com/deploy/create-deploys/) #### Reconnect the services that do not live in the archive Browser-local state, such as a calculator's preferences or a local task list, stays on a particular browser and origin. It does not automatically migrate from the preview to your new domain. Managed app authentication, personal records, and other enabled Uvilno services remain hosted services. They are not copied into a private database by downloading the frontend. Decide whether those dependencies match your long-term maintenance needs before treating the export as a fully independent application. For managed app sign-in on an external host, register the deployed origin through the supported service configuration. A preview origin working is not evidence that an unrelated domain is authorized. Test with a fresh visitor session: sign in, create a record, reload, read it again, sign out, and confirm private content is no longer available. Keep secret credentials on a trusted server or service; never paste them into the exported HTML or JavaScript to make a failed connection appear to work. - [Understand Google and Discord app login](/guides/how-to-add-google-and-discord-login-to-ai-websites) #### Test routes and interactions on the deployed URL Open every page directly from its public URL, then navigate between pages. A route that works only after clicking from the homepage may rely on a rewrite that your host has not configured. Test trailing slashes and refresh on a nested route. Look at the actual content and HTTP result, not just whether something appears on screen: a platform error page may also have a heading and a polished layout. Use the host's supported redirects or route rules for the chosen output. When an image or font is missing, inspect the browser's Network panel for a failed request and compare its URL with the uploaded path. When a button fails, check whether it depends on a hosted service, a blocked popup, or an incorrect destination. Test email, booking, and payment links with the intended account or test environment. A successful file upload does not establish that a form delivered a message or that a payment created a verified receipt. Common deployment problems | Symptom | Likely area | Next check | | --- | --- | --- | | Homepage returns 404 | Wrong output root | Locate index.html in the published directory. | | Images disappear | Asset path or capitalization | Compare the failed request with the uploaded filename. | | Nested route fails on refresh | Static routing configuration | Review the host's route and trailing-slash rules. | | Login works only in preview | Authorized origin | Register and test the deployed origin. | #### Connect the domain and make the public identity consistent Add your domain in the host dashboard, then apply the DNS records that provider gives you. Check whether you are changing the root domain, a www hostname, or a subdomain; those can require different records. Keep a record of the original configuration before editing DNS. Wait for the host to confirm HTTPS and domain ownership, then test the public address from another device. Domain registration and certificate provisioning happen through the relevant providers. Choose one preferred public URL and use it consistently in canonical metadata, shared links, and any sitemap. Redirect alternate hostnames where your host supports it. Review page titles and descriptions after deployment and ensure a temporary preview noindex instruction has not followed the site into production. Search Console submission can help search engines discover your site, but does not guarantee indexing or ranking. Accurate content, reachable pages, and a useful visitor experience remain your responsibility. - [Google's SEO starter guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide) #### Keep a release record and an update path Save the archive, version date, host project, public URL, and any service configuration notes together. Avoid including secret keys in this record. If you later edit the website in Uvilno, create a new export and deploy that release through your chosen workflow. Changes in the builder do not automatically replace files on an external host. Test the updated release before redirecting visitors to it, especially when the change touches routes or connected services. Use the host's previous deployment or your retained archive as a rollback option. Keep a separate backup of important application data because rolling back frontend files does not necessarily roll back hosted records. If you use GitHub, inspect the repository changes before synchronizing and retain a known-good commit. A modest release log makes future hosting moves, handoffs to a developer, and recovery from a broken upload much easier than trying to reconstruct what was published from memory. **Does a source unlock include managed hosting?** The unlock releases project source. External hosting, domains, and any required service configuration are separate. Uvilno sharing and an external production deployment are different workflows. **Can the exported frontend keep using managed services?** Supported managed services remain hosted dependencies. Configure the deployed origin where required and test authentication, records, and other connected behavior from the actual public URL. **Will future builder edits update my host automatically?** A manual deployment needs a new export and upload. Repository workflows depend on your configured synchronization and hosting pipeline; verify each release rather than assuming automatic publishing. ### Compare Emergent, Lovable, Bolt, and Uvilno using one brief Canonical: https://uvilno.com/guides/emergent-vs-lovable-vs-bolt-vs-uvilno Updated: 2026-10-27 A practical comparison method for AI builders: use the same requirements, test real interactions, record usage, and check source portability before choosing. #### Start with the decision you need to make Decide which requirements would disqualify a product before starting the trial. If source export is essential, an unavailable export is a blocker rather than a small deduction. If the project must keep personal records private, a two-account isolation failure should outweigh an attractive layout. Predefined blockers keep your decision consistent when a demo creates a strong first impression. Choosing an AI website builder is easier when the comparison starts with your project rather than a universal winner. A public portfolio, a browser game, and an authenticated record-keeping app need different things. The first might depend on typography and export quality; the second on responsive controls and performance; the third on identity, persistence, and authorization. Write down the outcome you need before looking at a plan table or a gallery of attractive first screens. This guide is written by Uvilno, one of the products being considered. It is a comparison framework, not an independent review or a claim that we ran an identical benchmark across all four services. Vendor documentation describes supported workflows; it does not establish the quality of your result. Keep those two kinds of evidence separate. Use the procedure below to collect your own dated observations, then decide which limitations are acceptable for the project you actually want to ship. #### Use each vendor's documentation to define the trial Read current first-party material for the features that matter to you. Emergent's public site describes a describe, refine, and launch workflow. Lovable's documentation covers building, connections, publishing, and account usage. Bolt's help center includes planning, visual edits, GitHub, and deployment topics. Those are starting points for your questions, not evidence that every route, integration, or subscription allowance is equivalent. Product packaging changes, so date your notes and retain links to the relevant pages. For Uvilno, the core journey is an editable brief, an explicitly submitted build, an isolated preview, revisions, and source access after unlock. Supported managed services include typed Uvilno.db collections, project-specific visitor accounts, transactional declarative automations and bounded Uvilno.ai inference. Native static and eligible Next.js frontend workflows retain their respective verification paths. Source exports and GitHub publishing require the appropriate project entitlement, and managed services remain hosted dependencies after export. Compare the complete workflow, including setup and operation outside the editor, rather than treating source access as independently provisioned backend infrastructure. - [Emergent's current product description](https://emergent.sh/) - [Lovable documentation](https://docs.lovable.dev/introduction/welcome) - [Bolt help center](https://support.bolt.new/) - [Uvilno pricing and source unlocks](/pricing) #### Give every builder the same small, demanding brief Choose a trial that resembles the work you need but remains small enough to inspect completely. A reading journal is useful because it combines several observable behaviors: adding, editing, filtering, deleting, reloading, and handling an empty list. A business-site trial might instead use three real pages, supplied images, a working inquiry path, and phone navigation. Provide the same facts, assets, page requirements, and acceptance criteria to each service. Do not improve one product's brief halfway through and compare it with another's original attempt. State where data should persist. Browser-local records can demonstrate an interaction without providing cross-device accounts; hosted private records are a different requirement. If your trial needs login or payments, include the setup time and the test environment in the record. Never put real customer data or production secrets into an exploratory comparison. Use a disposable test account and clearly fictional records, then remove those resources when the trial is complete. Example brief: Build a reading journal. A signed-in user can add a book, change its reading status, edit a note, and delete the entry. Records must remain after reload and belong only to that user. Show a useful empty state. A second account must not see the first account's list. Keep the public introduction reachable without login. #### Score observable behavior before visual preference Start with pass or fail observations. Did the homepage load? Did the required routes exist? Did a save actually persist? Could a second user read private records? A screenshot cannot answer those questions. Complete the main task from a fresh session and refresh at the most vulnerable points. Check both desktop and phone layouts, including a narrow screen where a menu or dialog is open. Record failures precisely enough that someone else could reproduce them. Then evaluate design with a separate rubric: hierarchy, content accuracy, spacing, consistency, and whether the interface suits the audience. This avoids allowing an attractive first screen to hide a broken application. It also avoids dismissing a functional result because it does not match your personal color preference. You can weight design heavily for a portfolio and data behavior heavily for a personal tool, but choose those weights before seeing the outputs. A comparison worksheet you can reproduce | Criterion | Evidence | Record | | --- | --- | --- | | Core task | Complete add, edit, delete, and reload | Pass/fail plus exact failure steps | | Private data | Repeat with two test accounts | Which records each account can read | | Responsive layout | Inspect the same phone and desktop widths | Overflow and blocked actions | | Design | Review hierarchy and audience fit | A short reasoned score | | Portability | Inspect exported output after authorization | Required hosting and services | #### Give every trial the same revision budget The initial result matters, but refinement is a large part of building with AI. Allow the same number of purposeful follow-up requests for each product. Use changes that test everyday work: shorten a heading, add a filter, repair a failed action, or preserve one section while changing another. Record whether unrelated behavior regresses. A product that responds well to a narrow correction can be a better fit than one with a dramatic opening result that is difficult to maintain. Track human time separately from generation time. Waiting for output, writing clarifications, configuring services, recovering a failed build, and manually testing all contribute to the cost of reaching a usable release. Do not call a stopwatch result a benchmark unless you controlled the conditions and repeated the trial enough to understand variability. A single slow or fast run is an observation with a date, a brief, and a particular account configuration. #### Compare the cost of the outcome, including dependencies Record the actual plan, the allowance consumed, any top-ups, source-access charges, and external hosting or service costs. Credit units from different vendors are not interchangeable currencies. One may represent requests, another token processing, and another an internal conversion. Comparing the printed number without its accounting rules can produce a meaningless conclusion. Ask what happens when an attempt fails, when automated repair runs, and when a subscription period ends. Uvilno currently lists Free at $0, a permanent project unlock at $4.99, Plus at $10 per month, Pro at $20, and Ultra at $59. Pro's monthly AI capacity is 2.5 times Plus, and Ultra's is five times Pro. These are Uvilno plan relationships, not evidence that another service costs a certain multiple more. Unlimited project unlocks or downloads also do not mean unlimited AI generation. Use your trial's completed outcome and recorded usage to estimate the plan you need. - [Understand credits and usage](/guides/why-credit-based-ai-builders-rip-you-off) #### Test how you will maintain and leave the project If source portability matters, inspect the permitted export rather than relying on a broad ownership slogan. Check whether the archive contains the referenced images, fonts, licenses, and instructions needed to run it. Identify managed dependencies that remain outside the repository. A frontend can be portable while its database, authentication service, or payment configuration still requires continued access to another platform. Decide whether that arrangement suits your business before committing valuable data. For GitHub workflows, test a small authorized round trip: export or push, make a controlled change, pull it back, and review the result. Understand how conflicts are handled and who can access the repository. In Uvilno, connecting GitHub does not bypass the source unlock. A shared preview does not expose raw source, private conversations, or visitor records. Those distinctions matter when evaluating collaboration, handoff, and recovery rather than only the first build. #### Choose the strongest fit and document the remaining work Finish the comparison with a short decision memo. State the project, the test date, the required behaviors, the results you observed, and the work still needed before release. Explain why the winning option fits your constraints. It is reasonable for one service to win for a static campaign and another for an application with specialized infrastructure. A useful recommendation has an audience and a scenario; it does not need to declare every competing product inadequate. Retain your brief, revision prompts, screenshots, and cost notes so you can revisit the decision when requirements change. Before purchasing a longer plan, recheck current pricing and the specific integrations you need in the vendor's own documentation. If an important condition was not tested, mark it unknown. Honest uncertainty is more useful than a fabricated score, a made-up review, or a claimed performance advantage that your experiment never measured. - Use the same brief, assets, and revision budget. - Separate vendor claims from observed behavior. - Record setup, waiting, revision, and review time. - Check source entitlement and ongoing service dependencies. - Name untested conditions rather than assigning invented scores. **Has Uvilno benchmarked all four builders for this article?** No. This is a Uvilno-authored method for running a fair comparison. It does not present a four-product benchmark, fabricated ratings, or unmeasured cost advantages. **Can I compare credits directly across builders?** Only after understanding each accounting system. Compare the total cost and time of reaching the same verified result, including revisions, source access, hosting, and connected services. ### How to add Stripe test payments without pasting API keys Canonical: https://uvilno.com/guides/how-to-add-stripe-payments-without-api-keys Updated: 2026-10-27 Build a real Stripe test-checkout flow with Uvilno's managed connection, understand Connect authorization, and prepare the separate work required for live payments. #### Define the payment journey before adding the button Write a short fulfillment rule in the brief. For example, a verified test receipt may reveal a test download message, while cancellation returns to the same selection without creating an order. Naming the rule helps you review the frontend and the server confirmation together. It also prevents a generic success page from standing in for the business behavior you intended to test. A payment button is the visible start of a larger system. Decide what the visitor is paying for, whether the amount is fixed, and what a successful payment should unlock or record. Also decide what happens when checkout is cancelled, the payment fails, or confirmation arrives later. A checkout page opening successfully proves only that a session was created; it does not prove money moved or that the application should grant access. For a first integration, keep the scope small. Build one test purchase with an explicit description, an authenticated visitor where required, and a visible receipt state. Avoid combining a first checkout with subscriptions, refunds, marketplace splits, inventory, and tax rules unless those are supported and deliberately specified. These are separate business processes. A simple, verifiable test path gives you evidence about the connection before you invest in a full commerce interface. #### Understand what ‘without API keys’ actually means A managed connection can remove the need to paste a secret into the builder. It does not remove credentials from the payment system. A trusted server holds the platform configuration and performs sensitive Stripe operations. The generated frontend receives only the information it needs to start the authorized journey. This division matters because exported browser JavaScript is readable by visitors; it cannot be a safe place for a Stripe secret key. Uvilno's managed Stripe path supports sandbox checkout without asking you to supply customer credentials. Optional Stripe Connect authorization is a separate permission flow for linking an account. Account linking alone does not enable live collection, complete onboarding, or establish payouts. Keep these actions distinct in your project plan. If an integration ever asks you to fix a payment by inserting a secret directly into a page or a public repository, stop and use the trusted service configuration instead. Separate the three payment decisions | Action | What it establishes | What it does not establish | | --- | --- | --- | | Enable managed test checkout | A supported sandbox journey | Live money collection | | Authorize a Stripe connection | An account permission grant | Completed business onboarding or payouts | | Configure and verify live payments | A production payment setup | Automatic tax, refund, or fulfillment policy | #### Select the connection and write a behavioral brief Open the composer's app connections and select the supported Stripe connection for the next build. Private payment-related behavior can require managed app login; keep the dependency the product identifies. Connection selection is draft state. It does not silently change the current saved website, start a model run, or charge a visitor. Review the brief and explicitly send it when you are ready to build the payment interface. Tell the builder exactly which states to show. The initial button should explain that this is a test checkout. While a session is being prepared, prevent duplicate submissions and show useful feedback. If the visitor cancels or a popup is blocked, preserve their context and offer a clear retry. After returning, show confirmation only when the trusted service reports a verified test receipt. Do not ask the model to invent a successful transaction to make the demo look complete. Example brief: Add one ‘Try test checkout’ action for the demo purchase. Label the flow as test mode. Show a preparing state, a cancellation message, a recoverable error, and a receipt only after server confirmation. Preserve the visitor's current selection and prevent repeated clicks while the session is opening. #### Treat sandbox success as test evidence Stripe's testing environments simulate payment objects and flows without moving real money. Use Stripe's documented test payment methods rather than a real card to investigate the integration. Current Uvilno payment and managed checkout configuration remains in test mode until the owner configures a live setup. A test receipt is therefore evidence about the software path, not a customer sale, revenue, or a live payout to your bank account. Record the environment alongside every result. A screenshot saying success is ambiguous if the page does not identify the mode. Test the success path, cancellation, failed payment, repeated clicks, and returning after an expired session. Keep test orders separate from any real operational records. If you demonstrate the website publicly before live payments are enabled, label checkout accurately and avoid copy such as ‘Your order is confirmed’ when the application has only created a sandbox transaction. - [Stripe testing documentation](https://docs.stripe.com/testing-use-cases) #### Let verified server events determine payment state A browser can revisit or alter a return URL. It can also close before a payment finishes. Payment authority therefore belongs to the trusted service handling Stripe confirmation, not to a query parameter or a local success flag. The integration should verify signed events, associate them with the right project and visitor, and handle retries without granting the same result twice. A return screen can ask the server for status while confirmation is pending. Uvilno's managed app checkout and Uvilno's own source unlock are different payment purposes. A test purchase inside your generated app must not unlock its private source or change your Uvilno subscription. Keep the product language distinct so visitors and owners understand which transaction they are testing. When you review the flow, verify the expected receipt in the application and confirm that unrelated entitlements remain unchanged. Do not use a celebratory animation as your only evidence of confirmation. - A browser return alone never marks the payment paid. - Confirmation belongs to the correct project and visitor. - Repeated confirmation does not duplicate fulfillment. - An app test payment does not alter source-unlock entitlements. - Pending and failed states have honest, useful copy. #### Use account authorization deliberately Stripe Connect OAuth is an authorization flow in which an account owner reviews a platform's request and returns through a configured callback. Stripe's documentation describes the relevant parameters and the separation between authorization and token exchange. The sensitive exchange belongs on a trusted server. The generated preview should not receive a client secret, raw access token, or private platform configuration as part of this process. If the supported connection opens an authorization popup, read the provider page and confirm the intended account and mode. Cancellation should leave the project usable and should not pretend that the connection succeeded. In an isolated preview, the trusted provider journey may need a popup rather than an embedded checkout. That behavior is intentional. Troubleshoot the allowed popup, callback configuration, and connection status instead of weakening the generated-code sandbox or copying authorization details into chat. - [Stripe Connect OAuth reference](https://docs.stripe.com/connect/oauth-reference) #### Plan live collection as a separate release Live payment collection requires more than changing the word test in the interface. The account and platform must be configured for live operation, the business must complete the applicable onboarding, and the production payment flow must be verified. Product descriptions, prices, currency, support contacts, refund terms, and fulfillment rules need to be accurate. Check Stripe's current requirements for your account and business; do not infer production readiness from a successful sandbox authorization. Treat this as a release gate. Identify who controls the Stripe account, who can respond to a payment issue, and how a customer receives the thing purchased. If the intended live capability is not enabled in the supported Uvilno integration, use an appropriate external checkout service or further development rather than implying it exists. Keep the live button hidden until the real path is ready. This is especially important for subscriptions and marketplaces, whose ongoing obligations extend beyond a single checkout session. #### Troubleshoot from the first unverified step When checkout does not open, check whether the selected service was included in the built version, whether the visitor is signed in if required, and whether the browser blocked a user-initiated popup. When checkout opens but the app remains pending, check the trusted receipt state and the environment rather than repeatedly pressing the button. If account authorization was cancelled, reconnect through the supported control; do not infer success from the popup closing. After export, retest from the deployed origin. Hosted services remain dependencies and origin registration can matter for the associated login flow. Keep a concise record of the steps, expected result, actual result, and a safe time reference when reporting a problem. Never include card details, secret keys, or raw authorization tokens. A well-described failure lets you isolate the checkout session, confirmation, or UI state without exposing the credentials that protect the business. Locate the failing payment step | Symptom | First check | Avoid | | --- | --- | --- | | No popup | User action and popup permission | Relaxing the preview sandbox | | Authorization cancelled | Connection status and intended account | Treating a closed popup as consent | | Return stays pending | Verified server receipt and mode | Setting paid in browser storage | | Export fails to sign in | Deployed-origin configuration | Publishing private service credentials | **Can I collect live payments immediately?** Current Uvilno payment setup remains test mode until live configuration and required account onboarding are completed. A test checkout or linked account is not evidence that live collection or payouts are enabled. **Does no API-key pasting mean there are no credentials?** No. The managed integration keeps sensitive credentials on a trusted server. They do not belong in generated frontend code, chat, or a public source repository. ### How to build a playable browser game with AI Canonical: https://uvilno.com/guides/how-to-build-a-playable-browser-game-with-ai Updated: 2026-10-27 Specify a real game loop, responsive controls, fair rules, and browser-local progress. Measure performance and test playability before sharing. #### Describe a playable loop rather than a genre label A game brief needs a repeated action, feedback, a challenge, and a reason to try again. ‘Make an arcade game’ leaves all four unresolved. Describe what the player does in the first few seconds: move toward a parcel, avoid debris, return to a station, and earn points. Then define the pressure that makes the choice interesting. It might be limited time, a gradually busier arena, or a tradeoff between a safe route and a valuable pickup. Keep the first project small enough to test completely. One arena, one movement system, and a handful of meaningful obstacles can produce a better game than a request for a sprawling world with incomplete systems. Define success and failure in visible terms. If the player loses health, explain when damage can occur and whether a short recovery period prevents instant repeated hits. Rules that are obvious to you still need to become part of the brief. Example brief: Collect one parcel at a time and deliver it to the station for ten points. A debris collision removes one shield and gives the ship a brief visible recovery period. The round ends after three lost shields. Restart resets the arena and score while preserving the local best score. #### Make the opening screen useful for playing The first viewport should show the game and a clear way to begin or resume. Do not spend most of the screen on a marketing headline while placing the arena below the fold. A short instruction beside the start action is enough for a simple game. Place the score, pause, and restart controls where the player can find them without covering the active area. On a phone, reserve room for touch controls and the browser's own interface. Choose whether the game starts automatically or waits for an explicit action, then test that behavior on a fresh page load. Sound should begin only after an appropriate user interaction and should have an obvious mute control. A long tutorial is rarely necessary for a small prototype; introducing the core action through the opening situation can teach more effectively. Keep instructions available after play starts so someone who misses the first message can recover. #### Specify controls, timing, and collision behavior Name keyboard controls and describe touch behavior separately. A ship steered by arrow keys needs a phone equivalent that does not depend on hover. Decide whether movement is direct, accelerated, or momentum-based; these produce different games even with identical graphics. Ask for consistent behavior across display refresh rates. Movement based only on frame counts can run at different speeds on different screens, so timing should reflect elapsed time with sensible limits after a long pause. Collision rules should match what the player sees. A large invisible hit area feels unfair, while an extremely small one can make danger meaningless. Describe the approximate shape, damage feedback, and recovery behavior. Pause when the game loses visibility if that suits the design, and avoid a huge simulation jump when returning to the tab. A restart should reset timers, enemies, temporary effects, and held-input state rather than leaving remnants of the previous round. - Keyboard and touch can both complete the main action. - Controls do not scroll the page during active play. - Pause freezes the simulation and resume behaves predictably. - Restart clears the whole round state. - Collision feedback explains why health or score changed. #### Keep temporary game state separate from saved progress A round contains rapidly changing state: player position, active projectiles, enemy timers, and score. Persistent progress contains slower-changing preferences or achievements, such as the best score and sound setting. Specify which data survives reload. Saving the entire simulation on every animation frame is unnecessary for a small game and can introduce stutter. A bounded save at meaningful moments is easier to reason about and easier to recover if storage is unavailable. Browser-local progress belongs to that browser and origin. It is not an online account, a cloud save, or an anti-cheat leaderboard. Label it honestly. Validate saved data and fall back to a clean state when it is missing or malformed. A local currency or upgrade system should stay separate from real payment, Uvilno usage, and source unlocks. If you later need competitive scores across devices, plan a trusted backend and abuse controls rather than uploading unverified browser scores as if they were authoritative. Decide where each kind of game data belongs | Data | Typical lifetime | Honest description | | --- | --- | --- | | Position and active enemies | Current round | Resets on restart | | Sound preference | Same browser | Local setting | | Best score | Same browser | Local personal best | | Competitive leaderboard | Trusted online service | Requires additional infrastructure and validation | #### Treat 60 fps as a measured target Smooth play is a useful goal, but a fixed frame-rate promise is not credible across every phone, browser, battery state, and display. Ask the builder to target responsive play and then measure the result on representative devices. At a 60 Hz display, a frame has roughly 16.7 milliseconds, but not all of that time is available for your game logic. Expensive effects, excessive object creation, and large canvases can make a visually small game surprisingly costly. Use the browser's performance tools to inspect slow moments, especially after several minutes of play. Look for an increasing number of particles, event handlers, or animation loops after restart. Prefer bounded effect counts and reuse where appropriate. The browser's requestAnimationFrame scheduling is useful for visual updates, but it is not a guarantee of a particular frame rate. Reduce decorative cost before changing the core control response; a game that feels immediate is more valuable than one with extra glow and intermittent input lag. - [MDN: requestAnimationFrame timing](https://developer.mozilla.org/en-US/docs/Web/API/Window/requestAnimationFrame) #### Make the rules readable and the effects optional Players need to distinguish the ship, hazards, pickups, and destination at a glance. Use shape, motion, and labels where appropriate instead of color alone. Keep score text readable against the actual game background. Provide visible keyboard focus on surrounding controls. For a canvas game, ordinary HTML instructions and status text can explain controls and state even when the arena itself is drawn as pixels. Do not rely on a sound cue as the only warning. Respect reduced-motion preferences by reducing decorative shake, flashes, trails, and transitions. Reduced motion does not necessarily mean stopping the gameplay simulation; decide what is essential to the game and what is ornamental. Provide pause independently. Avoid rapid flashing and make important effects understandable without a bright burst. Touch targets need room around them, and controls should remain reachable without requiring a gesture that conflicts with the browser's navigation. These choices improve playability even for players without a stated accessibility need. #### Play through failures, restarts, and longer sessions A game is not verified because the arena appears and the player moves. Complete the loop: collect, score, take damage, lose, restart, pause, resume, and reload. Test what happens at the edges of the arena and when two events occur almost together. Hold multiple controls, release a key outside the window, rotate a phone, and switch away from the tab. These small interruptions often reveal bugs that a short demonstration misses. Ask another person to play without an explanation. Watch where they hesitate and whether they understand why a collision occurred. Record the exact state and action when something fails. For a performance concern, note the device, browser, approximate session length, and whether it happens after repeated restarts. Make one focused correction at a time so you can tell whether it solved the problem or changed the feel of the game in an unintended way. Example brief: Keep the current artwork and scoring. After pausing and switching tabs, the first resumed frame sometimes moves the ship across the arena. Fix elapsed-time handling and clear held input on blur. Preserve normal movement speed, then test pause, resume, restart, and a long inactive tab. #### Share the tested version and preserve its dependencies Use a saved completed version for sharing. A public preview should let a visitor understand that they are playing the game, not purchasing a product or joining an imaginary multiplayer service. If a feature remains unbuilt, remove its button. A local best-score list should say local. Keep asset rights and sound licenses with the project, and avoid copying characters, music, or distinctive artwork that you do not have permission to use. When ready to export, unlock the project through the normal source entitlement and keep the archive intact. Test the game on its final host, including relative asset paths, audio behavior, touch controls, and local storage. Moving origins means the previous local progress may not follow. Retain the working archive before making a larger revision. A small, complete game with clear controls and reliable restart behavior is a stronger release than a long feature list with unfinished menus. **Can Uvilno guarantee every game runs at 60 fps?** No. Treat 60 fps as a measured target. Performance depends on the generated game, device, browser, display, and effects. Playtest and profile representative devices. **Is a local high score an online leaderboard?** No. Browser-local progress belongs to that browser and origin. Competitive online scores need a trusted service and validation beyond storing a value in the page. ### A practical prompt engineering guide for AI website builders Canonical: https://uvilno.com/guides/ai-website-builder-prompt-engineering-guide Updated: 2026-10-27 Write briefs that describe purpose, pages, state, behavior, and design. Use examples and acceptance checks to make revisions easier to verify. #### Treat the prompt as a product brief When several people contribute requirements, resolve their priorities before combining the text. Mark the primary task and separate required behavior from optional ideas. A designer's preference for an immersive opening and an operator's need for a fast inquiry form can coexist, but the brief must explain their relative importance. An unresolved collection of stakeholder comments gives the builder conflicting instructions without a decision rule. Prompt engineering for a website is mostly the work of making your intention explicit. The builder needs to know who the site serves, what those people should accomplish, what facts are available, and what behavior makes the result useful. Elaborate role-playing instructions rarely compensate for missing requirements. A brief that a designer and developer could understand is also a stronger input for an AI builder. Start with the outcome, then supply the information needed to make it concrete. Separate required facts from creative decisions. You may want the builder to invent a layout, but not a street address, a professional qualification, or a customer review. Say what is verified and what should be omitted. When the project is fictional, label it as a demonstration so invented records do not look like real business evidence. This distinction gives the model room to design while keeping public claims grounded in material you can review. #### Use six parts to remove the important ambiguity A reliable brief covers purpose, audience, content, structure, behavior, and visual direction. Purpose names the job; audience explains the visitor; content supplies facts and assets; structure lists actual pages or sections; behavior describes actions and state; visual direction sets the character of the result. These parts need not become a rigid form. A few connected paragraphs can cover them naturally, provided none is left for the builder to guess at a critical point. The most frequently missing part is behavior. ‘Include a search bar’ could mean filtering a local list, searching public content, querying a hosted database, or doing nothing until a later release. Describe the input, action, and result. Likewise, ‘save preferences’ needs a persistence boundary: the current tab, the same browser, or an authenticated account. Put these choices in the brief before polishing adjectives about the interface. Turn a vague requirement into an observable one | Vague phrase | Clarification | Check | | --- | --- | --- | | Modern and premium | Large project photography, restrained palette, compact navigation | The chosen hierarchy fits the studio. | | Add search | Filter the visible project list by title as the visitor types | A matching item remains; a missing term shows an empty state. | | Save my work | Persist private records after sign-in and reload | The same user can read them again. | | Add contact | Send a message through the enabled collector | A test submission reaches the owner. | #### Describe pages by the decisions they support List each page with its job, primary content, and main action. A homepage introduces the offer; a project page supplies detail; a contact page provides the next step. A page map prevents the builder from turning every requested destination into an anchor on one long page. If separate routes are important, say so and include direct navigation in your acceptance checks. Keep page names aligned with visitor language rather than internal team terminology. For an application, describe a complete user journey across routes. A reading-list page, an add-book form, and a profile page share identity and data even when their layouts differ. State which pages require sign-in and what happens when a visitor opens one directly while signed out. When the structure is complex, ask for a plan first and revise it before building. A plan is useful when it resolves choices, not when it merely repeats your feature list. Example brief: Use separate Home, Work, Project detail, About, and Contact routes. Home introduces the studio and links to Work. Each project opens a detail page with its supplied images and facts. Contact offers a real email link. Keep navigation consistent and make every route work when opened directly. #### Give visual references a specific role A reference is most useful when you explain what you want from it. One image might demonstrate a wide editorial composition; another might show the density of a navigation bar. Name those qualities so the builder does not treat every detail as a requirement. Distinguish a reference from an asset you own and want placed on the site. A screenshot of another business should not become a source of copied claims, brand identity, or unlicensed imagery. Describe a coherent direction rather than stacking conflicting style labels. For example, ask for an architecture portfolio with generous white space, large landscape photographs, quiet captions, and a clear inquiry link. Include the constraints that matter, such as an existing logo color or a requirement to avoid motion. Let the builder make lower-level choices unless you have a reason to pin them. A prompt that specifies every pixel can be both lengthy and internally contradictory. #### Include a short set of acceptance checks Acceptance checks translate intent into a review you can perform. They are especially useful for generated interactions because a control can look complete while having no meaningful result. Write a few checks in plain language: a visitor can reach all pages; an invalid email produces a helpful message; a filter with no matches explains the empty state; a saved record remains after reload. Focus on outcomes that matter rather than implementation trivia. Include failure and recovery, not only success. What should happen if a visitor cancels authorization, a hosted request fails, or local storage is unavailable? The interface should preserve useful input, explain the problem, and offer a real next step. Do not ask for fabricated success messages to make the demonstration appear finished. These checks guide the first build and remain valuable when a later edit changes a shared component or service connection. - Every requested route opens directly and through navigation. - Main actions have real, visible outcomes. - Data persistence matches the requested boundary. - Empty, loading, validation, and failure states are understandable. - Phone layout and keyboard navigation support the same core task. #### Write revisions as target, problem, result, and preservation After a build, a revision should identify the target and explain the difference you want. ‘Make it better’ makes evaluation subjective; ‘the phone headline wraps to five lines, shorten it to two or three without changing the offer’ is actionable. Add what should stay: the palette, photographs, navigation, or working form. Element selection can attach a target in Uvilno, but the written instruction still needs to explain the intended outcome. For a bug, describe the starting state, the action, the actual result, and the expected result. Mention the device or route when relevant. Group changes that share a purpose, then inspect the outcome before asking for another broad change. A sequence of small coherent revisions creates clearer evidence than a single request mixing typography, routes, auth, payments, and a new brand. It also makes recovering a previous direction easier. Example brief: On the Work page at phone width, opening the menu hides the close control below the viewport. Keep the current colors and links. Make the menu fit the visible screen, keep the close action reachable, and return focus to the opener when it closes. Preserve the project filter behavior. #### Use Enhance and Plan for different questions Enhance can help turn a rough idea into a clearer editable prompt. Review what it adds: it may make useful assumptions, but those assumptions still need your approval. In Uvilno, enhancement does not submit the build. You can undo or revise the text before sending it. Planning is a different step: it asks the system to propose a readable approach to pages, interactions, and service needs so you can approve that project direction. Use enhancement when the wording is incomplete and planning when the product decisions are unresolved. Neither replaces checking business facts or understanding service boundaries. Both involve processing that can count toward usage. Opening a starter brief, naming a project, attaching a source, or editing text is separate from explicitly submitting model work. Keep that sequence clear so you understand when an action prepares a request and when it actually asks the builder to perform it. #### Fix conflicting requirements before adding more text If the result repeatedly misses the goal, examine the brief for contradictions. A request for a minimal one-screen site conflicts with six long sections and a large catalog. A request for no external services conflicts with cross-device private accounts. A request for copied competitor content conflicts with original brand positioning. Resolve the underlying choice rather than appending increasingly emphatic instructions. The shortest accurate brief often works better than a long stack of unresolved compromises. Keep a small project note containing the audience, primary task, approved page map, important facts, and accepted boundaries. Reuse it when starting a related project, but remove old requirements that no longer apply. Do not include credentials, private customer records, or irrelevant source dumps. A good prompt makes the problem understandable; it does not need to expose sensitive implementation details. The final test is still the working site and the visitor's ability to complete the intended task. **Does a longer prompt always produce a better website?** No. A clear prompt with purpose, facts, pages, behavior, and a coherent visual direction is more useful than a long prompt containing contradictions or repeated adjectives. **Should I tell the builder how to implement every detail?** Specify implementation details when they are real constraints. Otherwise describe observable behavior and acceptance checks, leaving room for the builder to choose an appropriate implementation. ### Understand credits and usage before choosing an AI builder Canonical: https://uvilno.com/guides/why-credit-based-ai-builders-rip-you-off Updated: 2026-10-27 Read AI-builder allowances without guesswork. Separate processing, project unlocks, downloads, refills, and external costs, then estimate a useful plan. #### A credit is useful only when its rules are clear A pricing page can display hundreds of credits without telling you how much useful work they buy. The unit might represent a message, token processing, a weighted task, or an internal conversion that changes with the model and context. That does not automatically make a credit system unfair. The problem is uncertainty: you cannot plan a project if the visible allowance and the work being metered are difficult to connect. This Uvilno-authored guide takes the concern seriously without claiming every competing builder is deceptive. It does not present evidence that another service costs five times more, or that a specific number of credits guarantees a finished site. Instead, use a few concrete questions to understand the system you are considering. What consumes allowance? What happens during retries? What expires? What remains yours? The answers matter more than whether a vendor calls its unit credits, tokens, or usage. #### Separate processing, source access, and running costs Building a website involves different purchases. AI processing produces or revises the work. Source access determines when you can inspect or download the generated project files. Hosting, domains, and connected services keep a public site or app running. Some products bundle several of these; others price them separately. A low monthly headline can be attractive while leaving an important deployment dependency outside the plan, so write down the full release path before comparing totals. Unlimited downloads are not the same as unlimited generation. An archive can be downloaded repeatedly without asking a model to revise it. Similarly, an included project unlock grants source access but does not necessarily create more processing capacity. In Uvilno, locked files remain private until unlock; a permanent unlock stays with the project. That ownership boundary is different from the monthly allowance used for builds, edits, planning, enhancement, continuations, and repair. The costs to keep separate | Cost | What it pays for | Question to ask | | --- | --- | --- | | AI usage | Actual model processing | Which operations count, including failed candidates? | | Project unlock | Access to project source | Does the unlock remain after cancellation? | | Downloads | Retrieving an authorized archive | Is this a new unlock or a repeat download? | | Hosting and services | Public delivery and runtime dependencies | Who operates and bills each dependency? | #### Read Uvilno's current plans as separate entitlements Uvilno currently offers Free at $0, a one-time project source unlock at $4.99, Plus at $10 per month, Pro at $20, and Ultra at $59. Free includes monthly trial usage and previewing. Plus includes standard monthly usage and two distinct new project unlocks per paid month. Pro and Ultra include unlimited project unlocks during the paid period. Already unlocked projects remain downloadable after a subscription ends; the unlock belongs to that project. The AI-capacity relationships come from the current configured monthly allowance: Pro provides 2.5 times Plus, while Ultra provides five times Pro, or 12.5 times Plus. These are capacity ratios, not promises of a fixed number of sites. A simple text revision and a large multi-page rebuild can consume different amounts. Monthly studio usage resets with the billing cycle; purchased project refills are separate and persist until used. Consult the current pricing and account balance before planning around a particular allowance. Current Uvilno offers | Offer | Price | Source access | | --- | --- | --- | | Free | $0 | Project unlock purchased separately | | One-time project unlock | $4.99 | One permanent project unlock | | Plus | $10/month | Two distinct unlocks per paid month | | Pro | $20/month | Unlimited unlocks during the paid period | | Ultra | $59/month | Unlimited unlocks during the paid period | - [Current Uvilno pricing](/pricing) #### Understand why two requests can use different amounts A model processes context as well as the text you type. A revision can include the existing requirements, relevant files, asset descriptions, and instructions needed to preserve the project. A larger task can produce more output, require continuation, or need repair before it becomes a valid saved version. Comparing requests only by the number of words in your message misses much of the work. The same short instruction can be cheap in one project and extensive in another. Uvilno reserves capacity for a model request and then settles actual provider processing, using labelled estimates where necessary. A failed HTTP attempt releases its hold; actual model work can still count even if the candidate later fails to compile or verify. There is no additional flat turn fee layered over the actual processing described by the current usage system. The practical implication is to distinguish a network failure before work begins from a completed but unusable attempt that still required computation. #### Reduce unnecessary work with a coherent release scope The most reliable way to control usage is to reduce ambiguity and unnecessary rebuilds. Prepare verified facts and assets, choose the first-release pages, and describe the behavior that matters. Ask for a plan when the structure is uncertain. Keep a successful design direction and request focused changes rather than repeatedly restarting from a new aesthetic. This does not guarantee a particular cost, but it makes the work easier to review and reduces avoidable churn. Avoid false economies. A brief that omits the data model or failure states may save a few words while causing a much larger correction later. Equally, a long prompt filled with unrelated features can expand the task far beyond what you need. Group revisions by purpose and test after each coherent change. Preserve a known-good version before a larger experiment. If the project has become confused, clarify the goal before asking the model to keep repairing an unstable direction. Example brief: Keep the existing pages, palette, and working inquiry form. Change only the Workshops page: add the supplied dates, show a clear sold-out state for full sessions, and keep the contact destination unchanged. Do not introduce checkout or accounts. #### Estimate a plan from a representative project Choose a project close to your real workload and record its initial build, purposeful revisions, and final export needs. Note the allowance before and after each explicit processing action and the time spent reviewing. A single trial cannot predict every future task, but it gives you a better basis than dividing a plan's credit count by a guessed message cost. Keep unusually large or failed attempts in the record instead of silently excluding them. Estimate a range, not a precise promise. A client campaign with supplied copy differs from an application whose behavior is still being discovered. Include your expected number of distinct source unlocks and the cost of external hosting or services. If you are comparing products, use the same brief and revision budget. Do not translate one vendor's credit into another vendor's unit without evidence about how both systems meter the same task. - Record the plan and date of the trial. - Measure before and after explicit processing actions. - Count unsuccessful attempts that used real processing. - Include distinct source unlocks and external dependencies. - Budget a range for revisions rather than a fixed site count. #### Ask the questions that reveal an unclear allowance Look for a clear explanation of resets, rollover, top-ups, cancellation, and included entitlements. Ask whether unused monthly allowance survives into the next period and whether a purchased refill behaves differently. Check what happens when a build is interrupted, when you retry it, and when automated repair runs. A product does not need to expose private provider credentials to explain these rules. It should give you enough information to understand the visible balance and the actions that change it. For source access, ask what remains available after cancellation and whether deleting a project restores an included unlock. In Uvilno, Plus counts distinct project unlocks and deletion does not restore that monthly allowance. For connected applications, ask whether the hosted services continue to be dependencies after export. A source archive is valuable, but it does not automatically move visitor records, authentication, or payment infrastructure into your hosting account. #### Judge value by a verified result and understandable terms The useful outcome is a working release you can maintain, not the largest number printed beside a credit icon. Evaluate the quality of the result, how much clarification it needed, what it costs to export, and which dependencies remain. A more expensive plan can be worthwhile if it fits a demanding workflow; a small one-time unlock can be enough for a finished static site. The correct choice depends on your use, not an unmeasured claim of universal savings. Keep screenshots or notes of the terms you relied on and recheck current pricing before a purchase. If a charge or balance change is unclear, report the project, action, time, and visible result without sending secrets. Clear accounting and useful recovery matter. So does honest marketing: no plan should be described as unlimited AI merely because downloads are unlimited, and no comparison should accuse another builder of overcharging without a fair record of the same completed task. **Are credit-based builders automatically unfair?** No. The important questions are what the unit measures, how retries and failures are handled, what resets, and whether the total cost of a verified result is clear. **Does unlimited source export mean unlimited AI generation?** No. Source entitlements, repeat downloads, and AI processing are separate. Uvilno's monthly generation capacity remains bounded on paid plans. **How much more usage does Pro include?** Current configured monthly AI capacity is 2.5 times Plus for Pro, and five times Pro for Ultra. These ratios do not guarantee a fixed number of completed websites. ### How to add Google and Discord login to an AI website Canonical: https://uvilno.com/guides/how-to-add-google-and-discord-login-to-ai-websites Updated: 2026-10-27 Plan hosted app sign-in, private records, account states, and export-origin setup. Keep OAuth on trusted pages and generated code inside its preview boundary. #### Separate your builder account from your app's visitors Draw a simple account map in your project notes: the owner edits the app, the visitor owns personal records, and a connected provider grants a specific permission. Include the intended sign-out behavior for each. This makes it easier to detect a misleading label, such as a visitor profile appearing to manage the owner's builder subscription, before that confusion becomes part of the generated interface. Signing in to Uvilno lets you own and edit a project. Signing in to a generated application lets a visitor use that application's supported private features. Connecting a provider for repository or payment access is another permission relationship. These journeys can involve familiar provider names while serving different purposes. Define which identity you are adding before asking the builder for a login button; otherwise a polished account screen can imply access that the service does not actually provide. Start with the visitor's reason to sign in. A private reading journal needs personal records; a public architecture portfolio probably does not. Avoid requiring an account for content that should be openly readable. List the actions that become available after authentication and what should remain public. That boundary guides the page structure, error handling, and authorization checks, and it keeps login from becoming an unnecessary obstacle in the visitor's journey. #### Understand the hosted authentication boundary Uvilno's supported managed app authentication is a hosted service, not a new customer-owned identity database provisioned inside the static export. The generated frontend uses the trusted service for sign-in and authorized requests. Provider credentials do not belong in the page, the prompt, or the exported archive. A browser-only website cannot keep a secret simply by hiding its text from the interface; downloaded scripts remain inspectable by visitors. Generated code also remains isolated from the main application origin. A trusted top-level consent or provider popup handles the sensitive authorization journey, then the application receives a scoped result through the supported runtime. This is why you should not solve a login problem by granting generated content broad same-origin privileges. Isolation and hosted consent are parts of the architecture. The goal is a working visitor journey that respects those boundaries, not an embedded imitation of a provider's login screen. - [MDN: iframe sandbox behavior](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/iframe) #### Enable the supported service and describe the account screens Select the managed app-login connection in the composer's app connections for the next explicit build. If you request private records, the product can require that login dependency as well. Selection prepares the next submission; it does not replace the current saved version or silently create a finished account system. Describe the needed screens and states in the brief, then send the request. Check the resulting application rather than assuming that a selected chip proves the full flow is ready. Request a dedicated login view, the available provider options, a profile, and sign-out where they serve the app. Include email/password registration and recovery only when supported by the selected service. The interface should show provider availability honestly. A Google or Discord button must start a real supported authorization path; an unavailable provider should not appear as a decorative action. Distinguish editable profile fields from account identity information that comes from the trusted service. Example brief: Keep the introduction public. Require app sign-in before opening My Books. Offer the providers actually supported by the hosted service, including Google and Discord when configured. After sign-in, show the visitor's own books and a profile. Preserve an unsent note if authentication expires and explain how to retry. #### Keep OAuth consent on the provider's trusted journey OAuth lets an application request a limited authorization from a provider through a defined flow. Google documents server-side authorization, redirect handling, and protecting credentials. Discord documents its own scopes and authorization process. The exact provider setup belongs to the trusted integration. A generated site should not ask visitors to type their Google or Discord password into a custom form that imitates those providers, and it should not receive a provider client secret. During testing, inspect the real consent page: the intended provider, application identity, and requested permissions should make sense for the task. Basic sign-in should not be described as permission to send Discord messages or read unrelated Google data. Cancellation must return to a usable signed-out state. If the popup is blocked, show an understandable recovery action. Closing the popup is not proof of consent; the application should wait for the trusted service's result. - [Google OAuth for web-server applications](https://developers.google.com/identity/protocols/oauth2/web-server) - [Discord OAuth2 documentation](https://docs.discord.com/developers/topics/oauth2) #### Make private records private on the server Authentication answers who a visitor is. Authorization determines which records that visitor can read or change. Hiding a page or disabling a button in the browser does not enforce record ownership. For a personal journal, the trusted service must bind requests to the app, project, and signed-in visitor. A second account should not be able to retrieve the first account's records by changing a visible identifier or reopening a URL. Describe the ownership model explicitly. Uvilno's typed managed collections support declared fields, references, private visitor-owned records and deliberately public reading where configured; they do not imply arbitrary server provisioning or an enterprise permission hierarchy. If you need shared workspaces, team roles or organization-wide administration, treat those as separate requirements and confirm the actual authorization model before building the interface. The Guest/Member/Admin preview selector changes presentation only. A login screen or an admin-looking drawer alone does not establish that the rest of an application's data model is safe or complete. Test identity and access separately | Check | Expected behavior | Why it matters | | --- | --- | --- | | Signed-out visitor | Private data is unavailable | A hidden menu alone is insufficient. | | Account A saves a book | A can read it after reload | The request used real persistence. | | Account B opens the app | B cannot read A's book | Record ownership is enforced. | | Sign out | Private view closes or clears safely | Old UI must not imply an active session. | #### Design the states around sign-in, not just the happy path Account features introduce waiting and failure into otherwise simple pages. Show a loading state while the service resolves the session so private content does not flash before authorization is known. Give an empty account a useful next step. Keep validation messages near the relevant field and preserve safe input after a recoverable failure. A disabled submit button needs an understandable reason; a permanent spinner gives the visitor no way forward. Test session expiration, provider cancellation, password recovery where supported, and sign-out followed by the browser's Back action. Do not leave an old account name or private record on screen in a way that suggests access continues. For asynchronous data, wait for the real result before rendering success. If the service is unavailable, explain that the action failed and provide a retry; do not substitute fictional private records or a fake successful save. - The signed-out view explains why login is needed. - Session loading has an explicit bounded state. - Provider cancellation preserves a usable page. - Private records render only after authorized retrieval. - Sign-out and expiration clear or protect private UI. #### Register and test the deployed origin after export A working preview does not automatically authorize a different production domain. Uvilno's managed app service accepts its supported isolated preview context or an owner-registered deployed origin. Register the external app origin through the available managed sign-in configuration before testing the exported frontend. Use the exact intended scheme and hostname. A temporary host URL, a www hostname, and a root domain can represent different origins even when they display similar pages. Run the whole journey from the actual deployed address: open a public page, start sign-in, complete provider consent, create a private record, reload, edit it, and sign out. Repeat with a second test account. Keep in mind that the hosted authentication and records remain dependencies after source export. If your goal is to operate a separate identity system, plan an intentional migration with appropriate development rather than assuming the downloaded frontend contains the service and visitor database. #### Troubleshoot the first boundary that fails If no provider window opens, confirm the button starts from a real user action and check popup permission. If consent returns an error, check the supported connection, provider configuration, and intended origin. If sign-in succeeds but records fail, investigate authorization and service availability rather than rebuilding the login layout. If only the exported site fails, check deployed-origin registration before changing generated code. Keep the preview sandbox intact throughout the investigation. Report safe reproduction details: which view was open, which provider was selected, whether you were in preview or on a deployed host, and the visible error. Never include raw session credentials, authorization codes, or private visitor data in a prompt or public issue. Once corrected, repeat the two-account access test and the sign-out test. Authentication is complete only when the surrounding private data journey works predictably and the interface explains failures honestly. **Does app login create a separate backend in my export?** No. Supported managed authentication and personal records remain Uvilno-hosted services. The export contains the frontend and its supported runtime integration, not a separately provisioned identity database. **Why does sign-in use a popup?** Generated code runs in an isolated preview. A trusted top-level consent or provider window can handle authorization without granting generated content broad privileges on the application origin. **Why does login fail only after deployment?** Check that the external app origin is registered through the supported managed sign-in configuration. Preview authorization does not automatically authorize another hostname. ### Plan a multi-page AI application before you build Canonical: https://uvilno.com/guides/planning-a-multi-page-ai-application Updated: 2026-10-27 Map routes, user journeys, state ownership, service dependencies, and acceptance checks so a multi-page app is more than linked mock screens. #### Start with one complete journey across the app Write the journey with sample inputs and expected outputs. ‘Add a book’ becomes ‘Enter a title, save it, return to the list, and see that title once.’ ‘Edit a note’ becomes ‘Change the text, save, reload, and read the new text.’ These examples reveal duplicate saves, stale lists, and missing persistence while giving you a compact test script after generation. A multi-page application is not simply a homepage plus several destinations. Its pages share state, identity, navigation, and rules about what a visitor can do. Start by writing one complete journey: a visitor understands the tool, signs in, creates a record, finds it again, changes it, and leaves safely. This exposes dependencies that a feature list hides. It also gives you a way to decide whether the first release is actually usable. Choose one primary job for the first version. A personal reading journal can support adding books and notes without becoming a social network, bookstore, recommendation engine, and subscription service at once. Put later ideas in a separate list. Smaller scope is useful when it creates a complete loop, not when it removes the save action or hides an unfinished route. Every promised part of the first journey should work before adding a second major workflow. #### Map routes to purpose, access, and actions For each route, record its audience, purpose, required data, and main action. A public introduction explains the product; a private list shows the current visitor's records; an edit view changes one record. Identify how someone reaches the route and what happens if they open it directly. Do not rely on a previous page silently preparing essential state. A bookmarked URL and a refresh are normal browser behavior, not unusual edge cases. State whether you need actual separate pages or a section on one page. In Uvilno's supported multi-page static frontend, each approved route should have real content; an anchor on the homepage is not a substitute for a requested route. Keep navigation labels stable and show the current location. For private routes, define the signed-out destination and whether a visitor can return to the intended task after authentication. Avoid losing their safe unsent input during that transition. A route map for a small personal app | Route purpose | Access | Main action | | --- | --- | --- | | Home | Public | Understand the app and begin | | Login | Signed out | Start supported authentication | | My Books | Signed in | Find and filter personal records | | Add or edit a book | Signed in, own record | Validate and save changes | | Profile | Signed in | Review profile and sign out | #### Decide where every kind of state belongs A form's unsent text, a selected filter, and a saved book record are different kinds of state. Temporary interface state can live in the current view. A preference may be browser-local. Private records that should survive across devices need a supported hosted service and authentication. Write down these boundaries before building. Without them, an app can look as though it saved data while merely keeping a JavaScript array until the next refresh. Describe ownership as well as storage. In a personal app, each visitor reads and edits their own records. Shared workspaces and role-based administration require a different authorization model; do not infer that they exist because the interface has a team selector. Uvilno.db offers typed fields and declared references through a bounded hosted service, with optional transactional create/update/increment/notification rules. It is not arbitrary backend provisioning. If your application needs scheduled processing, cross-organization permissions or custom server logic, identify that as separate development or a supported external service and verify it independently. - Unsent form text has a clear lifetime. - Local preferences are labelled as browser-local. - Saved private records use a real hosted service. - Record ownership is checked beyond the visible interface. - Unsupported backend requirements are identified before generation. #### Write an interaction contract for each important control A control needs a trigger, a state transition, and a visible result. For a save action, specify validation, pending feedback, successful persistence, and a recoverable failure. For a filter, define which records it affects and what happens when none match. For deletion, decide whether confirmation or undo is appropriate and where focus goes afterward. These small decisions make the difference between an application and a collection of styled components. Keep actions consistent across routes. If a record changes on an edit page, the list should reflect that change when the visitor returns. If a delete request fails, the record should not vanish permanently from the interface as if it succeeded. Avoid duplicate submissions and stale success messages. Describe these outcomes in ordinary language; you do not need to dictate a particular state-management library to make the expected behavior precise. Example brief: When Save is selected, validate the title, show a pending state, and persist through the managed personal-record service. Navigate back to My Books only after success. On failure, retain the text and explain how to retry. Returning to the list must show the saved title without a manual full-page refresh. #### Define the shared design and the intentional differences A multi-page app needs a stable visual language: navigation, page titles, form fields, primary actions, empty states, and feedback should feel related. Provide a coherent direction and ask the builder to reuse those patterns. A public introduction can be more expressive than a compact record list, but both should belong to the same product. Consistency helps a visitor transfer what they learned on one page to the next. Specify content density by task. A reading list needs scanable titles, status, and a clear next action; an edit page needs a calm form and visible validation. Avoid asking every route to have a giant hero and a decorative card grid. On phones, check where navigation, filters, and save controls go when space shrinks. Shared components should support the actual task rather than forcing all content into one impressive-looking but inconvenient template. #### Use the plan to resolve decisions before generation In Uvilno, Plan mode returns a readable proposal in the conversation. Review its page map, service needs, and intended interactions, then use the explicit approval action when the proposal matches your goal. Planning does not expose private source architecture to a locked project. It is a product discussion that prepares a build. Ask for a revision when the plan invents a service, misses a route, or turns private persistence into a local demonstration. Approval is tied to the current project, brief, draft revision, and base version. If those change, a new approval may be needed. This protects you from building an old plan against a different project state. Planning involves actual processing and can count toward usage, so use it for meaningful uncertainty. A tiny text change on a finished page usually needs a focused edit rather than a new application-wide planning exercise. #### Turn the plan into a route and behavior test map After the build, test every required route directly and through navigation. Reload private and nested pages, use Back and Forward, and try the main journey on a phone. Check the actual expected page content rather than accepting any heading as proof the route exists. A polished platform 404 is still a missing page. Confirm that menus, dialogs, and keyboard focus behave correctly as you move between views. For data, create a record, reload, edit it, delete it, and repeat with a second account. Test the empty state after deletion and a failed request without losing input. For service dependencies, test consent cancellation and the deployed origin separately from the preview. Record the first failing step with the route, state, action, and visible result. This produces a useful correction request and prevents a broad redesign from hiding the original behavior problem. Verify the plan with observable checks | Area | Test | Evidence | | --- | --- | --- | | Routes | Open and reload every required URL | Expected content and successful response | | State | Save, navigate away, and return | The same saved record is visible | | Privacy | Repeat with two accounts | Records stay with their owner | | Recovery | Cancel auth or simulate failure | Useful input and a real retry remain | | Phone | Complete the whole task | No blocked action or overflow | #### Expand through complete, reviewable slices Once the first journey works, add a related capability as another complete slice. A status filter is a smaller extension than a public social feed. Describe how the addition changes routes, state, ownership, and failure handling. Preserve a known-good version before the larger change and test the existing main journey afterward. A saved version gives you a recovery point; it does not prove that new changes are safe to publish. Before export, record hosted dependencies and the service configuration needed on your chosen domain. Source unlock releases the frontend files, not a separately provisioned database or identity system. Keep a release note listing the completed journey and any deliberate limits, such as personal records rather than team collaboration. A small app with honest boundaries is easier to maintain, hand off, and extend than a large interface whose underlying behaviors were never decided. **Do multiple navigation links prove an app is multi-page?** No. Verify each required route opens directly, reloads correctly, and contains the expected content. Homepage anchors do not replace separate routes when separate pages were requested. **Does adding login solve the data model?** No. You must define persistence, record ownership, supported operations, and recovery states. Authentication identifies a visitor; authorization still controls their records. ### Make precise visual website edits with AI Canonical: https://uvilno.com/guides/visual-website-editing-with-ai Updated: 2026-10-27 Use element selection, screenshots, and focused instructions to change layout and copy without losing the parts of your website that already work. #### Describe what is wrong before describing a style Capture the affected state before requesting the change. A menu that fails only after opening, a headline that breaks only with the real business name, or a form that overflows only after validation needs that context. Include the state in your request so the builder repairs the situation a visitor encounters. Otherwise it may improve the resting screenshot while leaving the original problem intact. A visual edit works best when it starts with an observable problem. The headline may dominate the opening image, the navigation may look detached from the page, or the phone layout may hide the main action. These observations are more useful than asking for a premium, modern, or polished result. Name the element, explain how it interferes with the visitor's task, and describe the relationship you want to change. Separate taste from usability. A color preference is a legitimate design choice, but it is different from insufficient text contrast. A large heading may suit an editorial portfolio while making a dense application harder to scan. Use the purpose of the page to judge the change. The goal is not to apply the same fashionable styling everywhere; it is to make this particular page clearer, more coherent, and easier to use. Convert a reaction into a useful edit | Initial reaction | Concrete diagnosis | Useful direction | | --- | --- | --- | | The hero feels wrong | Heading competes with the photograph | Reduce heading width and preserve the image's focal area. | | The page looks cramped | Section boundaries are unclear | Increase separation between sections, not every item. | | The form looks unfinished | Labels and feedback lack hierarchy | Clarify labels, spacing, validation, and focus states. | | Mobile feels broken | Navigation covers the primary action | Keep menu controls reachable and preserve the task. | #### Use selection to identify the target, then explain the intent Uvilno's canvas selection can attach an element target to the same conversation input you use for other requests. This helps distinguish one repeated button or heading from another. Selection supplies location; your instruction supplies intent. Say what should change and what the visitor should experience afterward. If the target appears on multiple pages, specify whether the request applies to one instance or the shared pattern throughout the site. Before sending, confirm that the selected element belongs to the displayed version you mean to edit. If you restored another version or changed routes, recheck the context. Avoid piling unrelated selections into one ambiguous request. A targeted revision should remain understandable even when read later in conversation history. Mention the section or route in plain language so the request is useful beyond the temporary outline drawn around the element. Example brief: On the Contact page, refine the selected submit area. Keep the fields and real collector connection. Place the primary action closer to the privacy explanation, shorten its label to ‘Send inquiry’, and keep validation messages associated with their fields. Apply the change only to this contact form. #### Use screenshots as evidence, not as unexplained commands A screenshot can show a problem that is difficult to describe, such as an awkward image crop or a menu clipped on a phone. Attach it through the source controls and explain what it demonstrates. Include the route, approximate viewport, and state if the issue depends on an open menu or validation message. A screenshot of the resting page cannot show how focus moved, where a form submitted, or why a button failed, so add those details in text. For a design reference, identify the qualities you want: a quieter header, a larger project image, or tighter caption spacing. Say which aspects should not be copied. Do not treat another business's screenshot as permission to reproduce its identity, photographs, reviews, or copy. Your own assets and verified facts should remain the content of the site. Reference-driven editing is most effective when the borrowed relationship is clear and the result still belongs to your project. #### Write the preservation boundary into every substantial edit A useful edit names both the intended change and the parts that already work. Preserve the page order, palette, supplied photographs, and functioning interactions when those remain approved. This gives the builder a narrower problem and gives you a regression checklist. ‘Keep everything else the same’ is less helpful than naming the important boundaries, especially when the requested change touches shared spacing or typography that may legitimately affect several elements. Think in coherent groups. Adjusting a heading's size, line length, and nearby introduction can be one visual decision. Adding a new account system while changing the heading is a separate decision with different verification needs. Split those requests. After an edit, inspect both the changed section and the neighboring content. A shorter heading may improve the first screen while exposing an awkward gap below it; a local fix still needs to fit the surrounding composition. Example brief: Keep the existing colors, project images, routes, and inquiry behavior. Change only the opening composition: shorten the introduction, give the headline a narrower measure, and make the photograph the dominant element. Preserve the current mobile navigation and verify its open state after the change. #### Adjust hierarchy and spacing before adding decoration Many pages feel weak because the relationships are unclear, not because they need more effects. Check which element should be read first, which content belongs together, and where one section ends. Heading size, line length, alignment, and space can solve those problems directly. Increase the separation between distinct sections while keeping related labels and fields close. If every gap grows equally, the page becomes longer without becoming easier to understand. Use the real copy when judging the result. A two-word sample title and a real seven-word service name create different line breaks. Check image focal points at desktop and phone widths; a beautiful wide crop may cut off a face on a narrow screen. Avoid asking for layers of shadows, gradients, and animation merely to compensate for weak structure. Decoration can support an approved direction, but it cannot make an unclear task or missing destination useful. - The primary information is visually dominant. - Related content is grouped more tightly than separate sections. - Headings use real copy and readable line lengths. - Images retain useful focal points at phone width. - Decoration supports the page instead of covering a structural problem. #### Specify what should happen when space changes A desktop screenshot is only one arrangement. Describe the intended phone behavior when revising a layout: columns may stack, navigation may collapse, and secondary detail may move below the main action. Do not simply ask the builder to shrink everything. Text still needs a readable size, controls still need room, and the important journey should remain possible. Check an intermediate width as well as the largest and smallest previews when a layout changes dramatically. Pay special attention to fixed and sticky elements. A floating action can be useful on a tall desktop but cover half a short phone screen when the keyboard opens. Menus and dialogs need a reachable close action, sensible internal scrolling, and focus behavior. Review long labels, validation messages, and expanded content rather than only the default state. A responsive design is a set of workable relationships, not a collection of screenshots with identical content scaled down. #### Protect behavior while changing appearance Visual changes can affect behavior even when the request sounds cosmetic. Replacing a button with a styled text element can break keyboard use. Moving a form can detach its labels or obscure feedback. Changing an overlay can trap focus or let background content remain interactive. Ask the builder to preserve semantics and existing service connections, then actually test the control. A screenshot review and a behavior review answer different questions. Test focus, hover, active, disabled, loading, and error states where relevant. The main action should remain identifiable without relying on color alone. Reduced-motion preferences should reduce decorative movement without hiding content or disabling essential behavior. If an edit changes the order of content, check the reading and tab order. A visually pleasing rearrangement that leaves keyboard focus jumping unpredictably is not a finished improvement. - [Check accessible generated websites](/guides/accessible-ai-generated-websites) #### Review the saved result and keep a recovery point After the revision completes, review the saved version named by the workspace. Compare it with the intended outcome, not just the previous screenshot. Did the original issue disappear? Did the preserved areas remain intact? Complete the primary task on desktop and phone. If the change missed the goal, explain the remaining difference precisely rather than requesting a fresh redesign. The accumulated context is useful when it stays focused. Keep a known-good version before larger experiments. Restoration changes the displayed version; check it before making another request or exporting. A saved version is different from a recoverable unfinished draft, which may still contain unverified behavior. If you work through GitHub, review diffs and resolve conflicts before pushing a new release. Visual iteration becomes much less risky when you can name what changed, verify its effect, and return to a working baseline. **Does selecting an element make the edit automatically?** Selection identifies the target for your next request. Write the intended change in the same chat, review the brief, and explicitly send it to start the revision. **Can a visual edit break a working form?** It can. Preserve semantics and the existing service connection, then test validation, submission, loading, error feedback, and keyboard behavior after changing the layout. ### Make an AI-generated website more accessible Canonical: https://uvilno.com/guides/accessible-ai-generated-websites Updated: 2026-10-27 Review keyboard access, semantics, contrast, forms, motion, and responsive behavior with concrete checks that go beyond a polished screenshot. #### Start with the task a visitor must complete Include content changes in the review. A new photograph can reduce caption contrast, a longer translated label can clip a button, and a newly added field can disturb the tab order. Accessibility work is therefore part of ordinary publishing, not only a final technical audit. Keep the important task checks with the project's release notes and repeat them whenever content or shared components change. Accessibility is easier to review when you begin with a real journey: find a service, navigate to a project, send an inquiry, or save a personal record. A website can look elegant while blocking that task for someone using a keyboard, screen reader, magnification, or reduced-motion setting. Describe the important journey in your brief and test it through more than one input method. The objective is useful access to the same outcome. AI generation does not remove the need for human review. Automated checks can identify some problems, but they cannot decide whether an image description is meaningful, whether navigation labels make sense, or whether a complex task is understandable. Treat the W3C's current WCAG guidance as a reference for your review. Do not turn a passing automated score into a blanket claim that the entire website is accessible or compliant in every context. - [W3C: How to meet WCAG](https://www.w3.org/WAI/WCAG22/quickref/) #### Give the page a meaningful structure Use headings to describe the content hierarchy, not merely to obtain a larger font. A page needs a clear main heading, logical section headings, and landmarks that distinguish navigation, main content, and supporting information. Link text should make its destination understandable. Repeated ‘learn more’ labels can be ambiguous when read outside their visual context; a label such as ‘View the Willow Road project’ gives the destination a useful name. Choose native elements for their behavior. A link moves to a destination; a button performs an action. Replacing either with a clickable generic container can lose keyboard support and semantics. Ask the builder to preserve these relationships when restyling. If a visual order changes on a phone, check the underlying reading and focus order as well. A screen reader or keyboard user should not have to follow a sequence that contradicts the visible page. Example brief: Keep the current visual design. Use one meaningful main heading, logical section headings, and a main landmark. Make project destinations real links with descriptive names. Keep action controls as buttons and ensure the reading order remains logical when the layout stacks on a phone. #### Complete the journey with a keyboard Set the pointer aside and use Tab, Shift+Tab, Enter, Space, arrow keys where appropriate, and Escape. The focus indicator should remain visible on every interactive control. The order should follow the task, without jumping unexpectedly between columns or disappearing behind a fixed header. Make sure all main actions can be reached and activated. A control that responds to a mouse click but never receives keyboard focus is a real functional defect. Menus and dialogs need special attention. Opening a dialog should place focus somewhere sensible inside it, keep interaction within the active dialog, and return focus to the opener after closing. Escape should close a dismissible overlay. A phone menu must have a reachable close action even on a short viewport or with enlarged text. Do not trap visitors inside a component, and do not let an invisible overlay intercept clicks after it appears to close. - Every interactive control has visible focus. - The tab order follows the content and task. - Menus and dialogs can be opened and closed without a pointer. - Closing an overlay returns focus sensibly. - Sticky content does not obscure the focused control. #### Check contrast against the actual background Readable text depends on the foreground and the background it actually appears on. A light caption over a photograph may pass in one crop and disappear in another. Secondary text, placeholders, disabled controls, and validation messages need deliberate review, not only the largest headline. WCAG's common minimum contrast requirements include 4.5 to one for ordinary text and three to one for large text, with the relevant definitions and exceptions in the standard. Do not use color as the only way to communicate a state. An error needs text or another clear indicator; a chart needs distinguishable labels or patterns; a selected filter should remain recognizable beyond a subtle hue change. Preserve the project's visual identity while adjusting the combinations that fail. If an orange button cannot support a readable label in its current shade, changing the shade or text treatment is a precise design correction rather than a reason to abandon the palette. Review more than body text | Element | What to inspect | Useful correction | | --- | --- | --- | | Photo caption | Contrast across responsive crops | Provide a dependable text background. | | Form error | Meaning beyond red color | Add specific text associated with the field. | | Focused button | Visible indicator on its surface | Use a distinct, unclipped focus treatment. | | Chart category | Distinction without color alone | Add labels and another visual cue. | #### Make forms understandable before and after submission Every field needs a persistent accessible label. A placeholder disappears when the visitor types and should not be the only description. Explain required formats before submission where useful, and associate instructions and errors with the relevant input. Use appropriate input types and autocomplete values for common personal information. A clear label and a helpful error often improve the form more than decorative containers or elaborate animations around each field. Test the entire form lifecycle: empty submission, invalid values, pending request, success, and failure. Keep safe input after a recoverable error. Make status changes available to assistive technology without unexpectedly moving focus or repeatedly announcing the whole page. A form must also have a real destination; accessible fields attached to a fake submit action still fail the visitor. For connected collection or private records, test the actual service outcome as well as the visible confirmation. Example brief: Keep the inquiry form connected to its current collector. Add persistent labels, explain required fields, associate each validation message with its input, and announce submission status. On a failed request, retain the message and offer a retry. Do not show success until the service confirms acceptance. #### Describe images by their purpose An image description should explain the information the image contributes in this context. A project photograph may need a concise description of the space; a decorative texture may need an empty alternative so it does not interrupt reading. Avoid repeating a nearby caption verbatim when it adds no information. For a linked image, consider the destination as well as the picture. The right text depends on the role, not on a generic formula applied to every asset. For audio and video, provide appropriate alternatives such as captions and transcripts when the content carries information. Do not make audio start unexpectedly, and give visitors clear playback controls. A background film should not be the only place essential instructions appear. For a canvas game or chart, put meaningful instructions and important status in ordinary document content where possible. Pixels can be an effective presentation, but they should not become an unexplained barrier to the surrounding task. #### Test zoom, narrow screens, and reduced motion Review the page with enlarged text and browser zoom. Content should reflow where appropriate rather than requiring horizontal scrolling to read ordinary paragraphs or reach the main action. Check long names, expanded accordions, and form errors; these states often reveal layout assumptions that a short sample does not. Tables may need a clearly usable scrolling region, but the whole page should not overflow because one cell contains a long string. Respect reduced-motion preferences by removing or reducing decorative movement, parallax, and unnecessary transitions. Keep content visible if animation does not run. Provide pause for moving content when appropriate. For a game, distinguish essential gameplay movement from decorative shake and flashes; reduced motion should not silently make the game impossible to start. Test real settings rather than assuming that a CSS rule covers every animation library, canvas effect, or timed interaction in the project. #### Combine automated checks with human review Use automated accessibility tools to find mechanical issues, then inspect the rendered page and complete its main task manually. A useful review record names the route, state, issue, expected behavior, and the way you tested it. Prioritize blockers such as unreachable navigation, missing form labels, invisible focus, and unreadable text. After a correction, repeat the task and check adjacent behavior. A visual edit can fix contrast while accidentally removing a button's semantics. Ask for feedback from people who use different access methods when the project scope allows it. Document remaining issues honestly and avoid publishing a compliance claim you have not established. Accessibility remains part of maintenance: new content, longer translations, a different hero photograph, or a changed menu can introduce new problems. Keep the review checklist with your release process so improvements survive later AI revisions and the exported site's deployment. - Run mechanical checks on the actual rendered routes. - Complete the main task with a keyboard. - Review meaningful labels and descriptions manually. - Check phone layout, zoom, and reduced motion. - Retest after edits and record unresolved limitations. **Does passing an automated accessibility scan prove compliance?** No. Automated tools cover only part of the review. Manual task testing, meaningful content, and assessment against the applicable requirements are still needed. **Can an accessible site still use animation?** Yes, when the movement serves the experience and remains controllable. Respect reduced motion, avoid harmful flashing, preserve content without animation, and provide pause where appropriate. ### Use GitHub sync and saved versions without losing your work Canonical: https://uvilno.com/guides/github-sync-and-version-recovery Updated: 2026-10-27 Understand GitHub authorization, imports, source-gated publishing, conflict review, saved-version restoration, and unfinished-build recovery in Uvilno. #### Keep saved versions, Git history, and drafts distinct When reporting a problem, name the artifact you are looking at. ‘The site is broken’ could refer to a retained draft, the current saved preview, a repository branch, or an old deployment. Include the safe version date or branch name and the failing route. This avoids correcting the wrong copy and makes it easier to verify that the recovery reached the destination you actually use. A saved Uvilno version is a completed website result you can review and restore. A Git commit records repository content and history. A recoverable build draft may contain completed private files from an unfinished run but has not necessarily passed verification. These are useful recovery tools with different guarantees. Before choosing one, identify whether you are recovering a design direction, synchronizing code changes, or inspecting work from an interrupted build. Keep a small record of the current release: the saved version, repository and branch if connected, and deployed URL. That gives you a stable reference when a later revision fails. A preview that looks correct is not proof that a repository has been updated, and a successful push is not proof that an external host deployed the right output. Treat each boundary as an action with its own result to verify. Choose the right recovery tool | Artifact | Useful for | Limit | | --- | --- | --- | | Saved version | Returning to a completed design | Does not rewind an external host automatically | | Git commit | Reviewing and coordinating source changes | Does not necessarily include hosted visitor data | | Recoverable draft | Inspecting retained unfinished work | Verification is still unfinished | | Exported archive | Keeping a portable release copy | Needs its own deployment and service setup | #### Authorize GitHub through the real provider flow Uvilno uses an authenticated GitHub authorization popup for the supported repository connection. Review the provider consent page and requested access before continuing. GitHub recommends checking the application identity and the information it requests. Repository access and a builder account are related but distinct permissions; do not assume that clicking a familiar provider logo is merely a harmless visual preference. Use the intended GitHub account and confirm any organization restrictions that apply. Never paste a personal access token into chat or generated code to repair a connection. The supported flow keeps sensitive authorization on the trusted server. If consent is cancelled or the popup fails, the interface should report the real connection state and offer reconnection. Existing repository access may be affected by revocation or organization policy. Check authorization rather than repeatedly initiating a source operation that cannot succeed with the current permission grant. - [GitHub: authorizing OAuth apps](https://docs.github.com/en/apps/oauth-apps/using-oauth-apps/authorizing-oauth-apps) #### Import supported frontend projects with clear expectations A repository import is more than attaching a text reference. It needs a supported project shape, bounded source, reproducible dependencies, and an isolated build or preview path. Uvilno supports its documented static and compatible frontend import workflows, including supported Vite and Next.js static-export projects. That is not a promise that any arbitrary server application, deployment script, or monorepo can run unchanged. Inspect the import result and the runtime it reports. Choose the repository and intended branch carefully. Review what the project contains before bringing it into an AI workflow, especially environment files, private data, and generated artifacts. Keep secrets out of the imported source and configure needed services through trusted mechanisms. After import, open the actual preview, test routes and interactions, and record any unsupported dependency. A successful file read does not establish a successful build, and a successful compile does not establish the application's main behavior. #### Unlock source before publishing it to a repository Connecting GitHub does not bypass Uvilno's source entitlement. Generated files stay private until the project has its permanent unlock or an included paid-plan unlock is applied. Source push and repository export follow that same rule. The $4.99 one-time unlock remains attached to the project; Plus, Pro, and Ultra provide their configured unlock allowances. Review the entitlement state before attempting a source handoff rather than treating repository authorization as proof that export is allowed. After authorization, review the repository destination and visibility. A public repository makes its contents public; a private one still grants access to its authorized collaborators and services. Check assets, font licenses, deployment instructions, and hosted dependencies before publishing. A repository export can contain actual Git history objects without storing your remote credentials. Keep those credentials out of the archive and avoid committing an environment file merely because a local build depends on it. - [Source unlock pricing](/pricing) #### Use a deliberate pull, review, and push cycle Before starting a new source change, determine where the latest accepted work lives. If someone edited the repository, pull and review that change before adding another conflicting revision in the builder. If the builder contains the latest work, inspect the intended push destination and the changes being published. Avoid treating synchronization as an invisible continuous process. Explicit operations make it easier to understand what happened when two people or tools work on the same files. Test a small round trip before relying on the workflow for a major handoff. Make a controlled change, confirm it appears in the expected repository content, then pull an authorized repository change and verify the preview. Preserve a known-good version first. Do not assume that changing the repository triggers external hosting; that depends on your configured deployment pipeline. Likewise, a frontend sync does not copy private visitor records, leads, receipts, or managed-service credentials into Git. - Confirm the intended repository and branch. - Identify where the latest accepted work lives. - Pull and inspect remote changes before overlapping edits. - Review the actual source change before publishing. - Verify preview behavior and any separate deployment afterward. #### Resolve conflicts by choosing the intended final content A conflict means the system cannot safely combine competing changes automatically. It commonly occurs when two changes touch the same content or one side deletes something the other edits. GitHub's documentation explains why a merge needs a deliberate resolution. Do not interpret a conflict as permission to overwrite the repository wholesale. First identify the shared baseline, what changed in the builder, and what changed remotely. Then decide which final behavior should exist. Resolve related files together. A changed button may depend on a handler, style rule, and destination route; keeping only the visual part can create a broken control. After resolving, test the affected journey and nearby features. If the changes are large or the intended result is unclear, preserve both versions and involve the person responsible for the code. A forced replacement can remove work while appearing to simplify the sync, so use the conflict-aware workflow and review the outcome. - [GitHub: understanding merge conflicts](https://docs.github.com/en/pull-requests/reference/merge-conflicts) #### Restore a saved version with an explicit review Use saved-version restoration when a completed revision moved in the wrong direction and you want an earlier website result. Confirm the version's content, assets, and behavior before continuing. Restoration changes the displayed version; pending draft requirements can still be a separate state. If you want the restored version's applied settings to become the basis of future work, use the supported explicit workflow and review what is being copied rather than assuming every draft field rewinds automatically. Restoring frontend content does not necessarily roll back hosted records, payments, or an external deployment. A reading journal's saved books remain service data, not simply part of a page snapshot. If the restored UI expects a different data shape, test it carefully. Keep the release record updated and decide whether the repository or external host also needs a reviewed rollback. Recovery is complete when the visitor journey works again, not merely when the older homepage reappears. #### Use unfinished-build recovery without treating a draft as verified An interrupted build can retain completed private files and a recoverable candidate. Uvilno distinguishes these drafts from the last verified version. A renderable draft may be explored in the isolated owner preview while verification is unfinished, including retained candidates from failed or cancelled runs within the supported retention period. Opening that draft does not unlock source, promote it to a completed version, or prove its interactions are safe to publish. Retrying an unchanged eligible run can reuse retained work after the owner, project, base version, requirements, and assets are checked. If you materially change the brief or base version, do not assume the same recovery applies. Inspect the status and follow the supported retry path. Once the whole candidate passes and saves, test its main journeys before export or sync. Keep failures described accurately: recovered files, a usable draft, a verified version, and a deployed release are four different milestones. **Does linking GitHub unlock my project's source?** No. Repository authorization and project source entitlement are separate. Source push and repository export require the persisted project unlock or an applied included-plan unlock. **Does restoring a version rewind my external host or database?** Not automatically. Review the restored frontend, then handle repository, deployment, and hosted-data changes through their own supported workflows. **Is an unfinished draft safe to publish?** A recoverable draft is explicitly unverified. It remains separate from the last verified version until the required checks and save complete. ## Comparison facts and source citations ### Uvilno and Emergent Compare Uvilno and Emergent for database-backed apps, isolated accounts, multi-file editing, source ownership and separately budgeted deployment. Choose Emergent when a full-stack web or mobile application, backend logic and an agent-driven deployment workflow are central to the brief. Choose Uvilno for conversation-led frontend apps with typed hosted collections, managed app AI, transactional automations and an individual permanent source unlock. A broader app platform can remove infrastructure setup, but its runtime and deployment costs belong in the budget. A source handoff still leaves hosting and service configuration to you. - Agent-led full-stack web and mobile app building. - Standard displays $20/month equivalent billed annually; monthly checkout is unverified here. - Free tier exists; official free-credit descriptions differ. - Code view; GitHub save on Standard and above. - Save source through GitHub; copy individual files in Code view. - Full-stack projects with backend and infrastructure support. - Prompt-driven app creation and iterative requirements. - Agent changes and follow-up prompts. - Build and review an application before deployment. - Managed deployment uses a separate credit allowance. - Custom-domain deployment is documented; check deployment charges. - Backend and database workflows are part of the app platform. - Generated app login requires configuration and testing. - App integrations require the relevant provider setup. - GitHub source handoff on Standard and above. - Review generated content, routes and metadata before launch. - Standard includes 100 credits; additional credits can be purchased. - Exported code excludes secrets and application data; migrate those separately. - Database Viewer and generated backend; export records separately from code. - One-click LLM integration is listed; app configuration and usage still apply. - Custom backend logic can be generated; an equivalent atomic rule contract was not measured here. - Emergent Auth supports visitor accounts; generated authorization needs testing. - Agent chat and Code view provide project editing; no edit-time benchmark was run. - Testing, debugging and troubleshooting consume credits in the published credit model. Sources: - [Emergent plans](https://emergent.sh/pricing) (checked 2026-10-27) - [Emergent website builder and deployment FAQ](https://emergent.sh/learn/ai-website-builder-faq) (checked 2026-10-27) - [Emergent data and code ownership](https://help.emergent.sh/your-data-ownership) (checked 2026-10-27) - [Emergent product FAQ](https://help.emergent.sh/faqs) (checked 2026-10-27) - [Emergent free-tier grant terms](https://help.emergent.sh/plans-the-free-tier) (checked 2026-10-27) - [Emergent credit accounting and testing costs](https://help.emergent.sh/plans-and-credits) (checked 2026-10-27) ### Uvilno and Lovable Uvilno vs Lovable: compare typed app data, built-in AI, source access, Git sync, credit billing and backend portability using current official documentation. Choose Lovable for a web application with managed Cloud services, a visual editor and repository synchronization. Choose Uvilno for schema-driven frontend apps, transactional collection rules, explicit @ context and a permanent source unlock without a required recurring source subscription. Both can produce portable source. Their starting workflows and service dependencies differ; ownership does not automatically migrate a database or authentication service. - AI builder for websites and full-stack web apps. - Pro 100: $25 monthly or $250 annually upfront. - Free plan includes capped daily build grants and limited Cloud/app-AI grants. - Repository sync is available; direct download depends on plan. - Export source and move hosting; services require separate migration. - New apps use TanStack Start; older projects may use React and Vite. - Prompting with a visual editor and preview environment. - Chat changes and repository-backed development. - Preview environments before publishing. - Managed Lovable hosting or your own infrastructure. - Custom-domain workflow is documented; plan and DNS requirements apply. - Built-in Cloud backend with database, storage and compute billing. - App authentication is part of the backend configuration. - Payment integrations require provider credentials and testing. - Two-way GitHub, GitLab and Bitbucket sync; existing-repo import differs. - SEO tools exist; review crawlability and final content. - A shared credit balance funds build, runtime and supported integrations. - Code and data can move; replace or reconfigure backend, AI and connector calls. - Built-in backend with database tables and record editing in the project tools. - Managed app AI connector provides real model calls and workspace usage billing. - Backend functions and scheduled jobs are documented; execution differs from Uvilno's bounded atomic rules. - Backend users and sign-in tools; actual access follows configured permissions. - Chat, generated modules and repository sync; no same-brief timing benchmark was run. - Build/chat and app runtime use the documented credit balance; check action-specific charges. Sources: - [Lovable subscription plans](https://docs.lovable.dev/introduction/subscription-plans) (checked 2026-10-27) - [Lovable credits and usage](https://docs.lovable.dev/introduction/credits-and-usage) (checked 2026-10-27) - [Lovable deployment, hosting and ownership](https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership) (checked 2026-10-27) - [Lovable Git sync](https://docs.lovable.dev/integrations/git-sync-overview) (checked 2026-10-27) - [Lovable built-in backend and jobs](https://docs.lovable.dev/features/cloud) (checked 2026-10-27) - [Lovable managed AI features for apps](https://docs.lovable.dev/features/ai) (checked 2026-10-27) ### Uvilno and Base44 Uvilno vs Base44: compare typed app data, auth, built-in AI, workflows, GitHub source handoff and the difference between a $4.99 unlock and recurring app hosting. Choose Base44 when an integrated app platform with its own data dashboard, hosted backend, access controls and scheduled or event-driven workflows suits your operating model. Choose Uvilno for a chat-and-preview workflow with declared collections, real app AI, transactional data rules, explicit context mentions and a permanent $4.99 source entitlement per project. Both offer source handoff and managed backend services. Exporting files does not itself migrate records, identities, credentials or the hosted services those files call. Compare the actual exit plan, not a claim of universal zero lock-in. - Integrated AI app building, hosted backend and data management. - Starter $192/year; GitHub-listed Builder $480/year, annual billing. - Free includes 25 monthly message credits and 100 integration credits. - In-app code editing; repository workflows through Base Code. - Advertises ownership and two-way GitHub source export; plan conditions apply. - App source plus managed Base44 backend services and developer tooling. - AI chat, visual editor, design controls and project references. - AI edits and repository-based changes with a development preview. - Preview changes and review branch-based repository work. - Apps use Base44 hosting and backend infrastructure. - Paid plans list domain connection; check exact plan and DNS setup. - Built-in entities, records and a data dashboard; test and production data controls. - App sign-in and role/access settings; data permissions require review. - Payments and Stripe setup are documented integrations, not a source-export entitlement. - GitHub integration on Builder and above; Base Code edits connected repositories. - Review generated pages and published metadata; ranking is not guaranteed. - Separate message and integration credit allowances with plan-dependent limits. - Source ownership is documented; migrate backend data and connected services separately. - Typed entities and visual record management are part of the built-in backend. - invokeLLM and app agents use supported managed model presets. - Scheduled, data-event and connector triggers; workflows are replacing automations. - App access and role settings; data permissions remain a separate security configuration. - Base Code edits connected repositories with branch previews and commit history. - Building and live integration work use distinct message/integration credit allowances. Sources: - [Base44 plans, included services and source ownership](https://base44.com/pricing) (checked 2026-10-27) - [Base Code and GitHub repository workflow](https://docs.base44.com/Getting-Started/base-code) (checked 2026-10-27) - [Base44 app data management](https://docs.base44.com/Building-your-app/Managing-your-app-data) (checked 2026-10-27) - [Base44 access and roles](https://docs.base44.com/Setting-up-your-app/Managing-access) (checked 2026-10-27) - [Base44 automation triggers and workflow migration](https://docs.base44.com/Building-your-app/Creating-automations) (checked 2026-10-27) - [Base44 Stripe payment integration](https://docs.base44.com/documentation/setting-up-your-app/setting-up-payments) (checked 2026-10-27) - [Base44 app inference and supported models](https://docs.base44.com/developers/backend/resources/models) (checked 2026-10-27) ### Uvilno and Bolt.new Compare Uvilno and Bolt.new across 24 practical criteria: app data, source handoff, token usage, hosting, integrations and annual budget assumptions. Choose Bolt when you want an in-browser development environment, app services and a hosted publishing path alongside AI editing. Choose Uvilno for a compact chat-and-preview workflow, declared app collections, transactional data rules and an individual permanent source unlock. Bolt bundles a broader development and hosting workflow. Uvilno's source purchase makes the handoff explicit, with production hosting chosen separately. - Browser-based AI website and application development. - Entry Pro $25/month, billed monthly. - Free includes 1M monthly tokens with a 300K daily limit. - Code view and a downloadable project are documented. - Download a project or use GitHub for source handoff. - Web development environment with supported frameworks and packages. - Prompting, image references and visual edits. - Plan Mode, Code view, follow-up prompts and restoration. - In-browser preview controls and project review. - Website hosting is included, with plan-dependent capacity. - Custom domains and branding removal on paid plans. - Bolt Cloud databases and supported external providers. - Authentication integrations are part of the app-building workflow. - Stripe integration is documented; configure your account. - GitHub import, sync and branch workflows. - Paid plans list SEO boosting; audit the actual published pages. - Tokens are limited; large context and changes affect consumption. - Source can be self-hosted; migrate database and service dependencies too. - Bolt Cloud creates databases and provides a data table, logs and user tools. - AI integrations can be implemented in the project; this review did not measure an app-AI proxy. - Server functions and connected services can implement workflows; no atomic-rule equivalence is claimed. - Cloud authentication and user management; verify app-level authorization. - Code view, prompting and GitHub version control; no fixed edit latency established. - Reading and modifying project files consumes model tokens under its usage model. Sources: - [Bolt pricing and plan limits](https://bolt.new/pricing) (checked 2026-10-27) - [Build and refine with Bolt](https://support.bolt.new/building) (checked 2026-10-27) - [Bolt GitHub integration](https://support.bolt.new/integrations/git) (checked 2026-10-27) - [Bolt project download and WebContainer troubleshooting](https://support.bolt.new/faqs/troubleshooting/webcontainer) (checked 2026-10-27) - [Bolt Cloud data and user management](https://support.bolt.new/building/intro-bolt) (checked 2026-10-27) - [Bolt model-token usage](https://support.bolt.new/faqs/account-and-subscription/tokens) (checked 2026-10-27) ### Uvilno and v0 Uvilno vs v0 by Vercel: compare website source unlocks with framework-led app development, GitHub, deployment and current per-user pricing. Choose v0 when React or Next.js development, a shared codebase and Vercel deployment are important to the project. Choose Uvilno when you want to refine a website in a preview and unlock its source as a discrete purchase. v0 is closely integrated with the Vercel development workflow while also allowing source export. Hosting and team subscriptions are separate budget decisions. - AI UI and full-stack app development by Vercel. - Plus is advertised at $30/user/month. - Free lists seven daily messages, Design Mode, Vercel deployment and GitHub sync. - Code viewer, repository integration and export. - Source can be exported and deployed outside Vercel. - React, Next.js, TypeScript, Tailwind and shadcn/ui workflows. - Text, screenshots, Figma inputs and Design Mode. - Chat, code edits, versions and GitHub branches. - Branch preview deployments and production review. - Publishing deploys to a connected Vercel project. - Custom domains are managed through the Vercel project. - Database and API integrations; provision services as needed. - Implement app authentication with the chosen provider. - Commerce setup can include Stripe or Shopify; claim/configure services. - GitHub-backed branches, pull requests and CI workflows. - Framework metadata and rendered routes need your review. - Plus includes credits; model token rates and extra usage apply. - Exported code can move; reconfigure framework runtime and service integrations. - Database integrations provision a chosen provider; generated application code uses that service. - App AI can be implemented with model/provider services; verify runtime billing separately. - Generated server code can implement workflows; no Uvilno-style rule parity was tested. - Application roles and authentication depend on generated code and connected providers. - Code changes and GitHub branches support precise development; no edit-speed ranking established. - Messages consume model-priced tokens/credits; Design Mode is a separate editing workflow. Sources: - [v0 current pricing](https://v0.app/pricing) (checked 2026-10-27) - [v0 product and export FAQ](https://v0.app/docs/faqs) (checked 2026-10-27) - [v0 deployments](https://v0.app/docs/deployments) (checked 2026-10-27) - [v0 teams and Vercel billing](https://v0.app/docs/teams) (checked 2026-10-27) ### Uvilno and Replit Agent Compare Uvilno's website source workflow with Replit Agent's development workspace, effort-based AI billing and hosted application infrastructure. Choose Replit Agent when the project needs a development workspace, backend services and a running application under one platform. Choose Uvilno when your first goal is a website you can review visually and unlock for a source handoff. Replit combines development and application operations. That convenience comes with several metered resources, so a subscription alone is not a complete deployment quote. - Agent-assisted application building and development workspace. - Core exists; verify its current price at checkout. - Starter provides limited AI and a time-limited published-app allowance. - Development workspace contains editable project files. - Plan source, dependencies and service data as separate handoff items. - A general development platform with app runtime services. - Agent-led implementation from natural-language requirements. - Effort-based Agent work and developer-controlled edits. - Development review and published deployment are separate stages. - Deployment resources have usage-based billing rules. - Production domain setup belongs to the deployment workflow. - Production databases, compute and network resources are metered. - App authentication requires a configured and reviewed implementation. - Payment behavior needs provider integration, secrets and end-to-end testing. - Development workspace for maintaining application code. - Review generated routes, rendered metadata and public access. - Agent effort and runtime resources are not unlimited. - A migration must include runtime, environment variables and production data. - Managed database development and deployment are documented platform capabilities. - Agent-generated application integrations need their own runtime and provider configuration. - Application code and deployment services determine background-work behavior. - Generated app authentication and access checks must be configured and tested. - An editable development workspace and Agent operate on the project codebase. - Agent work uses effort-based billing; operating resources have their own charges. Sources: - [Replit current pricing](https://replit.com/pricing) (checked 2026-10-27) - [Replit Core plan](https://docs.replit.com/billing/plans/replit-core) (checked 2026-10-27) - [Replit Starter plan](https://docs.replit.com/billing/plans/starter-plan) (checked 2026-10-27) - [Replit AI billing](https://docs.replit.com/billing/ai-billing) (checked 2026-10-27) - [Replit usage-based billing](https://docs.replit.com/billing/about-usage-based-billing) (checked 2026-10-27) ### Uvilno and Cursor Compare Uvilno with Cursor for website projects: visual review versus developer-led code work, current plan pricing and independent hosting responsibilities. Choose Cursor when a developer needs an AI-assisted code editor, repository control and flexibility over the application stack. Choose Uvilno when the owner wants a conversation-led website preview without starting from a development environment. Cursor is a coding environment rather than a like-for-like managed website studio. Developer time, deployment and service setup belong in its budget. - AI-assisted coding environment for developer-led software work. - Plus $8 monthly / $80 annually; Cursor-model allowance, no third-party models. - Free has limited Agent and Chat requests. - Read and edit project files directly in the Agent workflow. - Project files are edited in the development workspace; no per-site source unlock. - Developer chooses the framework, dependencies and runtime. - Developer-led implementation with AI assistance. - Agent edits and code review in a development workflow. - Agent can run terminal commands and inspect applications through its browser tools. - Plan production hosting independently from editor usage. - Configure domains through the selected hosting provider. - Choose and operate backend/database providers yourself. - Implement and configure an authentication provider. - Implement provider SDKs, server validation and payment flows. - Repository-centric work; Premium adds Origin hosting and Bugbot features. - Developer implements metadata, rendering and crawl controls. - Plan usage is limited; third-party models have separate usage charges. - Project source remains yours; infrastructure and licenses still matter. - Works with databases in your project; a managed app database is not established by this pricing page. - Coding-agent model access is distinct from app visitors' inference infrastructure. - Cloud agent automations concern development; app database workflows remain project code. - Your application implements visitor roles; editor/team permissions are a different boundary. - Repository-aware coding and agent tools in your development environment. - AI pool and separately billed third-party model usage depend on the selected subscription. Sources: - [Cursor current pricing](https://cursor.com/pricing) (checked 2026-10-28) - [Cursor models and pricing](https://cursor.com/docs/models-and-pricing) (checked 2026-10-28) - [Cursor Agent tools and workflow](https://cursor.com/docs/agent/overview) (checked 2026-10-28) ### Uvilno and Framer Uvilno vs Framer: compare conversational website source exports with a visual design canvas, hosted CMS workflow and current annual site-plan pricing. Choose Framer for a visual design canvas, hosted marketing site, CMS content and an ongoing publishing workflow. Choose Uvilno when the desired handoff is exportable website source and you are prepared to choose a production host. Framer's managed publishing is convenient for a design-led site. Its official documentation does not offer HTML export for independent self-hosting, which is a meaningful distinction for source handoff. - Visual website design and managed publishing. - Basic $10/month equivalent, billed yearly ($120 upfront). - Free Framer domain, limited bandwidth and trial AI credits. - Work in Framer's visual project and supported code components. - Officially no HTML export for independent self-hosting. - Framer-managed rendering, assets and hosting infrastructure. - Visual design canvas, CMS and AI-assisted work. - Edit the design and content within the platform. - Published site workflow; staging/branch features vary by plan. - Managed hosting is part of the site plan. - Paid plans support connecting your own domain. - CMS collections with plan limits; external app services need integration. - Site password features differ from a full visitor-account application. - Commerce and payment requirements need a specific supported integration. - Design platform rather than an arbitrary code-repository editor. - Built-in SEO; inspect final metadata, links and content. - AI credits, bandwidth, CMS and editor limits depend on plan. - Independent source hosting requires rebuilding rather than native HTML export. - CMS collections organize published content; they are not a general app-record ORM. - AI design agents are listed; app-user inference is a separate integration question. - Publishing and content tooling differ from arbitrary transactional app database rules. - Editor roles and site password protection are not per-record visitor authorization. - Visual design, components and overrides; native HTML source export is not supported. - Agents consume credits; editor/hosting charges follow their respective plan rules. Sources: - [Framer site plans](https://www.framer.com/pricing) (checked 2026-10-27) - [Framer HTML export and self-hosting policy](https://www.framer.com/help/articles/can-i-export-my-website-to-html-and-self-host-it/) (checked 2026-10-27) - [Framer subscriptions and charges](https://www.framer.com/help/articles/subscriptions-and-charges/) (checked 2026-10-27) ### Uvilno and Webflow Compare Uvilno and Webflow across site publishing, CMS, code export, workspace versus site billing, and practical source portability limits. Choose Webflow when a visual website system, structured CMS content and an ongoing managed publishing workflow are the main requirements. Choose Uvilno when you want to build by conversation and purchase a permanent source entitlement for an individual project. Webflow separates site hosting plans from workspace features such as code export. Price the specific combination you need rather than assuming every paid site can export all its services. - Visual website platform, CMS and managed publishing. - Basic site $15/month billed yearly ($180 upfront). - Starter includes two static pages and a Webflow.io domain. - Visual designer; code export is a paid Workspace feature. - HTML/CSS/JavaScript/assets export with important feature exclusions. - Visual site model; exported static assets differ from hosted app services. - Visual styling, components, CMS and AI features. - Edit and publish through Webflow's design and content tools. - Review a staged site before publishing changes. - Site plans provide managed hosting; Workspace billing is separate. - Paid site plans support a custom domain. - CMS is in applicable site plans; its database is not included in code export. - User account behavior does not transfer in a static code export. - Ecommerce functionality is excluded from the static source export. - Static code export is distinct from ongoing repository-based app editing. - Platform SEO tools; review content and export behavior. - Pages, bandwidth, AI and CMS limits depend on site/workspace plan. - Static export can move; CMS, ecommerce, forms and other services need replacement. - CMS content records and APIs; a static code export excludes the hosted CMS backend. - Webflow AI supports building/content workflows; visitor AI needs an app integration. - CMS APIs and application integrations differ from a bundled per-record transactional rule SDK. - Site/Workspace governance is distinct from generated app visitor permissions. - Visual designer, code components and export rather than a source-first chat-only workflow. - AI and hosting allowances vary by plan; verify the action and service being billed. Sources: - [Webflow current site and workspace pricing](https://webflow.com/pricing) (checked 2026-10-27) - [Webflow code export requirements and exclusions](https://help.webflow.com/hc/en-us/articles/33961386739347-How-do-I-export-my-Webflow-site-code) (checked 2026-10-27) ## Three-way builder comparisons ### Emergent vs Lovable (2026): backend, billing and code ownership Canonical: https://uvilno.com/compare/emergent-vs-lovable Updated: 2026-10-28 Emergent and Lovable both address conversation-driven application building. Emergent's published offer includes web and mobile building and GitHub integration on Standard. Lovable documents a managed backend with database, authentication, storage and functions. The decision should follow the required runtime, collaboration workflow, usage policy and a tested service handoff; neither the presence of a backend nor one successful preview proves that an application meets its requirements. **Uvilno:** Uvilno belongs on this shortlist when a creator wants a chat-and-preview workflow, typed managed app data and a permanent source unlock for one project. It is particularly relevant to a frontend app whose scope fits the documented SDK. Its $4.99 source entitlement does not include unlimited generation or migration of every hosted dependency. #### Start with the backend contract For a client portal, specify who can read each record, where a server-only operation runs, and how uploads are authorized. Lovable's built-in backend means separate Supabase setup is not universally required. Ask each platform to implement the same permission boundary, then exercise it with two visitor accounts rather than judging the opening screen. Sources: - https://docs.lovable.dev/features/cloud - https://emergent.sh/pricing #### Separate the building allowance from operation Emergent's rendered pricing page marks its Standard $20 monthly equivalent as annual billing. Lovable publishes a Pro 100 option at $25 monthly or $250 annually. Lovable's current documentation describes one credit balance covering building and running the app. Record the billing period, included allowance, extra usage and running costs before comparing a twelve-month budget. Sources: - https://emergent.sh/pricing - https://docs.lovable.dev/introduction/subscription-plans - https://docs.lovable.dev/introduction/credits-and-usage #### Make a handoff prove something Create a small project with a protected route, one saved record and an uploaded file. Export or synchronize the code, then account separately for data, identity configuration, environment variables and deployment. Lovable explicitly distinguishes the database from source code; a repository alone should not be counted as a completed service migration on any of these platforms. Sources: - https://docs.lovable.dev/introduction/faq Uvilno publishes this comparison and is displayed first as an editorial presentation choice, not an independent ranking. Vendor statements come from the linked official documentation reviewed on October 28, 2026. No common-brief generation contest, aesthetic score, universal frame rate or edit-latency benchmark was performed for this page. A source handoff and migration of hosted data, accounts and services are separate tasks. ### Lovable vs Bolt.new (2026): cloud, credits and source handoff Canonical: https://uvilno.com/compare/lovable-vs-bolt Updated: 2026-10-28 Lovable and Bolt.new both provide app-building workflows with managed backend options. Lovable documents a shared credit balance for building and app operation; Bolt advertises token allowances and Bolt Cloud hosting and databases. A useful comparison follows the cost and responsibility for the same deployed workflow, rather than assuming that one product needs manual backend wiring or that the other's subscription covers every operating expense. **Uvilno:** Consider Uvilno for a narrowly defined web application whose source entitlement should remain separate from recurring generation. The visible remaining-usage meter, saved versions and free mapped visual changes can make iteration easier to account for. A $4.99 unlock is a permanent source handoff for one project, not a substitute for a generation or infrastructure budget. #### Both products can supply a backend Lovable Cloud includes managed database, authentication and storage. Bolt Cloud also includes database and user-management facilities. A universal claim that either product can only work after manually connecting Supabase would misdescribe the current offer. Compare schema editing, permission review, backup and recovery behavior for the particular backend you choose. Sources: - https://docs.lovable.dev/features/cloud - https://support.bolt.new/bolt-cloud - https://support.bolt.new/bolt-cloud/database #### Credit counts are not token counts Lovable Pro 100 and Bolt Pro both list a $25 monthly entry in the reviewed sources, but their included units and operating policies differ. Lovable uses credits; Bolt's entry Pro offer lists a token allowance. Do not equate one credit with a fixed number of tokens or forecast project cost from subscription price alone. Sources: - https://docs.lovable.dev/introduction/subscription-plans - https://docs.lovable.dev/introduction/credits-and-usage - https://bolt.new/pricing #### Evaluate the second edit, not only the first page Ask for one navigation change after a working build. Compare the changed files, check that existing form behavior survives, and reopen the saved version. Then repeat a database-backed interaction. These observations reveal the workflow cost for your app without presenting an undocumented edit-speed or error-repair ranking as a fact. Sources: - https://docs.lovable.dev/introduction/faq - https://support.bolt.new/bolt-cloud Uvilno publishes this comparison and is displayed first as an editorial presentation choice, not an independent ranking. Vendor statements come from the linked official documentation reviewed on October 28, 2026. No common-brief generation contest, aesthetic score, universal frame rate or edit-latency benchmark was performed for this page. A source handoff and migration of hosted data, accounts and services are separate tasks. ### Base44 vs Lovable (2026): managed data and code portability Canonical: https://uvilno.com/compare/base44-vs-lovable Updated: 2026-10-28 Base44 and Lovable both document managed app backends, so the choice is more specific than database versus no database. Compare their data model, visitor authorization, operating allowances and export workflow. Base44's CLI eject command copies frontend and backend resources into a separate project but does not copy application data. Lovable also treats code and database exports as separate responsibilities. **Uvilno:** Uvilno offers a third route for an app that fits typed schema collections and the supported SDK: build by chat, review the isolated preview and unlock source permanently for $4.99. Its exported frontend can still depend on Uvilno-managed auth and data. Apply the same migration checklist to Uvilno rather than calling every export a fully independent backend. #### Compare data operations and permission rules Base44's documented core features include database functionality and authentication; Lovable supplies a managed backend too. Define the entities, relationships and allowed operations before choosing. A convincing demonstration should save real records and deny an unauthorized write, not simply display an editable table in the preview. Sources: - https://docs.base44.com/Account-and-billing/Billing-and-plans - https://docs.lovable.dev/features/cloud #### Source access is not a complete data transfer Base44's eject workflow produces a separate local project and a new app identity. Its copied schema starts with an empty database. Lovable's database export is also separate from Git-synchronized code. Record whether files, secrets, functions, user identities and existing rows need additional work; do not describe either platform as universally unable to export source. Sources: - https://docs.base44.com/developers/references/cli/commands/eject - https://docs.lovable.dev/introduction/faq #### Model an operating month Choose a realistic number of active visitors, form submissions and AI requests, then inspect each vendor's current plan and usage policy. A plan's message or integration allowance is not a guaranteed number of complete applications. Preserve the billing interval and quote when estimating a move, and include the work of recreating hosted-service behavior. Sources: - https://docs.base44.com/Account-and-billing/Billing-and-plans - https://docs.lovable.dev/introduction/credits-and-usage Uvilno publishes this comparison and is displayed first as an editorial presentation choice, not an independent ranking. Vendor statements come from the linked official documentation reviewed on October 28, 2026. No common-brief generation contest, aesthetic score, universal frame rate or edit-latency benchmark was performed for this page. A source handoff and migration of hosted data, accounts and services are separate tasks. ### Emergent vs Base44 (2026): application workflow and backend handoff Canonical: https://uvilno.com/compare/emergent-vs-base44 Updated: 2026-10-28 Emergent's offer emphasizes conversation-led web and mobile building with an agent workflow. Base44 documents managed application features including database and authentication, plus a separate-project CLI eject path. Choose around the required runtime, data operations and operational handoff. Neither a broad platform label nor the presence of Git integration establishes that an exported app is independent of its hosted services. **Uvilno:** Uvilno is useful for a browser application that can express its persistence and bounded automations through the published SDK and benefits from a permanent per-project source entitlement. Its chat, preview and saved-file history give a smaller surface to review. Confirm the SDK and frontend runtime meet the brief; this is not a claim that arbitrary server workloads are bundled. #### Write the application boundary first Separate interactive frontend behavior from privileged server operations and external services. Then ask Emergent and Base44 for the same minimal acceptance journey. A working dashboard must demonstrate the record and permission boundary behind its controls; a populated screen or a generated backend file is not the same as a verified integration. Sources: - https://emergent.sh/pricing - https://docs.base44.com/Account-and-billing/Billing-and-plans #### Compare the resource handoff Emergent advertises GitHub integration with Standard. Base44's eject documentation describes copying frontend code and backend resources while leaving data behind. These are useful but different handoff steps. Include a written inventory of environment variables, data, identity configuration and deploy commands before treating either project as moved. Sources: - https://emergent.sh/pricing - https://docs.base44.com/developers/references/cli/commands/eject #### Price a maintenance workflow Include the first build, a permissions correction, a new route and a data migration rehearsal in a trial. Record the allowance used by each action in the vendor's actual units. The cheapest-looking plan does not reveal the number of retries your particular brief will need, and this comparison does not fabricate a completion rate to fill that gap. Sources: - https://emergent.sh/pricing - https://docs.base44.com/Account-and-billing/Billing-and-plans Uvilno publishes this comparison and is displayed first as an editorial presentation choice, not an independent ranking. Vendor statements come from the linked official documentation reviewed on October 28, 2026. No common-brief generation contest, aesthetic score, universal frame rate or edit-latency benchmark was performed for this page. A source handoff and migration of hosted data, accounts and services are separate tasks. ### Emergent vs Bolt.new (2026): runtime, usage and multi-page review Canonical: https://uvilno.com/compare/emergent-vs-bolt Updated: 2026-10-28 Emergent and Bolt.new both offer conversation-led app creation, but their runtime, service and usage contracts need separate review. Emergent's published plans include web and mobile building. Bolt Cloud documents hosted apps and built-in databases. Test the framework and server behavior your application requires, then compare actual usage for the same multi-page edit rather than inferring a winner from a token count or an animated preview. **Uvilno:** Uvilno is another option for a multi-page web app with an explicit route and data contract. Saved files, bounded continuation, preview inspection and file-level restoration make the implementation easier to review. Its finite generation allowance and framework limitations still apply; no platform receives a universal build-completion or response-time guarantee here. #### Verify the required runtime List any privileged backend operation, long-running task and external SDK before evaluating a builder. Then confirm the chosen project's runtime and deployment support those requirements. Bolt's built-in cloud services should not be dismissed as absent, and Emergent's product scope should not be treated as a guarantee that every generated integration is correct. Sources: - https://emergent.sh/pricing - https://support.bolt.new/bolt-cloud #### Check shared navigation across real routes Build a small portal with an index, detail page and settings route. Add a shared navigation change and verify each route directly after refresh. This is a repeatable assessment of multi-page structure and preservation. It does not turn one observed result into a universal claim about either provider's edit precision. Sources: - https://support.bolt.new/bolt-cloud - https://emergent.sh/pricing #### Do not convert allowances with invented ratios Emergent expresses plan capacity in credits, while Bolt's pricing page advertises token allowances. The rendered Standard offer on Emergent is labelled annual; Bolt Pro's reviewed entry is billed monthly. Keep those distinctions visible and measure your own trial. A synthetic credits-to-tokens conversion would make an annual budget look more precise than the evidence allows. Sources: - https://emergent.sh/pricing - https://bolt.new/pricing Uvilno publishes this comparison and is displayed first as an editorial presentation choice, not an independent ranking. Vendor statements come from the linked official documentation reviewed on October 28, 2026. No common-brief generation contest, aesthetic score, universal frame rate or edit-latency benchmark was performed for this page. A source handoff and migration of hosted data, accounts and services are separate tasks. ### Bolt.new vs v0 (2026): app runtime, backend and Git workflow Canonical: https://uvilno.com/compare/bolt-vs-v0 Updated: 2026-10-28 Bolt.new and v0 both address more than isolated UI components. Bolt documents managed cloud services, while v0 documents an app workflow with an editor, Git integration, deployments and backend integrations. The useful distinction is the runtime and operating workflow that fits the project. Verify the chosen framework, service configuration, hosting bill and repository review process rather than describing v0 as UI-only or Bolt as lacking a backend. **Uvilno:** Uvilno provides a conversation-first alternative when a creator wants multi-file frontend generation, supported managed app services and a separate $4.99 source unlock. Its source and compiled exports are useful handoff formats, but its eligible Next.js workflow has its own supported capabilities. Choose from the actual application contract, not a framework name alone. #### Compare app workflows, not old product labels v0's current FAQ describes Git-connected projects, an integrated editor and a sandboxed workflow. Bolt Cloud documents hosting and databases. These products should be assessed as app workflows with their own limits. A current comparison cannot rely on the older shorthand that one only draws React components and the other only runs a browser demo. Sources: - https://v0.app/docs/faqs - https://support.bolt.new/bolt-cloud #### Plan the deployment account v0's pricing offer includes deployment to Vercel and GitHub sync even on Free, while its paid Plus offer adds included credits and collaboration features. Bolt advertises hosting on Free and custom domains on Pro. Include the selected hosting and backend accounts in a deployment rehearsal; a builder subscription is not automatically a cap on infrastructure costs. Sources: - https://v0.app/pricing - https://bolt.new/pricing #### Review a repository change as a team Start from a small application, request one shared component edit and inspect the resulting change set. Verify the saved source, direct route refresh and backend error handling before accepting it. v0's own FAQ warns that generated output can be incomplete or contain bugs; the same review discipline is appropriate for every product on this page. Sources: - https://v0.app/docs/faqs Uvilno publishes this comparison and is displayed first as an editorial presentation choice, not an independent ranking. Vendor statements come from the linked official documentation reviewed on October 28, 2026. No common-brief generation contest, aesthetic score, universal frame rate or edit-latency benchmark was performed for this page. A source handoff and migration of hosted data, accounts and services are separate tasks. ### Replit Agent vs Lovable (2026): hosted apps, usage and ownership Canonical: https://uvilno.com/compare/replit-agent-vs-lovable Updated: 2026-10-28 Replit Agent and Lovable both combine building tools with app-operation features. Replit Core documents Agent modes, connectors, visual editing and publishing. Lovable documents a managed backend and Git synchronization. Decide how much development-environment control, app-service management and deployment responsibility the team needs, then check the current plan quote and actual usage for the intended workload. **Uvilno:** Uvilno is worth considering when a creator wants a focused chat-and-preview studio rather than a broader workspace, with managed data and app identities for supported web applications. A permanent $4.99 unlock covers source access for one project. It should be compared with the full cost of generation, service operation and any required migration, not presented as a fixed total application price. #### Choose who will maintain the app Define whether the maintainer needs to inspect packages, run development commands, review database changes or mostly adjust the interface by conversation. Replit Core documents several development and artifact workflows. Lovable supplies a managed backend and source synchronization. A team with an existing engineering process should test how its own repository review and release checks fit each workflow. Sources: - https://docs.replit.com/billing/plans/replit-core - https://docs.lovable.dev/features/cloud - https://docs.lovable.dev/introduction/faq #### Check plan and operating allowances separately The reviewed Replit Core documentation directs readers to its pricing page for the current quote; this page does not fill a missing machine-readable quote with a guessed price. Lovable publishes specific Pro credit tiers. Preserve taxes, billing periods, app-operation usage and any model-routing choices when preparing a budget. Sources: - https://docs.replit.com/billing/plans/replit-core - https://replit.com/pricing - https://docs.lovable.dev/introduction/subscription-plans - https://docs.lovable.dev/introduction/credits-and-usage #### Test handoff with the application running Save a record and upload a disposable file, then inspect the code handoff and its environment configuration. Test the app on the intended destination before planning a real move. Lovable explicitly separates code and database export; Replit's development environment is also not evidence that every attached service and secret is portable without work. Sources: - https://docs.lovable.dev/introduction/faq - https://docs.replit.com/billing/plans/replit-core Uvilno publishes this comparison and is displayed first as an editorial presentation choice, not an independent ranking. Vendor statements come from the linked official documentation reviewed on October 28, 2026. No common-brief generation contest, aesthetic score, universal frame rate or edit-latency benchmark was performed for this page. A source handoff and migration of hosted data, accounts and services are separate tasks. ### Cursor vs Lovable vs Uvilno (2026): choose the development workflow Canonical: https://uvilno.com/compare/cursor-vs-lovable Updated: 2026-10-28 Cursor and Lovable are different starting points. Cursor's editor and agent workflow revolves around a codebase and its development tools; Lovable combines conversation-led building with managed app infrastructure. The choice depends on who owns runtime configuration, service setup and deployment. Compare the actual current plan and model allowance, then test how a developer or non-developer will maintain the same app after the first build. **Uvilno:** Uvilno combines a smaller chat-and-preview workspace with file, page and inspected-element context, managed SDK services and permanent per-project source access. It can suit creators who want concrete source review without configuring a general development environment first. It does not claim to replace every local editor tool, package ecosystem or arbitrary backend workload. #### Match control to the person doing the work For a developer who already owns a repository, infrastructure and test suite, editor-oriented assistance can fit the existing process. For a creator starting without that environment, a hosted builder can manage more of the initial setup. Run the maintenance task with the actual maintainer; an abstract feature count cannot decide which workflow is easier for that person. Sources: - https://cursor.com/docs/models-and-pricing - https://docs.lovable.dev/features/cloud #### Do not treat editor pricing as app hosting Cursor's current pricing page lists plan-specific model and product allowances; these should not be mistaken for the full operating cost of an application. Lovable's current balance covers both building and running its managed app services. Record which service pays for the database, visitor AI and deployment before interpreting a subscription figure as a project budget. Sources: - https://cursor.com/pricing - https://docs.lovable.dev/introduction/credits-and-usage #### Compare context with a bounded request Use an existing app and request one narrowly described change, such as removing a duplicate navigation control. Review the actual affected files, run the existing checks and test the control in the rendered app. Uvilno's file and selected-element references are another way to scope that task; this page does not convert the presence of a context mechanism into an unmeasured speed ranking. Sources: - https://cursor.com/docs/models-and-pricing - https://docs.lovable.dev/introduction/faq Uvilno publishes this comparison and is displayed first as an editorial presentation choice, not an independent ranking. Vendor statements come from the linked official documentation reviewed on October 28, 2026. No common-brief generation contest, aesthetic score, universal frame rate or edit-latency benchmark was performed for this page. A source handoff and migration of hosted data, accounts and services are separate tasks. ## 2026 full-stack engineering evaluation rubric Uvilno first because Uvilno publishes this comparison; not a measured rank. The five publisher-selected criteria total 100 points. A documented capability is not an equivalent hands-on result. Unknown checks stay unmeasured, never failed. Overall scores remain null until a comparable test protocol is completed. - **Code ownership & export cost: 25 possible points.** Build the same app, obtain its complete source, record the actual purchase, and rebuild on a separate host. Test continued source access and document the backend services that still need migration. - **Database, accounts & app AI: 25 possible points.** Create, edit and remove the same records; reload; repeat with another account; check record permissions; run a real app-AI request and inspect a triggered automation. Record each managed or external dependency. - **Targeted edit precision & speed: 20 possible points.** Apply the same specified changes to matched projects. Compare exact file deltas, verify the rendered target and unchanged routes, and record end-to-end timings including verification. Publish failures as well as successes. - **No-usage editing & recovery: 15 possible points.** Make the same direct edit and introduce the same reproducible fault. Inspect actual usage ledgers, repair limits and saved-version behavior. A limited free path must not be described as unlimited free coding. - **Multi-page & interactive applications: 15 possible points.** Build and navigate the same route plan, exercise state across pages, then measure frame time and input response on named devices. Framework support or an attractive screenshot does not establish a universal 60 FPS result. ### Uvilno Overall score: not measured. 17 documented or recorded checklist conditions; 3 unmeasured; 0 explicitly unmet. This is evidence coverage, not product quality. **Code ownership & export cost** - Documented: An owned, unlocked project can export its runtime-appropriate source and referenced media. Sources: https://uvilno.com/docs. - Documented: Supported frontends can use authorized GitHub import, push and pull; a source push requires unlock. Sources: https://uvilno.com/docs. - Documented: Free is $0; a source unlock is $4.99 once. Plus is $10/month, Pro $20/month and Ultra $59/month. Generation and hosted services are separate. Sources: https://uvilno.com/pricing. - Documented: The $4.99 purchase permanently unlocks one project's source; subscription generation remains finite. Sources: https://uvilno.com/pricing. - Documented: Source export is not a copy of managed records, visitor identities, payment credentials or hosted services. Sources: https://uvilno.com/docs. **Database, accounts & app AI** - Documented: Uvilno.db CRUD and App Data use schema-declared, persistent app records. Sources: https://uvilno.com/benchmarks. - Documented: Managed visitor identities are isolated per project from the creator's platform session. Sources: https://uvilno.com/benchmarks. - Documented: Uvilno.ai.ask/json makes real owner-funded calls; admission limits and a 600-output-token ceiling apply. Sources: https://uvilno.com/benchmarks. - Documented: data/schema.json declares collection fields and access; the runtime exposes validated data operations. Sources: https://uvilno.com/docs. - Documented: Bounded record effects and notifications execute in the triggering record transaction; arbitrary server code, email and network actions are outside this rules engine. Sources: https://uvilno.com/benchmarks. **Targeted edit precision & speed** - Documented: @file, @page, @db and bounded repository retrieval supply explicit context. Sources: https://uvilno.com/docs. - Documented: The mapped inspector supplies selected-element context or a supported direct text, link or color change. Sources: https://uvilno.com/docs. - Unmeasured: Recorded targeted checks do not establish a comparative edit-accuracy rate across vendors. - Unmeasured: No matched cross-vendor timing establishes a universal 4–8 second edit duration. **No-usage editing & recovery** - Documented: Mapped direct text, link and color changes use 0% model usage; unsupported computed elements use the normal scoped-edit path. Sources: https://uvilno.com/docs. - Documented: A reproduced native-static runtime fault was repaired and rechecked without customer usage. This bounded path is rate-limited and does not cover every engine error. Sources: https://uvilno.com/benchmarks. - Documented: Saved-version and entitled per-file restores preserve checkpoints without invoking the generation model; verification still applies. Sources: https://uvilno.com/docs. **Multi-page & interactive applications** - Documented: Contract-first route plans and reusable modules support multi-page frontends; saved legacy and eligible Next.js projects retain their respective runtimes. Sources: https://uvilno.com/docs. - Documented: The portable Canvas game runtime and authored interactive fixtures provide workload evidence, not a promise about every generated game. Sources: https://uvilno.com/benchmarks. - Unmeasured: A matched hardware/workload frame-time study has not been published; 60 FPS is not guaranteed. ### Emergent Overall score: not measured. 7 documented or recorded checklist conditions; 13 unmeasured; 0 explicitly unmet. This is evidence coverage, not product quality. **Code ownership & export cost** - Documented: Save source through GitHub; copy individual files in Code view. Sources: https://help.emergent.sh/your-data-ownership. - Documented: GitHub source handoff on Standard and above. Sources: https://help.emergent.sh/your-data-ownership. - Unmeasured: The displayed Standard offer is $20/month equivalent under Annual billing ($240/year). A month-to-month checkout price is not verified here. An equivalent complete source-access purchase has not been priced by a matched export test. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Documented: Exported code excludes secrets and application data; migrate those separately. Sources: https://help.emergent.sh/your-data-ownership. **Database, accounts & app AI** - Documented: Backend and database workflows are part of the app platform. Sources: https://help.emergent.sh/faqs. - Documented: Generated app login requires configuration and testing. Sources: https://help.emergent.sh/faqs. - Documented: One-click LLM integration is listed; app configuration and usage still apply. Sources: https://emergent.sh/pricing. - Unmeasured: An equivalent schema-backed SDK contract has not been inspected here. - Unmeasured: This automation condition has not been established here; supported integrations may provide it. **Targeted edit precision & speed** - Unmeasured: Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. - Unmeasured: Equivalent selected-element context has not been checked here. - Unmeasured: No equivalent before/after edit-accuracy benchmark is recorded here. - Unmeasured: No comparable end-to-end edit-timing distribution is recorded here. **No-usage editing & recovery** - Unmeasured: No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. - Unmeasured: The same injected fault and actual customer usage ledger have not been inspected on this product. - Unmeasured: A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison. **Multi-page & interactive applications** - Documented: Agent-led full-stack web and mobile app building. Sources: https://help.emergent.sh/faqs. - Unmeasured: An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. - Unmeasured: No matched workload/device frame-time measurement is recorded here. ### Lovable Overall score: not measured. 9 documented or recorded checklist conditions; 11 unmeasured; 0 explicitly unmet. This is evidence coverage, not product quality. **Code ownership & export cost** - Documented: Export source and move hosting; services require separate migration. Sources: https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership. - Documented: Two-way GitHub, GitLab and Bitbucket sync; existing-repo import differs. Sources: https://docs.lovable.dev/integrations/git-sync-overview. - Unmeasured: Pro 100: $25 billed monthly, or $250 paid for a year. Annual payment is upfront. An equivalent complete source-access purchase has not been priced by a matched export test. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Documented: Code and data can move; replace or reconfigure backend, AI and connector calls. Sources: https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership. **Database, accounts & app AI** - Documented: Built-in Cloud backend with database, storage and compute billing. Sources: https://docs.lovable.dev/introduction/credits-and-usage. - Documented: App authentication is part of the backend configuration. Sources: https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership. - Documented: Managed app AI connector provides real model calls and workspace usage billing. Sources: https://docs.lovable.dev/features/ai. - Unmeasured: An equivalent schema-backed SDK contract has not been inspected here. - Unmeasured: This automation condition has not been established here; supported integrations may provide it. **Targeted edit precision & speed** - Unmeasured: Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. - Documented: The preview toolbar attaches one or more selected elements to the chat as edit context; sending a requested change consumes standard build usage. Sources: https://docs.lovable.dev/features/preview-toolbar. - Unmeasured: No equivalent before/after edit-accuracy benchmark is recorded here. - Unmeasured: No comparable end-to-end edit-timing distribution is recorded here. **No-usage editing & recovery** - Documented: The preview toolbar includes 100 free inline text edits per account, replenished after 24 hours, with a shared 2,000-edit workspace limit per 24 hours. Further edits use standard credits. Sources: https://docs.lovable.dev/features/preview-toolbar. - Unmeasured: The same injected fault and actual customer usage ledger have not been inspected on this product. - Unmeasured: A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison. **Multi-page & interactive applications** - Documented: AI builder for websites and full-stack web apps. Sources: https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership. - Unmeasured: An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. - Unmeasured: No matched workload/device frame-time measurement is recorded here. ### Base44 Overall score: not measured. 9 documented or recorded checklist conditions; 11 unmeasured; 0 explicitly unmet. This is evidence coverage, not product quality. **Code ownership & export cost** - Documented: Advertises ownership and two-way GitHub source export; plan conditions apply. Sources: https://base44.com/pricing. - Documented: GitHub integration on Builder and above; Base Code edits connected repositories. Sources: https://docs.base44.com/Getting-Started/base-code. - Unmeasured: Starter is displayed at $16/month billed annually ($192 upfront). Builder, which lists GitHub integration, is $40/month billed annually ($480 upfront). An equivalent complete source-access purchase has not been priced by a matched export test. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Documented: Source ownership is documented; migrate backend data and connected services separately. Sources: https://docs.base44.com/Getting-Started/base-code. **Database, accounts & app AI** - Documented: Built-in entities, records and a data dashboard; test and production data controls. Sources: https://docs.base44.com/Building-your-app/Managing-your-app-data. - Documented: App sign-in and role/access settings; data permissions require review. Sources: https://docs.base44.com/Setting-up-your-app/Managing-access. - Documented: invokeLLM and app agents use supported managed model presets. Sources: https://docs.base44.com/developers/backend/resources/models. - Documented: Typed entities and visual record management are part of the built-in backend. Sources: https://docs.base44.com/Building-your-app/Managing-your-app-data. - Documented: Scheduled, data-event and connector triggers; workflows are replacing automations. Sources: https://docs.base44.com/Building-your-app/Creating-automations. **Targeted edit precision & speed** - Unmeasured: Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. - Unmeasured: Equivalent selected-element context has not been checked here. - Unmeasured: No equivalent before/after edit-accuracy benchmark is recorded here. - Unmeasured: No comparable end-to-end edit-timing distribution is recorded here. **No-usage editing & recovery** - Unmeasured: No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. - Unmeasured: The same injected fault and actual customer usage ledger have not been inspected on this product. - Unmeasured: A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison. **Multi-page & interactive applications** - Documented: Integrated AI app building, hosted backend and data management. Sources: https://base44.com/pricing. - Unmeasured: An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. - Unmeasured: No matched workload/device frame-time measurement is recorded here. ### Bolt.new Overall score: not measured. 6 documented or recorded checklist conditions; 14 unmeasured; 0 explicitly unmet. This is evidence coverage, not product quality. **Code ownership & export cost** - Documented: Download a project or use GitHub for source handoff. Sources: https://support.bolt.new/integrations/git. - Documented: GitHub import, sync and branch workflows. Sources: https://support.bolt.new/integrations/git. - Unmeasured: Entry Pro is $25 billed monthly. No unverified annual discount is applied. An equivalent complete source-access purchase has not been priced by a matched export test. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Documented: Source can be self-hosted; migrate database and service dependencies too. Sources: https://support.bolt.new/integrations/git. **Database, accounts & app AI** - Documented: Bolt Cloud databases and supported external providers. Sources: https://bolt.new/pricing. - Documented: Authentication integrations are part of the app-building workflow. Sources: https://support.bolt.new/building. - Unmeasured: App-user inference has not been established in this source set; builder AI alone is not treated as app AI. - Unmeasured: An equivalent schema-backed SDK contract has not been inspected here. - Unmeasured: This automation condition has not been established here; supported integrations may provide it. **Targeted edit precision & speed** - Unmeasured: Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. - Unmeasured: Equivalent selected-element context has not been checked here. - Unmeasured: No equivalent before/after edit-accuracy benchmark is recorded here. - Unmeasured: No comparable end-to-end edit-timing distribution is recorded here. **No-usage editing & recovery** - Unmeasured: No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. - Unmeasured: The same injected fault and actual customer usage ledger have not been inspected on this product. - Unmeasured: A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison. **Multi-page & interactive applications** - Documented: Browser-based AI website and application development. Sources: https://support.bolt.new/building. - Unmeasured: An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. - Unmeasured: No matched workload/device frame-time measurement is recorded here. ### v0 Overall score: not measured. 6 documented or recorded checklist conditions; 14 unmeasured; 0 explicitly unmet. This is evidence coverage, not product quality. **Code ownership & export cost** - Documented: Source can be exported and deployed outside Vercel. Sources: https://v0.app/docs/faqs. - Documented: GitHub-backed branches, pull requests and CI workflows. Sources: https://v0.app/docs/deployments. - Unmeasured: Plus is $30 per user per month at the checked published offer; one user is modeled. An equivalent complete source-access purchase has not been priced by a matched export test. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Documented: Exported code can move; reconfigure framework runtime and service integrations. Sources: https://v0.app/docs/faqs. **Database, accounts & app AI** - Documented: Database and API integrations; provision services as needed. Sources: https://v0.app/docs/faqs. - Documented: Implement app authentication with the chosen provider. Sources: https://v0.app/docs/faqs. - Unmeasured: App-user inference has not been established in this source set; builder AI alone is not treated as app AI. - Unmeasured: An equivalent schema-backed SDK contract has not been inspected here. - Unmeasured: This automation condition has not been established here; supported integrations may provide it. **Targeted edit precision & speed** - Unmeasured: Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. - Unmeasured: Equivalent selected-element context has not been checked here. - Unmeasured: No equivalent before/after edit-accuracy benchmark is recorded here. - Unmeasured: No comparable end-to-end edit-timing distribution is recorded here. **No-usage editing & recovery** - Unmeasured: No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. - Unmeasured: The same injected fault and actual customer usage ledger have not been inspected on this product. - Unmeasured: A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison. **Multi-page & interactive applications** - Documented: AI UI and full-stack app development by Vercel. Sources: https://v0.app/docs/faqs. - Unmeasured: An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. - Unmeasured: No matched workload/device frame-time measurement is recorded here. ### Replit Agent Overall score: not measured. 6 documented or recorded checklist conditions; 14 unmeasured; 0 explicitly unmet. This is evidence coverage, not product quality. **Code ownership & export cost** - Documented: Plan source, dependencies and service data as separate handoff items. Sources: https://docs.replit.com/billing/about-usage-based-billing. - Documented: Development workspace for maintaining application code. Sources: https://docs.replit.com/billing/plans/replit-core. - Unmeasured: The current official pricing page did not expose a verifiable Core amount in accessible text. Enter your confirmed current monthly quote below. An equivalent complete source-access purchase has not been priced by a matched export test. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Documented: A migration must include runtime, environment variables and production data. Sources: https://docs.replit.com/billing/about-usage-based-billing. **Database, accounts & app AI** - Documented: Production databases, compute and network resources are metered. Sources: https://docs.replit.com/billing/about-usage-based-billing. - Documented: App authentication requires a configured and reviewed implementation. Sources: https://docs.replit.com/billing/plans/replit-core. - Unmeasured: App-user inference has not been established in this source set; builder AI alone is not treated as app AI. - Unmeasured: An equivalent schema-backed SDK contract has not been inspected here. - Unmeasured: This automation condition has not been established here; supported integrations may provide it. **Targeted edit precision & speed** - Unmeasured: Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. - Unmeasured: Equivalent selected-element context has not been checked here. - Unmeasured: No equivalent before/after edit-accuracy benchmark is recorded here. - Unmeasured: No comparable end-to-end edit-timing distribution is recorded here. **No-usage editing & recovery** - Unmeasured: No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. - Unmeasured: The same injected fault and actual customer usage ledger have not been inspected on this product. - Unmeasured: A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison. **Multi-page & interactive applications** - Documented: Agent-assisted application building and development workspace. Sources: https://replit.com/pricing. - Unmeasured: An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. - Unmeasured: No matched workload/device frame-time measurement is recorded here. ### Cursor Overall score: not measured. 4 documented or recorded checklist conditions; 16 unmeasured; 0 explicitly unmet. This is evidence coverage, not product quality. **Code ownership & export cost** - Documented: Project files are edited in the development workspace; no per-site source unlock. Sources: https://cursor.com/docs/agent/overview. - Documented: Repository-centric work; Premium adds Origin hosting and Bugbot features. Sources: https://cursor.com/pricing. - Unmeasured: Current Plus is $8 monthly or $80 annually upfront. Included Cursor models are Grok and Composer; third-party models are not included on Plus. An equivalent complete source-access purchase has not been priced by a matched export test. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Documented: Project source remains yours; infrastructure and licenses still matter. Sources: https://cursor.com/docs/models-and-pricing. **Database, accounts & app AI** - Unmeasured: A general app-record database has not been established in this source set; a CMS is not assumed equivalent. - Unmeasured: An equivalent managed app-visitor identity flow has not been checked here. - Unmeasured: App-user inference has not been established in this source set; builder AI alone is not treated as app AI. - Unmeasured: An equivalent schema-backed SDK contract has not been inspected here. - Unmeasured: This automation condition has not been established here; supported integrations may provide it. **Targeted edit precision & speed** - Unmeasured: Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. - Unmeasured: Equivalent selected-element context has not been checked here. - Unmeasured: No equivalent before/after edit-accuracy benchmark is recorded here. - Unmeasured: No comparable end-to-end edit-timing distribution is recorded here. **No-usage editing & recovery** - Unmeasured: No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. - Unmeasured: The same injected fault and actual customer usage ledger have not been inspected on this product. - Unmeasured: A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison. **Multi-page & interactive applications** - Documented: AI-assisted coding environment for developer-led software work. Sources: https://cursor.com/docs/models-and-pricing. - Unmeasured: An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. - Unmeasured: No matched workload/device frame-time measurement is recorded here. ### Framer Overall score: not measured. 2 documented or recorded checklist conditions; 17 unmeasured; 1 explicitly unmet. This is evidence coverage, not product quality. **Code ownership & export cost** - Documented limitation: Officially no HTML export for independent self-hosting. Sources: https://www.framer.com/help/articles/can-i-export-my-website-to-html-and-self-host-it/. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Unmeasured: Basic is advertised at $10/month with yearly billing: $120 paid upfront for one site. An equivalent complete source-access purchase has not been priced by a matched export test. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Documented: Independent source hosting requires rebuilding rather than native HTML export. Sources: https://www.framer.com/help/articles/can-i-export-my-website-to-html-and-self-host-it/. **Database, accounts & app AI** - Unmeasured: A general app-record database has not been established in this source set; a CMS is not assumed equivalent. - Unmeasured: An equivalent managed app-visitor identity flow has not been checked here. - Unmeasured: App-user inference has not been established in this source set; builder AI alone is not treated as app AI. - Unmeasured: An equivalent schema-backed SDK contract has not been inspected here. - Unmeasured: This automation condition has not been established here; supported integrations may provide it. **Targeted edit precision & speed** - Unmeasured: Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. - Unmeasured: Equivalent selected-element context has not been checked here. - Unmeasured: No equivalent before/after edit-accuracy benchmark is recorded here. - Unmeasured: No comparable end-to-end edit-timing distribution is recorded here. **No-usage editing & recovery** - Unmeasured: No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. - Unmeasured: The same injected fault and actual customer usage ledger have not been inspected on this product. - Unmeasured: A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison. **Multi-page & interactive applications** - Documented: Visual website design and managed publishing. Sources: https://www.framer.com/pricing. - Unmeasured: An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. - Unmeasured: No matched workload/device frame-time measurement is recorded here. ### Webflow Overall score: not measured. 3 documented or recorded checklist conditions; 17 unmeasured; 0 explicitly unmet. This is evidence coverage, not product quality. **Code ownership & export cost** - Documented: HTML/CSS/JavaScript/assets export with important feature exclusions. Sources: https://help.webflow.com/hc/en-us/articles/33961386739347-How-do-I-export-my-Webflow-site-code. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Unmeasured: Basic site: $15/month billed yearly ($180 upfront). This models hosted publishing, not a paid export workspace. An equivalent complete source-access purchase has not been priced by a matched export test. - Unmeasured: This specific source-access condition has not been established here; it is not marked unsupported. - Documented: Static export can move; CMS, ecommerce, forms and other services need replacement. Sources: https://help.webflow.com/hc/en-us/articles/33961386739347-How-do-I-export-my-Webflow-site-code. **Database, accounts & app AI** - Unmeasured: A general app-record database has not been established in this source set; a CMS is not assumed equivalent. - Unmeasured: An equivalent managed app-visitor identity flow has not been checked here. - Unmeasured: App-user inference has not been established in this source set; builder AI alone is not treated as app AI. - Unmeasured: An equivalent schema-backed SDK contract has not been inspected here. - Unmeasured: This automation condition has not been established here; supported integrations may provide it. **Targeted edit precision & speed** - Unmeasured: Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. - Unmeasured: Equivalent selected-element context has not been checked here. - Unmeasured: No equivalent before/after edit-accuracy benchmark is recorded here. - Unmeasured: No comparable end-to-end edit-timing distribution is recorded here. **No-usage editing & recovery** - Unmeasured: No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. - Unmeasured: The same injected fault and actual customer usage ledger have not been inspected on this product. - Unmeasured: A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison. **Multi-page & interactive applications** - Documented: Visual website platform, CMS and managed publishing. Sources: https://webflow.com/pricing. - Unmeasured: An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. - Unmeasured: No matched workload/device frame-time measurement is recorded here. ## Use-case briefs and requirements ### Full-Stack AI App Builder with Managed Data and Auth Canonical: https://uvilno.com/build/full-stack-ai-app-builder Build multi-page apps with typed collections, isolated visitor accounts, transactional automations and real in-app AI. Review the architecture before launch. An application becomes useful when its records survive a reload, its accounts protect the right data, and every action reports what actually happened. Uvilno combines a contract-first frontend workflow with managed project accounts, typed Uvilno.db collections, declarative automations and optional Uvilno.ai inference. Start with the user journey and the data it requires, then inspect the saved result. These hosted capabilities support a defined application scope; exporting the frontend does not independently provision the backend. Audience: Founders and small product teams building an account-based application around a specific record workflow. Routes: - /: Explain the product. Describe the task, supported result and real route into the app. - /login: Isolated app identity. Use project-specific visitor accounts, never the creator’s platform session. - /workspace: Persistent working records. Declare fields and ownership in data/schema.json; connect forms and lists to Uvilno.db. - /activity: Explain committed changes. Show bounded, scoped automation activity rather than invented live metrics. - /profile: Account preferences. Expose supported profile controls and sign-out with clear failure states. Interactions: - Create, update and remove real records with validation, revision checks and refresh-safe lists. - Run declared transactional create/update/increment/notification actions and inspect Automations & Logs. - Request real, bounded Uvilno.ai text or JSON results when AI is part of the product, then validate the domain fields. Service boundaries: - Guest/Member/Admin preview personas change presentation only; private records remain protected by the actual visitor identity. - Managed auth, database, AI and payments remain hosted dependencies after source export. Stripe checkout is currently test mode. - Free automatic runtime repair is bounded and applies to native static projects; production security and operational review remain necessary. Starter briefs: **A customer follow-up workspace** Build a multi-page client follow-up application with Home, Login, Register, Workspace, Activity and Profile routes. Define private customers and followups collections in data/schema.json with typed fields and a valid customer reference. Use Uvilno.db for every create, list, update and removal, with subscriptions and clear pending/error states. On creating a follow-up, record a scoped activity entry through a declarative automation. Keep visitors isolated; a preview admin persona must not grant database rights. Use fictional seeds only when visibly labelled. Exclude email sending and live billing, and verify persistence after reload. **An AI-assisted study journal** Create an account-based study journal with Library, Topic detail, Practice and Profile pages plus dedicated app login/register routes. Save topics and practice attempts through private Uvilno.db collections. Use Uvilno.ai.json for short practice-question generation, validate returned question/answer fields, show real inference failure and usage limits, and never return canned success. Store an attempt only after a successful real record write. Label fictional examples, protect each visitor’s records, and keep background scheduling, sensitive student data and live payments outside scope. Use a readable responsive layout with keyboard-accessible forms. **An inventory review application** Plan a stock review app with Overview, Items, Item detail, Adjustments, Activity and account routes. Declare private inventory and adjustment collections with typed quantity fields and references. Connect all CRUD operations to Uvilno.db and use a bounded declarative automation for a validated adjustment and matching activity entry. Show the actual saved values, not fixed KPI arrays. Reject impossible quantities, keep failed form input, and confirm removals. Member/Admin preview sections may demonstrate layout only; do not create real cross-user admin access. Exclude external warehouse sync and live checkout. Check every route and phone layout. **Does every website need a database?** No. Informational websites can remain frontend-only. Collections and managed accounts belong in applications whose requirements need persistence; unnecessary services add complexity and usage. **Can I inspect the real saved data?** The owner’s App Data drawer shows declared collections and actual records. Automations & Logs exposes scoped workflow definitions and committed event metadata, separate from source access. **Do I own the exported backend?** A source unlock gives you exportable frontend/runtime files, not an independently provisioned copy of Uvilno’s hosted auth, database or AI infrastructure. Continue using the documented services or implement a reviewed replacement. ### A Base44 and Emergent Alternative with Source Export Canonical: https://uvilno.com/build/base44-and-emergent-alternative Evaluate Uvilno for multi-page managed-data apps, focused edits and a $4.99 permanent project source unlock. Compare service dependencies before switching. Choosing an app builder means choosing how to design records, review changes, pay for iteration and maintain the result. Uvilno offers isolated app accounts, typed managed collections, transactional automations and bounded in-app AI alongside a $4.99 permanent source unlock per project. Compare the actual workflow against Base44 or Emergent using the same brief and acceptance checks. Source access is useful, but an exported interface still depends on any hosted services it calls; plan that dependency explicitly before moving. Audience: Teams comparing builders for a defined project or planning a careful, permission-respecting migration from an existing app. Routes: - /: Preserve the user’s purpose. Describe the existing job and approved content without copying another platform’s proprietary assets. - /app: Rebuild one complete workflow. Use typed collections and real CRUD for the highest-value existing task. - /login: A separate identity boundary. Implement isolated project accounts; plan identity migration independently. - /settings: Review dependencies. Explain storage, billing mode, export and integration setup before launch. Interactions: - Use file mentions such as @js/app.js, @db:tasks and inspected-element references to request a focused change while retaining unrelated pages. - Compare record persistence, navigation and failure recovery with a written acceptance checklist. - Export an unlocked source package or use supported GitHub handoff, then test the hosted service configuration separately. Service boundaries: - Uvilno has not run a controlled completion-rate or latency benchmark against every competitor; compare published features and your actual trials. - A source export does not migrate customer records, provider credentials, visitor passwords or hosted backend infrastructure automatically. - The $4.99 unlock covers source access for one project, not unlimited generation, free external hosting or live Stripe activation. Starter briefs: **Rebuild a verified task workflow** Rebuild my task application from the functional description I provide, not by copying a competitor’s branding or proprietary content. Keep the first release to Home, App login/register, Tasks, Task detail and Profile. Declare private tasks in data/schema.json and connect create/edit/remove/status/search to real Uvilno.db methods. Preserve the field meanings and explain any unsupported requirement before building. Use file mentions such as @js/app.js and @db:tasks context for later focused edits. Do not imply that existing users, passwords or data have migrated. Label fictional demo rows, test persistence after reload, and list hosted service dependencies in the handoff. **Compare a narrow product slice** Build a project intake tracker I can evaluate against another app builder with the same checklist. Routes: Overview, Login, Register, Requests, Request detail and Profile. Private requests contain title, category, status and notes; all writes use Uvilno.db. Add one transactional activity-log rule and display saved activity. Use no external email, payments or organization permissions. Include empty, validation, failed-write and signed-out states. Keep data fictional until reviewed. I will compare task completion and actual usage myself, so do not publish a competitor score, benchmark claim or estimated completion time in the app. **Prepare a source handoff** Create a multi-page personal project organizer using managed project auth and typed private projects/tasks collections. Support real record creation, editing, filtering and removal, with accessible confirmation and error recovery. Separate shared navigation, data controller and feature modules. Include a concise dependency page explaining that exported auth/data calls still use Uvilno services until replaced, and do not place credentials in client files. Keep GitHub/source actions outside the generated user UI. No fake migration success, live payments or team admin roles. Verify every route and the clean unlocked export workflow separately. **Is Uvilno a like-for-like replacement for every Base44 or Emergent app?** No builder is a universal replacement. Compare the particular authorization rules, integrations, data model, hosting and operational needs. Start with one complete workflow and inspect what remains to configure. **Is the $4.99 unlock a monthly charge?** It is a one-time permanent source unlock for one project. Plus, Pro and Ultra are separate monthly plans with finite AI usage and their stated source entitlements. **Can I keep my existing customer accounts?** Identity and data migration require an explicit implementation and permission to transfer the data. An exported frontend or imported repository alone does not migrate passwords or accounts. ### AI CRM and Internal Tool Builder with Persistent Records Canonical: https://uvilno.com/build/ai-crm-and-internal-tool-builder Build a focused CRM, record manager or operational dashboard with typed fields, real CRUD and inspectable automation activity. Keep authorization explicit. A CRM earns its place when people can find the right customer, record the next action and trust that a change was saved. Define the objects and ownership first, then build the list, detail and form views around them. Uvilno.db connects those routes to typed managed records while declarative automations can log changes or update related values in the same transaction. Begin with a single-visitor workflow and non-sensitive test data; organization access and real administrator powers require a separately reviewed authorization design. Audience: Consultants and operations teams prototyping customer, project, intake or inventory workflows with a clear ownership model. Routes: - /dashboard: Operational summary. Compute counts and status summaries from actual returned records. - /customers: Find the right record. Provide search, sort and filters with empty and failed-load states. - /customers/[id]: Customer context. Link follow-ups and notes through declared references within the same visitor scope. - /activity: Changes you can explain. Display scoped, committed workflow events rather than a fabricated audit trail. - /profile: Personal access. Use isolated project identity and supported account preferences. Interactions: - Create and edit customer records through validated forms, preserving unsaved text when a write fails. - Make status changes and related activity entries atomic, without recursive rules or arbitrary background code. - Keep list totals, detail views and charts synchronized with the actual subscribed collection rows. Service boundaries: - The owner’s App Data manager is not a generated visitor admin role. Preview personas cannot grant access to another visitor’s records. - Avoid real personal or regulated data until permissions, retention, deletion and operational controls have been reviewed for that workload. - Email delivery, calendar sync, multi-organization sharing and external ERP integrations need real configured services and additional implementation. Starter briefs: **A consultant’s client tracker** Build a personal consultant CRM with dedicated app account routes, Dashboard, Customers, Customer detail, Follow-ups and Profile. Define private customers and followups collections with required names, status options and a valid customer reference. Use Uvilno.db for lists and all create/edit/remove forms; derive KPIs from saved rows and include real pending/error states. Add a declarative activity entry when a follow-up is created. Clearly disclose fictional demo records. Exclude email sending, external CRM sync, team sharing and live billing. Make the mobile list and detail navigation work and verify reload persistence. **An equipment service log** Create a private equipment service log with Overview, Equipment, Equipment detail, Service entries and Profile routes. Use typed Uvilno.db collections for equipment and service entries with references, dates and supplied status options. Support create, edit, search, filter and confirmed deletion, including reference-conflict feedback. Use an automation to record a successful service-entry event; do not invent scheduled reminders or external maintenance integrations. Compute due counts from actual records. Label all sample equipment as fictional and do not collect safety-critical approvals. Test accounts remain isolated and every save must survive reload. **An intake review workspace** Build a personal intake-review tool for fictional non-sensitive project requests. Include Login/Register, Overview, Requests, Request detail, Activity and Profile. Declare typed private requests and activity_logs collections and wire every form to Uvilno.db with validation and error recovery. Let me filter by status, update a review note and confirm deletion. Record meaningful updates through bounded declarative automations. A preview Admin section is presentation-only and must not bypass visitor ownership. Do not send email, approve real contracts or imply shared team access. Use a dense readable table with a practical phone alternative. **Will dashboard totals use my real saved rows?** The requested implementation should derive totals from Uvilno.db results and refresh subscribed views. Fixed illustrative metrics must not be presented as operational data. Check the record set and pagination scope before relying on a total. **Can I edit records without spending AI usage?** The owner’s App Data interface performs supported data operations without a generation call. This differs from asking the AI to change the application’s schema or behavior. **Can I give my team administrator access with the persona selector?** No. The selector tests a view. Real team access needs explicit server-side authorization, appropriate data scope and verification; it cannot be granted by client presentation state. ### AI Wrapper and Micro-SaaS Builder with Real In-App AI Canonical: https://uvilno.com/build/ai-wrapper-and-micro-saas-builder Build a narrow AI product using real Uvilno.ai inference, private saved results and explicit usage controls. Prototype checkout in Stripe test mode. A small AI product needs a well-defined input, a useful output and an honest account of failures and limits. Uvilno.ai.ask and Uvilno.ai.json provide real bounded inference through a project-scoped service, while Uvilno.db can store validated results for the signed-in visitor. Design around the current 600-output-token response ceiling and the creator-funded usage allowance. Start with a narrow task that fits those constraints rather than promising unlimited essays, specialist advice or invisible background work. Audience: Founders testing compact AI utilities such as study prompts, brief analysis, categorization or structured content helpers. Routes: - /: Explain the task and limit. Describe supported inputs, intended output and what the tool does not guarantee. - /app: Real inference form. Validate bounded input, show actual loading/failure feedback and render checked results. - /history: Private saved work. Store user-approved, validated results in visitor-owned managed collections. - /pricing: A truthful checkout prototype. Use configured Stripe test checkout with an explicit test label; do not grant fictional live entitlements. - /profile: Account and preferences. Keep generated-app visitor identity separate from the Uvilno creator account. Interactions: - Call actual Uvilno.ai.ask/json requests and show errors or limits without substituting canned successful output. - Validate JSON shape and required domain fields before rendering cards or saving results through Uvilno.db. - Let a visitor review, save, rename and remove their own results while retaining honest inference and persistence states. Service boundaries: - App AI is funded by the creator’s metered studio allowance and is rate-limited; source unlock does not provide unlimited inference. - Stripe is currently in test mode. Live billing, subscription entitlements, refunds and fraud controls need further reviewed configuration. - Do not use a general AI wrapper for regulated decisions or promise factual correctness. Exported AI/auth/data calls remain hosted dependencies. Starter briefs: **An AI research-question helper** Build a compact AI research-question helper with Home, isolated app Login/Register, Generate, History and Profile pages. Use real Uvilno.ai.json to return at most three short questions and a caveat from bounded topic input. Validate the JSON structure and fields before rendering or saving, and show actual inference failures and quota limits without fake responses. Store approved results in a private Uvilno.db collection with rename/remove/search controls. Keep all responses within the managed 600-token output ceiling. Do not claim sources were fetched, provide specialist advice or create live payments. Clearly label test content. **A product-brief review tool** Create an AI brief-review micro-tool with a public explanation page, account routes, Review, Saved reviews and Profile. Call Uvilno.ai.json to produce a short summary, missing-information list and suggested next question from a bounded product brief; validate every required field. Save only when the visitor chooses Save, using private Uvilno.db records and clear pending/error states. No canned analysis, invented market statistics or claims of external research. Explain the inference limit and avoid collecting secrets. If a pricing page is included, use explicitly labelled Stripe test checkout only; do not invent paid account entitlements. **A study-prompt micro-SaaS prototype** Plan a focused study-prompt application with Home, Login/Register, Topic workspace, Saved prompts and Profile pages. Use real Uvilno.ai.ask for a short practice prompt based on a visitor-supplied topic and selected difficulty, within the 600-token response ceiling. Show loading, provider failure and exhausted-allowance feedback honestly. Let visitors save, edit labels and remove their own outputs through typed Uvilno.db records. Do not grade real exams, collect sensitive student information, claim authoritative answers or simulate subscriptions. Separate shared data/auth modules and use an accessible mobile-first reading layout. **Are generated AI answers real model responses?** When the managed AI connector is enabled, Uvilno.ai calls the project-scoped inference endpoint. It requires a real app visitor session, uses the creator’s allowance and returns safe errors on failure. A marketing site about an AI company does not automatically run inference. **Does Uvilno.ai.json guarantee my business schema?** It returns parsed, bounded JSON checked for structural safety. A schema description is not arbitrary JSON-schema validation; the generated app must validate its required domain fields before use. **Can I charge real customers immediately?** The current managed checkout is test mode. Live charging requires live configuration, onboarding and a reviewed entitlement workflow. Test payment confirmation is not a real purchase. ### AI Website Builder for Real Multi-page Sites Canonical: https://uvilno.com/build/ai-website-builder Plan a useful multi-page website, refine it in chat, and review an isolated live preview. Start with three editable business website briefs. A useful website answers a visitor’s questions in an order that makes sense. Give Uvilno the audience, the facts you can stand behind, and the action you want someone to take. Build the home page and its supporting routes together, then refine the actual result in chat. This plan is a starting point for a service business whose offer needs more explanation than one long page can provide. Audience: Independent businesses and small teams with an established offer, real content, and a clear enquiry or signup goal. Routes: - /: The offer. Explain who you help, what changes for them, and where to go next. - /services: Scope and fit. Separate services, deliverables, exclusions, and the questions buyers actually ask. - /work: Evidence. Use supplied projects and photographs with honest descriptions of your contribution. - /contact: A useful enquiry. Collect a name, reply address, and project context through a configured managed form. Interactions: - Navigation opens real routes, with a visible current page and a usable phone menu. - A services selector helps a visitor describe their enquiry without hiding essential content. - The contact form shows validation, a genuine submission result, and a recoverable failure state. Service boundaries: - Supply business facts, prices, testimonials, and legal wording; the builder should not invent evidence. - Managed collection supports suitable contact, newsletter, and waitlist forms. Other services need an explicitly configured connector. - Review responsive behavior and content before sharing. A preview link does not provision a custom domain or a production hosting account. Starter briefs: **An independent consultancy** Build a four-page website for my independent consultancy: Home, Services, Selected work, and Contact. Ask me for missing business facts instead of inventing clients or results. Use an editorial layout with a restrained palette and generous case-study imagery. Services must explain the scope, audience, and deliverables. Connect a simple enquiry form to the managed collector when available, with honest success and error feedback. Make the navigation work on phones. Keep scheduling and payments out of scope. Start with a clear page plan before building. **A neighborhood service** Create a practical website for my local service business. Build separate Home, Services, Service area, and Contact pages. I will supply the business name, actual towns served, contact details, opening hours, and photographs. Prioritize readable mobile information, click-to-call links using the supplied number, and a contact form. Avoid fictional reviews, badges, and guarantees. Add a useful FAQ about the service process and make every call to action lead to a real page or configured form. **A small product company** Plan and build a website for a small product company with Home, Product, How it works, and Contact pages. I will provide the product facts and approved claims. Give the product explanation room for screenshots, use cases, and limitations. Include an accessible image gallery and a genuine contact or waitlist submission flow. Do not show customer logos or usage statistics without supplied evidence. Use a consistent navigation and footer across real routes, and check the phone layout. **Should my first build be one page or several?** Use one page when one audience needs one short explanation and one action. Use real routes when services, work, or supporting information need their own space. State your preferred scope in the brief so navigation reflects that decision. **Can I change a heading without starting another AI build?** Inspect & Edit supports mapped text, link, and color changes without model usage. Larger structural changes can be requested in chat. Saved edits still follow ownership, verification, and source-lock rules. **What do I receive when I unlock source?** The saved project’s exportable source and included assets become accessible. Existing projects may be static HTML, CSS, and JavaScript; eligible new projects may use the multi-file Next.js engine. Review the generated project and its integration requirements before deploying. ### AI SaaS Builder — Scope Your First Product Canonical: https://uvilno.com/build/ai-saas-builder Plan a focused SaaS interface with accounts, a core record workflow, and clear service boundaries. Explore three editable product briefs. A SaaS idea becomes easier to evaluate when one person can complete one meaningful task. Start with the account journey, the record that person owns, and the result they return for. Uvilno can build the interface and use supported managed app services when they are explicitly configured. Keep your first scope small enough to review every state; a convincing dashboard alone does not establish a complete subscription business. Audience: Founders validating a narrow workflow before adding organization accounts, billing complexity, or specialist infrastructure. Routes: - /: Product explanation. Explain the job, show labelled illustrative screens, and link to the app. - /login: Project-specific accounts. Use configured managed identity with registration, sign-in, and recovery states. - /app: The core workflow. Create, list, edit, and archive personal records through the supported managed database. - /profile: Account controls. Let visitors manage supported profile fields and preferences, then sign out. Interactions: - A first-use state guides a signed-in visitor to create their first real record. - Record forms validate input and distinguish saving, failure, and successful persistence. - List filters and detail routes retain enough context to make repeated work comfortable. Service boundaries: - Managed project identities and personal-record CRUD do not imply team roles, enterprise SSO, or arbitrary tenant permissions. - Stripe connector checkout is currently test mode until live configuration is completed. Do not present test purchases as active subscriptions. - Background jobs, transactional email, external APIs, and deployment operations require their own reviewed implementation and configuration. Starter briefs: **A personal client tracker** Build a focused SaaS MVP for independent consultants to track their own client follow-ups. Include a public explanation page, managed app registration and login, a personal client list, client detail, and profile. Use supported managed database records scoped to the signed-in visitor. Support create, edit, archive, next-contact date, notes, and search with real loading and error states. No team sharing, billing, email sending, or calendar sync. Clearly label any fictional seed records and keep them separate from saved user data. **A saved research workspace** Create a small research organizer with public Home and a signed-in app. Visitors can save their own links with a title, summary, tags, and review status, using the configured managed auth and database connectors. Include search, tag filtering, a detail page, empty states, and profile settings. Do not claim that links have been fetched or summarized unless that service is actually connected. Exclude team workspaces and subscriptions. Begin by proposing the data fields and real routes for approval. **A subscription interface prototype** Build a clearly labelled SaaS concept for a solo project planner. Include marketing, signup, a personal projects dashboard, task detail, and settings. First implement a useful personal record workflow with managed auth and CRUD if available. If adding pricing and Stripe checkout, keep every payment surface explicitly labelled test mode and use only the configured connector. Do not grant fictional paid entitlements or imply live billing. Document unsupported features in the plan and hide their action controls. **Can this become a production SaaS?** It can be a starting codebase and working supported workflow. Production readiness depends on the particular data, services, authorization rules, deployment, monitoring, and operational requirements. Review those against your actual product before admitting real customers. **Are app accounts separate from my Uvilno account?** Generated-app visitors use isolated project-specific identities. Their app authentication does not sign them into the Uvilno platform. Request dedicated login, registration, and profile routes in your brief. **Can I add monthly subscriptions immediately?** The Stripe connector is currently in test mode until live configuration is completed. A test checkout can help evaluate a payment flow, but live subscription entitlements and their failure cases need deliberate implementation and review. ### AI Web App Builder for Focused Workflows Canonical: https://uvilno.com/build/ai-web-app-builder Turn a workflow into real routes, usable states, and an explicit data plan. Start an AI web app with one of three editable briefs. A web app needs more than a polished default view. It needs empty lists, invalid input, saved changes, failures, and a way back. Describe the objects people work with and what each action should do. Uvilno can build a multi-page interface, browser-local interactions, or supported managed account and record flows. Choose the data model deliberately so a local demonstration is never mistaken for a connected service. Audience: People turning a specific repeatable task into a browser application with a bounded feature set. Routes: - /: Task overview. Show the main object and a direct route to the next useful action. - /items/new: Validated creation. Collect the minimum fields with clear constraints and a recoverable submit state. - /items/[id]: Record detail. Explain status, expose supported edits, and preserve context when returning to the list. - /settings: Preferences. Make persistence explicit: browser-local preferences or configured account data. Interactions: - Search, filter, and sorting work together with a clear reset and useful no-results state. - Create and edit forms explain validation beside the relevant field. - Destructive actions require a meaningful confirmation and update the list only after the chosen storage operation succeeds. Service boundaries: - Browser-local state stays on the same browser/device; it is not a shared database or a cross-device account. - Use managed auth and database connectors only for the supported scope. External services need configuration and cannot be assumed connected. - An app with user data still needs a security and operational review appropriate to that data before public use. Starter briefs: **An equipment checklist** Build a browser-local equipment checklist app with Overview, Lists, List detail, and Settings routes. Let me create lists, add items, change quantities, mark packed, filter incomplete items, and duplicate a list. Persist within the same browser using bounded project-scoped storage and explain that limitation. Include empty, invalid, and no-results states, accessible keyboard controls, and a clear reset confirmation. Do not claim account sync or shared access. Use neutral fictional sample lists only when clearly labelled. **A personal reading log** Create a personal reading log with configured managed app accounts and private saved records. Include login, registration, a library, book detail, add/edit, and profile pages. Fields: title, author, format, status, optional finish date, and personal notes. Build search and status filters and show real save failures without losing input. Do not fetch book metadata or share notes publicly. If the connectors are unavailable, describe the missing setup rather than simulating a successful save. **A quote comparison tool** Plan a web app for comparing supplied vendor quotes. Build a workspace, quote entry form, comparison view, and help page. Start as a local browser tool with explicit local-only persistence. Users enter line items, tax assumptions, and terms themselves; calculate totals with transparent rules and support removing a quote. Label sample figures as fictional. Do not imply procurement approval, financial advice, vendor verification, or external accounting integration. **How do I choose between local state and managed records?** Use local state for personal experiments and low-stakes tools that can remain on one device. Request configured managed accounts and records when visitors need their own saved data. State the persistence choice in the brief and verify it in the result. **Can the app include multiple pages?** Yes. Request named routes and describe what visitors do on each. Eligible new projects may use the multi-file Next.js engine; existing static projects can also have real pages. The generated project remains subject to engine and execution limits. **What should I test before sharing an app?** Follow the primary workflow from an empty state, submit invalid input, refresh after saving, and test errors and authorization. Check the phone layout and keyboard behavior. Do not rely on a populated default screen as proof that the full workflow works. ### AI Browser Game Builder — Playable Game Briefs Canonical: https://uvilno.com/build/ai-browser-game-builder Scope a playable browser game with real controls, restart states, and honest persistence limits. Explore three editable game briefs. A strong first game has a clear verb, readable feedback, and a reason to try again. Describe the rules before the visual effects: how a run starts, how someone succeeds, what ends it, and how they restart. Uvilno can generate browser game code and an isolated playable preview. Keep the initial loop modest so input, collision, progression, sound consent, and phone controls can be checked together. Audience: Creators exploring compact single-player games, interactive promotional experiences, and game prototypes for the browser. Routes: - /: Play immediately. Place the game and its start state at the center, with controls and sound preference nearby. - /how-to-play: Understand the rules. Explain keyboard and touch controls, scoring, pause, and the end condition. - /records: Know what was saved. Show browser-local best runs, clearly distinguishing them from shared or verified records. Interactions: - Start, pause, resume, game over, and restart are distinct reachable states. - Keyboard and touch controls produce the same core action; focus stays usable outside the canvas. - Sound begins muted, visual effects respect reduced motion, and local best scores survive an ordinary refresh. Service boundaries: - Performance depends on the generated code, assets, device, and browser. Do not promise a universal frame rate. - Local records are editable client data. A shared leaderboard requires the supported explicitly requested service and must be labelled client-submitted. - Multiplayer servers, anti-cheat, game-store publishing, and monetization are separate implementation work. Starter briefs: **A one-button arcade** Build a single-player browser arcade game about guiding a small orb through opening gates. Use one action: press Space or tap to change direction. Create a clear start screen, brief playable tutorial, pause/resume, game-over summary, and restart. Increase difficulty gradually and keep collision rules readable. Store only a local best score with an explicit local-device label. Start audio muted with an opt-in sound control. Provide touch controls and reduced-motion effects. Do not add online rankings, payments, or claims about guaranteed frame rate. **A turn-based puzzle** Create a compact turn-based browser puzzle with a 5 by 5 board. Players move a token to collect three keys and reach an exit within a move limit. Build ten authored levels, an accessible level selector, undo for the last move, reset, win, and failure states. Explain keyboard controls and allow tapping board cells. Save completed levels locally on the current browser. Keep animation short and optional. Add a How to play route with the exact rules; no timers, account requirement, or fictional global achievements. **An interactive brand game** Plan a short browser game for a fictional coffee brand, explicitly labelled as a concept. Players sort falling beans into two baskets with keyboard and touch controls during a 45-second run. Include a practice mode, pause, score breakdown, restart, and an optional muted-by-default sound control. Build an About the game route and a local records page. Use original geometric art rather than third-party characters. Do not collect personal data, grant real prizes, or add an email form that pretends to submit. **Can I request a leaderboard?** Request it explicitly and distinguish local scores from a shared board. Supported shared leaderboards publish pseudonymous client-submitted scores through isolated project accounts. They are not evidence of anti-cheat or verified competitive results. **What makes a good first game prompt?** Define one core action, a success condition, a loss condition, and restart behavior. Name keyboard and touch inputs. Add the visual direction after those rules so the generated result can be evaluated as a game. **Will the game work equally well on every phone?** That cannot be guaranteed. Test actual touch controls, viewport sizing, audio permissions, and performance on the devices you intend to support. Reduce effects and asset complexity when the core loop needs more headroom. ### AI Stripe Ecommerce Store Builder — Test-mode Plans Canonical: https://uvilno.com/build/ai-stripe-ecommerce-store-builder Plan product pages, cart states, and a Stripe test checkout with clear commerce limitations. Start from three editable store briefs. A store connects product information to a payment flow and then to real fulfillment. Uvilno can help build the catalog, product pages, cart interactions, and a configured Stripe connector checkout. Stripe is currently in test mode until live configuration is completed. Treat this scope as a store concept and integration exercise, with explicit boundaries around inventory, delivery, refunds, tax, and customer support. Audience: Makers and developers preparing a small catalog and evaluating a test purchase journey before operational launch. Routes: - /shop: A clear catalog. Show supplied products with genuine variants, prices, and availability rules. - /shop/[product]: A buying decision. Explain materials, dimensions, variant selection, and the limits of the offer. - /cart: An honest order draft. Update quantities and totals locally, with an unmistakable test checkout label. - /checkout-result: Verified payment state. Reflect the configured test payment result; never treat a return URL alone as proof of payment. Interactions: - Product options validate before adding an item, and cart totals update when quantity changes. - Cart state can persist on the same browser with that limitation disclosed. - Configured Stripe test checkout exposes success, cancellation, and failure without suggesting a real order was placed. Service boundaries: - Stripe Connect and checkout are currently test mode until live configuration is completed. No page should imply that live payments are already available. - Catalog UI is not inventory control, shipping, tax calculation, returns handling, or marketplace payout infrastructure. - Supply product rights, policies, prices, and fulfillment details. Live commerce requires service setup and a complete operational review. Starter briefs: **A small maker catalog** Build a concept store for a ceramic maker with Shop, Product detail, Cart, About, and Care pages. I will supply the real products, images, dimensions, variants, and prices. Implement variant selection and browser-local cart quantities. If the configured Stripe connector is used, label checkout and its result as test mode everywhere. Do not claim live purchases, stock reservations, shipping quotes, tax compliance, or automatic fulfillment. Keep unsupported actions hidden and explain the remaining commerce setup in the plan. **A digital product test** Create a store concept for three digital design resources, with a catalog, detailed product pages, cart, and a configured Stripe test checkout. Use my supplied prices and license terms. Label all checkout steps as test mode; a successful test payment must not imply a real license grant or protected file delivery. Include cancellation and payment-failure recovery. Do not expose paid downloads from a public route. Ask for the secure delivery service and entitlement rules before implementing actual fulfillment. **A single-product shop** Plan a single-product shop with Home, Product, Materials, Cart, and Help routes. The product has two color options and a quantity control. Make the product photography and specification table accessible on phones. Persist the cart locally and disclose it. Connect only the available Stripe test checkout, visibly labelled test mode, and show genuine configured result states. Do not invent reviews, inventory counts, delivery promises, or refund terms. Identify what needs review before live commerce. **Can this accept live customer payments today?** The current Stripe connector is in test mode until live configuration is completed. A generated checkout surface must make that clear. Live payments need appropriate account configuration, verified payment handling, and reviewed order and fulfillment behavior. **Does a cart mean stock is reserved?** No. Browser-local cart state is an order draft on one device. Inventory reservation, stock reconciliation, overselling prevention, and fulfillment need an actual backend designed for those operations. **Can I sell downloads securely?** A product page and test checkout are only part of that flow. Protected delivery requires server-verified payment, explicit entitlements, access-controlled storage, and recovery for failed delivery. Do not put paid files in a public bundle. ### AI Landing Page Generator for a Focused Offer Canonical: https://uvilno.com/build/ai-landing-page-generator Build a campaign page around one audience and one action. Use editable launch, waitlist, and service-offer briefs with real form states. A landing page should make one decision easier. Tell Uvilno where visitors are coming from, what they already know, and the action the page should support. Then build the explanation around that context: the offer, the evidence you can actually supply, the objections, and the response. A focused page can still include depth; it does not need fabricated urgency or a wall of generic benefits. Audience: Founders, campaign owners, and service teams with a specific offer and an actual destination for enquiries or signups. Routes: - /: The campaign page. Lead with the offer, follow with relevant proof and objections, and repeat one meaningful action. - /thank-you: The real next step. Explain what a successfully submitted visitor should expect without inventing an automated response. - /privacy: Collection context. Use your reviewed privacy information and explain what the form collects. Interactions: - A managed waitlist or enquiry form provides field validation and real success or error feedback. - FAQ disclosures keep answers available to keyboard and assistive-technology users. - In-page navigation targets actual sections, and the primary action stays consistent on narrow screens. Service boundaries: - A signup confirmation does not mean an email campaign, CRM workflow, or analytics pipeline has been connected. - Supply proof, deadlines, availability, and policy wording. Avoid invented countdowns, conversion rates, and testimonials. - A/B testing, ad-platform events, and consent tooling require explicit implementation and configuration. Starter briefs: **A product waitlist** Build a focused landing page for my upcoming product. I will supply the audience, product facts, launch status, and approved screenshots. Use one primary action: join the waitlist through the configured managed collector. Include useful field validation, duplicate-friendly wording, failure recovery, and a real confirmation state. Explain what people are signing up for and link my reviewed privacy text. Do not invent a launch date, subscriber count, logos, or email automation. Keep the first screen concise and make the rest answer genuine objections. **A service campaign** Create a landing page for one specific consulting service, aimed at visitors from a targeted campaign. Include the problem, who the offer fits, concrete deliverables, process, supplied evidence, FAQ, and an enquiry form. I will provide pricing or choose to omit it. Make the form collect only contact details and project context. Do not promise a booked meeting, instant quote, or guaranteed result. Use a strong editorial hierarchy and one consistent CTA across desktop and phone views. **An event announcement** Build an event announcement page with my supplied event name, date, venue, schedule, speaker biographies, and registration destination. Use a real external registration link if I provide one; otherwise offer a managed interest form, clearly named as an interest list. Include travel details, accessibility information supplied by me, and an FAQ. Do not simulate ticket purchases, remaining seats, speaker credentials, or calendar delivery. Make long schedule entries and links usable on a small phone. **Should every button use the same action?** The primary action should remain consistent when the campaign has one goal. Supporting links can explain the offer or answer questions, but they should not introduce competing commitments without a clear reason. **Can a waitlist form collect real submissions?** Suitable forms can use the configured managed collector. Builder submissions are tests; public-link and exported submissions are live. The owner can manage collected leads through the supported collection controls. **Can Uvilno guarantee conversion improvements?** No. A clear page and functioning form are useful foundations, but outcomes depend on the offer, audience, traffic, and execution. Test with real visitors and avoid claims unsupported by your own evidence. ### AI Portfolio Website Builder for Selected Work Canonical: https://uvilno.com/build/ai-portfolio-website-builder Create a portfolio with project detail routes, image-led storytelling, and useful enquiry flows. Edit three briefs for different creative practices. A portfolio is an edited argument about the work you want next. Choose a small set of projects, explain your role, and show the decisions behind the final artifact. Uvilno can help shape real project routes, responsive galleries, and an enquiry path around your own images and writing. Different disciplines need different pacing; a photographer’s sequence should not read like a product designer’s process document. Audience: Designers, photographers, artists, and independent creatives with work they own or have permission to publish. Routes: - /: A deliberate selection. Show fewer, stronger projects with clear titles and an immediate sense of your practice. - /work/[project]: The project story. Present supplied images, role, context, decisions, and outcomes you can substantiate. - /about: A human introduction. Explain your perspective, experience, availability, and the collaborations you want. - /contact: The right conversation. Offer real contact details or a configured form with a useful project-type field. Interactions: - Gallery controls work by keyboard and touch and provide meaningful image descriptions. - Project filters reveal existing work without implying categories contain projects that were never supplied. - Previous and next project links retain the editorial sequence, with a clear route back to all work. Service boundaries: - Use images you have permission to publish and supply accurate client, role, and credit information. - A portfolio can describe a process; it should not manufacture clients, awards, metrics, or testimonials. - Large image sets need deliberate compression, layout checks, and accessibility review before publishing. Starter briefs: **A product designer** Build my product design portfolio with Selected work, three real case-study pages, About, and Contact. I will upload project images and supply my actual role and outcomes. Use a quiet editorial design that lets diagrams and interface images stay legible. Each case study needs context, constraints, decisions, and a final result without invented metrics. Include keyboard-accessible image viewing, next-project navigation, and a managed enquiry form if configured. Do not invent clients, awards, or placeholder projects. **A photographer** Create a photography portfolio with Home, Collections, individual Collection pages, About, and Enquiries. I will supply owned photographs, collection titles, captions, and contact details. Prioritize image sequencing, aspect-ratio preservation, usable touch galleries, and concise text. Include visible previous/next controls rather than relying only on swipe gestures. Avoid fictional publications and awards. The enquiry form should collect project type and reply details through the available managed collector; it must not claim to book a shoot. **A creative developer** Build a creative developer portfolio with an expressive home page, Selected projects, project detail routes, About, and Contact. I will provide live project links, my contribution, and approved screenshots. Make interactions deliberate but preserve readability, keyboard navigation, and reduced motion. Label concept work clearly. Add project filters only for actual supplied categories. Do not fabricate clients or performance results, and do not load arbitrary third-party embeds without explaining their setup. **How much work should I include?** Start with the smallest selection that supports the work you want next. A few complete project stories are more useful than many unexplained thumbnails. Supply enough material to show your role and the decisions that distinguish each project. **Can I use uploaded project photographs?** Yes. Supported uploaded image formats are validated and processed, and saved versions pin their image manifests. Confirm publication rights and add useful image descriptions. Unlocking source enables exports with the included project assets. **Should concept projects be included?** They can be useful when clearly labelled as concept or personal work. Describe your intent and contribution accurately; do not present them as commissioned work or evidence of customer outcomes. ### AI Architecture Studio Website Builder Canonical: https://uvilno.com/build/ai-architecture-studio-website-builder Plan an architecture studio website around projects, drawings, material context, and enquiries. Use three editable practice-specific briefs. Architecture needs a sequence: place, intention, plan, material, and lived scale. A studio website should preserve that sequence while helping a prospective client understand your practice. Use Uvilno to organize project routes and supplied photography into a calm, readable presentation. Credit collaborators and image makers, distinguish built work from proposals, and let the enquiry journey collect enough context for an informed first conversation. Audience: Architecture studios, interior practices, and independent spatial designers with approved project material. Routes: - /projects: The project index. Browse by actual project type, location, or built/proposal status. - /projects/[name]: From site to detail. Sequence photography and drawings with supplied location, year, credits, and scope. - /practice: The studio’s approach. Explain the people, process, and services without invented accreditation or awards. - /enquiries: A project conversation. Collect site context, approximate scope, timing, and a reply address. Interactions: - Project filters reflect real supplied metadata and provide a useful reset. - Drawing and photography galleries preserve proportions and offer accessible captions. - The enquiry form makes optional project context clear and does not imply a fee proposal has been issued. Service boundaries: - Drawings shown on a website are presentation material, not reviewed construction or permitting documents. - Supply permission-cleared photography, collaborator credits, qualifications, and project facts. - The site does not provide professional design advice, cost certainty, appointment scheduling, or planning approval. Starter briefs: **A residential practice** Build an architecture studio website for a residential practice with Projects, individual Project pages, Practice, Process, and Enquiries. I will supply approved photographs, drawings, credits, project status, and locations. Arrange each project from setting to plan to material detail. Keep built projects and proposals visibly distinct. Include accessible gallery navigation and a managed enquiry form for site context, scope, and timing. Do not invent awards, qualifications, project costs, or planning outcomes. **An interiors studio** Create an interior design studio website with Selected interiors, project detail routes, Studio, Services, and Contact. Use my supplied images and factual project descriptions. Emphasize material palettes, room sequences, and the studio's actual scope. Show photographer and collaborator credits. Include filters only for real project types and a useful enquiry form when collection is configured. Avoid simulated booking, budget guarantees, fictional client praise, or claims that proposals are completed commissions. **A small spatial practice** Plan a website for a small architecture and exhibition practice. Build separate project routes for Built work, Installations, and Research only when I provide examples. The home page should lead with one selected project, then explain our actual approach. Preserve drawing proportions and make long captions readable on phones. Add a simple enquiry page with real submission states. Ask for missing credentials and project facts; do not invent them or offer planning or construction advice. **Can drawings and photography share a project page?** Yes. Describe the desired sequence and upload approved material. Ask for layouts that preserve drawing legibility and image proportions, with captions and credits that remain readable on phones. **How should an unbuilt project be presented?** Label its status directly, such as proposal, competition, or research. Use accurate dates and credits and explain the scope of your contribution. A compelling presentation does not require implying that a proposal was constructed. **Can an enquiry form produce a project quote?** A managed form can collect initial context. It does not establish professional scope, fees, a contract, or an appointment. State that the studio will review the enquiry using your actual process. ### AI Restaurant and Bakery Website Builder Canonical: https://uvilno.com/build/ai-restaurant-and-bakery-website-builder Build a useful restaurant or bakery site with readable menus, real opening information, and clear enquiry routes. Explore three editable briefs. People looking for a restaurant or bakery often need practical answers quickly: what is served, when the doors open, where to go, and how to ask a question. Put those answers before decorative effects. Uvilno can build a characterful site with real menu routes, supplied food photography, and straightforward contact actions. Keep reservations, online orders, and availability tied to actual services rather than plausible-looking controls. Audience: Independent restaurants, cafés, bakeries, and food businesses with supplied menus and verified visitor information. Routes: - /: A sense of the place. Introduce the food and atmosphere, then make hours and directions easy to find. - /menu: A readable menu. Show supplied items, prices, dietary information, and a last-reviewed note where appropriate. - /visit: Plan a visit. Publish the real address, service hours, access information, and provided map destination. - /enquiries: Ask the team. Use a genuine contact form or supplied external reservation/order service link. Interactions: - Menu category navigation works without forcing visitors to download a PDF. - Phone and directions actions use supplied, valid destinations. - An enquiry form confirms receipt only when its configured submission succeeds; an external reservation link stays clearly external. Service boundaries: - Do not simulate a confirmed reservation, order, delivery estimate, or kitchen inventory. - The business must supply and maintain accurate menu, allergen, dietary, pricing, and opening information. - Live ordering and booking require a real configured provider; a contact form is an enquiry channel. Starter briefs: **A neighborhood bakery** Build a neighborhood bakery website with Home, Daily menu, Our bakery, Visit, and Enquiries. I will supply product names, prices, dietary notes, photos, opening hours, and address. Make menu categories readable on phones and show when information was last reviewed. Link to my real ordering provider only if supplied; otherwise use a managed enquiry form for cake and catering questions. Do not simulate orders, stock counts, guaranteed allergen safety, or confirmed pickup slots. **A seasonal restaurant** Create a restaurant website with Home, Food and drink menus, About, Visit, and Contact. Use my approved menu content and photography. Prioritize opening hours, address, accessible menu text, and a real reservation-provider link that I will supply. If no booking service is configured, show a contact action rather than a booking widget. Do not invent awards, reviews, dietary guarantees, table availability, or prices. Include warm visual character while keeping practical information immediate. **A café with catering** Plan a café website with Menu, Catering, Our space, Visit, and Enquiries pages. I will provide the actual packages, minimum quantities, notice periods, and contact details. Build a catering enquiry form with event date, approximate guest count, and reply details, using the configured collector. Explain that an enquiry is not an accepted order. Keep dietary information exactly as supplied and avoid promises about food safety, live delivery, or availability. **Can visitors reserve a table?** Link to your real reservation provider when you supply one. A generated booking form without a connected reservation system must remain an enquiry and must not claim a table is confirmed. **Can the menu be a real page instead of a PDF?** Yes. Supply the current menu and ask for readable HTML categories, item descriptions, and prices. The business remains responsible for checking and maintaining menu and dietary information. **Can the site take cake or catering orders?** It can collect an enquiry with the supported managed collector. Actual order acceptance, availability, payment, and fulfillment require the appropriate configured services and business process. ### AI Dental and Medical Clinic Website Builder Canonical: https://uvilno.com/build/ai-dental-and-medical-clinic-website-builder Plan a clinic information website with service pages, practitioner details, and cautious enquiry forms. Start with three editable non-clinical briefs. A clinic website should help visitors understand the practice and find the right contact route. It should be especially clear about who provides care, where the clinic is, and what happens after an enquiry. Uvilno can organize supplied, professionally reviewed information into accessible pages. Keep this build focused on public practice information: medical advice, clinical triage, patient records, and sensitive data collection require a different reviewed system. Audience: Clinics preparing a public information site with approved service descriptions and verified practitioner information. Routes: - /: The practice at a glance. Show verified location, contact information, and the services the clinic actually offers. - /services: Reviewed service information. Publish supplied general descriptions without generating diagnoses or treatment advice. - /team: Who provides care. Present approved biographies, verified titles, and supplied credentials. - /contact: A non-clinical enquiry. Collect minimal reply details, with a visible instruction not to include medical information. Interactions: - Service navigation helps visitors find public information without suggesting a diagnosis. - Location and contact actions use verified clinic details. - A minimal enquiry form avoids health-history fields and explains that submitting does not confirm an appointment. Service boundaries: - This scope does not provide medical advice, symptom assessment, emergency triage, or treatment recommendations. - Do not collect patient records or sensitive health details through a general marketing form. Specialized handling needs appropriate professional review and infrastructure. - Clinic staff must approve credentials, claims, policies, emergency wording, and any linked appointment service before publishing. Starter briefs: **A dental practice** Build a public information website for a dental practice with Home, Services, Team, First visit, and Contact. I will provide professionally reviewed service descriptions, verified credentials, hours, address, and images. Keep content informational; do not generate treatment recommendations, outcomes, or before-and-after claims. Use a minimal non-clinical enquiry form asking only for name, reply address, and general enquiry category, with a warning not to include health information. Do not simulate appointment confirmation or collect patient histories. **An outpatient clinic** Create a clinic information site with Services, Practitioners, Location, Patient information, and Contact pages. Use only the approved material I supply. Emphasize readable type, keyboard navigation, verified contact details, and clear directions. Link an actual external appointment provider only when supplied. The contact flow must remain a non-clinical enquiry and must not request symptoms, diagnoses, insurance records, or patient documents. Ask for approved emergency and privacy wording; do not invent it. **A physiotherapy studio** Plan a public website for a physiotherapy studio using supplied, reviewed descriptions of its services and staff. Build Home, Approach, Team, Visit, and Contact pages. Explain the actual first-contact process without giving health advice or promising recovery outcomes. Use a minimal managed enquiry form only for non-clinical contact details and make its limits visible. Do not add symptom quizzes, patient records, appointment confirmation, or unverified testimonials. Keep all professional titles and claims exactly as approved. **Can this store patient records?** That is outside this marketing-site scope. General managed forms should not be treated as a clinical record system. Patient-data workflows need purpose-built infrastructure and appropriate professional, security, and legal review. **Can the builder write treatment advice?** Use clinic-approved informational copy instead. The page plan here does not include diagnosis, symptom assessment, or personalized recommendations. Qualified clinic staff should review all public service descriptions and claims. **Can I link an existing appointment service?** Yes, when you supply the real destination and approve the wording. Make the external handoff clear. A general contact submission should never claim an appointment has been scheduled. ### AI Real Estate Website Builder for Property Portfolios Canonical: https://uvilno.com/build/ai-real-estate-website-builder Plan property detail pages, useful filters, and genuine viewing enquiries without implying a live listing feed. Explore three editable real estate briefs. Property pages earn their space with accurate details, useful images, and context about the place. Uvilno can turn a supplied property portfolio into real routes with searchable or filterable listings and a clear enquiry journey. Keep asking prices, availability, dimensions, and photography tied to verified source material. A polished listing interface does not mean a property feed or agency system is connected. Audience: Independent agents, property developers, and portfolio owners presenting a bounded set of verified properties. Routes: - /properties: Find a relevant property. Filter the supplied catalog by meaningful fields such as area, type, and asking price. - /properties/[name]: Inspect the details. Show approved photos, specifications, floor plans, status, and contact context. - /areas: Understand the setting. Use supplied factual neighborhood information rather than invented travel or investment claims. - /enquire: Request a conversation. Pass the selected property into a genuine enquiry without claiming a viewing is booked. Interactions: - Filters work on the actual supplied catalog and explain when nothing matches. - Photo galleries and floor-plan viewing remain usable by keyboard and on phones. - A property enquiry retains the listing reference and provides real submission feedback. Service boundaries: - Live MLS, portal feeds, inventory synchronization, valuation, and CRM integrations require configured services. - Supply approved listing facts and rights-cleared assets; review property, advertising, and privacy requirements for your jurisdiction. - An enquiry is not a confirmed viewing, offer, reservation, mortgage decision, or investment recommendation. Starter briefs: **An independent agency** Build a property agency website with Properties, individual Property pages, Areas, About, and Enquiries. I will supply current property data, approved photographs, floor plans, prices, and status. Implement filters for area, type, and price with a reset and no-results state. Property enquiry forms must include the property reference and use the configured collector. Do not claim a live listing feed, confirmed viewing, valuation, guaranteed yield, or CRM sync. Keep all illustrative data visibly labelled until replaced. **A residential development** Create a website for one residential development with Overview, Residences, individual Unit pages, Location, and Enquiries. Use only supplied specifications, renderings, completion information, and availability. Label architectural visualizations accurately. Build a browsable unit list and accessible plan viewing, but do not simulate reservations or stock holds. A managed enquiry form can request a conversation; it must not promise a confirmed appointment, price guarantee, or investment return. **A rental portfolio** Plan a rental portfolio website for a small owner-managed collection. Include Properties, property detail, Renting process, About, and Contact. I will provide verified rent, status, dimensions, terms, and images. Add useful filters and a genuine enquiry form without requesting financial documents or identity uploads. Do not run tenant screening, collect deposits, approve applications, or imply live availability synchronization. Make the next steps clear and subject to the owner's actual review process. **Does the property list update from an agency feed?** Only when a real integration has been implemented and configured. A generated catalog initially reflects the supplied records. Do not describe it as live or synchronized without verifying that connection. **Can visitors book viewings?** A managed form can request a viewing conversation. A confirmed appointment needs an actual scheduling service and availability logic. Keep enquiry wording clear so visitors understand what has and has not happened. **Can I include floor plans?** Yes, using supplied assets you have permission to publish. Preserve legibility and label any approximate or illustrative material using approved wording. Verify measurements and listing facts before publishing. ### AI Fintech Dashboard Builder for Product Prototypes Canonical: https://uvilno.com/build/ai-fintech-dashboard-builder Prototype a financial interface with labelled sample data, explicit calculation rules, and honest connection states. Edit three focused dashboard briefs. Financial interfaces need unusually careful labels. A balance, return, or payment status can look authoritative even when it is only a sample. Use Uvilno to explore the information architecture, tables, filters, and interaction states with unmistakably illustrative data or manually entered records. Treat bank connectivity, financial advice, trading, money movement, and regulatory obligations as separate specialist work. Audience: Product teams prototyping financial information flows, personal record tools, and dashboard presentation before sensitive integrations. Routes: - /overview: Explain the figures. Show period, currency, source, and a visible illustrative-data label. - /transactions: Inspect the records. Use a searchable table with clear statuses and an accessible small-screen alternative. - /reports: Understand the calculation. Expose assumptions and provide text summaries alongside charts. - /connections: Tell the connection truth. Show unavailable or unconfigured services honestly without simulated account linking. Interactions: - Date and category filters update both tabular and chart views using the same disclosed records. - Currency and amount fields validate inputs and keep rounding rules consistent. - Empty, delayed, and failed-data states remain distinct from a genuine zero balance. Service boundaries: - No bank connection, brokerage service, trading execution, identity verification, or money movement is implied by dashboard UI. - Sample or user-entered figures are not verified financial records, forecasts, or advice. - Sensitive financial data and regulated services require an appropriate architecture, provider setup, and qualified review before use. Starter briefs: **An expense dashboard concept** Build a clearly labelled financial dashboard concept with Overview, Transactions, Reports, and Settings. Use fictional sample expenses with a persistent illustrative-data label. Implement working date and category filters, transparent totals, searchable tables, accessible chart summaries, and useful empty states. No bank connection, payment action, accounting certification, or financial advice. Keep currency and rounding consistent and distinguish missing data from zero. Provide a responsive table alternative for phones. **A manual cash-flow tool** Create a browser-local cash-flow planning tool where users manually enter expected income and expenses. Include Entry list, Monthly view, Assumptions, and Help routes. Explain that results are calculations from user inputs and are not financial advice or verified forecasts. Make all formula assumptions visible and label fictional examples. Persist only on the current browser with a clear reset confirmation. Do not connect bank accounts, move funds, or imply tax or accounting compliance. **A payment operations prototype** Plan a payment operations interface prototype with Overview, illustrative payment records, payment detail, and Connection status pages. Show all records as fictional and do not include live refund, transfer, payout, or dispute buttons. Build working filters and detail navigation with accurate state labels. If showing Stripe checkout, use only the configured test connector and mark it test mode. Focus on information design and error states; do not imply a regulated financial service or connected bank account. **Can this connect to a bank account?** A bank integration is outside the dashboard scope described here. It needs an appropriate provider, consent flow, secure data handling, and reviewed implementation. Do not represent an unconfigured connection as active. **Can I trust the displayed figures as financial advice?** No. These briefs are for interface prototypes or explicit calculations from supplied inputs. Sample data should be labelled, assumptions should be visible, and specialist decisions require appropriate independent review. **Why distinguish missing data from zero?** A zero is a value; unavailable data is an unknown. Financial interfaces should display those states differently so a failed request or unconfigured source does not appear to be an authoritative balance. ### AI Agency Website Builder for Clear Positioning Canonical: https://uvilno.com/build/ai-agency-website-builder Build an agency site around a defined offer, credited case studies, and qualified enquiries. Explore three editable agency briefs. An agency site should help the right prospect recognize their problem and understand how your team approaches it. Replace broad capability claims with a defined offer, complete project stories, and an honest explanation of the engagement. Uvilno can build the supporting routes and enquiry flow around supplied work. Use the process to edit your positioning rather than filling every page with interchangeable promises. Audience: Design, development, branding, and specialist service agencies with permission-cleared work and a defined engagement model. Routes: - /: A clear position. State the audience, the problem, and the actual kind of engagement. - /work/[project]: A complete case study. Explain the brief, your contribution, constraints, and supported outcomes. - /services: An understandable offer. Describe deliverables, collaboration, and exclusions without invented package prices. - /start-a-project: A qualified enquiry. Collect scope, timing, and reply information through a real submission flow. Interactions: - Case-study navigation lets visitors move between comparable projects without losing context. - A service selector adapts optional enquiry questions while keeping the form understandable. - FAQ disclosures answer process questions without pretending to offer instant proposals or scheduled calls. Service boundaries: - Supply client permissions, project credits, testimonials, pricing, and outcomes; no fabricated proof. - Enquiry collection does not provision a CRM, proposal generator, calendar, or client portal. - If client login or project management is needed, scope the supported account and data workflows separately. Starter briefs: **A brand studio** Build a brand studio website with Home, Work, individual Case studies, Services, Studio, and Start a project. I will supply approved projects, credits, and actual client quotes. Give each case study a clear story from context to decisions to final system. The enquiry form should collect organization, scope, timing, and contact details through the configured managed collector. Do not invent awards, revenue results, package prices, availability, or a meeting booking. Use a confident editorial visual direction. **A development agency** Create a website for a specialist development agency. Include Home, Expertise, three supplied Case studies, Approach, and Contact routes. Explain actual technologies and deliverables without claiming every integration is supported. Show credited project work and supplied outcomes only. Add a brief enquiry flow with useful validation and failure recovery. No fictional team members, client logos, security certifications, or instant cost estimates. Make technical content readable for a non-technical buyer. **A solo creative practice** Plan an agency-style website for my independent creative practice with Selected work, Services, About, Process, and Enquiries. Make the scope and direct working relationship clear without pretending I have a large team. I will supply project images and factual descriptions. Use a restrained, distinctive layout and accessible project navigation. Connect a genuine enquiry form if available and explain the real next step. Avoid invented testimonials, calendar slots, prices, and guaranteed outcomes. **What makes an agency case study useful?** Explain the client context, your role, the constraints, and the decisions behind the work. Use approved artifacts and supported outcomes. A case study can be persuasive without invented metrics or a testimonial. **Can the site qualify enquiries?** Yes. A configured managed form can collect a small set of relevant details such as scope and timing. Keep questions proportionate and explain the actual follow-up process; submission does not itself produce a quote or meeting. **Can I add a client portal?** Treat it as a separate app scope with explicit identity, data, and authorization requirements. Supported managed accounts and personal records do not automatically provide agency-client collaboration or organization roles. ### AI Directory and Marketplace Builder — Define the Scope Canonical: https://uvilno.com/build/ai-directory-and-marketplace-builder Plan a directory with real filters, useful listing pages, and honest marketplace boundaries. Edit three distinct catalog and listing briefs. A directory helps people find something. A marketplace also coordinates trust, supply, payment, and fulfillment. Start by deciding which of those jobs your first version actually owns. Uvilno can build a browsable supplied catalog, listing detail routes, and supported enquiry or account workflows. Keep moderation, seller permissions, payouts, and transaction guarantees explicit rather than letting interface labels imply a complete marketplace backend. Audience: Curators and founders validating a focused discovery experience before committing to transaction infrastructure. Routes: - /browse: Discover relevant listings. Combine search and meaningful filters over actual supplied or supported saved records. - /listings/[name]: Evaluate a listing. Show provenance, relevant attributes, and a clear enquiry or external handoff. - /submit: Suggest an entry. Collect a suggestion for review without pretending that it is automatically approved. - /about: Explain the rules. State selection criteria, update process, and the limits of any verification claim. Interactions: - Search, category filters, and clear-all controls work together with useful no-results guidance. - Saved favorites can use browser-local storage when that scope is clearly disclosed. - Listing suggestions show genuine submission feedback and an honest review status. Service boundaries: - Seller accounts, organization roles, moderation queues, dispute resolution, and payouts need explicit backend design. - A submitted listing is not verified, approved, available, or endorsed merely because it appears in the interface. - Stripe is currently test mode until live configuration is completed; a marketplace should not imply live transactions or seller payouts. Starter briefs: **A curated local directory** Build a curated directory of independent workshops using a supplied dataset. Include Browse, category routes, listing detail, Suggest a workshop, and About. Implement search, location and craft filters, and browser-local favorites labelled as local. Show actual source and last-reviewed information when supplied. Suggestions go through a managed enquiry form and are not automatically published. Do not invent verification badges, live availability, reviews, seller accounts, or payments. **A specialist resource catalog** Create a directory of resources for a niche professional audience. I will provide titles, categories, descriptions, source links, and access notes. Build Browse, Resource detail, Collections, Suggest a resource, and Editorial policy routes. Make search and multi-filter behavior real and provide no-results recovery. Clearly separate editorial descriptions from third-party claims. Do not simulate paid access, automatic link checking, endorsement, or user reviews. Use external links only for provided destinations. **A marketplace discovery prototype** Plan a clearly labelled marketplace concept for renting creative spaces. Build supplied listing search, detail pages, local favorites, and an enquiry flow. Show sample listings as fictional until I supply real data. Do not confirm reservations, take live payments, promise seller payouts, verify hosts, or imply inventory sync. If accounts are added, use only supported project-specific identity and personal records. Identify moderation, permissions, booking, and commerce as separate work in the plan. **What is the difference between a directory and a marketplace?** A directory supports discovery and a handoff. A transactional marketplace also needs the rules and infrastructure for sellers, buyers, availability, payment, fulfillment, and disputes. Name that scope explicitly before building controls. **Can visitors submit listings?** A configured managed form can collect suggestions. Automated publication, moderation, ownership, and editing permissions need an actual data and authorization workflow. Do not treat a contact form as a completed publishing system. **Can the first version include payments?** The current Stripe connector is test mode until live configuration is completed. Live marketplace payments and seller payouts require additional service configuration, business rules, and review beyond a catalog and checkout screen. ### HTML, CSS and JavaScript AI Code Generator Canonical: https://uvilno.com/build/html-css-js-code-generator Scope portable static pages and browser interactions with a practical AI code-generation brief. Review previews before unlocking source export. Static HTML, CSS, and JavaScript are a useful choice when the job belongs in the browser: a small site, a calculation tool, or a compact game. Tell Uvilno the file and route scope, the allowed dependencies, and how each control behaves. Review the rendered result before unlocking its source. Static output keeps deployment straightforward, while forms and any remote data still need a real configured service. Audience: Developers and creators who prefer a bounded static front end with portable files and clear integration requirements. Routes: - /index.html: Semantic structure. Use actual headings, navigation, sections, and labelled form controls. - /styles.css: A coherent visual system. Keep responsive layout, focus states, and reduced-motion behavior consistent. - /script.js: Real browser behavior. Wire the requested interactions, validation, and explicit local persistence. - /about.html: Supporting content. Use a real second page when the content deserves its own navigation destination. Interactions: - Navigation, menu toggles, and form controls work through semantic browser behavior. - Local calculations expose their inputs and assumptions instead of hiding fixed sample results. - Browser storage is bounded and project-scoped, with a clear explanation of its device-local nature. Service boundaries: - Static browser code cannot safely hold secrets or implement trusted server authorization. - Source inspection, ZIP download, and repository source pushes remain behind the project’s unlock entitlement. - A static export still needs suitable hosting and real services for remote writes, payments, or private account data. Starter briefs: **A portable service site** Build a static HTML, CSS, and JavaScript service website with index.html, services.html, about.html, and contact.html plus shared assets. Use semantic structure, real page navigation, accessible mobile menus, and a coherent responsive stylesheet. I will supply the business facts and images. Use the managed collector for contact only when configured; otherwise describe the missing service rather than faking success. Avoid unnecessary libraries, inline secrets, and unsupported backend claims. Review the rendered pages before source export. **A small browser utility** Create a static browser utility that compares two user-entered text lists and shows shared and unique entries. Use HTML, CSS, and JavaScript with no remote data processing. Support case sensitivity, whitespace trimming, copy results through a real user action, clear, and empty states. Explain that text stays in the browser and avoid persistence by default. Add keyboard labels and readable phone layouts. Do not show fake processing or send input to a service. **An interactive explainer** Build a three-page static explainer using HTML, CSS, and JavaScript: Overview, Interactive example, and Method. The example should let visitors adjust two inputs and see the result of a formula I will supply. Show assumptions and a text summary alongside any visual. Use real navigation, keyboard controls, visible validation, and reduced motion. Do not invent scientific evidence or claim data comes from a live source. Keep assets and dependencies portable for source export after unlock. **Can I inspect the code before unlocking?** The live preview is available within the product’s access rules, but raw project files stay private until the project is unlocked or covered by an included source entitlement. Chat should not reveal full source as a way around that rule. **Can static JavaScript use an API secret?** Secrets should remain on a trusted server. Browser code and exported public assets are visible to visitors. A service that requires private credentials needs an appropriate server integration rather than a key embedded in the page. **Can I export the uploaded assets too?** Unlocked exports include the saved project’s included images and bundled fonts with their licenses. Inspect the archive and its integration instructions before deploying it to a compatible host. ### Next.js and Tailwind AI Builder for Multi-file Projects Canonical: https://uvilno.com/build/nextjs-tailwind-ai-builder Plan a modular Next.js and Tailwind build with real routes, interaction states, and export boundaries. Explore three editable developer briefs. A multi-file project should make future changes easier. Describe the routes, reusable pieces, data boundaries, and expected behavior before asking for visual polish. Eligible new Uvilno projects can use a gated Next.js static-export engine with cloud compilation and browser checks. That provides a useful foundation for a frontend codebase, while deployment, secrets, and any runtime server features still need to match the actual host and service configuration. Audience: Developers who want a modular frontend starting point and intend to review, export, or continue the source after unlocking. Routes: - /: App entry. A clear route with shared layout, navigation, and the primary content hierarchy. - /work/[slug]: Content routes. Generate known detail pages from explicit data rather than duplicating page markup. - /about: Shared interface patterns. Reuse navigation, content, and layout components across a real supporting page. - /contact: Explicit data boundary. Give a configured managed form real validation, submission feedback, and recovery. Interactions: - Client-side state is scoped to the component that owns the interaction. - Navigation resolves to actual routes and dynamic content has meaningful missing and empty states. - Forms distinguish browser validation, configured submission, pending state, and failure recovery. Service boundaries: - The Next.js engine is gated and applies to eligible new projects; an existing static project should not be assumed migrated. - Static export does not provide arbitrary server runtime features. Hosting and connector choices must match the generated output. - Compilation and browser checks reduce specific errors; they do not replace a full review of security, accessibility, content, or production operations. Starter briefs: **A modular marketing site** For an eligible Next.js project, build a multi-file Tailwind marketing site with Home, Product, Use cases, individual Use-case pages, and Contact. Use shared layout and navigation components, explicit content data, and focused modules. Keep the result compatible with the available static-export engine. Build real routes and a configured managed contact flow, with validation and failures. Do not add server-only features unsupported by the export host. Keep secrets out of client code and avoid fictional claims. **A content-rich product catalog** Build an eligible multi-file Next.js and Tailwind project for a supplied product catalog. Include an index, category pages, known product detail routes, About, and Enquiries. Put product facts in a clear data module and use reusable list and detail components. Implement useful search and filters in the browser. No cart or live commerce. Keep static-export constraints explicit, validate route parameters, and use accessible empty states. Do not invent product specifications or connected inventory. **A frontend app foundation** Plan a modular Next.js and Tailwind frontend for a personal project tracker. Include real Overview, Project detail, Create/edit, and Settings routes with focused components and typed record shapes. Choose browser-local storage explicitly for the first version and disclose its device-local limitation. Implement full create/edit/archive behavior, validation, empty states, and failure handling. Do not imply a backend or team permissions. Keep the project within the supported static-export engine and list integration work separately. **Does every project use Next.js?** No. Existing projects can use static HTML, CSS, and JavaScript. The gated multi-file Next.js static-export engine is available to eligible new projects. Inspect the actual project output and engine scope rather than assuming a framework migration. **Can I continue the project in GitHub?** Supported GitHub workflows include repository import, edit, push, and pull. Source pushes retain the project unlock requirement. Review the exported repository, dependencies, and integration configuration before continuing development. **Does static export include a production backend?** No. It produces output compatible with its export scope. Managed services must be explicitly configured, and runtime server features require an appropriate implementation and deployment target. Do not infer backend capabilities from a Next.js file structure. ### AI Internal Tool Builder for a Bounded Workflow Canonical: https://uvilno.com/build/ai-internal-tool-builder Plan an internal tool with clear records, useful tables, and explicit permission limits. Start with three editable operations briefs. Internal tools succeed when they fit the work people already do. Name the record, the person responsible, the status changes, and the questions they need to answer quickly. Uvilno can build a focused interface with local state or supported managed personal records. Shared team permissions, sensitive operational data, and integrations deserve their own scope; a table with an edit button does not establish an authorization model. Audience: Small teams prototyping an operational workflow, or individuals replacing a personal tracking sheet with a clearer interface. Routes: - /queue: The working list. Show priority, status, and the next action with useful sorting and filters. - /records/[id]: The full context. Keep notes, relevant fields, and supported edits together. - /new: A consistent intake. Validate required fields and protect entered data when saving fails. - /help: The workflow rules. Explain status meanings and the actual storage and permission model. Interactions: - Queue filters expose overdue or incomplete work without hiding the active filter state. - Status changes use the chosen persistence layer and show pending or failed updates. - Bulk actions appear only if their real behavior, validation, and recovery have been implemented. Service boundaries: - Supported personal records do not automatically provide shared organization data, manager roles, or audit-grade history. - Do not place confidential production records in a concept dataset or imply an external system is connected. - Imports, exports, scheduled jobs, and business-system synchronization need explicit implementation and review. Starter briefs: **A personal request queue** Build a personal request tracker with Queue, Request detail, Add/edit, and Help routes. Use configured managed identity and private personal records if available. Fields: title, requester label, priority, due date, status, and notes. Implement real create, edit, archive, filters, and overdue views with loading and save failures. Do not imply shared team permissions, automatic email, audit-grade history, or an external ticketing integration. Use clearly fictional sample requests separated from saved records. **An equipment inspection prototype** Create a browser-local prototype for tracking equipment inspection notes. Include Equipment list, item detail, add/edit, and workflow help. Use fictional sample equipment and label the app as a concept. Let users record a date, checklist result, and notes, with search and status filters. Explain local-only persistence. Do not claim safety certification, regulatory compliance, shared access, or automated maintenance scheduling. Keep all actions real within this limited local scope. **A content approval concept** Plan an internal content queue concept with List, Content detail, Add/edit, and Process routes. Build functioning local status transitions between Draft, In review, and Ready, with explicit browser-local persistence. Use labelled fictional entries. Do not imply multiple reviewers, permission enforcement, notifications, or publication to a CMS. Show validation and no-results states and explain what a future shared backend and authorization model would need to support. **Can everyone on my team edit the same records?** Shared team data and roles require an explicitly designed backend and permission model. The supported personal-record scope should not be presented as collaborative organization storage. Begin by naming who can view and change each record. **Can the tool replace an existing business system?** It can help evaluate a bounded workflow. Replacement depends on actual integrations, data migration, permission rules, recovery, and operations. Prototype with non-sensitive data before connecting production systems. **What should a good queue show?** Show the fields that change the next decision: status, priority, owner where actually supported, and due date. Make filters visible and keep the empty state distinct from a failed data load. ### AI Calculator Builder with Transparent Assumptions Canonical: https://uvilno.com/build/ai-calculator-builder Build an interactive calculator from rules you supply, with accessible inputs and visible assumptions. Edit three practical browser-tool briefs. A useful calculator explains what goes in, what comes out, and where the answer stops being reliable. Supply the formula, units, valid ranges, rounding, and assumptions. Uvilno can build the browser interface and the actual calculation with clear validation and readable results. Start with a low-stakes planning or comparison tool, and keep financial, medical, legal, or engineering decisions outside an unreviewed generated calculation. Audience: Teams and creators with an explicit formula who want a usable, explainable browser utility rather than fixed illustrative results. Routes: - /calculator: Inputs and result. Keep units, constraints, assumptions, and a useful result explanation close together. - /method: The calculation rules. Publish the supplied formula, rounding, limitations, and worked examples. - /help: Interpretation. Answer input questions and explain cases that the tool intentionally excludes. Interactions: - Number inputs validate ranges, missing values, and edge cases such as division by zero. - Results update with a readable text explanation and a clear indication of units. - Reset restores known defaults; copy or print controls use actual browser behavior only when implemented. Service boundaries: - The formula and examples need your review; a generated interface is not evidence that a model is correct. - Estimates based on user input are not quotes, guarantees, or professional advice. - Live rates, tax rules, bank data, and specialist standards need verified sources and configured services. Starter briefs: **A material quantity estimator** Build a browser calculator for estimating the number of rectangular tiles for a non-structural craft project. I will supply the exact formula, units, allowed ranges, and waste allowance rule. Include Calculator, Method, and Help pages. Validate zero and negative dimensions, show rounding explicitly, and explain that the output is a planning estimate to verify before buying. No structural or safety advice. Make all inputs labelled, results readable by assistive technology, and reset behavior predictable. **A transparent price comparison** Create a unit-price comparison tool for up to four manually entered products. Users supply price, quantity, and compatible units; show normalized prices using rules I will approve. Include the calculation method, validation for incompatible units, missing values, and zero quantity. Use labelled fictional examples and no live retailer data. Keep the tool browser-local without tracking or accounts. Do not give financial advice or imply a product recommendation; explain only the entered comparison. **A time planning tool** Build a simple project-time calculator using a formula I will provide for task count, minutes per task, and contingency percentage. Include Calculator, Assumptions, and Worked examples routes. Show hours and workday conversion with the workday length explicitly editable. Validate every input and show how rounding works. Explain that results are estimates rather than delivery promises. No invented productivity statistics, AI prediction claims, calendar sync, or automatic billing. **Who supplies the formula?** You should supply or approve the actual rules, valid ranges, units, and expected examples. Test edge cases as well as ordinary inputs. Visual polish does not establish calculation accuracy. **Can I use live prices or exchange rates?** Only with an actual configured data service and suitable source, freshness, and failure labels. Without that connection, use manually entered values and make the limitation explicit. **Can the result become a customer quote?** Only if your business has deliberately implemented and reviewed the quoting rules. A planning estimate should not imply a binding price, availability, or professional recommendation. ### AI Event Website Builder for Clear Attendee Information Canonical: https://uvilno.com/build/ai-event-website-builder Plan an event site with real schedule routes, speaker information, and honest registration handoffs. Edit three event-specific starter briefs. An event website serves people at different moments: deciding whether to attend, choosing a session, and finding the venue on the day. Build those journeys around a real schedule and verified logistical information. Uvilno can create speaker and session routes, useful filters, and a registration handoff. Ticket inventory, confirmed attendance, automated reminders, and access control need real event services rather than a simulated success screen. Audience: Organizers of conferences, workshops, exhibitions, and local gatherings with a confirmed information source. Routes: - /: The reason to attend. Explain audience, purpose, supplied date, location, and actual registration destination. - /schedule: The day’s structure. Make sessions, tracks, timezone, and breaks easy to understand. - /speakers/[name]: Relevant expertise. Use approved biographies and connect each speaker to actual sessions. - /visit: Arrival and access. Publish supplied directions, access information, and organizer contact details. Interactions: - Schedule filters preserve visible track and day state with a simple reset. - Local saved sessions can create a device-local shortlist without pretending to reserve seats. - Registration links open the real provider; interest forms show actual managed submission outcomes. Service boundaries: - A local agenda is not a seat reservation or confirmed event registration. - Tickets, payments, calendar invitations, reminders, and attendee check-in require real configured services. - Supply approved speaker details, accessibility information, cancellation terms, dates, and timezone. Starter briefs: **A one-day conference** Build a conference website with Home, Schedule, Speaker detail pages, Visit, and FAQ. I will supply confirmed date, timezone, sessions, approved biographies, venue information, and the real registration URL. Add working track filters and a browser-local saved-session list labelled local only. Do not imply reserved seats, ticket inventory, calendar delivery, or confirmed registration. Make the schedule accessible on phones and distinguish session times from visitor timezone assumptions. **A workshop series** Create a site for a small workshop series with Workshops, individual Workshop pages, Facilitators, Location, and Enquiries. Use supplied dates, prerequisites, material lists, and registration destinations. If no registration provider is configured, collect interest through a managed form and label it as an enquiry. No fake seats remaining, certificates, payment success, or calendar sync. Keep practical information visible and handle long workshop titles cleanly on phones. **An exhibition program** Plan an exhibition website with Overview, Program, Exhibitors, Visit, and Contact routes. I will supply approved images, dates, opening hours, venue details, credits, and access information. Build real program filters and detail links. Link to an actual ticket provider only if supplied; otherwise do not show a purchase action. Avoid invented press quotes, visitor counts, and sponsor logos. Include an honest contact or interest form with real feedback if configured. **Can visitors save sessions?** A browser-local shortlist can be useful when clearly labelled. It stays on that browser and does not reserve a seat, enroll the visitor, or synchronize to their calendar unless those services are actually implemented. **Can this sell event tickets?** Use your actual ticketing provider and a supplied registration destination. A generated ticket UI does not provide inventory, payment verification, refunds, or entry control. Stripe connector checkout is currently test mode until live configuration is completed. **What event details should I supply first?** Start with the confirmed date and timezone, venue, audience, schedule, approved participants, access information, and registration process. Those facts determine the site structure more reliably than a generic event template. ### AI Nonprofit Website Builder for Programs and Action Canonical: https://uvilno.com/build/ai-nonprofit-website-builder Build a nonprofit information site with clear programs, supported impact claims, and genuine volunteer or donation handoffs. Edit three starter briefs. A nonprofit site should connect a real need to a concrete program and an honest action. Explain who the organization serves, what it does, and how someone can participate. Uvilno can organize program pages, supplied reports, and volunteer enquiries. Publish impact figures only with their source and period, and link giving to the organization’s actual donation service rather than treating a button as fundraising infrastructure. Audience: Community organizations and nonprofits with verified program details, approved stories, and an established contact or giving process. Routes: - /: Mission and action. State the purpose, show a concrete program, and offer a genuine way to help. - /programs/[name]: The actual work. Explain eligibility, location, activity, and available contact information. - /impact: Accountable evidence. Publish supplied reports with sources, dates, and appropriate context. - /get-involved: A useful handoff. Collect a volunteer enquiry or link to the real donation provider. Interactions: - Program navigation helps visitors distinguish getting support from offering support. - A minimal volunteer interest form uses genuine submission feedback. - Report links and donation destinations point to supplied, valid resources. Service boundaries: - Supply consent for personal stories, photographs, and case material; avoid publishing sensitive beneficiary information. - Donation processing, tax receipts, recurring gifts, and volunteer screening require actual services and reviewed procedures. - Do not invent beneficiary counts, effectiveness measures, charity status, partners, or fundraising urgency. Starter briefs: **A community nonprofit** Build a nonprofit website with Mission, Programs, Impact, Get involved, and Contact pages. I will supply approved program descriptions, dates, reports, images with consent, and actual organization details. Distinguish seeking support from volunteering. Use a minimal managed volunteer interest form and link to our real donation provider only when supplied. Do not invent impact statistics, charity credentials, partner logos, tax benefits, or a donation confirmation. Keep sensitive beneficiary information out of forms and examples. **A conservation project** Create an information site for a conservation organization with Projects, project detail pages, Research and reports, Volunteer, and Contact. Use supplied evidence and clearly date any measurements. Build an accessible report list and location/category filters over actual projects. Volunteer registration is an interest enquiry unless a real service is configured. No invented scientific outcomes, donation receipts, automatic membership, or urgency counters. Credit all supplied photography and respect consent requirements. **An arts organization** Plan an arts nonprofit website with Programs, Artists, Events, Support, and About routes. I will provide approved biographies, program facts, permissions, and actual ticket or donation links. Make event information practical and separate from donation actions. A managed contact form can collect non-sensitive enquiries, with real validation and submission results. Avoid fictional sponsors, audience numbers, grants, memberships, or tax claims. Keep the visual style expressive while maintaining readable navigation. **Can the site collect donations?** Link to the organization’s real donation provider when available. Processing gifts, issuing receipts, recurring billing, and compliance need appropriate services and review. The current Stripe connector is test mode until live configuration is completed. **How should impact figures be presented?** Use supplied figures with their source, measurement period, and relevant limitations. Do not turn illustrative numbers into organizational proof. A clear program explanation is useful even when no numerical impact claim is available. **Can people apply to volunteer?** A managed form can collect an initial interest enquiry. Screening, approval, safeguarding, scheduling, and document collection are separate procedures and should not be implied by the submission confirmation. ### AI Educational Website Builder for Lessons and Resources Canonical: https://uvilno.com/build/ai-educational-website-builder Plan a learning resource with lesson routes, accessible exercises, and honest progress limits. Start with three editable educational briefs. A learning website needs an understandable sequence, a way to practice, and feedback that explains the answer. Uvilno can build structured lessons, supplied resource collections, and browser-based exercises. Start with a narrow topic and approved teaching material. Local completion marks can help someone continue on the same device, but they should not be presented as formal assessment, accredited progress, or a complete learning-management system. Audience: Educators and subject specialists building supplementary resources for a defined audience with reviewed content. Routes: - /learn: A clear learning path. Show prerequisite knowledge, lesson sequence, and realistic learning goals. - /lessons/[slug]: One idea at a time. Combine supplied explanation, worked examples, and practice. - /practice: Useful feedback. Implement deterministic exercises with approved answers and explanations. - /resources: Continue learning. Organize actual supplied references with meaningful descriptions. Interactions: - Lesson navigation preserves sequence and provides clear previous, next, and overview links. - Practice questions give feedback from reviewed rules and keep answers accessible without color alone. - Browser-local progress is labelled local and includes a reset without implying formal assessment. Service boundaries: - Supply reviewed educational material and answer keys; generated prose should not be treated as subject authority. - Enrollment, grading, certificates, learner administration, and safeguarding require a properly designed system. - Avoid collecting children’s information or sensitive learner records through a general marketing form. Starter briefs: **A short learning module** Build a supplementary learning site for a narrow topic I will define, using reviewed content and answer keys I supply. Include Learning path, five Lesson routes, Practice, and Resources. Each lesson needs an explanation, example, and next step. Implement deterministic quiz feedback and browser-local completion marks clearly labelled as local. No certificates, grades, account requirement, or invented educational authority. Make exercises keyboard-accessible and do not collect learner personal information. **A resource library** Create an educational resource library with Browse, resource detail pages, Topic collections, and About. I will supply reviewed titles, descriptions, age guidance, and actual resource links. Add working topic and format filters, search, and an optional browser-local reading list. Keep download links real and distinguish external sources. Do not invent curriculum approval, learner outcomes, certifications, or automated marking. Use readable layouts for long descriptions and accessible mobile navigation. **An interactive concept lesson** Plan an interactive lesson that explains a concept using a deterministic visual model and rules I will supply. Build Overview, Interactive model, Explanation, and Resources routes. Include labelled controls, a reset, text descriptions of changes, and reduced-motion support. State the model's simplifying assumptions. Do not invent research citations or imply a simulation is a validated real-world predictor. Keep the experience browser-local without accounts or tracking. **Can learners save progress?** A local completion list can persist on the same browser when explicitly implemented and labelled. Cross-device progress needs a supported account and data workflow. Formal grades and learning records need additional design and review. **Can the builder create quizzes?** It can implement exercises from supplied or approved rules and answer keys. Review both the content and the feedback. A working quiz interface does not establish the educational accuracy of its questions. **Is this a learning-management system?** The scope here is supplementary lessons and resources. Enrollment, formal assessment, certificates, learner administration, and sensitive records require a dedicated system and appropriate operational review. ### AI Local Services Website Builder for Genuine Enquiries Canonical: https://uvilno.com/build/ai-local-services-website-builder Build a local service website with verified coverage, practical service pages, and honest quote enquiries. Edit three useful starter briefs. Local service customers need a quick answer to a practical question: can this business help with this job in this area? Build the site around that question. Uvilno can create service routes, a real coverage page, and a useful enquiry form using supplied business details. Keep service-area content substantive and accurate; dozens of near-identical location pages are less useful than one clear explanation of where and how you work. Audience: Independent trades and local service businesses with verified service areas, contact details, and work photography. Routes: - /: The service and area. State what the business actually does, its coverage, and how to ask for help. - /services/[service]: The job scope. Explain supplied deliverables, exclusions, preparation, and the actual enquiry process. - /areas: Real coverage. List verified areas with useful access or travel information where relevant. - /request-a-quote: A job enquiry. Collect enough context for a human follow-up without pretending to issue an instant quote. Interactions: - Service choices prefill relevant enquiry context without submitting automatically. - Click-to-call and contact links use supplied business destinations. - The quote enquiry validates minimal contact and job details and explains that availability still needs confirmation. Service boundaries: - Do not invent licensing, insurance, safety certifications, service coverage, reviews, or guaranteed response times. - An enquiry is not a booking, accepted quote, emergency response, or job confirmation. - Scheduling, route optimization, dynamic pricing, and field-service synchronization need real services and business rules. Starter briefs: **A specialist trades business** Build a local trades website with Home, separate Service pages, Service area, Work, and Request a quote. I will supply actual services, coverage, contact details, approved photographs, and verified credentials. Make the quote form an enquiry with service type, town, short job description, and reply details through the managed collector. Do not claim instant prices, emergency response, accepted bookings, insurance, or qualifications unless supplied. Avoid duplicate town pages and keep phone navigation practical. **A garden service** Create a local garden service website with Services, Seasonal work, Selected projects, Areas, and Enquiries. Use real supplied scope, coverage, images, and contact information. Explain what is included and excluded in each service. A managed form may collect a project enquiry, but it must not confirm availability or a price. No fictional environmental credentials, reviews, before-and-after results, or recurring service signup. Prioritize readable mobile information and clear contact actions. **A home organization practice** Plan a website for a local home organization service with Approach, Services, Work, Areas, FAQ, and Contact. I will supply approved images, actual coverage, and process details. Use a reassuring, practical tone and explain the initial enquiry step. Keep the form minimal and discourage sensitive personal information. Do not invent client stories, guaranteed results, prices, available slots, or a booking service. Make all actions lead to real routes or configured submission flows. **Should I create a page for every town?** Only when each page has a real purpose and distinct useful information. Start with a verified service-area page. Repeating the same text with a different town name does not help visitors understand the service. **Can visitors get an instant quote?** A general enquiry form does not calculate or accept a quote. Instant pricing needs explicit, reviewed business rules and a real implementation. Otherwise name the action Request a quote and explain the human follow-up. **Can I show qualifications and insurance?** Yes, when you provide accurate, current details and approve their presentation. The builder should not invent credentials, badges, coverage, or safety claims to make the site appear established. ### AI Documentation Website Builder for Clear Product Guides Canonical: https://uvilno.com/build/ai-documentation-website-builder Plan product documentation with real navigation, readable examples, and explicit search limits. Edit three documentation-specific starter briefs. Good documentation starts with the reader’s job and the product’s actual behavior. Organize setup, concepts, tasks, and reference material so each page answers one question. Uvilno can build a documentation shell and content routes around supplied, reviewed material. Be precise about versions and examples: a plausible endpoint, command, or configuration option can waste more time than a missing paragraph. Audience: Product teams and maintainers with verified reference material who need a clear, navigable documentation site. Routes: - /docs: Choose a task. Guide new and returning readers to setup, common tasks, and reference material. - /docs/getting-started: Reach a real result. Use verified prerequisites and commands with an explicit expected outcome. - /docs/guides/[slug]: Solve one problem. Write task-oriented pages with complete context and useful failure recovery. - /docs/reference: Find the exact detail. Present supplied options, parameters, versions, and limitations consistently. Interactions: - Navigation shows the current page and expands relevant groups without hiding the document. - Local search indexes the supplied documentation content and explains no-results states. - Copy-example buttons use a real user action and provide honest success or failure feedback. Service boundaries: - Supply verified commands, API behavior, configuration, and version information; do not publish invented product interfaces. - Local content search is not a hosted search service, semantic retrieval system, or live documentation sync. - Interactive code execution, API testing, authentication, and version publishing need their own configured infrastructure. Starter briefs: **A developer product** Build a documentation site for a developer product using verified content I supply. Include Docs home, Getting started, task guides, Reference, and Troubleshooting routes. Use a responsive sidebar, current-page state, real heading anchors, readable code blocks, and working copy controls. Add local text search over the supplied pages with clear no-results feedback. Do not invent API endpoints, SDK methods, commands, or version support. Keep interactive execution and authenticated API calls out of scope. **A customer help center** Create a help center for a product with supplied reviewed articles. Build Help home, topic collections, article pages, and Contact support. Organize articles by customer tasks, show related articles, and implement local title/body search. Contact support must use a configured managed enquiry form or supplied destination, not simulate ticket creation. Do not invent product behavior, support hours, service guarantees, or account access. Keep long titles and navigation usable on phones. **An internal handbook prototype** Plan a handbook website from non-sensitive approved sample material. Include Overview, Processes, process detail routes, Glossary, and Search. Clearly label it as a prototype and do not imply access control or private company storage. Build real navigation, local search, article anchors, and print-friendly content. Exclude confidential employee data, document sync, approval workflows, and analytics unless separately configured. Preserve the supplied wording and flag gaps rather than filling them with invented policy. **Can documentation search work without a search provider?** A local search can index a bounded set of supplied pages in the browser. It should explain its scope and handle no results. Large-scale search, semantic retrieval, and live indexing need an appropriate service and implementation. **Will generated code examples be correct?** They require verification against the actual product and version. Supply tested examples when possible and run them in their intended environment. A readable code block is not evidence that an endpoint or command exists. **Can I publish private internal documentation?** Privacy requires a genuine access-control and deployment design. A static site or hidden navigation link does not protect content. Use non-sensitive material until authentication and authorization are explicitly implemented and reviewed. ### AI Community Website Builder for Programs and Resources Canonical: https://uvilno.com/build/ai-community-website-builder Plan a community information hub with useful resources, event routes, and explicit membership boundaries. Explore three editable community briefs. A community hub should make it easier to understand the purpose, find the next event, and access shared resources. Start with what the community actually offers and how someone joins the existing process. Uvilno can build those public routes and supported interest collection. A member directory, forum, moderation system, or private group workspace needs its own identity, permission, and data design; do not imply those systems with decorative member cards. Audience: Organizers of local groups, professional circles, clubs, and interest communities who need a clear public information hub. Routes: - /: Purpose and welcome. Explain who the community serves, what happens, and the actual first step. - /events: What is happening. Publish supplied events with dates, timezone, location, and real registration destinations. - /resources: Shared knowledge. Organize approved links and documents with useful categories and descriptions. - /join: An honest invitation. Link the existing membership process or collect an interest enquiry. Interactions: - Resource filters and search work on actual supplied entries. - Event detail links distinguish an external registration from a local interest form. - A join-interest form confirms a submission without claiming approved membership or private access. Service boundaries: - Forums, member-to-member messaging, moderation, shared permissions, and private directories need explicit backend and safety design. - Do not publish personal member details, photos, or stories without permission. - An interest form does not grant membership, send invitations, process dues, or establish access to a private space. Starter briefs: **A local club** Build a public website for a local club with About, Events, Resources, Join, and Contact. I will supply approved dates, organizer details, images with permission, and the actual joining process. Add real event detail routes and resource filters. Use a managed interest form if configured, clearly stating that submission is not approved membership. Do not invent members, activity statistics, dues payments, private forums, invitations, or group messaging. Keep phone navigation direct and welcoming. **A professional circle** Create an information hub for a professional community with Purpose, Program, Events, Resources, and Join interest pages. Use supplied speakers, links, and reviewed descriptions. Make event and resource discovery work with categories and search. Do not publish a member directory or imply verified professional status. A join form should collect minimal reply details through the actual collector and explain the next review step. No fake membership approval, private access, dues, or automated introductions. **A creative collective** Plan a public site for a creative collective with Projects, approved Contributor profiles, Gatherings, Resources, and Contact. I will provide permission-cleared profiles and work. Clearly distinguish collective projects from individual contributions. Build real routes and a genuine enquiry or interest flow. Do not fabricate members, endorsements, collaboration tools, private messaging, or payments. Use expressive typography and images while preserving keyboard access, reduced motion, and readable mobile layouts. **Can the site include a private member area?** Treat that as a separate app scope. Project-specific managed identity can support explicit account workflows, but shared member data, roles, moderation, and private content need a deliberate authorization model and review. **Does submitting Join create a membership?** Only if a real reviewed membership workflow has been implemented. A managed interest form records an enquiry. Its confirmation should explain the actual next step without claiming approval or access. **Can I show contributor profiles?** Yes, when the people involved approve the information and assets. Publish only the details you have permission to share and distinguish a public editorial profile from an account or verified membership record. ## Machine-readable resources - [Capabilities and recorded checks](https://uvilno.com/ai-benchmarks.json): Dated vendor sources, prices, nullable feature flags, recorded Uvilno checks and explicitly unmeasured scores. - [Complete public reference](https://uvilno.com/llms-full.txt): Expanded product, guide, comparison and use-case content. - [Sitemap](https://uvilno.com/sitemap.xml): Canonical public pages and reference resources. - [Crawler rules](https://uvilno.com/robots.txt): Public crawl access and private-route exclusions. - [Open evaluation CSV](https://uvilno.com/benchmarks-2026.csv): Recorded checks and explicitly unexecuted cases.