Pet grooming request hub.
The engineering brief.

The complete prompt.

Edit business facts, service boundaries and the first-release scope before building. The specification is original public documentation, not a customer project source bundle.

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.

Related workflows.

• Dental appointment request portal
• Wellness class reservation planner
• Home repair service portal

Questions before you choose.