This skill should be used when the user asks to "research camps", "find camps near me", "search for camps", "look up camp providers", "what camps are available", "compare camp options", "create camp provider files", "find day camps in [area]", or needs help discovering, evaluating, and documenting camp providers in their area. Creates structured provider markdown files in the research folder.
Researches local camp options and creates structured provider files for family planning and comparison.
/plugin marketplace add reggiechan74/cc-plugins/plugin install kids-camp-planner@cc-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples/boulderz-etobicoke.mdexamples/ymca-cedar-glen.mdreferences/provider-template.mdLocate research directory: Read .claude/kids-camp-planner.local.md to get the research_dir path (default: camp-research). All user data paths below are relative to this directory. The family profile is at <research_dir>/family-profile.md.
Discover, evaluate, and document camp providers for a family's area, creating structured provider files in the <research_dir>/providers/ directory. Each provider gets its own markdown file with standardized information for easy comparison. Providers are cross-referenced from period-specific schedule files (summer, March break, PA days).
Read the family profile from <research_dir>/family-profile.md to determine:
Use web search to find camp providers. Search in this order:
1. Municipal programs (best value):
2. Established organizations:
3. Private and specialty camps:
4. Niche and interest-based:
For each camp provider found, create a markdown file in <research_dir>/providers/ using the standard template.
File naming: Use kebab-case: provider-name.md (e.g., ymca-downtown.md, city-of-toronto-parks-rec.md)
Provider file template: Use the template at <research_dir>/templates/provider-template.md (seeded during setup from the plugin). The template includes sections for: basic information, distance & commute, programs offered, costs (with discount tracking), quality indicators, logistics, suitability rating, and notes.
For completed examples showing all fields filled in with realistic data, see <research_dir>/examples/ymca-cedar-glen.md and <research_dir>/examples/boulderz-etobicoke.md.
For the most promising providers, verify critical details:
If details cannot be confirmed via web search, note them as "needs verification" and suggest the user confirm by phone/email (offer to draft an inquiry email via the draft-email skill).
After researching multiple providers, generate a comparison table:
# Camp Provider Comparison - [Area]
| Provider | Ages | $/Day | $/Week | Before Care | After Care | Lunch | Distance | Rating |
|----------|------|-------|--------|-------------|------------|-------|----------|--------|
| YMCA Downtown | 4-12 | $56 | $280 | $10/day | $10/day | Pack | 3.2 km | Strong |
| City Parks Rec | 6-12 | $39 | $195 | $8/day | $8/day | Pack | 1.5 km | Strong |
| Science Camp | 7-12 | $85 | $425 | No | No | Incl | 8.1 km | Good |
Include daily rates ($/Day) alongside weekly rates for accurate partial-week and PA day costing.
Save this comparison to <research_dir>/providers/comparison-summary.md.
<research_dir>/templates/provider-template.md - Blank provider file template for quick copying (seeded during setup)<research_dir>/examples/ymca-cedar-glen.md - Completed example provider file (YMCA Cedar Glen, multi-program)<research_dir>/examples/boulderz-etobicoke.md - Specialty camp example (Boulderz Climbing, single-program)Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.