offplan-report
Build a client-ready Dubai/UAE off-plan property evaluation report (HTML page + PDF) from a sales offer, brochure, or a project on Reelly / GenieMap / Property Finder / Bayut. Use when someone shares
SKILL.mdskills/offplan-report/SKILL.md
GitHubOff-plan evaluation report
Version 1.5.0 (see VERSION and CHANGELOG.md).
Turns one off-plan unit into a polished, phone-friendly report: verdict, deal checks, what-if scenarios, supply & demand, payment plan, location comfort, full step-by-step maths, photo gallery, and a client PDF. Everything is driven by one data file; the template does the maths.
Read these before starting (all in references/):
workflow.md– the exact step-by-step process (follow it in order)sources.md– every website, what to read on it, URL patterns, gotchas, fallbacksrules.md– formulas, growth bands, premiums, valuation cases, labels, wording rulesdesign.md– section order and the design/wording decisions the report must keeplistings-and-evidence.md– how to collect the project's sales, similar listings and resale infomodules.md– optional modules (distressed deal, mortgage, market evidence, developer) and the section orderdata-schema.md– every field of the data file, with the Weston example
The build kit is in kit/ (copy it to a working folder first – see step 0).
Golden rules
- Answers, not a calculator. The output is a finished report, not a form.
- Never invent data. Every number comes from a source you actually opened, or from the user.
If a source is missing (no account), use the fallback in
sources.mdand say so in the report. Minimum sample: 5 transactions; widen 3 months → 6 months → 1 year; else say "no data". - Facts, not advice. Headline says e.g. "Profitable at handover, not before"; never "good buy", "hold", "you should". Keep the disclaimer.
- Say each number once. Don't repeat the same figure in two places.
- Ask before downloading anything the user didn't ask for, before publishing/sharing outside their account, and before typing into anything that isn't a search/filter box. Never enter passwords.
- Credit line stays. Never remove the footer line "The Ultimate Real Estate Calculator · Off-plan Report v… © 2026 Abdulla Alzarooni …" or the copyright notices; they are required by the LICENSE.
- Verify before handing over: run the checks in
workflow.md(step 9). Report failures honestly. - Before every report (not only the first one), ask whether they want the optional Developer section (step 2b: it takes a long time) and whether the unit is a resale or new from the developer (step 2c).
Quick start
cp -R ~/.claude/skills/offplan-report/kit "<working folder>/offplan-reports" # once
# first time only: fill config/agent.js and drop logo/photo into brand/ (optional)
cp data/example-weston-109.js data/<project>-<unit>.js # per property
# ...fill the data file following workflow.md...
python3 build.py data/<project>-<unit>.js # -> <project>-<unit>.html
node tools/domtest.js <project>-<unit>.html </dev/null # must print the summary, no errors
# then: every image must load (workflow.md step 9) – never deliver a report with a missing photo
node tools/dump.js <project>-<unit>.html # must print: bad 0 []
Then make the PDF and publish/share (workflow steps 10–11).
First run for a new person
Guide them step by step, in plain words; don't assume they are technical.
0. Check the setup before anything else and help fix what's missing (one item at a time):
python3 --version, node --version, Python packages pymupdf and pillow (pip3 install pymupdf pillow: read image-only brochures, resize photos), Google Chrome installed, and the Claude in Chrome
extension connected (needed to read the data sites). If something is missing, explain what it is
in one line and walk them through installing it (official sites only; ask before downloading).
Then copy kit/ to a working folder they choose (default ~/Documents/Off-plan Reports).
- Ask once, then save into
config/agent.jsof their working folder (and remember it): name, company, BRN, WhatsApp number, social links (any of Instagram, Facebook, TikTok, YouTube, Threads, X, LinkedIn, Snapchat), optional formulas credit line; optional files inbrand/of the working folder:logo-dark.png+logo-light.png(transparent; light/dark versions) andagent.jpg(square headshot – crop to the face, it shows in a circle). Anything left empty is simply hidden. - Ask which data accounts they have (DXB Interact, Reelly, GenieMap) –
this decides which sources and fallbacks to use (no paid accounts → Reelly + DXB Interact + Bayut).
Never use Property Monitor, even if they have an account: it prohibits AI / automated use (
sources.md). 2b. Ask about the optional Developer section before collecting any data, in these words or close: "The Developer section is optional and takes a long time to build. Would you like it? If yes, it shows every project by this developer – ready, under construction and planned – each with photos, completion date and DLD target, % built, unit mix, rented % or absorption rate, and price / rent premium vs its area for each unit type (off-plan premium for projects not finished yet), with area and unit-type filters and a search box." If no, build the report without it. If yes, tell them it adds a lot of time, then followreferences/developer-section.md(data format:data-schema.md→ Developer section). 2c. Ask whether the unit is a resale (from an owner) or bought new from the developer. Only resales get the distressed deal test (listings-and-evidence.mdstep 0). For a mortgage, seemodules.md. - Then ask for the first property (sales offer PDF, brochure, or a project link) and follow
workflow.md. Tell them what you are doing as you go (e.g. "Reading Bayut rents…") and what each step needs from them.
Developer × bank offers: for every off-plan property, look the developer up in references/bank-offers.md; if it has a deal (e.g. Ellington × ADCB, Emaar × ADCB, Dubai Holding × ADCB/ENBD/CBD, Expo City × DIB, Sobha × ENBD/ADIB/RAKBANK), add the bank-offer option to the mortgage section (workflow step 1b).