菜单
Generate and review documentation for competition organizers using Diataxis framework. Use when writing docs for organizer workflows like creating competitions, managing divisions, scheduling heats, handling registrations, entering results, or managing volunteers/judges.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | competition-organizer-docs |
| description | Generate and review documentation for competition organizers using Diataxis framework. Use when writing docs for organizer workflows like creating competitions, managing divisions, scheduling heats, handling registrations, entering results, or managing volunteers/judges. |
Generates Diataxis-compliant documentation for WODsmith competition organizers.
Who they are: CrossFit gym owners, event directors, competition coordinators. Time-constrained, varying technical comfort, may run 1-2 events/year (casual) or 10+ (professional).
Documentation needs by experience:
| Level | Primary Need | Doc Types |
|---|---|---|
| First-time | "How do I even start?" | Tutorials |
| Experienced | "How do I do X efficiently?" | How-to guides |
| Power user | "What are the exact options?" | Reference |
REQUIRED: Before writing organizer docs:
skills_use(name="documentation")documentation/references/REQUIRED: Before writing docs, load the relevant reference:
| If documenting... | Load this reference |
|---|---|
| Create, Edit, Settings, Delete competition | references/competition-setup.md |
| Registrations, Divisions, Pricing, Athletes | references/athlete-management.md |
| Events, Schedule, Heats, Results, Scoring | references/event-operations.md |
| Volunteers, Judges, Rotations | references/volunteer-coordination.md |
| Revenue, Sponsors, Series | references/business-operations.md |
Journey 1: First-Time Organizer (11 steps) Create competition → Set divisions → Add events → Configure scoring → Set pricing → Open registration → Process registrations → Schedule heats → Recruit volunteers → Event day ops → Publish results
Journey 2: Event Day Operations Check-in athletes → Assign heats → Enter results → Handle disputes → Publish live scores
Journey 3: Post-Competition Finalize results → Export data → Track revenue → Thank sponsors → Archive competition
# Documentation request
type: documentation-request
persona: organizer
workflow: <workflow-name>
doc_type: tutorial | how-to | reference | explanation
context:
route: <route-path>
complexity: low | medium | high | very-high