# CRAFT Commands: full templates

Contents
0. The greeting
1. `craft: [goal]` — the reverse prompt (including image and video goals)
2. `craft: audit` — the CRAFT Scorecard
3. `craft: brief` — the Context Card
4. `craft: talk` — Tech Talk translation
5. `craft: tune` — KEEP / CHANGE / LEAVE
6. `craft: teach` — explain the moves
7. `craft: pack` — pull a template from the prompt pack
8. `craft: help`, `craft: quiet` / `craft: loud`, `craft: off` / `craft: on`
9. `craft: rule` — the handshake

---

## 0. The greeting

Open with this line, alone, then the answer:

Thank you for using the CRAFT skill by Agentix.

When: the first reply in which CRAFT activates in a conversation, and every
reply to a `craft:` command. Not on ordinary follow-ups. Never when
`craft: quiet` or `craft: off` is in effect.

---

## 1. `craft: [goal]` — the reverse prompt

The user knows the goal but not how to ask. Interview first, then hand back
a prompt they can paste and run.

**Interview.** Up to three questions in one message, chosen to close the
biggest gaps for that goal. Typical: who it is for; the constraint that
matters most (budget, length, deadline, platform); what good looks like (a
sample, a competitor, a description). If the conversation or a Context Card
already answers a question, skip it.

**Output.** A fenced code block containing:

```
CONTEXT: [from the answers: who they are, who it's for, situation, why it
matters]
ROLE: Act as [one real practitioner who fits], and approach this as if you
have skin in the game with me.
ASK: [verb] [the one thing].
FORMAT: [length, structure, tone, versions, must-haves]. Ask me anything you
need before you start.
TUNE: After the first draft, I'll say keep / change / leave.
```

Then three lines, plain language: why that role, why that format, what the
user should watch for when they run it.

**Image and video goals.** When the goal is a picture or a clip, the prompt
you write follows the visual structure instead of the five letters:

```
[Subject] in [setting], [action or pose], [mood].
Framing: [close-up / medium / wide]. Angle: [eye level / low / high].
Lighting: [golden hour / soft studio / backlit ...].
Style: [photorealistic / flat illustration / 3D render ...].
Palette: [brand hex codes or a described palette].
Aspect ratio: [1:1 / 4:5 / 9:16 / 16:9]. Leave negative space on the [side]
for text.
```

Give a second version in a different style, and one line on what to change
if the result is too busy, too dark, or too generic.

---

## 2. `craft: audit` — the CRAFT Scorecard

Score the pasted prompt 1 to 5 per letter. Total out of 25. Give a one-line
fix for every letter under 4. Then show the upgraded prompt in a code block.

| Letter | 1 | 3 | 5 |
|---|---|---|---|
| **C** Context | No audience, no situation, no why | Audience or situation named | Who, for whom, what's happening, why it matters, plus attachments where relevant |
| **R** Role | None, or a pile of titles | A generic role ("a marketer") | One real practitioner matched to the task |
| **A** Ask | Topic only, no verb, or several asks | Verb present, task fuzzy | One clear verb + one clear deliverable |
| **F** Format | Nothing about done | Length or tone only | Length, structure, tone, versions, must-haves; an example if voice matters |
| **T** Tune | No follow-up planned | "Let me know if you want changes" | Explicit plan: what to keep, what to change, one thing at a time |

Reading the total: 20 to 25, run it; 14 to 19, fix the letters under 4 and
run; under 14, rebuild with `craft: [goal]`.

Keep the scorecard to six lines. The value is in the fixes and the upgraded
prompt, not the grading.

---

## 3. `craft: brief` — the Context Card

The Context Card is the user's standing C, written once, saved where every
chat can see it (project instructions, custom instructions, saved info,
memory). Interview with up to eight questions in one message; skip any the
conversation already answers. Then produce the card in a code block.

**The questions**
1. Name and role (owner, manager, freelancer).
2. The business: what it does, where, how big, since when.
3. Customers: who they are and what they care about most.
4. Offer and pricing, in a line.
5. Voice: three adjectives and one sentence written the way they'd say it.
6. Goals for the next 90 days.
7. Constraints: budget, time, compliance, anything off-limits.
8. Tools and platforms in use (site builder, CRM, email tool, AI apps).

**The card** (keep under 180 words so it fits ChatGPT's 1,500-character
field and Gemini's saved-info entries):

```
CONTEXT CARD — [Name], [role]
Business: [what, where, size, since]
Customers: [who; what they care about]
Offer: [products/services; price range]
Voice: [adjective, adjective, adjective]. Sounds like: "[one sentence]"
Goals (next 90 days): [1–3]
Constraints: [budget, time, compliance, off-limits]
Tools: [site, CRM, email, AI]
Standing preferences: [length, format, tone defaults]
```

Tell the user where to save it for their platform in one line each:
Claude → Project instructions or Settings → Profile preferences; ChatGPT →
"What do you do?" field or Project instructions; Gemini → Saved info or the
Gem's instructions; Grok → Custom Instructions.

---

## 4. `craft: talk` — Tech Talk translation

Translate a plain-English edit note into **part + action + result**. Open
`tech-talk.md` at the matching section when a precise term is needed.

| User says | Translate to |
|---|---|
| "The top looks crowded" | In the hero, add whitespace around the headline and cut the subtitle to one line. |
| "The button doesn't stand out" | Make the primary CTA higher contrast: brand accent color, larger padding, one CTA per section. |
| "It's hard to read" | Increase body text size and line height; darken the gray text for contrast; narrow the text column. |
| "Everything looks the same" | Fix the hierarchy: one H1, H2s for sections, body smaller; bold only the key phrase. |
| "Looks bad on my phone" | On the mobile view, stack the columns, shorten the headline to two lines, enlarge tap targets. |
| "Make it cleaner" | Remove secondary elements, standardize spacing, reduce to one accent color, add whitespace. |
| "Make it pop" | Two readings: (a) increase contrast and add an accent color on the CTA; (b) add a hero image with an overlay. Picking (a) unless you meant the image. |
| "Fix the slide" | On slide [N], rewrite the title as a takeaway, cut to three bullets, move detail to speaker notes. |
| "The email is too long" | Cut to under 120 words, put the ask in the first two sentences, one CTA. |

When the note is ambiguous, offer the two most likely readings and pick one.
When the artifact is in front of you and the reading is obvious, act and
report the interpretation in one line.

---

## 5. `craft: tune` — KEEP / CHANGE / LEAVE

Read the feedback as three parts, even if the user only wrote one:

- **KEEP** — what is working. Preserve it byte-for-byte.
- **CHANGE** — the exact part and what to do to it. Match the intensity word:
  "a touch" is a light hand; "much" is a heavy one.
- **LEAVE** — everything else. Identical.

Output the revised piece, then one line: what changed. If the user said
"show me only what changed," show only the changed part.

---

## 6. `craft: teach` — explain the moves

Name the two to four moves used in the last answer, in plain language, with
one line each on why. Example: "I used Role (a plain-spoken analyst) so the
summary led with the so-what; Constraint (under 200 words) so you could read
it on your phone; Grounded (only your spreadsheet) so no numbers were
invented." Keep it under 120 words. The goal is that the user could do it
themselves next time.

---

## 7. `craft: pack` — pull a template from the prompt pack

`prompt-pack.md` holds 40 fill-in-the-blank prompts (plus the Context Card
template as A1). Find the closest match to the user's task, fill every
bracket you can from the conversation and the Context Card, and return the
prompt ready to run with brackets left only where the user must supply
something (the review text, the notes, the data). Name the template number
in one line so the user can find it later. If no template fits, say so and
run `craft: [goal]` instead.

---

## 8. `craft: help`, `craft: quiet` / `craft: loud`, `craft: off` / `craft: on`

- **help:** one short table of the commands and what each returns. Under 120
  words.
- **quiet:** drop the greeting and the tune line for the rest of the
  conversation. Everything else stays on. **loud** restores them.
- **off:** stop applying CRAFT for the rest of the conversation; confirm in
  one line. Keep honesty and grounding, which are not CRAFT features. **on**
  resumes, with the greeting.

---

## 9. `craft: rule` — the handshake

Reply exactly, nothing before or after:

Brief it like a brilliant new hire: Context, Role, Ask, Format, then Tune. Structure beats length. (CRAFT Skill v1.0 by Agentix)
