@kennethsolomon/shipkit 3.14.0 → 3.15.1

package/skills/sk:website/references/handoff-template.md

@@ -0,0 +1,261 @@
+# Handoff Template
+
+Use this to generate the 3 client deliverable files after the site is built. Populate using real project details — replace all `[PLACEHOLDER]` values.
+
+---
+
+## HANDOFF.md template
+
+```markdown
+# [Business Name] — Website Handoff
+
+Built with Next.js + Tailwind CSS. Hosted on [Vercel/Netlify].
+
+---
+
+## What was built
+
+| Page | URL | Purpose |
+|---|---|---|
+| Home | `/` | Main landing + primary CTA |
+| About | `/about` | Brand story + trust signals |
+| [Services/Menu] | `/[path]` | [Purpose] |
+| Contact | `/contact` | Inquiry form + location |
+| [Additional pages] | | |
+
+**Features included:**
+- [ ] WhatsApp floating button — wired to [phone number / ⚠️ REPLACE: see below]
+- [ ] Contact form with spam protection
+- [ ] SEO metadata on all pages
+- [ ] Sitemap + robots.txt
+- [ ] [Other features]
+
+---
+
+## What still needs replacing
+
+Before going live, update these:
+
+| Item | File | What to change |
+|---|---|---|
+| WhatsApp number | `app/layout.tsx` line ~[N] | Replace `+[PHONE]` with your WhatsApp number |
+| Hero photo | `public/images/hero.jpg` | Replace with your actual photo |
+| Google Analytics ID | `.env.local` | Add `NEXT_PUBLIC_GA_ID=G-XXXXXXXXXX` |
+| [Other placeholder] | [file] | [instruction] |
+
+---
+
+## Editing content
+
+Most content lives in one file: `content/site.ts`
+
+**To change your business name or tagline:**
+Open `content/site.ts`, find `name:` and `tagline:` near the top.
+
+**To change opening hours:**
+Open `content/site.ts`, find `hours:` and update the values.
+
+**To change services/menu items:**
+Open `content/site.ts`, find `services:` (or `menu:`) and edit the list.
+
+**To change contact info (phone, email, address):**
+Open `content/site.ts`, find `contact:` and update.
+
+**To change social media links:**
+Open `content/site.ts`, find `social:` and update the URLs.
+
+---
+
+## Need help?
+
+For technical changes beyond content editing, contact your developer or post in the project repo.
+
+---
+
+## Developer notes
+
+- Stack: Next.js [version] + Tailwind CSS
+- Node version: 18+
+- Deploy: Vercel (see DEPLOY.md)
+- Local dev: `npm install && npm run dev`
+```
+
+---
+
+## DEPLOY.md template
+
+```markdown
+# Deploying [Business Name] Website
+
+Step-by-step guide to go live. Total time: ~10 minutes.
+
+---
+
+## Option 1: Vercel (recommended — free tier available)
+
+### One-click deploy
+
+1. Push the project to a GitHub repository (create one at github.com if needed)
+2. Go to vercel.com and sign in with GitHub
+3. Click "Add New Project" → select your repository
+4. Set environment variables (see below)
+5. Click "Deploy"
+6. Your site is live at `[project].vercel.app`
+
+### Custom domain (recommended)
+
+1. In Vercel dashboard → your project → Settings → Domains
+2. Add your domain (e.g., `cornerbrew.ph`)
+3. Follow the DNS instructions (add CNAME or A record in your domain registrar)
+4. Takes 5–30 minutes to propagate
+
+### Via CLI
+
+```bash
+npm install -g vercel
+vercel login
+vercel --prod
+```
+
+---
+
+## Option 2: Netlify (alternative)
+
+1. Go to netlify.com → "Add new site" → "Import from Git"
+2. Connect GitHub and select the repository
+3. Build command: `npm run build`
+4. Publish directory: `.next`
+5. Set environment variables
+6. Deploy
+
+---
+
+## Environment variables
+
+Set these in Vercel dashboard → Settings → Environment Variables (or in `.env.local` for local development):
+
+| Variable | Required | Description | Example |
+|---|---|---|---|
+| `NEXT_PUBLIC_SITE_URL` | Yes | Your full site URL (no trailing slash) | `https://cornerbrew.ph` |
+| `NEXT_PUBLIC_GA_ID` | Optional | Google Analytics 4 Measurement ID | `G-XXXXXXXXXX` |
+| `NEXT_PUBLIC_PLAUSIBLE_DOMAIN` | Optional | Plausible domain (alternative to GA4) | `cornerbrew.ph` |
+| `CONTACT_EMAIL` | If using contact form | Email to receive form submissions | `hello@cornerbrew.ph` |
+| `RESEND_API_KEY` | If using Resend | API key for email sending | `re_xxxxxxxxx` |
+
+---
+
+## Estimated monthly costs
+
+| Service | Cost | Notes |
+|---|---|---|
+| Vercel hosting | Free | Hobby plan — sufficient for most small business sites |
+| Domain name | ~$12–20/year | Buy from Namecheap, GoDaddy, or Cloudflare Registrar |
+| Google Analytics | Free | Optional — Plausible is $9/mo for privacy-friendly alternative |
+| Custom email | ~$6/mo | Google Workspace or Zoho for @yourdomain.com email |
+| **Total** | ~$18–26/year minimum | Domain + free hosting |
+
+---
+
+## After going live
+
+- [ ] Test all pages on mobile and desktop
+- [ ] Test the contact form by submitting it yourself
+- [ ] Test the WhatsApp button
+- [ ] Submit sitemap to Google Search Console: `yourdomain.com/sitemap.xml`
+- [ ] Set up Google My Business if not already done (helps local SEO)
+```
+
+---
+
+## CONTENT-GUIDE.md template
+
+```markdown
+# Content Editing Guide — [Business Name]
+
+This guide is for updating your website content without a developer.
+
+---
+
+## Where content lives
+
+Most of your site content is in one file:
+
+**`content/site.ts`** — open this file to edit most things
+
+---
+
+## Editing your content
+
+### Business name and tagline
+File: `content/site.ts`
+```
+name: "[Your Business Name]",
+tagline: "[Your Tagline]",
+```
+Change the text inside the quotes.
+
+### Contact details
+File: `content/site.ts`
+```
+contact: {
+  phone: "[Your Phone]",
+  email: "[Your Email]",
+  address: "[Your Address]",
+}
+```
+
+### Opening hours
+File: `content/site.ts`
+```
+hours: [
+  { day: "Monday–Friday", time: "8:00 AM – 6:00 PM" },
+  { day: "Saturday", time: "9:00 AM – 5:00 PM" },
+  { day: "Sunday", time: "Closed" },
+]
+```
+
+### Services / Menu items
+File: `content/site.ts`
+```
+services: [
+  { name: "[Service Name]", description: "[Short description]" },
+  ...
+]
+```
+Add or remove items by copying/pasting a line.
+
+### Social media links
+File: `content/site.ts`
+```
+social: {
+  facebook: "https://facebook.com/yourpage",
+  instagram: "https://instagram.com/yourhandle",
+}
+```
+
+---
+
+## Adding a photo
+
+1. Save your photo as a `.jpg` or `.webp` file
+2. Copy it to the `public/images/` folder
+3. In the relevant page file, change the image filename to match
+
+---
+
+## After editing
+
+Save the file, then run the site locally with:
+```bash
+npm run dev
+```
+Visit `http://localhost:3000` to preview your changes before deploying.
+
+To deploy changes live: push to GitHub — Vercel will automatically redeploy.
+
+---
+
+## Need more help?
+
+For changes beyond this guide (new pages, new features, design changes), contact your developer.
+```

package/skills/sk:website/references/launch-checklist.md

@@ -0,0 +1,99 @@
+# Launch Checklist
+
+Run this before generating the handoff package. The site must not only look complete — it must be operationally ready to ship.
+
+---
+
+## 1. Search and Metadata
+
+- [ ] Every page has a unique title tag (not "Home | Site Name" cloned across pages)
+- [ ] Every page has a unique, useful meta description (150–160 chars)
+- [ ] OG title, description, and image are defined (check `layout.tsx` or equivalent)
+- [ ] Twitter card metadata defined
+- [ ] Canonical URL handling in place (no duplicate content risk)
+- [ ] Structured data present where appropriate (LocalBusiness, Organization, etc.)
+- [ ] All important images have descriptive alt text (not empty, not "image.jpg")
+- [ ] `sitemap.xml` is generating correctly (visit `/sitemap.xml`)
+- [ ] `robots.txt` is correct (`/robots.txt` — no `Disallow: /` in production)
+
+---
+
+## 2. Conversion and Content
+
+- [ ] Clear primary CTA visible above the fold on the homepage
+- [ ] CTA is consistent and repeated across all key pages
+- [ ] No placeholder copy remains (`[Business Name]`, `Lorem ipsum`, `TODO`, `PLACEHOLDER`)
+- [ ] No invented testimonials, fake reviews, or made-up certifications
+- [ ] Contact information is real and visible (phone, email, address, hours)
+- [ ] WhatsApp link is wired (if injected) — test that `wa.me/[NUMBER]` opens correctly
+- [ ] Contact form submits without error (test in dev)
+- [ ] Booking/reservation link works (if applicable)
+- [ ] Footer includes business name, key navigation links, and contact info
+
+---
+
+## 3. Accessibility and UX
+
+- [ ] One H1 per page — no pages have multiple H1s
+- [ ] Heading hierarchy is correct — no skipping H2 → H4
+- [ ] Semantic landmarks in place: `<header>`, `<main>`, `<footer>`, `<nav>`
+- [ ] Interactive elements are keyboard-navigable (tab through the page)
+- [ ] Focus rings are visible (not `outline: none` without a replacement)
+- [ ] Color contrast passes AA (4.5:1 for body text, 3:1 for large text)
+- [ ] Images have alt text — decorative images have `alt=""`
+- [ ] No horizontal scroll on mobile (375px viewport)
+- [ ] Touch targets are at least 44×44px
+- [ ] `prefers-reduced-motion` is respected for animations
+
+---
+
+## 4. Performance and Implementation
+
+- [ ] No unnecessary client-side JS (prefer server/static rendering for marketing content)
+- [ ] Images are optimized — use Next.js `<Image>` or equivalent, specify `width`/`height`
+- [ ] No layout shift visible on load (set explicit dimensions on media)
+- [ ] Google Fonts loaded via `next/font` or with `display=swap` (no FOIT)
+- [ ] `next build` (or equivalent) passes without errors or warnings
+- [ ] No broken internal links or dead routes
+- [ ] No console errors in the browser
+- [ ] Required environment variables are documented in `.env.example`
+
+---
+
+## 5. Launch Operations
+
+- [ ] Analytics placeholder noted (GA4 measurement ID or Plausible domain to configure)
+- [ ] Consent banner approach defined if analytics requires it (GDPR/PH data privacy consideration)
+- [ ] Contact form submission endpoint configured or clearly marked as pending
+  - Local: API route created and tested
+  - External: Formspree/webhook endpoint documented
+- [ ] WhatsApp number placeholder clearly flagged in HANDOFF.md if not provided
+- [ ] `NEXT_PUBLIC_SITE_URL` or equivalent set for canonical and OG URL generation
+- [ ] Favicon is present (`/public/favicon.ico` or via `app/icon.tsx`)
+- [ ] Social preview image present (1200×630px OG image or dynamic via `/api/og`)
+- [ ] Privacy policy and terms pages exist or are noted as needed
+- [ ] Domain setup documented in DEPLOY.md
+
+---
+
+## Blocker vs. Polish
+
+**Must fix before handoff (blockers):**
+- Missing title/meta on any page
+- Broken contact form
+- Placeholder copy visible to users
+- `next build` failing
+- Broken navigation links
+- WhatsApp link not working
+
+**Medium priority (note in HANDOFF.md):**
+- Missing OG image
+- Analytics not yet configured
+- No privacy policy page
+- Lighthouse score 80–89 on any metric
+
+**Optional polish (mention, don't block):**
+- Additional page transitions
+- Image optimization for LCP
+- Schema markup enrichment
+- Blog or news section

package/skills/sk:website/references/niche/accountant.md

@@ -0,0 +1,75 @@
+# Accountant / Bookkeeper / Tax Firm
+
+Use for accountants, bookkeepers, tax preparers, CFO services, and financial advisory practices.
+
+## Priorities
+
+1. Establish competence and trust immediately — clients are trusting you with their money.
+2. Clarify who the firm serves and what it specifically helps with.
+3. Move visitors toward consultation or contact — the goal is a booked call, not a signup.
+4. Tone: specific, calm, and credible — never inflated or salesy.
+
+## Default page set
+
+- Home (audience + offer + consultation CTA)
+- Services (what you offer, who it's for, how it works)
+- About (firm story, team credentials, values)
+- Contact (consultation request form)
+- FAQ (common tax/accounting questions + process questions)
+
+Optional: Blog/Resources, Pricing (if transparent pricing is a differentiator), Client Portal link
+
+## Section guidance
+
+**Hero:**
+- Clear positioning: audience + service + location (if local SEO matters)
+- Example: "Tax prep and bookkeeping for freelancers and small businesses in Metro Manila"
+- Primary CTA: "Schedule a Free Consultation" or "Book a Call"
+- Phone number visible
+
+**Services:**
+- List with brief description of each service — what it includes, who it's for
+- Avoid jargon (e.g., "accrual accounting services" — say "monthly bookkeeping")
+- Link each to a detail page for SEO depth if possible
+
+**Why choose us:**
+- Specific credentials: CPA license, years in practice, types of clients served, notable affiliations
+- Process transparency: "We review your books monthly and flag issues before they become problems"
+- Never invent: no made-up client counts, invented savings amounts, or unverifiable claims
+
+**Team:**
+- Real names, credentials, and short bios
+- Even solo practitioners benefit from a professional headshot + credentials section
+
+**Consultation CTA:**
+- Make the first step easy: "30-minute free call, no obligation"
+- Simple form: Name, Email, Phone, Business type, What you need help with
+
+## Design guidance
+
+- **Art direction:** Restrained Editorial — calm, exact, composed.
+- Avoid: flashy visuals, startup aesthetics, anything that looks "too clever"
+- Typography: stable and precise — Source Serif, Libre Baskerville, or clean sans like Lato/Inter
+- Palette: navy, slate, charcoal, white — one warm accent (gold or teal) if any
+- Photography: real team photos if available; avoid generic "counting money" stock photos
+
+## SEO guidance
+
+- Title: "[Firm Name] — [Service] for [Audience] in [City, Region]"
+- H1: "[Accounting/Tax Service] for [Target Client Type] in [City]"
+- Target: "accountant for small business [city]", "bookkeeper [city]", "tax preparation [city]"
+- Structured data: `LocalBusiness` or `AccountingService` + `ProfessionalService`
+- FAQ page helps with "how much does X cost" and "do I need an accountant for X" queries
+
+## WhatsApp / contact
+
+- WhatsApp appropriate for PH/SEA accounting firms
+- Phone number always visible — clients with urgent tax questions call
+- Consultation booking: form + optional Calendly link works well
+
+## Avoid
+
+- Invented client testimonials, savings figures, or case outcomes
+- Generic financial stock imagery (coins, graphs, calculators)
+- Inflated language: "transforming your financial future" — be direct
+- Hiding pricing entirely when competitors are transparent (consider at least explaining the pricing model)

package/skills/sk:website/references/niche/agency.md

@@ -0,0 +1,75 @@
+# Agency / Studio / Consultancy
+
+Use for creative agencies, design studios, development firms, marketing consultancies, and any service firm where taste and credibility are core products.
+
+## Priorities
+
+1. Establish taste immediately — the site IS the portfolio.
+2. Make the offer and audience explicit — agencies often confuse "we do everything" with positioning.
+3. Build trust through work quality, process, and proof — not just claims.
+4. Move visitors toward inquiry or consultation.
+
+## Default page set
+
+- Home (positioning + selected work + CTA)
+- Work / Portfolio (case studies or project grid)
+- Services (what you do, who it's for, how you work)
+- About (team, story, values)
+- Contact (inquiry form)
+
+Optional: Case Study detail pages, Process page, Blog, Clients page
+
+## Section guidance
+
+**Hero:**
+- Clear positioning — who you help and what you do for them
+- Avoid: "We create experiences that matter" (vague)
+- Prefer: "Brand strategy and digital design for ambitious B2B companies"
+- CTA: "Start a Project" or "See Our Work"
+
+**Selected work:**
+- 3–6 real projects — thumbnail + client name + type of work
+- Never show fake case studies or vague "Project A" placeholders
+- If no portfolio available: skip this section and lead with process/services
+
+**Services:**
+- List with brief description — 3–8 services
+- Who benefits from each service
+- How you work (process overview or retainer/project model)
+
+**Why work with us:**
+- Specific: years in business, types of clients, notable partnerships if real
+- Process transparency: "We don't start until we understand your goals"
+
+**Team / About:**
+- Real photos, real bios — even for small teams
+- Mission or founding story if meaningful
+
+## Design guidance
+
+- **Art direction:** Restrained Editorial or Bold Brand-Forward — depending on the studio's own personality.
+- The site's design should demonstrate what the agency can do — it's a live portfolio piece.
+- Typography should be intentional and distinctive — not generic sans-serif defaults.
+- Photography of real work, team, and process > stock imagery.
+- Animation and transitions can be more expressive here than other niches.
+
+## SEO guidance
+
+- Title: "[Agency Name] — [Service] Agency in [City] (if local)"
+- H1: specific positioning statement
+- Target: "[service] agency [city]", "[service] studio", "[niche] design agency"
+- Case study pages are SEO gold — named projects, client industries, outcomes achieved
+- Structured data: `ProfessionalService` or `Organization`
+
+## WhatsApp / contact
+
+- Contact form with project type + budget range + timeline field
+- WhatsApp optional — appropriate in PH/SEA for smaller studios, less expected for enterprise agencies
+
+## Avoid
+
+- "We're passionate about design" — everyone says this
+- Vague case studies with no real outcomes or client names
+- Portfolio with no work shown (skip portfolio section instead of showing fake work)
+- Generic stock photos of teamwork and handshakes
+- Overpromising in the hero (claiming to do everything for everyone)

package/skills/sk:website/references/niche/cafe.md

@@ -0,0 +1,79 @@
+# Cafe
+
+Use for cafes, coffee shops, bakeries, brunch spots, and hospitality brands where atmosphere and local trust both matter.
+
+## Priorities
+
+1. Communicate the vibe immediately — people choose cafes by feel before they check the menu.
+2. Make location, hours, and menu access obvious — these are the most searched items.
+3. Encourage in-person visits, reservations, or online orders depending on what the business offers.
+4. Balance brand storytelling with practical information — never let atmosphere hide the basics.
+
+## Default page set
+
+- Home (hero + signature items + atmosphere + location/hours)
+- Menu (full menu or featured items by category)
+- About (brand story, team, sourcing story if relevant)
+- Find Us (location, hours, parking, directions, map embed)
+- Contact (reservation inquiry or general contact)
+
+Optional: Gallery, Events, Order Online (if third-party integrated), Press
+
+## Section guidance
+
+**Hero:**
+- Lead with brand atmosphere — warm image, specific place language
+- Sub-headline should be practical: "Specialty espresso and house-made pastries on [Street], [City]"
+- Primary CTA: "Reserve a Spot", "See the Menu", or "Find Us"
+
+**Signature offerings:**
+- 3–5 featured items with short, sensory descriptions
+- Real names only — no invented menu items
+
+**About / brand story:**
+- When it opened, who runs it, what they care about
+- Sourcing story if meaningful (single-origin, local farms, etc.)
+- Human — not a corporate mission statement
+
+**Location + hours block:**
+- Visible on every page (footer at minimum)
+- Hours listed clearly with day ranges
+- Include parking/transit notes if relevant
+- Google Maps embed or link
+
+**Reviews / social proof:**
+- Use real review counts from Google or Yelp if available (e.g., "4.8 stars · 240 reviews")
+- Never invent reviews or star ratings
+- Instagram embed or grid if the business has active social
+
+## Design guidance
+
+- Cafe sites should feel sensory and place-driven, not corporate or tech-startup.
+- **Art direction:** Warm Hospitality is almost always the right choice.
+- Typography: warm serif or humanist sans — pairs like Fraunces + Manrope, Lora + Inter.
+- Palette: warm neutrals — cream, sand, terracotta, olive, espresso brown. One accent.
+- Photography framing: close-ups of food/drink, ambient interior shots, hands-on-cup moments.
+- Use texture (paper grain, linen, concrete) in section backgrounds to create atmosphere.
+- Do not use generic stock coffee imagery — if no real photos exist, use strong typography + color instead.
+
+## SEO guidance
+
+- Homepage title: "[Cafe Name] — Specialty Coffee in [Neighborhood], [City]"
+- H1: "[Type of cafe] in [Location]" e.g., "Artisan Coffee Shop in Poblacion, Makati"
+- Mention neighborhood + city naturally in hero copy and about section
+- Include opening hours in structured data (LocalBusiness/CafeOrCoffeeShop schema)
+- Target "[coffee shop near me]", "[cafe in [neighborhood]]", "[brunch [city]]"
+
+## WhatsApp / contact
+
+- WhatsApp is default for reservation inquiries in PH/SEA
+- Pre-filled message: "Hi! I found you on your website. I'd like to inquire about a reservation."
+- If no WhatsApp, use a simple form with Name, Date/Time, Number of Guests fields
+
+## Avoid
+
+- Overdesigned navigation that hides hours, address, or menu
+- Generic stock images of coffee cups on marble — use real atmosphere or strong type
+- Keyword-stuffed city terms in headlines
+- Treating the site like a SaaS landing page — cafes are experiential, not transactional
+- Hidden or tiny contact info

package/skills/sk:website/references/niche/dentist.md

@@ -0,0 +1,78 @@
+# Dentist / Dental Clinic
+
+Use for dental clinics, cosmetic dentists, orthodontists, pediatric dentists, and oral care practices.
+
+## Priorities
+
+1. Build trust fast — dental anxiety is real; the site should feel calm and reassuring.
+2. Explain services clearly — patients often don't know the terminology.
+3. Reduce booking friction — easy appointment scheduling above the fold.
+4. Balance warmth with clinical credibility.
+
+## Default page set
+
+- Home (services overview + trust signals + booking CTA)
+- Services (full service list with brief descriptions)
+- About Us / Meet the Dentist (team profiles + clinic photos)
+- Book an Appointment (form or third-party booking link)
+- Contact (address, hours, map, phone)
+
+Optional: FAQ, Before/After Gallery (only with real consented photos), Insurance/Payment page, Blog
+
+## Section guidance
+
+**Hero:**
+- Lead with what you offer and who you serve, not a clever tagline
+- Example: "Family and Cosmetic Dental Care in Quezon City"
+- CTA: "Book an Appointment" — prominently placed
+- Phone number visible
+
+**Services:**
+- List all services with a brief, patient-friendly description
+- Group logically: General, Cosmetic, Orthodontic, Pediatric, etc.
+- Avoid jargon — "tooth-colored fillings" not "composite resin restorations"
+
+**Meet the dentist / team:**
+- Real photos, credentials (DDS, DMD, specializations), brief personal bio
+- Humanizes the practice — reduces patient anxiety
+
+**Trust signals:**
+- Years in practice, number of patients served (if real), certifications, PDA/ADA membership
+- Clinic accreditation if applicable
+- Reviews or patient count — only if real
+
+**Booking / appointment CTA:**
+- Simple form: Name, Contact, Preferred date/time, Type of concern
+- Or link to Calendly/SimplyBook or similar
+- WhatsApp for quick scheduling in PH
+
+## Design guidance
+
+- **Art direction:** Restrained Editorial or Premium Product-Led — clean and calm.
+- Never use garish or overly commercial aesthetics.
+- Typography: clean, legible sans — Inter, Lato, Poppins, or calm serif
+- Palette: soft and clinical — white, soft blue, mint, light grey, warm white
+- Photography: real clinic interior + real team photos are far more effective than stock dental images
+- Motion: minimal or none — calm is the signal
+
+## SEO guidance
+
+- Title: "[Clinic Name] — Dentist in [City/Neighborhood]"
+- H1: "Dental Clinic in [City]" or "Dentist in [Neighborhood], [City]"
+- Target: "dentist in [city]", "dental clinic near me", "cosmetic dentist [city]"
+- Separate service pages for high-intent searches: "teeth whitening [city]", "braces [city]"
+- Structured data: `Dentist` schema with full address, phone, opening hours
+
+## WhatsApp / contact
+
+- WhatsApp is high-value for appointment booking in PH — patients message before calling
+- Pre-filled: "Hi! I'd like to book a dental appointment. I found you on your website."
+- Simple booking form as backup
+
+## Avoid
+
+- Invented patient testimonials or before/after results
+- Generic "dental health" stock imagery
+- Complex navigation that buries the booking CTA
+- Clinical jargon in patient-facing copy
+- Hiding pricing entirely — patients ask "how much is cleaning/braces?" — provide at least a range or "contact for pricing"