agentleFS
florattuflorattu/claude-skills/service-booking-flow/SKILL.md

service-booking-flow

Skill0 starsChanged 5 months agoApache-2.0View on GitHub

Create or redesign appointment-based service websites for salons, barbers, spas, wellness studios, clinics, and hospitality brands. Use for warm editorial layouts, serif-led identity, documentary portrait crops, calm treatment selectors, location-aware booking, and operational states that remain elegant and trustworthy.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 15 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use original or licensed people and place photography.

    line 18
  2. Distinctive:

    Use warm ivory paper and near-black chapters.

    line 22
  3. Distinctive:

    Keep uppercase navigation sparse and quiet.

    line 25
  4. Distinctive:

    Use black for decisive actions.

    line 26
  5. Distinctive:

    Avoid glossy cards, glass effects, loud gradients, and beauty-template ornament.

    line 27
  6. Very specific:

    Use semantic buttons with tablist, tab, and tabpanel behavior when tabs are appropriate.

    line 43
  7. Distinctive:

    Keep duration, price, description, and action in the DOM.

    line 45
  8. Distinctive:

    Keep focus and hover cues equivalent.

    line 49
  9. Distinctive:

    Prefer native form controls and server-validated availability.

    line 53
  10. Distinctive:

    Never claim a slot before server confirmation.

    line 55
  11. Distinctive:

    Use 160–220ms for controls and 500–760ms for section entrances.

    line 62
  12. Distinctive:

    Keep the confidence loop slower than 14 seconds and pause it offscreen.

    line 63
  13. Distinctive:

    Use one layered photo reveal, simple section fades, and short treatment-media swaps.

    line 64
  14. Distinctive:

    Keep transforms shallow and reserve exact final layout pixels.

    line 65
  15. Distinctive:

    Test a stale slot, failed media, server error, invalid field, and retry.

    line 71
  16. Distinctive:

    Verify readable contrast, visible focus, alt text, 200% zoom, and correct tab order.

    line 73

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.