npm - @rubytech/create-maxy-code - Versions diffs - 0.1.114 → 0.1.115 - Mend

@rubytech/create-maxy-code 0.1.114 → 0.1.115

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (711) hide show

package/payload/premium-plugins/real-agent/plugins/brochures/skills/property-socials/SKILL.md DELETED Viewed

@@ -1,143 +0,0 @@
----
-name: property-socials
-description: Use when generating Open Graph / social-share images for a property page built by the real-estate brochure pipeline (estate-agents/<agent>/properties/<slug>/output/web/page.html). Produces landscape, square, and portrait JPGs that match the brochure's brand palette and typography, pulling copy from property.json and hero images already curated for that property. Triggers include "og images for <property>", "social collateral for <listing>", "Instagram tiles for that brochure", or any request to create share-card imagery for a published realagent.chat property page.
----
-# Property OG / Social Images
-The brochure pipeline already produces a styled property page at
-`estate-agents/<agent>/properties/<slug>/output/web/page.html` with curated hero
-images under `images/`, branding tokens in `:root` of the page CSS, and
-structured metadata in the property's `property.json`. This skill renders
-share-ready images by overlaying brand-consistent typography on those hero
-shots — it does not re-design anything.
-## Inputs the skill consumes (never invents)
-- **Palette and fonts** — read from `:root` in `output/web/page.html`. Use the
-  exact `--paper / --ink / --gold` tokens and Google Font imports already on
-  that page. Do not pick new colours.
-- **Copy** — `property.json` is canonical for address, price, qualifier,
-  bedrooms/baths/receptions, agent name + phone. The page's
-  `<meta name="description">` is the sub-headline. The property's display
-  name (`property.json -> property_name`, or the first address line if the
-  property has no distinct name) is the headline.
-- **Hero images** — `images/<slug>-hero-1-main.webp`, `hero-2-kitchen.webp`,
-  `hero-3-garden.webp` are the curated set. Use them by name; do not pick
-  numbered shots from the raw set unless the curated heroes are missing.
-## Output contract
-This skill owns the **full** social-collateral deliverable. Whether invoked directly or through `make-brochure`'s `+socials` add-on, the same files land on disk — no orchestrator-side gallery emission, no split contract.
-```
-output/web/
-  socials/
-    og-landscape-<hero>.jpg     # 1200×628  Twitter / LinkedIn / Facebook / OG
-    og-square-<hero>.jpg        # 1200×1200 Instagram feed
-    og-portrait-<hero>.jpg      # 1080×1350 Instagram portrait, mobile
-  socials.html                  # gallery page — the third HTML endpoint in the bundle
-  social-posts.md               # paste-ready captions, also linked from socials.html
-  og.html                       # template that renders the tiles, kept for re-runs
-```
-`<hero>` is `main`, `kitchen`, or `garden`. At minimum produce `og-landscape-main.jpg`; offer the full nine-variant set (landscape + square + portrait × main/kitchen/garden) when the user wants social collateral, not just a meta image.
-**Gallery page (`socials.html`)** sits at the root of the web bundle, alongside `brochure.html` and `index.html`. It previews each tile at its actual dimensions with download links, the suggested copy from `social-posts.md` inline next to each tile, and the platform's `<meta>` snippet ready to paste into a page `<head>`. Brand it from the same DESIGN.md tokens used for the brochure — same `:root` palette, same display family, same accent.
-**Captions (`social-posts.md`)** are written one section per image, ready to paste. Every caption is generated through the `plainly` skill's
-register: no em-dashes, no inflation vocabulary (*discover*, *unlock*,
-*nestled*, *stunning*, *boasts*, *bespoke* where it isn't literally bespoke),
-no antithetical "it's not X, it's Y", no rhetorical openers (*Imagine…*,
-*Picture this…*). Read each draft aloud; if it sounds like an estate-agent
-blurb-bot rather than a person, rewrite it.
-Per-platform shape (these are caps, not minimums):
-- **Landscape post (Twitter / X)**: under 280 characters. One sentence of
-  scene, one of specs, one of agent + phone. Link as last token.
-- **Landscape post (LinkedIn / Facebook)**: three short paragraphs. Opening
-  line that names the property and locality. A middle paragraph of concrete
-  features taken from `property.json`'s `key_features`. A closing paragraph
-  with price, agent name, phone, listing URL.
-- **Square (Instagram feed)**: property name + locality on line one, two or
-  three lines of concrete features, price, agent + phone, "link in bio", four
-  to six hashtags drawn from locality + property type + agency.
-- **Portrait (Instagram portrait / Reels cover)**: lead with what is visible
-  in *that specific hero* (exterior, kitchen, or garden), not the generic
-  property summary. Three lines maximum. Price + agent line at the bottom.
-Copy sources, in order: `property.json` for facts (address, price, beds, baths,
-acreage, key features); the page's `<meta name="description">` for tone of the
-hero sub-line; the brochure folder display name for the headline. Do not invent
-features that are not in those sources.
-## How rendering works
-A single `og.html` template lives at `output/web/og.html` alongside `page.html`
-so it can use relative `images/` paths. It accepts `?format=landscape|square|
-portrait` and `?hero=main|kitchen|garden`, applies the matching CSS class with
-explicit min/max width and height (no relative units), and sets the background
-hero image from the param. Playwright screenshots the URL at exactly the
-container's pixel size.
-Critical layout rules:
-- The stage div fixes its own width and height with `width / minWidth / maxWidth`
-  (and the height triple). Without max constraints the viewport bleeds.
-- Hero fills the stage with `background-size: cover; background-position: center`
-  so the same template works across all three aspect ratios.
-- A vertical gradient scrim (transparent → ink 0.85) sits between hero and copy.
-  On bright daytime shots the scrim's bottom stop must reach ≥ 0.85 or the
-  eyebrow/sub copy loses contrast.
-- Copy block sits in the bottom-left: eyebrow (locality, gold), headline
-  (display serif), sub (italic body serif), thin rule, specs row, footer line
-  with `realagent.chat / <agent>` left and `<agent name> · <phone>` right.
-## Generation flow
-1. Confirm `output/web/og.html` is in sync with the page's `:root` palette and
-   `property.json` copy. If the property page has been re-themed since the last
-   render, update the template before screenshotting.
-2. Start a static server in `output/web/` on any free port:
-   `python3 -m http.server <port> &`. Hold the PID so it can be killed at the
-   end. Relative `images/` paths require a real HTTP origin; `file://` won't
-   render webfonts either.
-3. On a fresh machine, `npx -y playwright install chromium` once. The first
-   `playwright screenshot` invocation otherwise fails with "Executable doesn't
-   exist".
-4. Screenshot each variant. Pass `--wait-for-timeout=2500` so Google Fonts
-   land before capture. Always quote URLs that contain `&`.
-5. Stop the server. Verify each JPG with `Read` so the user sees the rendered
-   collateral inline — file sizes alone aren't proof of a good render.
-## Failure modes seen on first use
-- **Filename mangling.** A bash loop using `for v in "landscape main" …; set --
-  $v` collapses to filenames like `og-landscape main-.jpg` (space, then dash).
-  Use an explicit per-variant call or an array; never rely on positional
-  splitting for two-word tuples.
-- **6 KB screenshots.** A screenshot under ~20 KB is a blank page. Common
-  causes: server not running, wrong port, Chromium not installed, or `og.html`
-  threw a JS error. Open the URL in a browser to confirm before re-running.
-- **Eyebrow on a light surface.** The garden / pool hero washes the eyebrow
-  out. Either deepen the scrim's bottom stop or move the eyebrow above the
-  hero crop on that variant. Don't ship a low-contrast tile.
-- **Treating this as a Next.js task.** The brochure site is static HTML. The
-  upstream `og-images` skill assumes `app/og/page.tsx`; ignore that scaffold
-  and render against the static page directly.
-- **Captions that sound like AI marketing.** "Discover this stunning home
-  nestled in the heart of Essex" is the failure mode. Strip *discover*,
-  *unlock*, *nestled*, *stunning*, *boasts*, *exquisite*, *charming*, every
-  em-dash, every exclamation mark used to fake enthusiasm. The aloud test from
-  the `plainly` skill applies: read the caption out; if you would not say it
-  in conversation to a buyer, rewrite it.
-## Out of scope
-- The brochure page itself (owned by `real-estate-brochure:property-brochure`).
-- Property metadata extraction (owned by
-  `real-estate-brochure:property-extract`).
-- Wiring `<meta property="og:image">` into `page.html`. Surface the snippet for
-  the operator; the page is regenerated by a separate skill and edits there
-  belong in that pipeline, not this one.

package/payload/premium-plugins/real-agent/plugins/buyers/.claude-plugin/plugin.json DELETED Viewed

@@ -1,8 +0,0 @@
-{
-  "name": "real-agent-buyers",
-  "description": "Full buyer lifecycle — enquiry handling, qualification, viewing management, feedback collection, educational guides, and the public-chat property recommender that surfaces current listings as rendered cards on visitor buyer intent.",
-  "version": "0.1.0",
-  "author": {
-    "name": "Rubytech LLC"
-  }
-}

package/payload/premium-plugins/real-agent/plugins/buyers/PLUGIN.md DELETED Viewed

@@ -1,35 +0,0 @@
----
-name: real-agent-buyers
-description: "Full buyer lifecycle — enquiry handling, qualification, viewing management, feedback collection, educational guides, and the public-chat property recommender that surfaces current listings as rendered cards on visitor buyer intent."
-tools: []
-always: false
-metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
----
-# Real Agent — Buyer Management
-Six skills covering the complete buyer lifecycle from initial enquiry through viewing management and educational content, plus the public-chat property recommender that fires on visitor buyer intent.
-## When to Activate
-The user is handling buyer enquiries, qualifying applicants, managing viewings, collecting post-viewing feedback, or providing educational guides for buyers and sellers at different life stages.
-## Skills
-| Skill | Purpose |
-|-------|---------|
-| `buyer-management` | Full buyer lifecycle — enquiry, qualification, viewing, feedback, offer |
-| `buyer-feedback` | Post-viewing feedback collection via conversational check-in |
-| `property-enquiry` | Structured intake for new buyer enquiries — requirements, finances, timeline |
-| `property-recommender` | Public-chat skill — render a property card (image + blurb + listing URL) on buyer intent, sourced from `:Listing` and `:ImageObject` via memory-search |
-| `viewing-management` | Viewing lifecycle — booking, confirming, rescheduling, reminders |
-| `buyer-seller-guides` | Educational guides for buyers and sellers — first-time, upsizing, downsizing, probate |
-## Tools Used
-No MCP server. Skills operate via existing platform tools:
-- `memory-search` — retrieve domain knowledge from the knowledge base
-## References
-Domain knowledge files loaded on demand by each skill. See individual skill files for their specific reference listings.

package/payload/premium-plugins/real-agent/plugins/buyers/skills/buyer-feedback/SKILL.md DELETED Viewed

@@ -1,109 +0,0 @@
----
-name: buyer-feedback
-description: "Collect structured post-viewing feedback from property buyers conversationally through the chat interface. Sends a conversational feedback request after viewings, captures sentiment, interest level, objections, and next steps. Stores feedback per-property and per-buyer for vendor reporting."
----
-# Buyer Feedback Collection
-Collect post-viewing feedback from buyers in a natural, conversational way through the chat interface. This is NOT a form — it's a friendly check-in that captures structured data.
-## When to Trigger
-This skill applies when:
-- The agent (or a scheduled event) initiates a post-viewing feedback request
-- A buyer messages after a viewing with unsolicited feedback
-- The business owner asks you to collect feedback on a specific viewing
-## Feedback Flow
-### Step 1: Opening
-Send a warm, brief message referencing the specific property and viewing date. Keep it personal — use the buyer's first name and the property address.
-Example:
-> Hi [Name]! Hope you're well. Just wanted to check in after your viewing at [Address] on [Date]. How did you find it?
-### Step 2: Capture Key Data Points
-Through natural conversation (NOT a bullet list of questions), gather:
-1. **Overall impression** — Did they like the property? First reaction.
-2. **Interest level** — Are they considering making an offer? Scale: Hot / Warm / Cool / Not interested
-3. **Positives** — What did they like most?
-4. **Concerns/objections** — What put them off or gave them pause? (Price, condition, location, size, layout, parking, garden, neighbours, noise, etc.)
-5. **Comparison** — How does it compare to others they've seen?
-6. **Next steps** — Would they like a second viewing? Are they ready to make an offer? Need more information?
-7. **Price perception** — Do they think it's fairly priced? (Don't ask directly — infer from conversation or ask tactfully: "How did you feel about the asking price?")
-### Step 3: Follow-up Questions
-Based on their responses, ask ONE follow-up at a time. Don't fire multiple questions. Match their energy — if they're brief, be brief. If they're chatty, engage.
-If they express interest:
-- "Would you like to book a second viewing?"
-- "Is there anything else you'd like to know about the property?"
-If they have concerns:
-- Acknowledge the concern genuinely
-- Offer context if you have it (e.g. "The vendor is open to offers" or "There's planning permission for an extension")
-- Don't be pushy — respect their assessment
-If not interested:
-- Thank them warmly
-- Ask what they ARE looking for (captures buyer criteria for future matching)
-### Step 4: Store Feedback
-After the conversation, save structured feedback to TWO locations:
-**Property file** — `memory/shared/properties/[property-slug]/feedback/[date]-[buyer-name].md`
-**Buyer profile** — `memory/users/[phone]/viewings/[date]-[property-slug].md`
-Use this template:
-```markdown
-# Viewing Feedback
-- **Property:** [Full address]
-- **Date:** [Viewing date]
-- **Buyer:** [Name] ([Phone])
-- **Agent present:** [Name if known]
-## Feedback
-- **Overall impression:** [Their words / summary]
-- **Interest level:** [Hot / Warm / Cool / Not interested]
-- **Positives:** [What they liked]
-- **Concerns:** [What they didn't like or worried about]
-- **Price perception:** [Fair / Too high / Bargain / Not discussed]
-- **Comparison:** [How it ranked vs other properties]
-- **Next steps:** [Second viewing / Offer / Thinking / Declined]
-## Quotes
-> [Any notable direct quotes from the buyer]
-## Notes
-[Any additional context — body language cues mentioned, timing factors, chain status, etc.]
-```
-## Vendor Reporting
-When the business owner or agent asks for a viewing feedback summary for a property:
-1. Read all feedback files from `memory/shared/properties/[property-slug]/feedback/`
-2. Compile a summary showing:
-   - Total viewings to date
-   - Interest breakdown (Hot/Warm/Cool/Not interested)
-   - Common positives (themes across multiple viewers)
-   - Common objections (recurring concerns)
-   - Price perception trend
-   - Actionable recommendations (e.g. "3 of 5 viewers mentioned the dated kitchen — consider adjusting marketing to acknowledge renovation potential")
-## Rules
-- **Never fabricate feedback.** Only report what buyers actually said.
-- **Never share one buyer's feedback with another buyer.** Feedback goes to the vendor/agent only.
-- **Be genuinely conversational.** Buyers who feel interrogated give shallow answers. Buyers who feel heard give honest ones.
-- **Respect "no."** If a buyer doesn't want to give feedback, thank them and move on. Don't chase.
-- **Timing matters.** Best results come 2-24 hours after the viewing. Same day is ideal. After 48 hours, response rates drop sharply.
-- **One message at a time.** Never send a wall of questions. This is a conversation, not a survey.

package/payload/premium-plugins/real-agent/plugins/buyers/skills/buyer-management/SKILL.md DELETED Viewed

@@ -1,42 +0,0 @@
----
-name: buyer-management
-description: "Handle buyer enquiries — qualification, viewing booking, feedback collection, offer capture, and ongoing buyer relationship management."
-publicEmbed: false
----
-# Buyer Management
-Guides the full buyer lifecycle — from initial enquiry through qualification, viewing management, feedback collection, and offer capture.
-## When to Activate
-Someone asks about a property, registers interest, requests a viewing, gives post-viewing feedback, wants to make an offer, or needs rescheduling/cancelling a viewing.
-## Reference Table
-| Task | When | Reference |
-|------|------|-----------|
-| Quick qualification (5 questions) | Early in conversation to gauge seriousness fast | `references/buyer-qualification-questions.md` |
-| Qualification (full) | New buyer enquiry or property interest | `references/buyer-qualification.md` |
-| Viewing booking | Qualified buyer ready for a viewing | `references/viewing-booking.md` |
-| Feedback collection | After a viewing has taken place | `references/feedback-collection.md` |
-| Offer capture | Buyer wants to make an offer | `references/offer-capture.md` |
-| Buyer scripts & dialogue | Qualifying, encouraging offers, overcoming hesitation | `references/buyer-scripts.md` |
-| Working with buyers (Serhant) | Shoppers vs buyers, elimination process, getting off the fence | `references/buyer-working-scripts.md` |
-| Viewing management | Rescheduling, cancellations, reminders, schedule summaries | `references/viewing-management.md` |
-## Key Rules
-- Always qualify before booking a viewing — understand their position first
-- One question at a time — don't overwhelm with a qualification form
-- Never disclose vendor circumstances, other offers, or pricing flexibility
-- Never negotiate — gather information and pass to the agent
-- Update the buyer's profile in memory after every interaction
-- Frame everything around helping them, not extracting information
-- Distinguish shoppers from buyers — qualify early, invest time wisely
-- "Buying a home is a process of elimination, not selection" — guide them through narrowing down
-- Post-viewing follow-up within 2 hours — never leave a viewing without a next step
-- An offer is "just a conversation starter" — help hesitant buyers understand nothing is final until exchange
-- Never double-book a property or team member at the same time
-- Access instructions (lockbox codes, keys) are confidential — only share with the conducting agent
-- Two no-shows = flag to agent before booking further viewings

package/payload/premium-plugins/real-agent/plugins/buyers/skills/buyer-management/references/buyer-qualification-questions.md DELETED Viewed

@@ -1,16 +0,0 @@
-# Buyer qualification — 5 non‑negotiable questions (Tom Panos)
-Use these to quickly learn whether a buyer is serious and where their friction is.
-1) **How long have you been looking?**
-2) **Have you made any offers on anything?**
-3) **What is the best home you've seen so far?**
-4) **Why didn't you buy that one?**
-5) **If I had a home that was suitable, will you be looking at making an offer?**
-## Notes for Max
-- Ask in a friendly, curious tone.
-- Capture the answers verbatim.
-- If #5 is not a clear "yes", they're browsing. Keep warm, don't over-invest.
-Source: *Tom Panos — Dialogue to Get More Listings* (Estate Agency Mastermind summary)

package/payload/premium-plugins/real-agent/plugins/buyers/skills/buyer-management/references/buyer-qualification.md DELETED Viewed

@@ -1,59 +0,0 @@
-# Buyer Qualification
-## Purpose
-Understand the buyer's situation so the agent can prioritise and serve them effectively. Qualification is not interrogation — it's a conversation that helps you help them.
-## The MAN Framework
-Gather these three dimensions naturally through conversation:
-### Motivation
-- Why are they looking to move?
-- What's their timeline — urgent, browsing, planning ahead?
-- What drew them to this particular property or area?
-- Are they relocating? Upsizing? Downsizing? First-time buyers?
-### Ability
-- Do they have a property to sell? If so, what's its status?
-  - Not yet on market → early stage, may need longer
-  - On market → check how long, any interest
-  - Sold STC → stronger position
-  - No property to sell → chain-free (cash or FTB)
-- Are they buying with cash or mortgage?
-- If mortgage, do they have an Agreement in Principle (AIP)?
-- If no AIP, suggest speaking with a mortgage adviser before viewings
-### Need
-- What type of property are they looking for? (beds, type, garden, parking)
-- Must-haves vs nice-to-haves
-- Any dealbreakers? (location, condition, budget ceiling)
-- How far along are they in their search — just started or seen several?
-## Conversational Flow
-Don't ask all of this in one message. Weave it naturally:
-1. **Start warm** — thank them for their enquiry, show enthusiasm about the property they've asked about
-2. **Open with motivation** — "What's prompted your move?" or "Are you local to the area or looking to relocate?"
-3. **Bridge to ability** — "Do you have a property to sell, or are you in a position to proceed?"
-4. **Understand need** — "What's on your wish list for your next home?"
-## After Qualification
-- **Proceedable** (chain-free, mortgage agreed, or sold STC) → book viewing promptly
-- **Needs steps** (no AIP, property not on market) → suggest next steps gently, keep them warm
-- **Browsing/long-term** → register their requirements, offer to send matching properties
-## Memory
-Save qualification status to `memory/users/{phone}/profile.md`:
-- Position (FTB, selling, sold STC, cash, renting)
-- Mortgage status (AIP yes/no, cash)
-- Requirements (beds, type, area, budget range)
-- Timeline (urgent, 3-6 months, browsing)
-- Properties of interest
-## Tone
-Curious and helpful, never clinical. You're having a chat, not filling in a form. If someone volunteers information, don't re-ask it. If they're clearly serious and ready, don't slow them down with unnecessary questions.

package/payload/premium-plugins/real-agent/plugins/buyers/skills/buyer-management/references/buyer-scripts.md DELETED Viewed

@@ -1,63 +0,0 @@
-# Buyer Scripts & Qualification Dialogue
-*Sources: Tom Panos (Real Estate Gym), Team LANC (Matt Lancashire), Serhant Agent Training Guide*
-## Qualifying Questions (Natural Conversation)
-Use these naturally — not as a checklist. Weave them into conversation.
-**Understanding motivation:**
-- "When buying a home, what's most important for you?"
-- "What's the best home you've seen so far?"
-- "What prevented you from making an offer on that one?"
-- "If there were 3 things you absolutely wouldn't compromise on, what would they be?"
-**Getting to an offer:**
-- "At what price on a contract represents great value for you?"
-- "If you could move into the right home next month, would that work for your timing?"
-**When a buyer is waiting for the market to bottom:**
-> "The only way to know you've bought at the bottom of the market is when the market goes up. But by then it's too late. Because the only way to know the market was at the bottom is when prices have already gone up. Do you want to make a decision based on the market, or based on your life?"
-## Post-Viewing Follow-Up Process
-**Within 2 hours of viewing:**
-1. Send warm check-in message (reference specific property, use first name)
-2. Capture overall impression, interest level, positives, concerns
-3. If interested — offer second viewing or next steps
-4. If not interested — ask what they ARE looking for (refine criteria)
-**10-Day Follow-Up (if no response or "thinking about it"):**
-- Brief, value-led message — share new comparable that just listed, or market insight
-- Never "just checking in" — always lead with something useful
-**Hot Buyer Management:**
-- Maintain a hot buyer list with key criteria
-- When new properties come to market, check against hot buyer criteria within 24 hours
-- Call (don't just text) for strong matches — "I've just seen something that ticks every box you mentioned"
-## Encouraging Offers
-**When a buyer is hesitant:**
-- "What would need to change for you to feel comfortable making an offer?"
-- "Is it the property itself, or the timing?"
-- "If this property sells to someone else this weekend, would you regret not having put an offer forward?"
-**When a buyer lowballs:**
-- Use comparable evidence: "Let me show you what similar properties have actually sold for recently"
-- Frame as collaboration: "Let's find a number that the seller will take seriously, so we don't lose the opportunity to negotiate"
-## Getting Buyers Off the Fence (Serhant)
-- Show them what they think they want (validates their criteria)
-- Show them the WOW listing (exceeds expectations, creates excitement)
-- Show them the consolation prize (makes the WOW listing feel essential)
-- This is about understanding their emotional journey, not manipulation
-## The Flip: Turning Negatives Into Positives
-When a buyer raises an objection about a property:
-1. **List the common objections** you expect (small garden, busy road, dated kitchen)
-2. **Find the silver lining** ("A contained garden is easy to maintain and beautify — you'll spend time enjoying it, not mowing")
-3. **Offer a solution** (share photos of beautiful small gardens, connect with a landscaper)
-Always acknowledge the concern genuinely before flipping it. Never dismiss a buyer's objection.

package/payload/premium-plugins/real-agent/plugins/buyers/skills/buyer-management/references/buyer-working-scripts.md DELETED Viewed

@@ -1,54 +0,0 @@
-# Working With Buyers — Scripts & Scenarios
-*Adapted from Serhant Team Agent Training Guide*
-## Phase 1: Selling Is ASKING
-### Qualify First — Shoppers vs Buyers
-You don't work with shoppers, you work with BUYERS. Determine if they're real:
-**Qualifying Questions:**
-1. "Where do you work?" (financial picture)
-2. "Do you currently own or rent?" (experience level + chain status)
-3. "When are you looking to move by? Is there a specific reason?" (urgency + motivation)
-4. "How long have you been looking? Seen anything you liked?" (stage in journey)
-5. "Have you already been pre-approved / spoken to a mortgage adviser?" (readiness)
-### Never Meet a Buyer for the First Time at a Listing
-Meet them first — in the office, for coffee, on a call. Understand their needs before showing properties.
-### Set Expectations
-List the steps to successfully purchasing a home. Buyers who understand the process make better decisions and don't panic at each stage.
-## Phase 2: Selling Is GUIDING
-### Elimination, Not Selection
-"Buying a home isn't a process of selection — it's a process of elimination. We'll narrow down what works and what doesn't until we find the right one."
-### Ask for Feedback After Every Viewing
-Don't assume silence means disinterest. Start the conversation, get them in the game.
-### Make Offers — Get Off the Fence
-Buyers can look forever without a push. Address the hesitation:
-"It's never a 'bad' time to buy. As long as you're comfortable with the purchase and don't overstretch yourself, you'll be in good shape."
-"I've never had a client who, at completion, said 'I got exactly what I wanted under budget!' — there's always a stretch."
-### Encouraging Offers
-"An offer is JUST a conversation starter. Nothing is final until contracts are exchanged."
-"What do you think the property is worth? What would you pay? ...[X]? Great — why don't we just see how the vendor responds?"
-### Make Them Fall in Love with the PROPERTY, Not the Discount
-Focus on lifestyle, not savings. "Can you see yourself here?" beats "You're getting £10k off."
-## Getting Buyers Off the Fence
-**Longer-Term Outlook:**
-"Will you be there for 5-10 years? If so, waiting for the 'perfect' property is like not taking a holiday because it might rain."
-**The Historical Perspective:**
-"Every buyer thinks it's SO expensive at the time. Then they look back and think they got the best deal ever."
-**The iPhone Analogy (for price objections):**
-If a buyer won't pay because the vendor only paid £X before — "How much did you pay for your iPhone? It costs £84 to make."

package/payload/premium-plugins/real-agent/plugins/buyers/skills/buyer-management/references/feedback-collection.md DELETED Viewed

@@ -1,42 +0,0 @@
-# Feedback Collection
-## Purpose
-Capture honest post-viewing feedback to relay to the vendor and inform the agent's strategy. Good feedback collection is one of the most valuable things an agent does — it tells you whether to chase, adjust, or pivot.
-## Timing
-Reach out within 24 hours of the viewing. Sooner is better — impressions fade.
-## Questions
-Ask conversationally, not as a checklist:
-1. **Overall impression** — "How did you find the viewing? What were your first impressions?"
-2. **Positives** — "What stood out to you? What did you like most?"
-3. **Concerns** — "Were there any reservations or things that gave you pause?"
-4. **Comparison** — "How does it compare to others you've seen?" (if applicable)
-5. **Interest level** — "Is it one you'd like to think about further, or would you like to explore other options?"
-6. **Next steps** — if interested: "Would you like to arrange a second viewing or discuss making an offer?" If not: "No problem at all — shall I keep an eye out for properties that might be a better fit?"
-## Reading Between the Lines
-- **"It was nice but..."** usually means no. Gently probe the "but"
-- **"We need to think about it"** — ask what specifically they're weighing up
-- **"We loved it"** — ask what specifically they loved (the agent uses this when presenting offers)
-- **Silence / no response** — follow up once more after 48 hours, then note as unresponsive
-## Recording Feedback
-Save to `memory/users/{phone}/viewings/YYYY-MM-DD-address-slug.md`:
-- Date of viewing
-- Property address
-- Overall reaction (positive / mixed / negative)
-- Key positives mentioned
-- Concerns raised
-- Interest level (keen / considering / not interested)
-- Next action (second viewing / offer / no further action)
-## Escalation
-If a buyer expresses strong interest or wants to discuss an offer, transition to offer capture immediately. If they raise concerns that could be addressed (price, condition), note these for the agent — they inform vendor feedback conversations.

package/payload/premium-plugins/real-agent/plugins/buyers/skills/buyer-management/references/offer-capture.md DELETED Viewed

@@ -1,38 +0,0 @@
-# Offer Capture
-## Purpose
-Gather all the information the agent needs to present an offer to the vendor professionally. You capture — the agent negotiates.
-## Information to Gather
-1. **The offer amount** — "What figure would you like to offer?"
-2. **How they arrived at it** — "How did you come to that figure?" (This helps the agent understand their thinking and position)
-3. **Their buying position:**
-   - Cash or mortgage?
-   - If mortgage: AIP confirmed? Lender? Deposit amount?
-   - Property to sell? Status? (Under offer, exchanged, no property)
-   - Chain length?
-   - Solicitor instructed?
-4. **What they love about the property** — "What is it about the property that's made you want to make an offer?" (the agent uses this when presenting to the vendor — emotional connection matters)
-5. **Timeline** — when would they ideally like to complete?
-6. **Any conditions** — is the offer subject to survey, sale of their property, or anything else?
-## Critical Rules
-- **Never counter-offer** — you do not negotiate on behalf of the vendor
-- **Never disclose other offers** — not the number, not the amount, not whether any exist
-- **Never hint at what might be acceptable** — no "I think the vendor would want more" or "that's quite low"
-- **Never disclose the vendor's circumstances** — their timeline, motivation, or financial position is confidential
-- **Stay neutral and professional** — "I'll make sure the agent presents this to the seller and they'll be in touch to discuss"
-## After Capture
-1. Save the offer to `memory/users/{phone}/offers/YYYY-MM-DD-address-slug.md`
-2. Include all gathered details
-3. **Escalate to the agent immediately** — offers are time-sensitive
-4. Confirm to the buyer: "Thank you — I've passed all of this to the agent and they'll be in touch once they've spoken with the seller. Is there anything else you'd like me to include?"
-## Multiple Offers
-If another buyer also wants to offer on the same property, capture their details separately. Never mention the other offer. The agent manages the best-and-final process if needed.

package/payload/premium-plugins/real-agent/plugins/buyers/skills/buyer-management/references/viewing-booking.md DELETED Viewed

@@ -1,32 +0,0 @@
-# Viewing Booking
-## Purpose
-Convert a qualified buyer into a confirmed viewing. Make it easy, organised, and professional.
-## Booking Flow
-1. **Confirm the property** — make sure you're both talking about the same one
-2. **Offer specific times** — "The agent has viewings available on Thursday afternoon or Saturday morning — which works better for you?" Two options, not open-ended
-3. **Confirm attendees** — will it be just them, or partner/family too? This helps the agent prepare
-4. **Set expectations** — the agent conducts all viewings personally. They'll walk them through the property and answer any questions on the day
-5. **Confirm details** — repeat the time, date, property address, and their name
-## Important
-- Viewings are arranged on set days where possible to be respectful of the seller's time
-- If the buyer's preferred time clashes, offer the next available slot — don't leave it hanging
-- If the property has high interest, mention this factually ("there's been good interest this week") but never fabricate urgency
-- Always confirm the buyer has been qualified before booking — if not, qualify first
-## After Booking
-- Save the viewing to `memory/users/{phone}/viewings/YYYY-MM-DD-address-slug.md`
-- Include: date, time, property address, buyer name, their position, any notes
-- If shared calendar is available, create the event there too
-## Cancellations and Rescheduling
-- Be understanding — things come up
-- Offer an alternative promptly
-- If a buyer cancels twice without rescheduling, note it in their profile — they may be going cold