# Customize /pilot for Your Workspace

Paste this entire file into Claude Code. Then paste the contents of `pilot.md` directly below it. Send.

---

I'm forking the `/pilot` skill from Russ Gardner's Jack's Community case study pack. The skill body is below this prompt. Before installing it, I need you to ask me 7 questions and customize the skill so it builds for me, not for him.

## Questions to ask (one at a time, wait for my answer before moving to the next)

1. **What do you sell?** One paragraph in plain language. What does your business / freelance practice / agency / personal project actually deliver? Don't list services, describe the outcome.
2. **Who buys it?** Target audience profile. Industry, company size, role, what's broken in their day that you fix.
3. **Three websites whose taste you respect.** URLs only. What do you find beautiful, well-built, or aesthetically right? These will anchor my design seed.
4. **Two websites whose taste you can't stand.** URLs. What looks generic, dated, AI-slop, or just wrong? These become anti-references the skill avoids.
5. **Your one-line promise to clients.** The sentence you'd put on the back of a business card. If you don't have one, the closest thing you'd say in an elevator.
6. **Default tech stack.** Astro / Next.js / SvelteKit / WordPress / Webflow / something custom? Pick one. The skill defaults to this stack unless a brief explicitly says otherwise.
7. **Default deploy target.** Cloudflare Pages / Vercel / Netlify / Railway / something else? The skill auto-deploys to this target on `npm run deploy` or equivalent.

## What to do with my answers

After I've answered all 7, do the following:

1. **Read the skill body below** (everything after the `---` separator at the bottom of this prompt).
2. **Replace every `{{PLACEHOLDER}}`** with my answer. Specifically:
   - `{{TECH_STACK_DEFAULT}}` becomes my answer to question 6, with a one-sentence justification I can read later. Example: "Astro + Tailwind v4 + Cloudflare Pages, picked because it's static-first, near-zero hosting cost, and the build is fast."
   - `{{BUILD_ROOT}}` defaults to `~/code` unless I gave you a different path. Show me the assumed value and let me override.
   - `{{DEPLOY_COMMAND}}` becomes the canonical deploy command for my target from question 7. Example for Cloudflare: `npx wrangler pages deploy . --project-name {project-slug}`. Pick the one that matches my answer.
3. **Replace every `> FILL IN:`** block with content derived from my answers. Specifically:
   - The "Voice / Brand Constraints" block: synthesize a starter list from my one-line promise and target audience. Things like banned phrases ("don't say 'innovative'"), tone ("terse declarative"), or content rules ("every section needs one specific number"). Keep it short, 3-5 rules max. Tell me to expand it as I gather corrections.
   - The "Project Directory" block: use my BUILD_ROOT plus the slug pattern. Show the exact path.
4. **Embed my taste anchors.** Add a section near the top called "Design References" with my 3 respected URLs and 2 anti-references, formatted so the skill knows to fetch them on first run. Like this:

```markdown
## Design References

**Anchor URLs (positive):**
- {URL 1 from question 3}
- {URL 2 from question 3}
- {URL 3 from question 3}

**Anti-references (avoid these patterns):**
- {URL 1 from question 4}
- {URL 2 from question 4}

When `/pilot` runs without a brain dump that explicitly names a design seed, the skill should default to fetching these URLs and synthesizing palette / type / motion vocabulary from the positive anchors. Avoid anything resembling the anti-references.
```

5. **Embed my one-line promise** in the description metadata near the top of the file, so the skill carries my voice.

6. **Save the customized skill** to `~/.claude/skills/pilot/SKILL.md`. Create the directory if it doesn't exist. If a file is already there, write the new version to `~/.claude/skills/pilot/SKILL.md.new` and tell me to compare before overwriting.

7. **Show me the diff** between the template and my customized version. Highlight the placeholders that got replaced and the new sections you added. Confirm I can run `/pilot` in any future Claude Code session.

## Bias toward action

If any of my answers are vague (which they will be), make a sensible call and tell me what you assumed. Don't loop on clarifying questions. The customize step is supposed to take 5 minutes total, not 30.

---

(Skill body follows below the next separator. Read it, then run the steps above.)

---