@kennethsolomon/shipkit 3.13.2 → 3.15.1

package/skills/sk:website/references/niche/med-spa.md

@@ -0,0 +1,78 @@
+# Med Spa / Aesthetics Clinic
+
+Use for med spas, aesthetic clinics, injectables studios, skin clinics, and wellness beauty businesses.
+
+## Priorities
+
+1. Build trust and premium appeal simultaneously — both are required.
+2. Make services and booking paths obvious.
+3. Balance aspiration with clinical credibility.
+4. Keep claims careful and believable — no invented outcomes or medical guarantees.
+
+## Default page set
+
+- Home (positioning + featured treatments + booking CTA)
+- Treatments / Services (full treatment menu with descriptions)
+- About Us / Our Team (provider credentials + clinic credentials)
+- Book a Consultation (booking form or link)
+- Contact (address, hours, phone, map)
+
+Optional: Before/After Gallery (only real, consented photos), FAQ, Blog
+
+## Section guidance
+
+**Hero:**
+- Balance of aspirational and professional
+- Example: "Skin Treatments and Injectables in Bonifacio Global City"
+- CTA: "Book a Consultation" — not "Buy Now"
+- Soft, clean aesthetic — not aggressive sales
+
+**Treatments / services:**
+- List each treatment with a patient-friendly name and brief description
+- What it's for, approximate duration, when results appear
+- Group logically: Injectables, Skin, Body, Laser, etc.
+- Never invent outcomes ("Guaranteed results in 2 weeks")
+
+**Provider / clinic credentials:**
+- Doctor or RN name + credentials (MD, RN, licensed aesthetician)
+- Clinic accreditation, brand partnerships (if real)
+- Years of practice
+
+**Before/after or results:**
+- Only real photos with patient consent
+- If no real photos: skip this section — no stock before/after imagery
+
+**Booking:**
+- Initial consultation form: Name, Contact, Treatment of interest, Preferred date
+- WhatsApp for quick inquiries in PH/SEA
+
+## Design guidance
+
+- **Art direction:** Quiet Luxury or Restrained Editorial — both work well for aesthetics.
+- Premium feel without being cold or sterile.
+- Typography: refined serif or elegant sans — Cormorant Garamond, Libre Baskerville, or DM Serif Display
+- Palette: very limited — cream, warm white, blush, champagne, one muted accent
+- Photography: clean clinic environment, soft lifestyle imagery — not clinical procedure photos
+- Motion: minimal and graceful — soft fades, no rapid animations
+
+## SEO guidance
+
+- Title: "[Clinic Name] — Skin Treatments and Injectables in [City]"
+- H1: "Aesthetic Clinic in [City]" or "Med Spa in [Neighborhood], [City]"
+- Target: "med spa [city]", "botox [city]", "skin clinic near me", "fillers [city]"
+- Separate pages per treatment help for high-intent searches
+- Structured data: `MedicalBusiness` or `LocalBusiness`
+
+## WhatsApp / contact
+
+- WhatsApp common for initial inquiries in PH — patients ask questions before booking
+- Pre-filled: "Hi! I found you on your website. I'd like to book a skin consultation."
+- Consultation form for more detailed intake
+
+## Avoid
+
+- Invented before/after results or patient outcomes
+- Aggressive discount banner aesthetics (contradicts premium positioning)
+- Over-promising treatment results
+- Medical jargon without plain-language explanations
+- Stock "beauty influencer" imagery — clinical warmth beats generic glamour

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

@@ -0,0 +1,77 @@
+# Portfolio / Freelance
+
+Use for designers, developers, photographers, illustrators, writers, videographers, and any individual showcasing personal work to attract clients or opportunities.
+
+## Priorities
+
+1. Show work immediately — the work is the argument.
+2. Make it clear what you do and who you help.
+3. Reduce friction to inquiry — simple contact, not a 10-field form.
+4. Personality matters — this is a personal brand, not a corporate site.
+
+## Default page set
+
+- Home (work showcase + brief intro + CTA)
+- Work / Projects (detailed project grid or case studies)
+- About (who you are, what you specialize in, personality)
+- Contact (email link or simple form)
+
+Optional: Services (if freelance pricing/packages), Blog, Process, Resume/CV
+
+## Section guidance
+
+**Hero:**
+- First impression: your name, what you do, and who you do it for
+- Example: "Freelance product designer for SaaS startups. Based in Manila."
+- CTA: "View My Work" or "Hire Me"
+- Optional: a featured project or short reel behind the text
+
+**Work / projects:**
+- Thumbnail + project name + brief role description
+- Real work only — no placeholder "Case Study 1"
+- If work is NDA/client-confidential, show anonymized screenshots with permission
+- Link to detail pages for case studies if depth helps your field
+
+**About:**
+- Human, first-person, specific — not a job description
+- What you specialize in, what types of clients you love working with
+- Photo (optional but humanizes the brand)
+
+**Contact:**
+- Email address directly (not buried) OR a simple form
+- No need for a full inquiry form — "Name, Email, Message" is enough
+- Response time expectation if applicable ("I typically reply within 24 hours")
+
+## Design guidance
+
+- **Art direction:** Highly flexible — match to the creator's own aesthetic.
+  - Designers: Restrained Editorial or Quiet Luxury work well
+  - Developers: Sharp Technical
+  - Photographers: Premium Product-Led (image-first)
+  - Illustrators: Playful Contemporary or Bold Brand-Forward
+- The portfolio IS the design direction signal — inconsistency between the site and the work undermines credibility.
+- Typography with personality — one distinctive display face is expected.
+- Minimal navigation — most portfolios don't need more than 4 nav items.
+- Dark mode optional and often effective for portfolios.
+
+## SEO guidance
+
+- Title: "[Your Name] — [Role] based in [City]"
+- H1: "[Role] specializing in [focus area]"
+- Target: "[role] freelance", "[role] [city]", "[specialty] designer/developer"
+- Project detail pages help SEO — name the technology, client industry, and outcome
+- Structured data: `Person` schema
+
+## WhatsApp / contact
+
+- Optional for portfolios — not expected in all markets
+- For PH-based freelancers: WhatsApp is common for client initial contact
+- Keep it simple — direct number or link is enough
+
+## Avoid
+
+- Faking clients, project outcomes, or publication features
+- "Available for hire" in the hero when you're not currently available
+- Cluttered project grids with no visual hierarchy
+- Effects that distract from the actual portfolio work
+- Overly long bio — be specific, not exhaustive

package/skills/sk:website/references/niche/real-estate.md

@@ -0,0 +1,72 @@
+# Real Estate Agent / Property
+
+Use for real estate agents, brokerages, property advisors, buyer's agents, and development marketing sites.
+
+## Priorities
+
+1. Build personal or brand trust quickly — people choose agents they trust with large decisions.
+2. Make listings, inquiry, or valuation CTAs obvious.
+3. Support location-based discovery — people search by area.
+4. Present market expertise without sounding inflated.
+
+## Default page set
+
+- Home (positioning + market expertise + featured listings/inquiry CTA)
+- Listings / Properties (property grid or search)
+- About / Our Team (agent profiles + credentials + track record)
+- Buyer / Seller Services (process, what you do, who you help)
+- Contact (inquiry form + phone)
+
+Optional: Sold/Leased Properties (with client permission), Market Updates/Blog, Neighborhoods guide
+
+## Section guidance
+
+**Hero:**
+- Who you help + what market you work in
+- Example: "BGC and Makati Condo Specialist — Helping Buyers and Sellers Since 2015"
+- CTA: "Search Listings", "Request a Valuation", or "Get in Touch"
+
+**Featured listings / property highlights:**
+- Real properties only — never placeholder listings
+- Photo + property type + location + price range (or "price on request")
+
+**Why work with us:**
+- Specific: areas covered, years of experience, notable transactions if real and permitted
+- Market expertise: "We've closed 40+ transactions in BGC over 5 years" — only if true
+
+**Agent profile:**
+- Real headshot, full name, license number if applicable, areas covered
+- Brief personal approach to real estate — not just credentials
+
+**Buyer / seller services:**
+- Walk through the process — buyers and sellers have different journeys
+- What you do at each step, what makes you different from other agents
+
+## Design guidance
+
+- **Art direction:** Premium Product-Led or Restrained Editorial — property is visual, let it lead.
+- Photography quality matters most — no low-res property shots.
+- Typography: clean and professional — avoid flashy display fonts.
+- Palette: neutral, aspirational — warm whites, slate, charcoal, one sophisticated accent.
+- Luxury properties: Quiet Luxury direction is appropriate.
+
+## SEO guidance
+
+- Title: "[Agent/Firm Name] — [City] Real Estate Agent"
+- H1: "Real Estate Agent in [City/Neighborhood]"
+- Target: "real estate agent [city]", "property for sale [city]", "buy condo [city]"
+- Neighborhood guide pages help SEO long-term
+- Structured data: `RealEstateAgent` or `LocalBusiness`
+
+## WhatsApp / contact
+
+- WhatsApp for property inquiries in PH/SEA — standard practice
+- Pre-filled: "Hi! I found you on your website. I'd like to inquire about a property."
+- Phone always prominently visible
+
+## Avoid
+
+- Invented transaction volumes or rankings
+- Luxury aesthetic for non-luxury market segments (creates trust mismatch)
+- Listings without real photos (use a "coming soon" placeholder or skip the section)
+- Cluttered homepage with too many property cards

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

@@ -0,0 +1,80 @@
+# Restaurant
+
+Use for full-service restaurants, casual dining, bistros, brasseries, and food-first hospitality brands where reservations, menus, and atmosphere all drive decisions.
+
+## Priorities
+
+1. Menu and reservation path must be the top two accessible things on the site.
+2. Atmosphere through photography — people decide before they taste.
+3. Location, hours, and parking are always important.
+4. Reduce friction to booking — no multi-step flows for a table inquiry.
+
+## Default page set
+
+- Home (hero + ambiance + signature dishes + reservation CTA)
+- Menu (full menu by category — starters, mains, desserts, drinks)
+- About (story, chef, kitchen philosophy)
+- Reservations (booking form or third-party reservation link)
+- Find Us (address, hours, parking, map embed)
+
+Optional: Events / Private Dining, Gallery, Takeout / Delivery, Press
+
+## Section guidance
+
+**Hero:**
+- Strong food or interior photography above the fold
+- Headline should set the dining experience: cuisine type + atmosphere + location
+- Two CTAs: "Make a Reservation" (primary) + "View Menu" (secondary)
+
+**Signature dishes:**
+- 3–6 featured dishes with short descriptions — texture, flavor, ingredient-forward
+- Real names from the actual menu only
+
+**About / story:**
+- Chef background if notable, kitchen philosophy, sourcing if meaningful
+- Warm and specific — not generic "passion for food" copy
+
+**Reservation section:**
+- Keep it simple: Name, Date, Time, Number of guests, Phone/Email
+- Link to OpenTable / Resy / Quandoo if integrated
+- WhatsApp for direct reservation inquiries
+
+**Location + hours:**
+- Prominently placed — in nav, on homepage, and on dedicated page
+- Include parking, valet, or transit notes
+- Map embed (Google Maps iframe)
+
+**Reviews:**
+- Real rating + review count from Google, Zomato, or TripAdvisor if available
+- Specific quotes if real reviews exist — never invent
+
+## Design guidance
+
+- **Art direction:** Warm Hospitality almost always. Bold Brand-Forward for trendy concept restaurants.
+- Photography is the design system's backbone — image quality matters more than any other element.
+- Typography: editorial serif for headlines (Playfair Display, Cormorant, Fraunces) + clean sans for menus.
+- Palette: warm, food-first colors — deep red, terracotta, cream, charcoal, dark green.
+- Menu page: well-structured table/list layout — legible at a glance, not overly designed.
+- Motion: minimal — slow hero crossfade, gentle parallax on food photography.
+
+## SEO guidance
+
+- Homepage title: "[Restaurant Name] — [Cuisine] Restaurant in [Neighborhood], [City]"
+- H1: "[Cuisine type] in [Location]" e.g., "Modern Filipino Restaurant in Poblacion, Makati"
+- Target: "restaurant in [city]", "[cuisine] restaurant near me", "best [cuisine] [city]"
+- Include structured data: `Restaurant` schema with address, hours, telephone, menu URL, accepts reservations
+- Separate menu page helps SEO — ensure it's crawlable HTML, not just a PDF
+
+## WhatsApp / contact
+
+- WhatsApp for reservation inquiries — high conversion for SEA restaurants
+- Pre-filled message: "Hi! I'd like to make a reservation. I found you on your website."
+- Combine with a simple form for advance/large-group bookings
+
+## Avoid
+
+- Menu as a PDF (not crawlable, terrible UX on mobile)
+- Reservations buried below the fold
+- Using SaaS/tech visual aesthetics for a warm dining brand
+- Generic stock photography of food
+- Hiding the address — locals google restaurants on the go

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

@@ -0,0 +1,80 @@
+# SaaS / Software Product
+
+Use for SaaS products, B2B tools, AI products, developer platforms, and software-first brands.
+
+## Priorities
+
+1. Clarify what the product does in the first 5 seconds — no mystery.
+2. Show who it's for — visitors self-qualify before trialing.
+3. Reduce perceived complexity — demos, how-it-works, and proof over feature lists.
+4. Move visitors toward signup, trial, or demo request.
+
+## Default page set
+
+- Home (outcome-driven hero + proof + social proof + pricing CTA)
+- Features (or use cases, if that's the better frame)
+- Pricing (3-tier with clear feature comparison)
+- About (team + mission + why this product)
+- Contact / Demo (simple lead capture or Calendly)
+
+Optional: Docs, Blog, Changelog, Integrations, Customers/Case Studies
+
+## Section guidance
+
+**Hero:**
+- One clear benefit statement — what the user can do with this product
+- Sub-headline: who it's for + how it works in one line
+- CTA: "Start Free Trial", "Request a Demo", or "Get Started Free"
+- Supporting visual: screenshot, short video loop, or product mockup (real only)
+
+**Social proof bar:**
+- Company logos or "X+ teams" or "Y+ users" — real numbers only
+- Even if small: "Trusted by 50+ early teams" is credible; invented logos are not
+
+**Features / value pillars:**
+- 3–6 cards: one benefit per card, not feature specs
+- Frame around outcomes: "Deploy in minutes, not days" not "One-click deployment button"
+
+**How it works:**
+- 3-step visual flow — numbered, no jargon
+- If there's a product tour or demo video, this is where it goes
+
+**Pricing:**
+- 3 tiers standard (Free/Starter/Pro or Starter/Growth/Enterprise)
+- Highlight the recommended tier
+- Annual toggle if applicable
+- Use real pricing if known; if not, use "Contact for pricing" not invented numbers
+
+**Testimonials:**
+- Real quotes from real customers, name + role + company
+- If none available, use social proof bar instead — never invent
+
+## Design guidance
+
+- **Art direction:** Premium Product-Led or Sharp Technical — depending on whether the product is design-forward or developer-facing.
+- Avoid generic SaaS visual tropes: purple gradients, glowing UI previews, "scale" metaphors.
+- Typography: clean, modern sans — DM Sans, Inter, Plus Jakarta Sans.
+- Palette: controlled — neutral background, one primary brand color, strategic accent.
+- Dark mode optional — great for developer tools, not necessary for all SaaS.
+- Screenshots of real product UI carry more weight than illustrations.
+
+## SEO guidance
+
+- Homepage title: "[Product Name] — [Primary Benefit] for [Audience]"
+- H1: specific value statement, not just a tagline
+- Target: "[problem the product solves]", "[product category] software", "[use case] tool"
+- Structured data: `SoftwareApplication` or `WebApplication`
+- Blog/docs pages help long-tail SEO significantly
+
+## WhatsApp / contact
+
+- Not applicable for SaaS — use demo form, trial signup, or Calendly
+- If B2B sales motion: contact form with company size, use case fields
+
+## Avoid
+
+- Fake product dashboards when no real screenshots exist
+- Purple-to-blue gradients as the primary design element
+- Feature lists without benefit framing
+- "Innovative" and "cutting-edge" — show, don't claim
+- Pricing page with no real tiers

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

@@ -0,0 +1,80 @@
+# Wedding / Event / Bridal
+
+Use for wedding planners, bridal brands, venues, photographers, florists, and wedding-focused event businesses.
+
+## Priorities
+
+1. Create emotional atmosphere immediately — couples are making an emotional, high-stakes purchase.
+2. Make inquiry or booking paths obvious — couples often browse multiple vendors before contacting.
+3. Show taste, portfolio, and experience.
+4. Balance romance with practical planning information.
+
+## Default page set
+
+- Home (emotional positioning + portfolio preview + inquiry CTA)
+- Services / Packages (what you offer, how it works, pricing approach)
+- Portfolio / Gallery (real work — weddings photographed, events planned, flowers arranged)
+- About (your story, why you do this, your team)
+- Contact / Inquire (inquiry form with date, venue, guest count)
+
+Optional: FAQ, Testimonials (real), Blog, Availability Calendar
+
+## Section guidance
+
+**Hero:**
+- Set the emotional tone before the practical details
+- Example: "Wedding Photographer in Manila — Candid, Intimate, Timeless"
+- CTA: "Check Availability" or "Inquire Now"
+- Strong hero photography (real work only)
+
+**Portfolio / gallery:**
+- Real weddings/events only — no stock wedding imagery
+- If portfolio is limited (new business), use 3–5 strong examples or focus on mood/process
+- Quality over quantity — 6 great photos beat 30 mediocre ones
+
+**Services / packages:**
+- Clear list of offerings: what's included, duration, deliverables
+- Pricing approach: "Packages starting from [X]" or "Contact for custom quote" — avoid total opacity
+- Separate wedding day vs. engagement vs. elopement if applicable
+
+**About / story:**
+- Personal and specific — why you do this work, your approach
+- Team photos if working with a crew
+
+**Testimonials:**
+- Real couple quotes, real names, optional wedding date/venue
+- Google Review count if available
+
+**Contact / inquiry:**
+- Form: Name, Email, Phone, Date, Venue (or location), Type of event, Guest count, Message
+- Response time expectation — couples often contact multiple vendors simultaneously
+
+## Design guidance
+
+- **Art direction:** Quiet Luxury or Restrained Editorial for premium brands; Warm Hospitality for approachable/bohemian styles.
+- Visual pacing and typography carry more weight than heavy ornament.
+- Typography: romantic but readable — fine serif (Cormorant, Playfair Display) + clean sans
+- Palette: soft and curated — blush, ivory, sage, champagne, dusty rose, eucalyptus green
+- Photography is the entire design system — never use stock wedding imagery
+- Motion: slow and graceful — crossfades, gentle scroll reveals
+
+## SEO guidance
+
+- Title: "[Business Name] — Wedding [Photographer/Planner/Florist] in [City]"
+- H1: "Wedding [Service Type] in [City]" — e.g., "Wedding Photographer in Manila"
+- Target: "wedding photographer [city]", "wedding planner [city]", "wedding florist near me"
+- Portfolio pages optimized per wedding style/venue help for style-specific searches
+- Structured data: `LocalBusiness` or `EventPlanner`
+
+## WhatsApp / contact
+
+- WhatsApp for initial availability inquiries in PH/SEA
+- Pre-filled: "Hi! I'm inquiring about availability for my wedding. I found you on your website."
+- Full inquiry form for packages/quotes
+
+## Avoid
+
+- Stock wedding photography — real work or no work
+- Generic "Love, Laughter, and Happily Ever After" copy
+- Hiding pricing entirely (couples will bounce if they have no price signal)
+- Burying the inquiry form below excessive intro copy