# Three Claude Code Skills, Yours to Fork

> A take-home pack from the Jack's Community case study walkthrough. Three skill files. Three customize prompts. One iteration log so you can see how `/taste` got fine-tuned to where it is now.

Each skill is a Markdown file Claude Code reads when you type the slash command. The files in this pack are templates. The leverage shows up after you fork them.

**Live deck:** https://case-study-jack-florian.pages.dev/

## What's in the box

```
skills/
├── README.md                 (this file)
├── pilot/
│   ├── README.md
│   ├── pilot.md              (the skill, genericized)
│   └── customize-prompt.md   (7 questions, paste into Claude Code)
├── 100x/
│   ├── README.md
│   ├── 100x.md
│   └── customize-prompt.md   (5 questions)
└── taste/
    ├── README.md
    ├── taste.md
    ├── customize-prompt.md   (6 questions)
    └── tuning-history.md     (how the skill learned what to look for)
```

## The three skills, one line each

- **`/pilot`** spawns a battle-tested project from a brain dump. Scaffold, build, screenshot-test, harden, deploy. Inherits structure from Jack's BLAST framework.
- **`/100x`** hires a parallel research team. Four to seven Opus agents, different lenses, synthesized findings, a red-team pass, a confidence gate.
- **`/taste`** runs a binary visual review on any HTML file or URL. Ten pass/fail evals plus a 34-principle constitution sweep.

## How to install (any one of them)

1. Pick the skill folder.
2. Open the README inside that folder. Read it once.
3. Copy the contents of `customize-prompt.md` into Claude Code, then paste the body of the skill file (`pilot.md` / `100x.md` / `taste.md`) underneath. Send.
4. Claude Code asks you 5 to 7 questions about your work. Answer them in plain language.
5. Claude Code writes the customized skill to `~/.claude/skills/{name}/SKILL.md` for you and confirms with a diff.
6. Type the slash command in any future session and it runs against your stack, your taste, your defaults.

## The recurring point

The skill file is a template. The customize prompt is where the leverage actually appears. Five minutes of setup buys hundreds of hours of compounded use later.

If you skip the customize step and just drop the raw file into your `~/.claude/skills/`, the skill will still run, but it will run against my opinions, my stack, my exemplars, my voice rules. That gets you maybe 30% of the value. The other 70% comes from the customize pass.

## Credit

`/pilot` is a fork of Jack's BLAST framework with my own additions for taste enforcement, screenshot QA, and post-deploy reflection. Credit where credit is due. The original BLAST is the spine. Everything else is layering.

`/100x` and `/taste` are mine, built from scratch and refined across 173 runs and 30+ validated wins / 40+ corrections respectively. The `taste/tuning-history.md` file shows the receipts.

## What done looks like for you

A listener of the Jack's Community interview should be able to:

1. Visit the deck.
2. Click a download chip for any of the 3 skills.
3. Get a folder with 3 or 4 files.
4. Read the README in 60 seconds and understand what they're getting.
5. Paste the customize prompt + skill into Claude Code.
6. Answer 5 to 7 questions about themselves.
7. End up with a working SKILL.md in their own `~/.claude/skills/` directory that codes for them, not me.

If any of those steps require effort you didn't sign up for, the package failed. Tell me where it broke. I'm at generuss.com.