Vertical Fitness
Domain-knowledge pack for fitness & wellness (boutique studios, gyms, coaches, on-demand brands) — the membership vocabulary, non-obvious billing/booking rules, and retention realities a builder must know so fitness products aren't speced naive. Covers the four products this niche ships (class-booking, coaching, churn-prevention, on-demand-video), how they wedge against Mindbody / PushPress / Zen Planner / Wodify / WellnessLiving, and the must-model entities (membership with freeze, recurring class template, waitlist, no-show policy, access tier). Applied by architect/pm during spec authoring
Install
npx skills add jeremybrasher/grokbot-skills --skill vertical-fitnessgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/vertical-fitness ~/.claude/skills/vertical-fitnessPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Fitness & wellness — spec it like a studio bills and books Boutique studios, gyms, coaches, on-demand brands. Members on recurring plans, classes with finite capacity, retention won or lost on attendance. A builder who models this as "events + tickets" ships something no studio owner will run their business on — because the hard parts are *billing* and *waitlists*, not the calendar. This skill is the domain briefing so the spec is right before code starts. ## 1. Domain vocabulary (know these or look naive) - **Class pack vs unlimited membership vs drop-in** — three distinct products. A **pack** is N prepaid classes that decrement (10-class pack); an **unlimited membership** is a recurring plan (often monthly auto-renew) with no per-class deduction; a **drop-in** is a single paid visit. The schema must hold all three, not collapse them into "credits". - **Recurring billing / auto-renew** — memberships rebill on a cycle (monthly is the norm) until cancelled. This is the revenue engine and the hardest thing to get right (see §2). - **Waitlist** — a full class has an ordered queue; when a spot opens (someone late-cancels), the system **auto-promotes** the next person and notifies them. Core, not optional. - **Late-cancel / no-show fee** — cancelling inside the policy window (e.g. <12h) or not showing forfeits the class (pack decrements) or charges a fee. The policy *is* the booking discipline.
Details
- Skill name
vertical-fitness- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/vertical-fitness/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Vertical Fitness skill do?
Domain-knowledge pack for fitness & wellness (boutique studios, gyms, coaches, on-demand brands) — the membership vocabulary, non-obvious billing/booking rules, and retention realities a builder must know so fitness products aren't speced naive. Covers the four products this niche ships (class-booking, coaching, churn-prevention, on-demand-video), how they wedge against Mindbody / PushPress / Zen Planner / Wodify / WellnessLiving, and the must-model entities (membership with freeze, recurring class template, waitlist, no-show policy, access tier). Applied by architect/pm during spec authoring
How do I install the Vertical Fitness skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill vertical-fitness. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Vertical Fitness popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
A11y Implementation Guide
39lionelsimai/claude-skills-collection
Implement accessibility. TRIGGERS - Use when user needs help with a11y-implementation-guide related tasks.
Accessibility Audit
39lionelsimai/claude-skills-collection
Audit workplace accessibility for compliance. TRIGGERS - Use when user needs help with accessibility-audit related tasks.
Wireframe Spec
48sethdford/claude-skills
Specify wireframe layouts with content priority, component placement, and annotation.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.