The Skills Library.

You finally got the proposal layout, the font pairing, the email tone exactly right — and next week you’ll rebuild it from scratch. Not anymore. Type /save-template and your AI captures the finished result as a new named skill you can call up forever.

SKILL: Save Template
PURPOSE: Turn any finished result — a design, a document layout, a font
and color combo, an email format, a report structure, a workflow — into
a reusable skill with a custom name, so you never rebuild it again.

HOW TO INSTALL
Paste this into your AI's custom instructions, a Claude Project's
instructions, or the top of a working chat. From then on, the command
"/save-template" is live.

TRIGGER
When I type "/save-template" (or say "save this as a template"),
run the SAVE FLOW below. When I type "/use-template" or mention a saved
template by name, run the USE FLOW.

SAVE FLOW
1. Identify what to capture. Look at the most recent result we landed on
   together in this conversation (a design, a document, a piece of
   writing, a process, a set of settings). If it's unclear which result I
   mean, ask ONE question: "Save the [X] we just finished, or something
   earlier?"
2. Ask me for a name: "What should this template be called?" Suggest one
   short kebab-case option based on the content (e.g. "client-proposal",
   "weekly-crew-update", "brand-fonts"). Wait for my answer.
3. Extract the reusable DNA — not the one-off content. Capture:
   - Structure: sections, order, headings, length of each part
   - Style: fonts, colors (exact hex codes), spacing, sizes, tone of
     voice, formatting rules, anything I corrected you on along the way
   - Fixed parts: text or elements that should appear every time
   - Variable parts: the slots that change per use, written as
     [BRACKETED PLACEHOLDERS] with a one-line note on what goes there
   - Rules: the do's and don'ts I stated or implied while we iterated
4. Write the new skill in exactly this format:

   SKILL: [template-name]
   PURPOSE: [one sentence — what this produces and when to use it]
   TRIGGER: When I say "/use-template [template-name]" or "make me a
   [template-name]".
   INPUTS TO ASK FOR: [the variable slots, as a short numbered list]
   INSTRUCTIONS: [step-by-step: how to build the result so it matches
   the original exactly — structure, style rules, fixed parts]
   REFERENCE EXAMPLE: [the finished result we just made, trimmed to the
   essential shape, with variable parts bracketed]
   RULES: [the do's and don'ts]

5. Show me the finished skill in one copyable code block and say:
   "Saved. Paste this into your custom instructions or Project to keep
   it permanently. Call it any time with /use-template [name]."
6. Keep the skill active for the rest of this conversation so I can
   test it immediately.

USE FLOW
1. Find the named template (in this conversation or in my instructions).
2. Ask ONLY for the inputs listed under INPUTS TO ASK FOR — in one
   message, as a short numbered list. Don't ask for anything the
   template already fixes.
3. Build the result following the INSTRUCTIONS and RULES exactly. Match
   the REFERENCE EXAMPLE's shape. Don't "improve" the template unless I
   ask.
4. If I make a correction while using it, offer once: "Want me to update
   the [template-name] template with that change?"

RULES
- Never save one-off facts (a specific client's name, this week's
  numbers) as fixed parts — those are variable slots.
- Never lose exact values. Hex codes, font names, sizes, and word counts
  go in verbatim.
- One template per /save-template. If the result contains several
  reusable pieces, ask whether to split them.
- Keep every saved skill under 400 words so it stays easy to paste.