Run any Skill in Manus with one click

booking-domain

Stars0

Forks0

UpdatedMarch 24, 2026 at 21:21

Implement or plan booking, availability, rescheduling, cancellation, and reminder flows in this salon SaaS. Use when touching calendars, time slots, deposits, booking states, or customer appointment journeys.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

MateoGs013

MateoGs013/SaaS-Peluqueria

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	booking-domain
description	Implement or plan booking, availability, rescheduling, cancellation, and reminder flows in this salon SaaS. Use when touching calendars, time slots, deposits, booking states, or customer appointment journeys.

Booking Domain

The booking system is a core domain. Treat it as business-critical.

Invariants

a stylist cannot be double-booked for overlapping services
availability must respect branch hours, staff schedules, breaks, and blocked times
booking status changes must be explicit
cancellation and no-show policies must be enforceable
payment state and booking state must not drift silently

Modeling hints

separate service duration from display order and marketing copy
support multiple branches
support optional deposit requirements
store timezone-aware timestamps consistently
keep reminder delivery asynchronous

Review checklist

does the flow create impossible overlaps?
is rescheduling audited?
can another tenant see or mutate the booking?
do tests cover happy path and denied path?

More from this repository

same repository

ai-assisted-laravel-workflow

MateoGs013/SaaS-Peluqueria

AI-first Laravel repository workflow for planning, implementing, and documenting work in this project. Use when bootstrapping the repo, setting up agent guidance, or performing changes that should update memory, ADRs, or AI instructions.

2026-03-240

api-v1-contracts

MateoGs013/SaaS-Peluqueria

Use when implementing or reviewing versioned API endpoints, request/response contracts, resources, and integration-facing payloads for this repository.

2026-03-240

commit-discipline

MateoGs013/SaaS-Peluqueria

Use when preparing commits, splitting work into commit boundaries, writing commit messages, or reviewing whether a branch is ready for GitHub PRs in this repository.

2026-03-240

filament-panel-work

MateoGs013/SaaS-Peluqueria

Build or change Filament-based internal panels in this Laravel salon SaaS. Use when working on superadmin dashboards, tenant admin pages, tables, forms, widgets, resources, or internal workflows.

2026-03-240

public-booking-experience

MateoGs013/SaaS-Peluqueria

Use when building the public salon pages, stylist profiles, booking journey, conversion-focused UI, or client-facing scheduling flows.

2026-03-240

superadmin-tenant-onboarding

MateoGs013/SaaS-Peluqueria

Use when implementing or changing superadmin flows for tenant creation, owner assignment, tenant lifecycle, status changes, and initial customer onboarding.

2026-03-240

name	booking-domain
description	Implement or plan booking, availability, rescheduling, cancellation, and reminder flows in this salon SaaS. Use when touching calendars, time slots, deposits, booking states, or customer appointment journeys.

Booking Domain

The booking system is a core domain. Treat it as business-critical.

Invariants

a stylist cannot be double-booked for overlapping services
availability must respect branch hours, staff schedules, breaks, and blocked times
booking status changes must be explicit
cancellation and no-show policies must be enforceable
payment state and booking state must not drift silently

Modeling hints

separate service duration from display order and marketing copy
support multiple branches
support optional deposit requirements
store timezone-aware timestamps consistently
keep reminder delivery asynchronous

Review checklist

does the flow create impossible overlaps?
is rescheduling audited?
can another tenant see or mutate the booking?
do tests cover happy path and denied path?