菜单
Documentation guidance for competition athletes and volunteers in WODsmith. Use when writing, reviewing, or improving athlete-facing documentation including registration, scheduling, workout viewing, leaderboards, check-in, and volunteer coordination.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | athlete-docs |
| description | Documentation guidance for competition athletes and volunteers in WODsmith. Use when writing, reviewing, or improving athlete-facing documentation including registration, scheduling, workout viewing, leaderboards, check-in, and volunteer coordination. |
Documentation guidance for the athlete persona in WODsmith competition platform.
Who they are: CrossFit athletes registering for and participating in competitions, and volunteers helping at events.
Key differences from organizers:
| Aspect | Athletes | Organizers |
|---|---|---|
| Interaction | Consumer (read-heavy) | Producer (write-heavy) |
| Complexity | Simple workflows | Complex multi-step setup |
| Discovery | High (browsing, exploring) | Low (knows what they need) |
REQUIRED: Before writing athlete docs:
skills_use(name="documentation")REQUIRED: Before writing docs, load the relevant reference:
| If documenting... | Load this reference |
|---|---|
| Registration, Division selection, Confirmation | references/registration-journey.md |
| Schedule, Heats, Workouts, Check-in | references/competition-day.md |
| Leaderboard, Scores, Final standings | references/results-tracking.md |
| Volunteer signup, Credentials, Assignments | references/volunteer-journey.md |
Journey 1: Discovery to Registration Find Competition → Explore Details → Register → Confirm
Journey 2: Pre-Competition Prep Check Schedule → View Workouts → Plan Strategy
Journey 3: Competition Day Check-in → View Heat Schedule → Track Scores
Journey 4: Post-Competition View Results → Compare Rankings → Share
Journey 5: Volunteer Experience Sign Up → Get Assignment → Event Day
| Route | Auth | Primary Doc Type |
|---|---|---|
/c/[slug] | No | N/A (entry point) |
/c/[slug]/register | Yes | Tutorial / How-to |
/c/[slug]/volunteer | No | Tutorial / How-to |
/c/[slug]/workouts | No | Reference |
/c/[slug]/schedule | No | How-to |
/c/[slug]/leaderboard | No | How-to / Tutorial |
/my-schedule | Yes | How-to |
Alchemy IaC patterns for deploying TanStack Start apps to Cloudflare Workers with PlanetScale databases via Hyperdrive. Use when setting up new TanStack Start projects, configuring Alchemy deployments, working with PlanetScale/Drizzle migrations, local development with Cloudflare bindings, or deploying to custom domains.
Guide for writing integration tests with Vitest and Testing Library. Use when testing multi-component workflows, database interactions, React components with context providers, or full user flows. Covers the Testing Trophy philosophy (integration > unit), factory patterns for test data, MSW for network mocking, async testing patterns (waitFor, findBy), and custom render with providers. Use this for tests that cross multiple modules or layers of the application.
Handle local database schema changes with Drizzle and PlanetScale. Use when making schema changes to src/db/schema.ts, adding/modifying database tables or columns, or when asked about database migrations. Covers the push-based local development workflow and when to generate migrations.
TanStack Start server-only patterns using createServerOnlyFn and cloudflare:workers env access. Use when: accessing Cloudflare environment variables (APP_URL, STRIPE_SECRET_KEY, etc.), creating server-only utility functions, working with Stripe or other server-only APIs, or when you need to ensure code only runs on the server and throws if called from client. Covers createServerOnlyFn vs createServerFn differences, env access patterns, and centralized server-only utilities.
Look up claim URLs for placeholder users created via manual registration. Use when needing to find the sign-up claim link for a specific email address, debug claim token issues, or verify claim tokens exist in local KV. Triggers on "claim URL", "claim token", "claim link", "placeholder user sign-up link", or requests to find the registration invite link for an email.
Store, search, and manage team memory from AI coding sessions. Use /remember to save observations (conventions, gotchas, debugging tips, architecture decisions, workflows). Use /recall to search memories by semantic query. Use /feedback to rate memory quality (helpful/harmful/irrelevant). Triggers on any request to save, recall, search, or rate team knowledge.