Availability
Weekends + weekday evenings
No availability overlap means no forced match. Real-world timing is a hard compatibility signal.
Build this page as part of the Xora controlled prototype system. SYSTEM CONTEXT: Xora is not a social network or swipe app. It is a structured connection system. The product loop is: Enter → Set mode → See few → Open one → Decide → Return This page must fit into that loop as a clear system state. --- 1. DESIGN CONSISTENCY (STRICT) - Use existing styles.css only - Use existing classes only (page, section, cards, button, hero, etc.) - Do not create new UI systems or styling patterns - Match layout, spacing, and structure from app.html and connection.html - Keep visual consistency across all pages --- 2. PRODUCT PHILOSOPHY (NON-NEGOTIABLE) - Fewer, better-aligned connections - No infinite feeds or scrolling loops - Clear decisions over passive interaction - Real-world movement over chat - “Not a fit is not failure” --- 3. SYSTEM STATE THINKING (CRITICAL) This page must represent a STATE, not just content. Define clearly: - Where is the user coming from? - What just happened? - What decision is available now? - Where does the user go next? --- 4. STRUCTURE RULES Every page must include: - One clear headline (what state this is) - One primary action (what the user should do) - Optional secondary action (safe alternative) - No dead ends (always link back into the system) --- 5. FLOW INTEGRITY Always keep the loop intact: - Entry → onboarding → app → connection → decision → app This page must NOT break that loop. --- 6. MINIMALISM (ENFORCED) - No feature bloat - No unnecessary inputs - No fake complexity - No long forms unless essential - No extra UI just to fill space --- 7. TONE - Direct - Calm - Clear - Functional - No hype, no fluff --- 8. OUTPUT REQUIREMENT Return a clean HTML structure using existing components. Do not: - Explain the code - Add comments outside the page - Overbuild --- PAGE-SPECIFIC GOAL:
Xora profiles are built around useful connection signals: mode, availability, interaction style, boundaries, and behavior over time.
Focused mode shows fewer, stronger matches with clearer intent.
Profile signal: simple plans, direct communication, and realistic scheduling.
Trust score: behavior patterns matter more than profile claims.
This is the editable-feeling profile layer. It shows the small set of inputs Xora needs to begin matching without turning onboarding into a personality maze.
Weekends + weekday evenings
No availability overlap means no forced match. Real-world timing is a hard compatibility signal.
Low-key, direct, simple plans
Xora uses practical interaction fit instead of vague personality claims.
Age, distance, dealbreakers
Boundaries are hard filters. Xora should not violate them just to fill a match slot.
Meet fewer, better-aligned people
Declared intent starts the match. Behavior proves whether the intent is real.
1 of 3 active
Users must progress or close connections before opening more slots.
Xora does not punish one mistake. It classifies patterns. The goal is to reduce flakiness and help high-effort users find each other.
Replies are consistent and reasonably timed.
Conversation shows effort, questions, and clarity.
User moves from chat toward simple plans.
Shows up, cancels rarely, and communicates changes.
Behavior is stable across repeated interactions.
Trust score is not a public vanity number. It is an internal ranking signal that improves match quality, reduces flakes, and protects serious users.
Mode, prompts, and stated intent are useful, but low-trust. Users guess, overthink, or misrepresent themselves.
Reply consistency, effort, tone stability, and initiation help the system understand communication quality.
Plans made, plans kept, cancellations, ghosting, and real-world follow-through carry the most weight.
The profile must support connection quality without turning into a performance page, popularity contest, or personality quiz maze.
Users should not need to write a life story before the system can start learning from real behavior.
The system should not pretend users know exactly what they want before interaction proves anything.
Behavior signals should improve quality and safety, not create public scores, status games, or social pressure.
Xora helps people meet fewer, better-aligned people with real-world follow-through by using declared input lightly and behavior seriously.
Join early access