@seldonframe/mcp 1.38.5 → 1.40.0

package/package.json

@@ -1,6 +1,8 @@
 {
   "name": "@seldonframe/mcp",
-  "version": "1.38.5",
+  "version": "1.40.0",
+  "description": "MCP server for SeldonFrame — AI-native Business OS platform. v1.40.0: TASTE + CONVERSION + ARCHETYPE SYNTHESIS — the structural ship that closes the gap between SF auto-generated workspaces and hand-tuned designer output. Three forces converge in one commit. (1) AESTHETIC ARCHETYPES (the 'fat skill', inspired by github.com/leonxlnx/taste-skill). NEW src/lib/workspace/aesthetic-archetypes.ts with 7 curated archetypes (editorial-warm / bold-urgency / clinical-trust / cinematic-aspirational / technical-restrained / soft-residential / brutalist), each defining palette + fonts + dials (DESIGN_VARIANCE / MOTION_INTENSITY / VISUAL_DENSITY) + heroVariant + bannedHere tokens + voice (tone / pace / lean-into / avoid words). NOT keyed by vertical — keyed by EMOTIONAL CATEGORY because vertical is too narrow (a custom-restoration roofer has different brand needs than a storm-chaser; both are 'roofing'). NEW classifyArchetype() picks based on (vertical + emergency_service + voice signals + business description keywords). Adding new archetypes = one entry. (2) TASTE-SKILL DISCIPLINE injected into the LLM prompt. enhance-blocks now renders an archetype-specific design brief at the top of every Opus call: voice tone, banned tokens (Inter banned, centered hero banned, 3-equal-card grids banned, AI purple/blue banned, pure black banned), universal taste-skill rules (max 1 accent < 80% sat, transform/opacity-only animation, asymmetric layouts), output discipline (headlines convey value standalone, 'so that' chaining, specific time numbers, effort-reduction subheads). Anti-AI-slop discipline becomes a hard constraint, not a passing instruction. (3) HORMOZI VALUE EQUATION baked into prompt. Above-the-fold gets 80-90% of generation weight per Hormozi: dream outcome in headline, 'so that' principle, time-delay numbers, effort-reduction in subhead, perceived-likelihood-of-success via proof + testimonials, risk-reversal via badges under CTA. NEW hero.tsx renders 4 variants by archetype: cinematic-fullbleed (image as page background, copy overlays), founder-portrait (square portrait right + copy left), split-screen-50-50 (classic 50/50, urgency-friendly), left-aligned-asymmetric (60/40 editorial — the default). NEW ProofTile component above CTA cluster (rating + count + descriptor in compact pill row). NEW RiskReversalBadges row under CTA with license #s, BBB, insured, certifications. (4) FONTS. DEFAULT_ORG_THEME flipped from Inter to Geist. OrgTheme.fontFamily union expanded with Cabinet Grotesk, Satoshi (added Fontshare CDN support to googleFontUrl helper). The taste-skill explicitly bans Inter as the AI-default font; we comply. Each archetype overrides the org theme with its own font pair on workspace creation, so a roofer gets Outfit/Geist, a medspa gets Cabinet Grotesk/Satoshi, a legal firm gets Cabinet Grotesk/Geist. (5) THEME PROPAGATION. After classifying archetype, enhanceLandingForWorkspace UPDATEs organizations.theme with the archetype's primary/secondary/font tokens so PublicThemeProvider cascades the right palette + font on every public surface (landing, booking, intake) automatically. (6) personality_vertical threaded from createFullWorkspace into enhance-blocks so classifier uses the resolved CRMPersonality vertical instead of inferring from soup. SOFT-FAIL on every step. NO new env vars. NO migrations. Backend redeploy required. EXPECTED IMPACT: a fresh roofing workspace renders with Outfit/Geist typography, deep-terracotta + warm-cream palette, left-aligned-asymmetric hero (NOT centered), proof tile above CTA, risk-reversal badges under CTA, taste-skill-disciplined section copy. A fresh medspa renders Cabinet Grotesk/Satoshi, muted gold + cream, cinematic-fullbleed hero. A fresh legal firm renders Cabinet Grotesk/Geist, deep navy + burgundy, restrained left-aligned hero. Same template, same pipeline, FUNDAMENTALLY different visual identities per niche. 9.5+/10 first-shot for the visual surface. Inspired by Trevor Foyer's manual workflow (inspiration → Stitch → design.md → Claude + taste-skill → 21st.dev), automated server-side in ~30s instead of 25min.",
+  "description": "MCP server for SeldonFrame — AI-native Business OS platform. v1.39.0: IMAGERY + ICON QUALITY PASS — five fixes that close the visible gap between SF auto-generated workspaces and a hand-tuned reference like dfwroofingpro.com. Pre-1.39.0, generation quality was at the $10k bar (Hormozi headline + verbatim testimonials + light mode + distinct service icons all rendered correctly in v1.38.5), but the Bluebonnet Roofing test surfaced four image/icon polish bugs: hero showed Austin city skyline instead of a residential roof, project gallery had random-feeling stock photos, the About section showed an empty 'Feature image' placeholder, and the 'What Sets Apart' benefits cards all rendered the same Sparkles icon. v1.39.0 fixes all of them. WHAT SHIPS: (1) HERO QUERY TIGHTENING. enhance-blocks prompt now teaches Claude to generate hero queries that contain a craft-specific physical noun + composition hint and AVOID leading with city names. 'asphalt shingle residential roof close-up' instead of 'austin storm roofing'. Pre-1.39.0 the city-led queries returned downtown skyline shots because Unsplash interpreted 'Austin' as the dominant subject. (2) SCENERY REJECTION in resolveHeroImageUrlForQuery. Defense-in-depth — even with a tightened prompt, an occasional query slips through and returns scenery. v1.39.0 scans the top 15 Unsplash results and skips ones whose description matches /(skyline|cityscape|aerial view of city|downtown|panorama|landscape|sunset over|view from|tourism)/. Falls back to first result if all match (a hero is better than no hero). per_page bumped from 10 → 15 for more rejection alternatives. (3) GALLERY QUERY GUIDANCE. enhance-blocks prompt extended with explicit GOOD vs BAD query examples per vertical (roofing, plumbing, HVAC). Each query now MUST contain a craft-specific physical noun, MUST NOT lead with a city, and MUST vary across the 6 (no repeated nouns). 'roofer installing shingles residential' instead of 'austin roofing'. (4) BENEFITS DYNAMIC ICONS. Pre-1.39.0 benefits.tsx had a 5-entry PascalCase iconByName map ({Sparkles, Star, Rocket, ShieldCheck, CircleCheckBig}) that didn't match the kebab-case names ('shield-check', 'badge-check', 'wrench') the LLM generates per the prompt. Result: every benefit card rendered Sparkles. Same root cause as v1.38.5's services-grid bug, just in a different component we hadn't touched. v1.39.0 extracts the 60+ entry icon map + normalized resolver to NEW components/landing/sections/icon-resolver.ts and refactors BOTH services-grid + benefits to import from it. Adds ~10 more aliases (trust, trusted, insured, licensed, bonded, family, familyowned, local, experience, experienced) so common LLM benefit-icon picks resolve. enhance-blocks prompt also explicitly tells Claude that benefits.icon must be DISTINCT across the 3 cards. (5) ABOUT SECTION CONDITIONAL IMAGE. features.tsx (used as the about-style block by enhance-blocks) now hides the entire image column when no image is set, instead of showing the 'Feature image' placeholder text — which read as broken/template-y on every workspace whose About we filled with body text but no image asset. When image is absent, renders single-column centered with headline + features pills. When image present, renders the original two-column grid (now using raw <img> with referrerPolicy=no-referrer, same pattern as hero + gallery). NO new env vars. NO migrations. Backend redeploy required. EXPECTED IMPACT: re-test of Bluebonnet (or fresh business) renders a real residential-roofing hero photo (close-up of shingles, roofer working, etc.) instead of city scenery; project gallery shows visibly different work-context photos; benefits cards show 3 distinct icons; About section is clean (no empty placeholder). 9.5/10 first-shot for the visual surface. Booking-form personalization (asking address/phone/issue per vertical) remains for v1.39.x.",
   "description": "MCP server for SeldonFrame — AI-native Business OS platform. v1.38.5: THREE PRESENTATION-LAYER FIXES discovered after the Texas MAGA Roofing test (v1.38.4 generation quality was at the $10k bar — Hormozi headline + per-business gallery + verbatim testimonials all rendered correctly — but three smaller bugs kept the page from being light-mode + properly iconed). (1) DEFAULT_ORG_THEME.mode flipped from 'dark' to 'light'. Customer-facing public surfaces (workspace landing, booking page, intake form) should be light by industry convention; operators who want a dark public brand can opt-in via theme settings. The 95% case wants light. Existing workspaces unaffected (their theme is already stored in organizations.theme); only newly-created workspaces inherit the new default. (2) /s/[orgSlug]/[...slug]/page.tsx now applies the same light-mode override v1.38.4 added to /l/ and /book/. proxy.ts rewrites the workspace subdomain root '/' to '/s/[slug]/[defaultLandingSlug]' — NOT /l/ as v1.38.4 assumed. So v1.38.4's landing-page light-mode fix never reached the workspace home; the page rendered against whatever theme.mode was stored. v1.38.5 adds publicTheme = {...theme, mode:'light'} + className='light' wrapper to /s/ so the workspace home is now light by default for both new (light by default per fix 1) and old (already-stored-as-dark) workspaces. (3) PER-SERVICE ICONS — services-grid was rendering <Sparkles> on every card even after v1.38.4 added the dynamic icon resolver, because the enhance-blocks prompt didn't ask Claude for an `icon` field per service AND payloadToSections didn't pass icon through. v1.38.5 adds (a) `icon` to the servicesGrid.services[] schema in the prompt, (b) a 'Per-service icons' instruction block teaching Claude which lucide names + vertical-aliases to pick (storm→cloud-rain-wind, shingle→home, gutter→droplets, drain→droplets, heater→zap, ductwork→home, treatment→leaf, etc.), and (c) icon propagation in payloadToSections.servicesGrid. Extended the ICON_MAP in services-grid.tsx with 24 more vertical aliases (roofing: shingle/metal/gutter/tarp/hail/roof; plumbing: drain/leak/heater/pipe/water; hvac: cooling/ac/heating/furnace/ductwork/duct/thermostat/hvac; spa: treatment/facial/massage/laser; auto: vehicle/van/fleet) so any LLM-generated icon name resolves to a sensible visual. NO new env vars. NO migrations. Backend redeploy required. EXPECTED IMPACT: Texas MAGA Roofing re-test (or fresh workspace) renders LIGHT MODE landing page + LIGHT MODE booking calendar + DISTINCT icons across the 7 service cards. 9.5/10 first-shot for the visual surface. Booking-form personalization (asking address/phone/issue per vertical) remains for v1.39.0.",
   "description": "MCP server for SeldonFrame — AI-native Business OS platform. v1.38.4: VISUAL-POLISH BUNDLE — fixes the four issues that kept Hill Mountain Roofing from being 10/10. Generation quality was already at the $10k bar (Hormozi headline + per-business gallery + verbatim testimonials all rendered correctly in v1.38.3); this ship fixes the presentation layer. (1) LIGHT-MODE-BY-DEFAULT for customer-facing surfaces. The pre-1.38.4 PublicThemeProvider only set --sf-* CSS variables; layout components increasingly use Tailwind utility classes (bg-card, text-foreground, bg-muted/15) which resolve to --card / --foreground / --muted-foreground controlled GLOBALLY by the .dark class on <html>. So flipping our theme.mode = 'light' updated --sf-bg to white but bg-card stayed dark, leaving half the page rendered against the global dark cascade. v1.38.4 adds a className='light' wrapper on /l/[orgSlug]/[slug]/page.tsx + book/[orgSlug]/[bookingSlug]/page.tsx to locally disable the global .dark cascade, AND extends themeToCSS to also set the shadcn-convention vars (--background, --foreground, --card, --card-foreground, --muted, --muted-foreground, --border, --input, --ring, --popover, --popover-foreground, --accent, --accent-foreground, --primary, --primary-foreground, --secondary, --secondary-foreground, --destructive, --destructive-foreground) so Tailwind utilities resolve to our intended palette. Two layers of defense — both required because Tailwind v4's :where() selectors otherwise win against inline-styled vars. Same fix kills booking page dark mode (the v1.36.3 bug we'd been failing to root-cause). (2) HERO IMAGE NOW RENDERS. Pre-1.38.4 hero.tsx used next/image, which silently fails when the source domain isn't in next.config.js images.remotePatterns. Hill Mountain Roofing's hero showed alt-text instead of the Unsplash photo because images.unsplash.com wasn't allowlisted. v1.38.4 (a) switches hero to raw <img> with referrerPolicy='no-referrer' + loading='eager' (same pattern project-gallery.tsx already used), AND (b) adds images.remotePatterns for images.unsplash.com / source.unsplash.com / *.public.blob.vercel-storage.com / *.app.seldonframe.com as defense-in-depth for any future next/image usage. (3) DYNAMIC SERVICE ICONS. Pre-1.38.4 services-grid.tsx hardcoded <Sparkles> on every card — even when the LLM generated distinct icon names per service, the component ignored them. v1.38.4 adds a 35-entry name→lucide-component ICON_MAP plus aliases (storm→CloudRainWind, repair→Wrench, install→Hammer, emergency→Zap, warranty→BadgeCheck, etc.) and a normalized-lookup resolver that handles 'BadgeCheck' / 'badge-check' / 'badge_check' equivalently. Each service card now picks its own icon based on the LLM's icon string. Falls back to <Sparkles> on unknown names so a stale icon string never breaks the render. (4) Defense-in-depth on PublicThemeProvider already covered above. NO new env vars. NO migrations. Backend redeploy required. EXPECTED IMPACT: Hill Mountain Roofing test reproduced with v1.38.4 should render light-mode landing + booking, real Unsplash hero photo in the right column, distinct icons across the 7 service cards, and a clearly-light booking calendar where future dates are visually distinguishable from past dates. 9.5/10 first-shot. Remaining gap to 10/10 = operator-supplied logo + real photos.",
   "description": "MCP server for SeldonFrame — AI-native Business OS platform. v1.38.3 (bundles 1.38.1 + 1.38.2 + 1.38.3): three quality-bar blocks shipped together. (1.38.1) NEW projectGallery block — masonry grid of 6 stock photos auto-fetched per service via Unsplash from queries Claude generates inside enhance-blocks. Closes the 'feels populated' gap that's the single biggest visible difference between a generic SF workspace and a real-business landing page. NEW src/components/landing/sections/project-gallery.tsx (responsive 2/3/4 col, hover-lift + zoom interaction, optional caption-on-hover, optional bottom CTA). NEW src/lib/crm/personality-images.ts → resolveGalleryImageUrlsForQueries() helper — square 800x800 thumbs via Unsplash API (when UNSPLASH_ACCESS_KEY env set) with deduplication across queries (avoids 6 services all returning the same generic photo) + keyless source.unsplash.com fallback with per-query random seed. enhance-blocks prompt extended with 'Gallery queries' section that teaches Claude to generate 6 vertical-specific Unsplash queries (e.g. for HVAC: 'hvac technician outdoor unit', 'ductwork installation', 'thermostat residential' — bias toward queries that return DIFFERENT photos). projectGallery section emitted between process and serviceArea in the LandingPageSection[] order. (1.38.2) NEW stickyMobileCTA block — fixed bottom-of-screen Call/Book bar, MOBILE ONLY (md:hidden via Tailwind). Industry-standard for trades sites with measured 2-3x mobile booking lift (Cal.com, Calendly, Mr. Rooter, Roto-Rooter precedent). NEW src/components/landing/sections/sticky-mobile-cta.tsx — 56px tap targets meet WCAG 2.5.5, position:fixed bottom:0 with safe-area-inset-bottom for iOS home indicator clearance, z-index:50 sits above sections but below modals, gradient-divided two-column layout (Call left, Book right). Auto-emitted as the LAST section whenever input.phone is set; position:fixed pulls it out of document flow at runtime so visual order doesn't matter. (1.38.3) Testimonial synthesis from Maps reviews paste. NEW testimonials field on create_workspace_from_google_paste MCP tool input — array of { quote, name?, role?, company?, rating? } extracted VERBATIM by Claude Code from review excerpts in the paste. NEVER fabricated — when paste has no review text, the testimonials field is OMITTED entirely (better empty than fake). Backend route /api/v1/workspaces/create-full reads + shape-validates via readTestimonials() (cap 8 entries, quote ≤800 chars, drop entries missing quote). Plumbed through CreateFullWorkspaceInput → createAnonymousWorkspace → soul + enhance-blocks. enhance-blocks emits a testimonials LandingPageSection (between serviceArea and faq in the order) when input.testimonials.length > 0. Quotes pass through verbatim — the LLM does not get to rewrite them. ALL THREE block types registered in src/components/landing/block-registry.tsx with grapesContent placeholders for the visual editor. EMAIL-FIRST GUARDRAIL UNCHANGED. NO new env vars (uses existing UNSPLASH_ACCESS_KEY for higher-quality gallery photos when set; works keylessly via source.unsplash.com when not). NO migrations. Backend redeploy required. EXPECTED IMPACT: every fresh paste-driven workspace now ships with 11 sections including a populated photo gallery + mobile sticky CTA + real testimonials when paste has reviews. Visible-quality bar: 9/10 first-shot. Remaining gap to 10/10 = operator-supplied logos + real photos.",

package/src/welcome.js

@@ -8,7 +8,7 @@
 // stripped. `create_full_workspace` is the only workspace-creation
 // path mentioned anywhere in this briefing.
 
-export const VERSION = "1.38.5";
+export const VERSION = "1.40.0";
 
 export const WELCOME_MARKDOWN = `# SeldonFrame — create a real Business OS in one conversation
 
@@ -433,4 +433,4 @@ admin dashboard. Pre-fills their email automatically.
 <https://seldonframe.com> · **Discord:** <https://discord.gg/sbVUu976NW>
 `;
 
-export const FIRST_CALL_BANNER = `🚀 SeldonFrame v1.38.5 is connected. STEP ZERO: for any workspace task call get_workspace_state({workspace_id}) FIRST — returns workspace identity + integrations status + agents with inline health stats + counts + tailored next_steps in ONE round-trip. Replaces 4-6 progressive discovery calls. ANTI-PATTERNS: don't ls/cat/read .env (SF is hosted, not local files); don't check node/npm versions (irrelevant); don't ask 'is Anthropic key configured?' (state response tells you); don't create a duplicate agent (state response shows existing ones — use update_website_chatbot instead of build_website_chatbot when one exists). Token-budget concept removed in v1.27.9 — ignore stale references. CAPABILITY MAP — pick the right primitive BEFORE exploring tools: (a) "build me a website" → WORKSPACE → create_workspace_v2 + block tools. (b) "add a chatbot to my website / landing page" → AGENT (web chat) → build_website_chatbot (v1.28+ skill bundle: configure_llm + create_agent + publish-test in 1 call; auto-detects ANTHROPIC_API_KEY from env). Drop to primitives (configure_llm_provider + create_agent + publish_agent) only for custom flows. CRITICAL ANTI-PATTERN: chat widgets are NOT blocks. Don't search list_blocks for chat — chat agents are a separate primitive (v1.26+). (c) "auto-reply to inbound SMS/email" → CONVERSATION → send_conversation_turn (one-shot Soul-aware reply, not a website widget). (d) "add hero/services/faq/cta section" → BLOCK → get_block_skill + persist_block. (e) "send campaign email/sms" → MESSAGING. (f) CRM ops → list_contacts/create_deal/etc. CHATBOT CANONICAL FLOW (v1.28+ — 1 call instead of 5): build_website_chatbot({workspace_id, name, faq, pricing_facts, greeting}) → wraps configure_llm + create_agent + publish-test in one call, auto-detects ANTHROPIC_API_KEY from env. Then: operator sandbox-tests at /agents/[id]/test → publish_agent({status:"live"}) auto-runs 8-scenario eval gate (≥87.5% pass required). Observability tools after publish: list_agents, tail_agent_conversations, get_agent_conversation, get_agent_metrics, run_agent_evals, replay_conversation. Dashboard surfaces /agents, /agents/[id]/test, /agents/[id]/settings, /agents/[id]/evals, /agents/[id]/conversations let operators iterate without leaving the browser. WORKSPACE FLOW (legacy reference): create_workspace_v2 → IN PARALLEL for all 7 recommended_blocks (hero, services, about, faq, cta, booking, intake): get_block_skill + persist_block → complete_workspace_v2 → finalize_workspace({workspace_id, email}). Run blocks in PARALLEL (Promise.all) — sequential takes 60+ seconds. v1.10+ CUSTOMIZE: regenerate_block, upload_workspace_image (image_url preferred over base64). v1.11+ STRUCTURAL: get_landing_structure, move_section, delete_section. v1.12+ COMPOSITES: add_composite_section / update_composite_section — manifest ANY block from 12 low-level primitives. Skipping finalize_workspace leaves the operator with no admin login. Every URL is real. NEVER create local files. v1.34+ UI POLISH (smart defaults + optional levers): every published page ships with motion baked in (RevealOnScroll on sections, Stagger on grid blocks, HoverLift on CTAs) — no operator action required. For operators who want to tune intensity: apply_motion_preset({preset: "minimal"|"subtle"|"balanced"|"editorial"}). For operators bringing their own design system: apply_design_md({design_md_content}) accepts the Google Labs DESIGN.md format; import_claude_design_handoff({bundle}) accepts Claude Design's handoff bundle. All three tools are OPTIONAL — surface them only when the operator's vibe asks for it ("make it feel premium", "I have a brand kit", "I just exported from Claude Design"). Never push these on a user who just wants a working site. v1.36+ PROMPT-FATIGUE GUIDANCE: workspace creation typically fires 8–18 MCP tool calls (workspace + blocks + agent + booking + intake + landing). Claude Code prompts on each by default and create_landing_page's Puck schema is verbose JSON the operator should NOT read. DO TWO THINGS to avoid spamming: (1) RECOMMEND THE OPERATOR pick option 2 ('Yes, and do not ask again for seldonframe – <tool>') the FIRST time create_landing_page / persist_block / build_website_chatbot fire — Claude Code caches per-tool autoapprove for the project, the rest of workspace creation runs without interrupting them. Mention this proactively before the flow starts. (2) BUNDLE TOOL CALLS in parallel via Promise.all — never call get_block_skill + persist_block sequentially for 7 blocks; fire them all at once. v1.36+ LANDING-PAGE COMPOSITION FOR LOCAL-SERVICE BUSINESSES: for trades/service businesses (plumbing, HVAC, locksmith, electrician, roofing, towing, dental, salon, mobile mechanic), default to a 10-section composition: navbar → hero (branded gradient empty-state when no photo) → emergencyStrip (sticky brand-colored banner with phone) → trust strip via the Grid block → servicesGrid (per-service cards with price + duration + Book CTA — replaces the SaaS-style pricing block) → benefits (3 differentiators) → process (3-step what-happens-after-booking) → serviceArea (chip cloud of cities/neighborhoods) → testimonials (5+ quotes — placeholder OK pre-launch) → faq → cta → footer. The Pricing block belongs to TIER-based businesses (SaaS, coaches, gyms) NOT per-service businesses — substitute servicesGrid. v1.36.0 added the servicesGrid, emergencyStrip, serviceArea block types — use them when persisting landing pages for trades verticals. The hero block ships a branded-gradient empty state when heroImage is missing; if the operator does not provide a photo, suggest a stock-photo prompt ('your tech truck on a job, sunset shot in Phoenix') so they can drop one in via /landing → Edit later. v1.37.0 GOOGLE MAPS PASTE → WORKSPACE: when the operator pastes a Google Maps business listing (Top Plumbing Experts, ABC Plumbing of San Antonio, etc.), use create_workspace_from_google_paste — NOT create_full_workspace. Same backend pipeline + same finalize_workspace follow-up; the paste-tool's docstring documents the extraction rules (name → bold title, phone → phone-icon row, address → location-pin line, services → categories chip row + 'Services' section deduped, rating + count → '4.7 ★ (950)' element, weekly_hours → 'Monday: 9 AM-5 PM, Tuesday: closed' parsed into canonical {monday:{enabled:true,start:'09:00',end:'17:00'},...} shape). The weekly_hours field flows DIRECTLY into the booking template's metadata.availability, so the operator's actual hours appear on the public /book page on first GET — no separate configure_booking call. 'Open 24 hours' → start:'00:00', end:'23:59'. 'Closed' day → enabled:false. Wrong key shape (e.g. 'mon' instead of 'monday') is silently dropped by the backend and falls back to Mon-Fri 9-5 defaults. NO Google Places API key required — the paste IS the source of truth. v1.36.4 paired fix: the booking page's normalizeAvailability now accepts both 3-letter and full-name day keys, so any legacy rows already in the DB also hydrate correctly. v1.38.3 ADDITIONAL QUALITY BLOCKS: (a) projectGallery — 6-photo masonry of stock photos auto-fetched per service via Unsplash from queries Claude generates inside enhance-blocks; closes the "feels populated" gap that's the single biggest visible difference between a generic SF workspace and a real-business landing page. (b) stickyMobileCTA — fixed bottom-of-screen Call/Book bar, MOBILE ONLY (md:hidden), industry-standard for trades sites with 2-3x mobile booking lift; auto-included whenever a phone is set. (c) testimonial synthesis from Maps paste — when the operator pastes a Google Maps listing that contains review excerpts, Claude Code extracts them VERBATIM into a 'testimonials' field on create_workspace_from_google_paste; backend renders them as-is. NEVER fabricated — if the paste has no review text, the testimonials block is OMITTED from the page entirely (better empty than fake). The testimonials field in the MCP tool input is OPTIONAL — Claude must omit it when the paste doesn't contain real review text. v1.38.0 ATOMIC HORMOZI-QUALITY OUTPUT: every workspace produced by create_full_workspace OR create_workspace_from_google_paste now ships with Hormozi value-equation hero copy + per-business Unsplash photos + scroll-triggered motion baked in — atomically, no follow-up tool calls, no operator action. Pre-1.38.0 the atomic create produced canned 'Welcome to X' copy from personality content templates; only workspaces where Claude Code did the BLOCK-AS-SKILL flow afterward (get_block_skill + persist_block per block) got the rich output. Tirionforge HVAC happened to look great because of that follow-up; atlantic-plumbing didn't get it. v1.38.0 closes the gap by adding Step 12.7 inside the orchestrator: ONE Claude Opus 4.7 call generates hero + servicesGrid + about + benefits + process + faq + cta from src/blocks/*/SKILL.md (the exact same fat skill files Claude Code reads via get_block_skill — single source of truth, no duplication). Output writes to landingPages.sections (LandingPageSection[]), contentHtml/Css get NULLED, route /l/[orgSlug]/[slug] falls through to <PageRenderer> which auto-wraps below-fold sections in <RevealOnScroll>. Hormozi copy + per-business Unsplash + motion all light up at once. EMAIL-FIRST GUARDRAIL UNCHANGED: create_full_workspace + create_workspace_from_google_paste both still RETURN BEFORE THE EMAIL DANCE — operator can't see URLs until they reply with email, finalize_workspace mints the magic admin link + sends the welcome email via Resend. BYOK pass-through: getAIClient checks organizations.integrations.anthropic.apiKey first, falls back to platform ANTHROPIC_API_KEY env. Cost ~$0.10 per workspace, irrelevant since the operator typically supplies their own key. SOFT-FAIL: any error in Step 12.7 leaves the workspace valid (canned-copy Path A intact); never blocks creation. EXPECTED IMPACT: every fresh workspace looks $10k-tier first-shot, no "create workspace then enhance blocks" two-step dance. ws1-webhook-pricing-fixes branch ships this; redeploy required.`;
+export const FIRST_CALL_BANNER = `🚀 SeldonFrame v1.40.0 is connected. STEP ZERO: for any workspace task call get_workspace_state({workspace_id}) FIRST — returns workspace identity + integrations status + agents with inline health stats + counts + tailored next_steps in ONE round-trip. Replaces 4-6 progressive discovery calls. ANTI-PATTERNS: don't ls/cat/read .env (SF is hosted, not local files); don't check node/npm versions (irrelevant); don't ask 'is Anthropic key configured?' (state response tells you); don't create a duplicate agent (state response shows existing ones — use update_website_chatbot instead of build_website_chatbot when one exists). Token-budget concept removed in v1.27.9 — ignore stale references. CAPABILITY MAP — pick the right primitive BEFORE exploring tools: (a) "build me a website" → WORKSPACE → create_workspace_v2 + block tools. (b) "add a chatbot to my website / landing page" → AGENT (web chat) → build_website_chatbot (v1.28+ skill bundle: configure_llm + create_agent + publish-test in 1 call; auto-detects ANTHROPIC_API_KEY from env). Drop to primitives (configure_llm_provider + create_agent + publish_agent) only for custom flows. CRITICAL ANTI-PATTERN: chat widgets are NOT blocks. Don't search list_blocks for chat — chat agents are a separate primitive (v1.26+). (c) "auto-reply to inbound SMS/email" → CONVERSATION → send_conversation_turn (one-shot Soul-aware reply, not a website widget). (d) "add hero/services/faq/cta section" → BLOCK → get_block_skill + persist_block. (e) "send campaign email/sms" → MESSAGING. (f) CRM ops → list_contacts/create_deal/etc. CHATBOT CANONICAL FLOW (v1.28+ — 1 call instead of 5): build_website_chatbot({workspace_id, name, faq, pricing_facts, greeting}) → wraps configure_llm + create_agent + publish-test in one call, auto-detects ANTHROPIC_API_KEY from env. Then: operator sandbox-tests at /agents/[id]/test → publish_agent({status:"live"}) auto-runs 8-scenario eval gate (≥87.5% pass required). Observability tools after publish: list_agents, tail_agent_conversations, get_agent_conversation, get_agent_metrics, run_agent_evals, replay_conversation. Dashboard surfaces /agents, /agents/[id]/test, /agents/[id]/settings, /agents/[id]/evals, /agents/[id]/conversations let operators iterate without leaving the browser. WORKSPACE FLOW (legacy reference): create_workspace_v2 → IN PARALLEL for all 7 recommended_blocks (hero, services, about, faq, cta, booking, intake): get_block_skill + persist_block → complete_workspace_v2 → finalize_workspace({workspace_id, email}). Run blocks in PARALLEL (Promise.all) — sequential takes 60+ seconds. v1.10+ CUSTOMIZE: regenerate_block, upload_workspace_image (image_url preferred over base64). v1.11+ STRUCTURAL: get_landing_structure, move_section, delete_section. v1.12+ COMPOSITES: add_composite_section / update_composite_section — manifest ANY block from 12 low-level primitives. Skipping finalize_workspace leaves the operator with no admin login. Every URL is real. NEVER create local files. v1.34+ UI POLISH (smart defaults + optional levers): every published page ships with motion baked in (RevealOnScroll on sections, Stagger on grid blocks, HoverLift on CTAs) — no operator action required. For operators who want to tune intensity: apply_motion_preset({preset: "minimal"|"subtle"|"balanced"|"editorial"}). For operators bringing their own design system: apply_design_md({design_md_content}) accepts the Google Labs DESIGN.md format; import_claude_design_handoff({bundle}) accepts Claude Design's handoff bundle. All three tools are OPTIONAL — surface them only when the operator's vibe asks for it ("make it feel premium", "I have a brand kit", "I just exported from Claude Design"). Never push these on a user who just wants a working site. v1.36+ PROMPT-FATIGUE GUIDANCE: workspace creation typically fires 8–18 MCP tool calls (workspace + blocks + agent + booking + intake + landing). Claude Code prompts on each by default and create_landing_page's Puck schema is verbose JSON the operator should NOT read. DO TWO THINGS to avoid spamming: (1) RECOMMEND THE OPERATOR pick option 2 ('Yes, and do not ask again for seldonframe – <tool>') the FIRST time create_landing_page / persist_block / build_website_chatbot fire — Claude Code caches per-tool autoapprove for the project, the rest of workspace creation runs without interrupting them. Mention this proactively before the flow starts. (2) BUNDLE TOOL CALLS in parallel via Promise.all — never call get_block_skill + persist_block sequentially for 7 blocks; fire them all at once. v1.36+ LANDING-PAGE COMPOSITION FOR LOCAL-SERVICE BUSINESSES: for trades/service businesses (plumbing, HVAC, locksmith, electrician, roofing, towing, dental, salon, mobile mechanic), default to a 10-section composition: navbar → hero (branded gradient empty-state when no photo) → emergencyStrip (sticky brand-colored banner with phone) → trust strip via the Grid block → servicesGrid (per-service cards with price + duration + Book CTA — replaces the SaaS-style pricing block) → benefits (3 differentiators) → process (3-step what-happens-after-booking) → serviceArea (chip cloud of cities/neighborhoods) → testimonials (5+ quotes — placeholder OK pre-launch) → faq → cta → footer. The Pricing block belongs to TIER-based businesses (SaaS, coaches, gyms) NOT per-service businesses — substitute servicesGrid. v1.36.0 added the servicesGrid, emergencyStrip, serviceArea block types — use them when persisting landing pages for trades verticals. The hero block ships a branded-gradient empty state when heroImage is missing; if the operator does not provide a photo, suggest a stock-photo prompt ('your tech truck on a job, sunset shot in Phoenix') so they can drop one in via /landing → Edit later. v1.37.0 GOOGLE MAPS PASTE → WORKSPACE: when the operator pastes a Google Maps business listing (Top Plumbing Experts, ABC Plumbing of San Antonio, etc.), use create_workspace_from_google_paste — NOT create_full_workspace. Same backend pipeline + same finalize_workspace follow-up; the paste-tool's docstring documents the extraction rules (name → bold title, phone → phone-icon row, address → location-pin line, services → categories chip row + 'Services' section deduped, rating + count → '4.7 ★ (950)' element, weekly_hours → 'Monday: 9 AM-5 PM, Tuesday: closed' parsed into canonical {monday:{enabled:true,start:'09:00',end:'17:00'},...} shape). The weekly_hours field flows DIRECTLY into the booking template's metadata.availability, so the operator's actual hours appear on the public /book page on first GET — no separate configure_booking call. 'Open 24 hours' → start:'00:00', end:'23:59'. 'Closed' day → enabled:false. Wrong key shape (e.g. 'mon' instead of 'monday') is silently dropped by the backend and falls back to Mon-Fri 9-5 defaults. NO Google Places API key required — the paste IS the source of truth. v1.36.4 paired fix: the booking page's normalizeAvailability now accepts both 3-letter and full-name day keys, so any legacy rows already in the DB also hydrate correctly. v1.38.3 ADDITIONAL QUALITY BLOCKS: (a) projectGallery — 6-photo masonry of stock photos auto-fetched per service via Unsplash from queries Claude generates inside enhance-blocks; closes the "feels populated" gap that's the single biggest visible difference between a generic SF workspace and a real-business landing page. (b) stickyMobileCTA — fixed bottom-of-screen Call/Book bar, MOBILE ONLY (md:hidden), industry-standard for trades sites with 2-3x mobile booking lift; auto-included whenever a phone is set. (c) testimonial synthesis from Maps paste — when the operator pastes a Google Maps listing that contains review excerpts, Claude Code extracts them VERBATIM into a 'testimonials' field on create_workspace_from_google_paste; backend renders them as-is. NEVER fabricated — if the paste has no review text, the testimonials block is OMITTED from the page entirely (better empty than fake). The testimonials field in the MCP tool input is OPTIONAL — Claude must omit it when the paste doesn't contain real review text. v1.38.0 ATOMIC HORMOZI-QUALITY OUTPUT: every workspace produced by create_full_workspace OR create_workspace_from_google_paste now ships with Hormozi value-equation hero copy + per-business Unsplash photos + scroll-triggered motion baked in — atomically, no follow-up tool calls, no operator action. Pre-1.38.0 the atomic create produced canned 'Welcome to X' copy from personality content templates; only workspaces where Claude Code did the BLOCK-AS-SKILL flow afterward (get_block_skill + persist_block per block) got the rich output. Tirionforge HVAC happened to look great because of that follow-up; atlantic-plumbing didn't get it. v1.38.0 closes the gap by adding Step 12.7 inside the orchestrator: ONE Claude Opus 4.7 call generates hero + servicesGrid + about + benefits + process + faq + cta from src/blocks/*/SKILL.md (the exact same fat skill files Claude Code reads via get_block_skill — single source of truth, no duplication). Output writes to landingPages.sections (LandingPageSection[]), contentHtml/Css get NULLED, route /l/[orgSlug]/[slug] falls through to <PageRenderer> which auto-wraps below-fold sections in <RevealOnScroll>. Hormozi copy + per-business Unsplash + motion all light up at once. EMAIL-FIRST GUARDRAIL UNCHANGED: create_full_workspace + create_workspace_from_google_paste both still RETURN BEFORE THE EMAIL DANCE — operator can't see URLs until they reply with email, finalize_workspace mints the magic admin link + sends the welcome email via Resend. BYOK pass-through: getAIClient checks organizations.integrations.anthropic.apiKey first, falls back to platform ANTHROPIC_API_KEY env. Cost ~$0.10 per workspace, irrelevant since the operator typically supplies their own key. SOFT-FAIL: any error in Step 12.7 leaves the workspace valid (canned-copy Path A intact); never blocks creation. EXPECTED IMPACT: every fresh workspace looks $10k-tier first-shot, no "create workspace then enhance blocks" two-step dance. ws1-webhook-pricing-fixes branch ships this; redeploy required.`;