This skill should be used when the user asks to "draft an email to a camp", "write an inquiry email", "email camp provider", "write registration email", "draft waitlist follow-up", "write cancellation email", "email about allergies", "contact camp about special needs", or needs help composing emails to camp providers for inquiries, registration, waitlist follow-ups, special needs requests, dietary accommodations, or cancellations. Provides email templates and personalization using the family profile.
Drafts personalized camp emails using family profiles and provider details for inquiries, registrations, and special requests.
/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/sample-inquiry-email.mdreferences/email-templates.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.
Draft professional, personalized emails to camp providers. Pull family details from the profile and provider details from research files to create complete, ready-to-send emails. Save drafts to <research_dir>/drafts/ for review before sending.
Before drafting, read:
<research_dir>/family-profile.md) for children's details, special needs, contact info<research_dir>/providers/[provider].md) for camp-specific details, contact email, program namesIdentify the purpose and use the appropriate template structure:
| Email Type | When to Use |
|---|---|
| Inquiry | Asking about program details, availability, pricing |
| Registration | Requesting enrollment or registration information |
| Waitlist follow-up | Following up on waitlist status |
| Special needs / dietary | Informing about allergies, medical needs, accommodations |
| Schedule / logistics | Questions about hours, pickup/dropoff, what to bring |
| Cancellation | Requesting cancellation or date change |
General email guidelines:
Save drafts to: <research_dir>/drafts/[type]-[provider].md
Six templates are available covering all common camp communication scenarios. The inquiry template is shown below as a representative example. For all other templates (registration, waitlist follow-up, special needs/dietary, cancellation, logistics inquiry), see references/email-templates.md.
Subject: Inquiry about [Program Name] for Summer [Year]
Hi [Camp Name] team,
I'm looking into summer camp options for my [son/daughter] [Child Name],
who is [age] years old (entering Grade [X] in September). We're interested
in the [Program Name] program.
I'd appreciate information on:
- Availability for the week(s) of [dates]
- Registration process and any deadlines
- Daily rates available? (for partial weeks or PA day drop-ins)
- [Any specific questions based on research gaps]
[If applicable: We're also considering enrollment for a second child,
[Child 2 Name], age [X]. Do you offer sibling discounts?]
Thank you for your time. Looking forward to hearing from you.
Best regards,
[Parent Name]
[Phone number - optional]
When drafting emails, apply these personalization rules:
Save each draft as a markdown file:
# Email Draft: [Type] - [Provider Name]
**To:** [Email address from provider file]
**Subject:** [Subject line]
**Date drafted:** [Today's date]
**Status:** Draft - ready for review
---
[Email body]
---
**Notes:**
- [Any context for the user about why certain details were included]
- [Reminders about attachments needed, e.g., allergy action plan]
references/email-templates.md - All email templates: registration, waitlist follow-up, special needs/dietary, cancellation, logistics inquiryexamples/sample-inquiry-email.md - Complete personalized inquiry email exampleExpert 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.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
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.