mcpField
E
editorial-service-booking

editorial-service-booking

github.com/mengtoDesign & UI7.1k1.4k installsUpdated 3d ago
Repository

About editorial-service-booking

A design skill for service businesses building editorial-style service browsing and booking pages. It combines a restrained visual system with accessible treatment selection and resilient booking-flow guidance.

Key features

  1. 01Editorial visual system and page structure
  2. 02Treatment comparison with media and details
  3. 03Keyboard-accessible treatment selection
  4. 04Booking state and error handling
  5. 05Motion, accessibility, and validation guidance

Use cases

  1. 01Designing a salon or service lookbook page
  2. 02Building a treatment selection interface
  3. 03Planning booking flows that preserve choices through errors

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mengto/skills --skill editorial-service-booking

After installing, type/editorial-service-bookingin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

REFERENCES.md
agents/
openai.yaml
demo/
index.html
PROMPT.md

Details

From the project README

Editorial Service Booking

Make browsing services feel like turning through a quiet lookbook, then carry that confidence into a resilient booking flow.

Establish the Journey

  1. Open with one strong portrait or place image and a short statement of craft.
  2. Build trust with environment, process, and practitioner evidence rather than generic badges.
  3. Let visitors compare treatments in one calm media-and-copy stage.
  4. Show favorites, results, or verified customer proof only when real.
  5. Move into location, professional, time, and confirmation without changing visual language.

Use original or licensed people and place photography. Replace every source service, price, person, location, review, and claim.

Build the Visual System

  • Use warm ivory paper and near-black chapters.
  • Pair an elegant high-contrast serif with compact sans-serif labels.
  • Favor hairline rules, minimal radius, editorial crops, and generous whitespace.
  • Keep uppercase navigation sparse and quiet.
  • Use black for decisive actions; use one muted accent only for selection or status.
  • Avoid glossy cards, glass effects, loud gradients, and beauty-template ornament.

Compose the Page

  • Header: show essential routes, current location, and one booking action.
  • Hero: use one cropped documentary portrait or place image with a large serif statement.
  • Confidence line: allow one slow text loop only when it carries real positioning.
  • About: layer two or three photographs with captions and clear reading order.
  • Treatments: pair a tab list with a reserved media stage, duration, price, and booking link.
  • Favorites: use a dark chapter to show verified popular services or results.
  • Locations: expose address, hours, accessibility, contact, and availability before booking.
  • Booking: keep selected service, professional, location, and time visible through confirmation.
  • Footer: prioritize operational information over marketing filler.

Implement the Treatment Selector

  • Use semantic buttons with tablist, tab, and tabpanel behavior when tabs are appropriate.
  • Support arrow-key movement plus Enter and Space selection.
  • Keep duration, price, description, and action in the DOM.
  • Reserve stage dimensions and preload only the next likely image.
  • Announce the selected treatment without repeating the whole panel.
  • Fall back to an expanded static list under reduced motion.
  • Keep focus and hover cues equivalent; touch must not depend on hover.

Implement the Booking Flow

  • Prefer native form controls and server-validated availability.
  • Persist service, professional, location, and time choices.
  • Never claim a slot before server confirmation.
  • Design loading, empty, disabled, stale slot, invalid details, payment failure, retry, reschedule, cancel, and success states.
  • Return focus to the correct field after an error and announce validation clearly.
  • Preserve selections across Back navigation and recoverable failures.

Motion Defaults

  • Use 160–220ms for controls and 500–760ms for section entrances.
  • Keep the confidence loop slower than 14 seconds and pause it offscreen.
  • Use one layered photo reveal, simple section fades, and short treatment-media swaps.
  • Keep transforms shallow and reserve exact final layout pixels.
  • Render the final state immediately for reduced motion.

Validate

  • Complete booking with keyboard and touch on mobile.
  • Test a stale slot, failed media, server error, invalid field, and retry.
  • Confirm no layout shift during treatment changes.
  • Verify readable contrast, visible focus, alt text, 200% zoom, and correct tab order.
  • Confirm all people, places, prices, results, and reviews are real, licensed, provided, or clearly marked internal placeholders.

Avoid

  • Dense price tables before desire or context exists.
  • Hover-only treatment previews.
  • Fake availability, reviews, results, or practitioner credentials.
  • Auto-advancing carousels, frantic motion, and decorative beauty gradients.
  • Losing booking selections after errors or navigation.

Comments

Markdown supported