Prototype guide
Explore all 25 screens and six workflows.
This is a navigable prototype with realistic demonstration data. Changes you make in the practitioner app are saved in your browser — use “Reset demo data” in the sidebar to start again.
Screens
Public website
Introduces the platform and converts visitors.
Practitioner application
The professional workspace, signed in as demo astrologer Celeste Morrow.
- 8Practitioner Dashboard
- 9Client Directory
- 10Client Profile — Amelia Hart
- 11Chart Directory
- 12Chart Workspace — Amelia Hart natal
- 13Notes & Observations
- 14Consultations & Calendar
- 15Tasks & Follow-Ups
- 16Reading Delivery
- 17Recording Studio
- 18Reports & Practice Insights
- 19Notifications
- 20Settings & Practice Configuration
Client portal
What a client sees — signed in as demo client Amelia Hart.
Workflows
Each workflow shows how the screens connect. Click through the steps in order.
New client
Create a client, enter birth data and generate their natal chart.
Chart analysis
Review a client’s chart and record an observation against it.
Returning consultation
Prepare for today’s session with Amelia using her history.
Recorded reading
Record a chart walkthrough and deliver it to the client portal.
Written reading delivery
Upload a PDF reading and follow it through to the client.
Knowledge retrieval
Search your observations by configuration and jump to the source.
Simulated functionality
Throughout the app, simulated features carry a dashed amber “Simulated” label. The full list, with what each would need to become functional, is in SIMULATED_FEATURES.md in the repository.
Chart calculations
Positions come from a clearly labelled demonstration engine behind an abstraction layer. A production adapter for an existing ephemeris-based engine is needed.
AI assistant
Responses are scripted from the chart data and saved observations. Requires an LLM integration with retrieval over the practitioner’s records.
Recording Studio
Recording uses the browser where permitted, otherwise a simulated timer and preview. Needs media capture, upload and transcoding services.
File uploads & delivery
Files are not uploaded; deliveries update local state only. Needs object storage, signed URLs and an email/notification service.
Authentication
Sign-in, sign-up, verification, reset and invitations are visual flows only. Needs an identity provider and role-based access.
Data persistence
Demo data lives in the browser (localStorage) and can be reset. Needs a database and API matching the store’s actions.
Import/export, billing, calendar sync, reminders
Shown as interface only; integrations are future work.