Skill instructions
booking-setup6.27 KB
View saved version →
---
{
"name": "booking-setup",
"description": "Add online appointment booking to a small-business app with the AppDeploy booking module. Ask the owner five critical questions with quick defaults or dig-in options, then build. Use when the user wants clients to book appointments, time slots or classes (salon, clinic, studio, tutor, court)."
}
---
# Booking setup
Use this when the owner wants clients to book appointments or classes (salon, clinic, studio, tutor, court, barber, pet groomer). The booking module does slots, holds, cancel and move rules, waitlist, reminders by email and push, calendar files and the widgets. You decide five things with the owner and leave the rest on defaults.
Keep the conversation short. Ask the five questions in one message, each with a one-line **quick** default. When the host has a native ask-user tool (`request_user_input_async` or `request_user_input`), put the five questions in one call with the quick default as the first option and "let me dig in" as the second; otherwise ask them as one chat message. The owner answers what they care about; anything they skip takes the default. Only open a **dig in** block when the owner asks for it or their answer needs it.
## The five questions
### 1. What can be booked, and by whom
**Quick:** list your services with duration and price, e.g. "haircut 45 min 40, color 90 min 90". One person (you).
**Dig in** when there is a team or classes:
- Team: names; who gets the staff role (they sign in and see the day view); which staff do which service.
- Classes with seats (yoga, workshop) in addition to or instead of appointments.
- Clean-up buffer after a service (default 0; 10 to 15 for color, treatments).
- More than one location (branches).
### 2. When
**Quick:** weekly hours, e.g. "Mon to Fri 9 to 18, Sat 9 to 14". Same for everyone.
**Dig in:**
- Different hours per staff member; lunch breaks; days off and holidays.
- Slot grid (default 15 minutes; 30 for long services, 10 for quick ones). It locks after the first booking, so settle it now.
- How far ahead clients can book (default 60 days) and minimum notice (default none; for example nothing in the next 2 hours).
### 3. Cancellation
**Quick:** 24 hours. After that the client is told to call.
**Dig in:**
- Different cutoff (48 hours for long treatments is common).
- Can clients move a booking themselves (default yes, same cutoff).
- Max open bookings per client (default 3).
- No-shows: marked by staff; no automatic penalty.
### 4. Money
**Quick:** no payment in the app; pay at the visit.
**Dig in:** deposits and online payment are not available yet. When the owner asks for them, say so plainly and do not build a payment step or add a payment provider by hand. Offer instead to show each price and one sentence about how and when to pay (and the no-show policy) on the booking page.
### 5. Messages
**Quick:** email confirmation and a reminder the day before at 18:00, in the app's language when the platform has it (English otherwise). The owner gets a daily summary of tomorrow's bookings.
**Dig in:**
- An email to the owner on every booking and cancellation (off by default; a busy business is better served by the daily summary).
- Quiet hours: no messages at night or on the owner's days off.
- WhatsApp and SMS messages are not available yet; when the owner asks, say so and keep email and push.
- Push notifications for clients who install the app.
- Sender: the platform address, or the owner's own domain (Plus).
- Waitlist when a day is full: on by default, first in line gets a 15-minute offer when a slot frees up.
## Not questions, just do it
- Clients sign in to book (Google, Apple, email). No guest booking. Free times are visible without sign-in; sign-in is asked when the client presses Book.
- Set the business timezone from where the business is (the city or country the owner mentioned); ask once when it is unclear. Never leave the default and never copy a timezone from an example.
- WidgetPreview of the first 4,000 characters. Read full instructions →
frontend-design2.21 KB
View saved version →
---
name: frontend-design
description: Use this skill whenever creating, deploying, or materially modifying an AppDeploy app with a user-facing interface. Apply its design guidance to typography, color themes, layout, motion, and backgrounds.
---
Apply this guidance when designing or restyling an AppDeploy app's frontend. Respect the user's explicit design requirements and any existing brand or design system.
You tend to converge toward generic, "on distribution" outputs. In frontend design, this creates what users call the "AI slop" aesthetic. Avoid this: make creative, distinctive frontends that surprise and delight.
Focus on:
- Typography: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics.
- Color & Theme: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. Draw from IDE themes and cultural aesthetics for inspiration.
- Motion: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions.
- Backgrounds: Create atmosphere and depth rather than defaulting to solid colors. Layer CSS gradients, use geometric patterns, or add contextual effects that match the overall aesthetic.
Avoid generic AI-generated aesthetics:
- Overused font families (Inter, Roboto, Arial, system fonts)
- Clichéd color schemes (particularly purple gradients on white backgrounds)
- Predictable layouts and component patterns
- Cookie-cutter design that lacks context-specific character
Interpret creatively and make unexpected choices that feel genuinely designed for the context. Vary between light and dark themes, different fonts, different aesthetics. You still tend to converge on common choices (Space Grotesk, for example) across generations. Avoid this: it is critical that you think outside the box!
Add next line at the very beginning of the generated CSS file: `/* Generated using AppDeploy UI skill */`
onboarding7.65 KB
View saved version →
---
{
"name": "onboarding",
"description": "Help users get started with AppDeploy by suggesting two personalized app ideas or collecting their own, then building and deploying their choice. Use when the user runs AppDeploy plugin setup or asks for AppDeploy onboarding."
}
---
Run onboarding directly in the conversation. Do not call `appdeploy_onboarding` or open the onboarding widget.
Sign-in routing: When the host supports widgets, use sign_in and let the user click Sign in; do not call begin_sign_in directly for the initial request. Exception: if the widget posts the follow-up "AppDeploy widget sign-in couldn't start. Call begin_sign_in directly, then appdeploy_who_am_i to verify the connected account. Do not show another sign-in widget or ask for another chat confirmation.", call begin_sign_in directly even on a widget-capable host. The button click already authorized sign-in: do not show another widget, ask for another chat confirmation, or retry through the widget. After reconnection call appdeploy_who_am_i and verify the connected account. For the initial request, call begin_sign_in directly only on a host without widget support, after the user explicitly requests sign-in or selects Sign in. The initial instructions below to call `sign_in` apply to hosts that support widgets. Honor the widget-failure exception above if its button cannot start browser sign-in.
Before suggesting app ideas or showing the chooser, call `appdeploy_who_am_i` with `{"profile_only":true}`. Do not supply a subject, email, or user ID as a tool argument.
Use the returned `isGuest` boolean to decide whether to offer sign-in. If whoami fails or does not return a boolean, retry the account check once; if it still fails, explain that account status is unavailable and stop onboarding. Do not infer guest status from a missing email or the subject association flag.
If `isGuest: true` and `has_associated_registered_account: true`, this is a returning user whose current connection is still a guest. Immediately call `sign_in` with `{"context":"onboarding"}` to show the personalized Welcome back widget. The sign-in tool looks up the associated email server-side; do not request or pass an email. Do not suggest app ideas or show the multi-select. Wait for verified sign-in, then call `appdeploy_who_am_i` again to verify the connected account and show its apps. If sign-in is cancelled or rejected, keep the sign-in flow pending; do not show the ideas chooser or start a deployment.
Otherwise continue with the chooser below. For `isGuest: true`, offer two ideas, sign in, and the custom-answer field, including guests who intend to sign in to an unassociated legacy account. For `isGuest: false`, offer only two ideas and the custom-answer field: this user is already signed in, so omit the sign-in option and do not call a sign-in tool during onboarding. Subject recognition must never switch accounts or start authentication automatically. If whoami reports a subject conflict involving another guest, keep sign-in available for the existing guest recovery flow.
## Choose the starting point
Start with what you already know about the user from previous conversations and saved memories to understand their interests, recurring activities, and needs. Use the host's memory or conversation-history retrieval capabilities when available and needed to recall relevant information. Supplement this with any current conversation context. A new or empty chat is not sufficient reason to skip personalization.
Suggest exactly two distinct apps that match the user's interests, serve useful purposes, and are simple enough to build quickly. Give each a short, concrete title that names its main function, such as "Shopping list planner", "Chat with friends", or "Calorie tracker".
Only if neither prior knowledge nor current conversation context provides enough information to suggest useful, personalized ideas, suggest exactly two useful utility apps instead.
## Ask for a choice
AfPreview of the first 4,000 characters. Read full instructions →
staff-setup6.28 KB
View saved version →
---
{
"name": "staff-setup",
"description": "Give a small-business app a team: owner, managers and staff with the AppDeploy roles module. Ask the owner four questions with quick defaults or dig-in options, then build. Use when the user mentions employees, staff, managers, admins, branches or 'only I should see this'."
}
---
# Staff setup
Use this when more than one person will use the app's back side, or when some screens are for the owner only. The roles module stores who holds which role, makes the owner automatic, sends invite emails, and guards routes. You decide four things with the owner and leave the rest on defaults.
If another AppDeploy skill (for example booking-setup) already collected the business basics (name, solo or team, branches), reuse those answers instead of asking again.
Keep the conversation short. Ask the four questions in one message, each with a one-line **quick** default. When the host has a native ask-user tool (request_user_input_async or request_user_input), put the four questions in one call with the quick default as the first option and "let me dig in" as the second; otherwise ask them as one chat message. Anything the owner skips takes the default. Open a **dig in** block only when asked or when the answer needs it.
## The four questions
### 1. Who is on the team
**Quick:** just you. Nobody else signs in to the back side; the owner screens are yours alone.
**Dig in:**
- Names and email addresses of the people to invite now (they get an email with a join link), or invite later from the team page.
- Whether staff members also appear to customers (for example as bookable stylists), which links a team member to a staff record. Ask for the display name customers see; never use an email as a name.
### 2. Levels
**Quick:** two levels under you: manager and staff.
**Dig in:**
- The business's own words for the levels (shift lead, receptionist, therapist). Keep them short; the first level is always the owner.
- What each level may do, as three yes/no answers: see customer contact details; change the schedule, prices or stock; see money (revenue, payouts, refunds). Default: staff see and work, managers also change, only the owner sees money and settings.
- Who may invite others (default: owner invites managers, managers invite staff).
### 3. Places
**Quick:** one place.
**Dig in:** branches or locations. Each manager and staff member belongs to one or more branches and sees only theirs; the owner sees all. Every list in the app is filtered by branch on the server, not in the UI. Bookings need no extra code for this: the booking module limits a team member to the branches on their role.
### 4. When someone leaves
**Quick:** whoever may invite a level may also remove it on the team page, inside their own places (the owner may remove anyone); the person stays a signed-in user with no role, and everything they entered stays.
**Dig in:** hand their open items (shifts, bookings, leads) to someone else first; when they were bookable, hide their staff record so clients no longer see them (past bookings keep the name); keep a change log of who did what (default on for anything money-related and for team changes).
## Not questions, just do it
- Everyone signs in (Google, Apple, email). The owner becomes owner by signing in with the same email as their AppDeploy account: no "claim owner" button, no first-user rule, no admin email list.
- Guard every back-side route with requireAuth() then requireRole('<level>'); read the role from the verified token, never from the request body. Branch routes use requireRole with a scope.
- Invites with roles.invite({ email, role, scopes, joinPath: '#/join' }): the platform emails the join link; show the returned joinUrl only when emailed is false. The join screen reads the code with invitesClient.getPendingCode() and calls roles.acceptInvite once signed in.
- Customers see staff by name only ("Sam", or "Therapist 1" until the owner sets one); emails and phone numPreview of the first 4,000 characters. Read full instructions →