moon-real is a real-estate web product whose purpose is to present residential property as architecture worth desiring. The product serves two audiences at once: people looking for a home to live in, and the property listers or agents who bring that inventory to market. The defining intent from the authoritative requirement thread is twofold — build a real-estate project, and make its design creative and more attractive than a conventional listings site. That second requirement is not decoration; it is a first-class product commitment that shapes how properties are presented, browsed, and evaluated.
The product therefore treats every property as a sculpted object rather than a database row. Seekers browse a curated offering and evaluate individual residences through imagery and detail. Listers and agents enroll themselves, then create, edit, and manage durable listings that carry compelling visuals and descriptions. The visual language — a dark lunar ground, pearl-grey parametric line-work, and a single restrained gold accent — is the mechanism by which the "creative and more attractive" requirement is delivered.
This document specifies the current delivery: seven pages, two active human personas, application-owned identity for listers and agents, and a public, no-account browsing experience for seekers.
moon-real is a first-party web application with a custom user interface and a backend that persists property listings and lister/agent identity. It delivers:
Actors. Two active human personas are in scope: the Property Seeker and the Property Lister / Agent. The application itself owns identity, listing persistence, and authorization of listing management. No third-party identity provider, external marketplace, or outbound-only recipient is established by the source.
Ownership. The application owns all seven pages. Identity is application-owned: listers and agents establish it themselves through Sign Up and re-establish it through Login. Listing management is restricted to the authenticated lister or agent who owns the listing.
Narrow exclusions. No payment, transaction, escrow, mortgage, or offer-negotiation capability is established. No messaging or contact-brokerage capability between seeker and lister is established. No third-party listing syndication or external marketplace integration is established. No administrative, moderation, or multi-role permission hierarchy beyond "the owning lister or agent manages their own listings" is established. These are not implemented in the current delivery.
Delivery. moon-real is delivered as a first-party web application with custom UI and a backend service. The public surface — Landing, Properties, and Property Details — is reachable without an account. The management surface — Listings and Listing Editor — requires an established, verified identity.
Access ownership. Identity is owned by the application, not by an external provider. A property lister or agent establishes identity through self-service enrollment on Sign Up, because no invitation, provisioning, or deployment-bootstrap boundary is established by the source. A returning lister or agent re-establishes identity through Login. Sign Up and Login are themselves anonymously reachable — a protected destination cannot own the interaction that grants access to itself. Only Listings and Listing Editor are protected, because only they carry durable, actor-specific state that must remain bound to the correct owner.
Current vs. future. Everything specified in Sections 3 through 5 is current. No future-horizon capability was accepted by the source; Section 11 records the boundaries that were explicitly left out rather than deferred.
Not applicable. No reference directive in this project declares a content_source, so no verified factual inventory is carried into this document. All property content is authored by listers and agents through the Listing Editor.
The page inventory below is the closed, ordered page contract for this generation: Landing, Sign Up, Login, Properties, Property Details, Listings, Listing Editor. Each page appears exactly once.
Each requirement below is a distinct story point. Provenance is marked explicit (stated by the user), basic_default (accepted default), or required_inference (indispensable mechanics inferred to make an accepted journey executable).
FR-1 — Public entry to the real-estate offering (explicit) As a Property Seeker, I should arrive at a public Landing page that introduces moon-real and its curated residences, so that I can understand what the site offers and begin browsing.
FR-2 — Browse the available property offering (explicit) As a Property Seeker, I should browse the available properties on a public Properties page, so that I can survey what is on offer.
FR-3 — Evaluate an individual property (explicit) As a Property Seeker, I should open a property's Property Details page and evaluate it through its imagery and details, so that I can judge whether it matches my needs.
FR-4 — Creative and attractive presentation of properties (explicit) As a Property Seeker, I should experience the real-estate offering through a creative and more attractive design, so that evaluating properties feels like viewing architecture rather than reading a spreadsheet.
prefers-reduced-motion, parallax and float stop, images swap instantly, and the flow line renders fully drawn — the presentation remains complete without motion.FR-5 — Self-service enrollment as a lister or agent (required_inference) As a Property Lister / Agent, I should complete self-service enrollment on Sign Up, so that I can establish an identity that owns my listings.
FR-6 — Returning verification for listers and agents (required_inference) As a Property Lister / Agent, I should verify my identity on Login, so that I can regain access to my durable listing-management workflow.
FR-7 — Review own durable listings (required_inference) As a Property Lister / Agent, I should review my own listings on the Listings page, so that I can see what I have published and what state each listing is in.
FR-8 — Create a property listing (required_inference) As a Property Lister / Agent, I should create a property listing in the Listing Editor, so that a new residence becomes part of the published offering.
FR-9 — Edit an existing listing (required_inference) As a Property Lister / Agent, I should edit one of my own listings in the Listing Editor, so that its imagery and details stay accurate and compelling.
FR-10 — Present listings with compelling, creative visuals and details (explicit) As a Property Lister / Agent, I should present my properties with compelling, creative visuals and details, so that seekers can evaluate them and my listings attract qualified interest.
FR-11 — Ownership-bound listing management (required_inference) As a Property Lister / Agent, I should have my listings remain bound to my own identity, so that no other actor can view or change my listing content.
Product context. The Property Seeker arrives at moon-real without an account and without a commitment. They are in an exploratory, comparative frame of mind: they want to see what exists, form an impression of quality, and narrow toward something that matches their needs. They may arrive from the Landing page's featured preview or go straight to the full offering.
Primary goal. Find a property that matches their needs and take the next step toward it.
Distinct accepted responsibilities. The Seeker is the sole actor on the public surface. They survey the offering on Properties, open individual residences on Property Details, and evaluate them through imagery and detail. They are the audience for whom the "creative and more attractive" requirement exists — the presentation is what lets them imagine living inside a sculpted space rather than reading a row of attributes.
Relevant inputs and decisions. The Seeker decides which properties to open and which to dwell on. Their inputs are the property imagery, the descriptive details, and the composition of the offering itself. They make no commitment inside the product; their decision is which property to pursue.
Interactions with other participants. The Seeker is the counterparty whose evaluation the Property Lister / Agent is trying to earn. The Seeker never interacts with the Lister directly inside the product — no messaging or contact capability is established — but the Lister's authored imagery and details are precisely what the Seeker evaluates.
Observable success. The Seeker has surveyed the offering, opened the properties that interested them, and identified a property that matches their needs.
Product context. The Property Lister / Agent is the party responsible for the real-estate inventory. They arrive with properties to present and a professional interest in how those properties read. They are not browsing for themselves; they are curating a gallery of residences and want each listing to feel like a piece rather than a row.
Primary goal. Publish listings that are compelling and attract qualified interest.
Distinct accepted responsibilities. The Lister is the only actor who establishes an identity. They enroll themselves on Sign Up, verify on Login when returning, review their own listings on Listings, and create and edit listing content — imagery and descriptive details — in the Listing Editor. They own the durable state of their listings and are the only actor authorized to change it.
Relevant inputs and decisions. The Lister's inputs are the property imagery they attach and arrange and the descriptive details they enter. Their decisions are what to include, how to present it, and when a listing is ready to be published. Their work is judged by whether the resulting listing reads as a sculpted object in the public offering.
Interactions with other participants. The Lister's authored content is what the Property Seeker evaluates. The Lister does not interact with the Seeker directly inside the product; their influence on the Seeker is entirely through the quality of the listing they publish.
Observable success. Their listings are published, render attractively in the public offering, and attract qualified interest.
prefers-reduced-motion, parallax and float stop, images swap instantly, and the flow line renders fully drawn. The Seeker's journey is unchanged.The creative direction is authoritative for this section. It names Zaha Hadid as the muse and "Fluid parametric grandeur — moon-real as a lunar-lit architectural object" as the headline. The direction is translated below into concrete tokens.
Mode. Dark mode is the product's native mode. There is no light-ground variant; the lunar void ground is what makes each property image glow.
Colour tokens by role.
| Role | Hex | Use |
|---|---|---|
| Background | #0E1014 | The lunar void ground; every page sits on it |
| Surface | #171A20 | Panels and cards, sitting on the ground as slightly raised slabs |
| Text | #F4F1EA | Warm bone; all readable text |
| Primary | #C9CDD4 | Brushed-silver / pearl grey; hairline curves, dividers, secondary buttons, the flowing line-work tracing Hadid's forms |
| Accent | #C9A227 | Single restrained gold; CTAs, the "moon-real" wordmark dot, price highlights, and one active state per screen — never more than ~5% of any view |
| Muted | #8A8F99 | Metadata, labels, captions |
Accent discipline. No more than one gold accent element per viewport. The accent must stay rare.
Forbidden. No blue, no indigo, no white-ground SaaS look. #0057FF, #2563EB, #4F46E5, #6366F1, #7C3AED and neighbours are excluded, as is the generic indigo/blue-on-white template.
Typography.
clamp(40px, 9vw, 112px).clamp(28px, 5vw, 56px).system-ui for headings or body.Shape language. Parametric curves everywhere; no right angles in decorative elements. Section boundaries are SVG arcs that flow between blocks. Cards are rounded-rectangle panels with a 28–40px radius and a 1px pearl-grey inner stroke that catches light like a curved edge. Buttons are pill capsules with a subtle inner highlight on the top edge. Image masks use asymmetric organic curves — a soft S-curve on one side — so property photos feel carved rather than cropped. One recurring motif: a thin continuous flow line that traces the page as the user scrolls, connecting sections like a single architectural gesture.
Spacing rhythm. Generous vertical rhythm: 96–160px section gaps on desktop, 56–88px on mobile.
Layout. Asymmetric editorial architecture on a 12-column grid. Heroes occupy columns 1–8 with a floating image arc bleeding off the right edge; detail pages invert to columns 5–12. Navigation is a top bar that condenses into a floating capsule after scroll, with a single gold CTA. The property grid uses two columns on desktop with staggered vertical offsets — one card raised 40px — so the page reads as a composition, not a spreadsheet. At 375px everything collapses to a single column, arcs become simple rounded corners, and the flow line hides.
Imagery style. Architectural photography treated as sculpture: wide-angle exterior shots at dusk with warm interior light, macro details of staircases, curves, glass and stone, and monochrome-to-colour hover reveals. Every property image sits inside an organic curved mask on a #0E1014 ground, with a faint pearl-grey arc echoing the building's silhouette behind it. No stock people shaking hands, no flat clip art, no gradient blobs, no generic city skylines.
Readable-text integrity. Headlines, wordmarks, labels, numbers, card text and controls stay entirely inside the viewport and their container at 375px, 768px and 1280px, wrapping or scaling to fit, and no other element covers any part of them. Imagery and decoration may be cropped, bled, rotated, or overlapped as the direction asks, provided they cover no readable text or control.
The lunar stage and the drawn line.
The public entry is composed as a single architectural gesture rather than a stack of blocks. The first screen is a full-viewport dark lunar stage on #0E1014. On the left, a nine-column stack of oversized Josefin Sans Light headline — "Homes shaped like the moon" — clamps from 40px on mobile to 112px on desktop, with tight leading so the lines read as one sculpted mass. Above it sits a small uppercase eyebrow, "MOON-REAL · CURATED RESIDENCES", in #C9A227. Beneath the headline, pinned, is a single gold pill CTA, "Explore properties".
On the right, a tall property photograph is masked by an asymmetric S-curve and bleeds off the right edge of the viewport, overlapping a thin pearl-grey parametric arc that draws itself on scroll. A second, smaller arc echoes the first near the bottom-left. The top-right of the hero holds the compact floating capsule navigation, carrying the "moon-real" wordmark with its gold dot on the "o".
The dominant element is the curved architectural image and the silver flow line; the headline is the second mass. There is no centred headline, no blue button, and no gradient blob. As the visitor scrolls, the flow line continues down the page and draws itself, connecting hero, property preview, and footer as one continuous architectural gesture — the same line that reappears inside the management surface, so the product reads as one building rather than two applications.
This concept recomposes only accepted content, states, and controls: the headline, the eyebrow, the CTA, the navigation, the property imagery, and the flow line. It introduces no new behaviour, page, or destination.
Interaction Model: Animated Motion Tempo: cinematic Hero Dimensionality: layered_2d
Landing Hero Motion Brief.
prefers-reduced-motion, all parallax and float stop, images swap instantly rather than crossfading, and the flow line renders fully drawn. The composition is complete and legible without any motion.NFR-1 — Creative and attractive presentation (explicit) The design must be creative and more attractive than a conventional listings site. This is a stated product requirement, not a preference. Rationale: the user explicitly required it, and it is the product's differentiating commitment.
NFR-2 — Readable text and controls stay whole (explicit, from the creative direction)
At 375px, 768px and 1280px, headlines, wordmarks, labels, numbers, card text and controls stay entirely inside the viewport and their container, wrapping or scaling to fit, and no other element covers any part of them. Imagery and decoration may be cropped, bled, rotated, or overlapped. Moving and scrollable content may cross the viewport edge by design, judged by whether it actually moves and whether every item becomes fully readable as it passes. Under prefers-reduced-motion, moving content stops and shows whole items, wrapping into rows or sitting in a horizontally scrollable row. Where any instruction asks readable text or a control to be cropped, clipped, covered, or run off an edge, this rule takes precedence and the gesture is carried by imagery or decoration instead.
NFR-3 — Reduced-motion support (explicit, from the creative direction)
prefers-reduced-motion must stop all parallax and float, swap images instantly, and render the flow line fully drawn.
NFR-4 — Accent restraint (explicit, from the creative direction) No more than one gold accent element per viewport; the accent stays under roughly 5% of any view.
NFR-5 — Palette and typography fidelity (explicit, from the creative direction) The specified hex values and the Josefin Sans / Jost pairing must be used as given. Blue, indigo, and white-ground SaaS treatments are excluded, as are the named forbidden typefaces.
NFR-6 — Durable listing persistence (required_inference) Listings must persist durably and remain bound to the identity that created them, because the accepted journey requires a lister or agent to return, review, and edit their own listings across sessions. Rationale: without durable, ownership-bound persistence, FR-7, FR-9, and FR-11 are not executable.
NFR-7 — Protected-surface access control (required_inference) Listings and the Listing Editor must be reachable only by the authenticated owner of the listings they expose. Rationale: the accepted journey requires that a lister's durable listing state remain bound to the correct participant.
NFR-8 — Backend integration (required_inference) The product requires a backend that serves the public offering and persists identity and listings. Rationale: the accepted journeys cannot complete without it.
No technology choices were specified by the user. The following are coherent defaults, labeled as such.
[Default — not specified by user]. Chosen because the product is a custom-UI web application with a rich, motion-driven public surface and a protected management surface.[Default — not specified by user]. Chosen because the product requires a backend serving the public offering and persisting identity and listings.[Default — not specified by user].[Default — not specified by user].[Default — not specified by user].Assumptions.
Constraints.
Explicitly out of scope for the current delivery.
#C9A227 element permitted per viewport.
A curated register of sculpted residences — each one photographed as architecture, drawn as a single continuous line, and offered to those who read a home the way they read a building.
A rotating selection of published residences from the moon-real collection — each one presented as a sculpted object rather than a listing row.
A curved concrete ridge house with a continuous terrace that follows the hillside contour.
View residenceA walled courtyard villa whose glazed spine opens onto a still reflecting pool.
View residenceA cantilevered penthouse wrapped in curved glazing above the city's night line.
View residenceA stone residence organised around a sculpted stair hall lit from a single curved skylight.
View residence
A curated register of sculpted residences — each one photographed as architecture, drawn as a single continuous line, and offered to those who read a home the way they read a building.
A rotating selection of published residences from the moon-real collection — each one presented as a sculpted object rather than a listing row.
A curved concrete ridge house with a continuous terrace that follows the hillside contour.
View residenceA walled courtyard villa whose glazed spine opens onto a still reflecting pool.
View residenceA cantilevered penthouse wrapped in curved glazing above the city's night line.
View residenceA stone residence organised around a sculpted stair hall lit from a single curved skylight.
View residence
No comments yet. Be the first!