Detected promise
Claude Power-User Framework: 25 Essential Terms + When to Use Them (No Comment/DM Needed)
Reconstructed contract
framework
Below is a self-contained framework that replaces the typical “comment SYSTEME to get the guide” gate. It gives you a working vocabulary of 25 Claude-related concepts (plus practical rules for choosing the right mode), and 3 plug-and-play systems for freelancers: (1) a weekly content engine, (2) a brand-consistent visual pipeline, and (3) a lightweight launch machine. This resource is generated from the pasted post context (no live web research), so names/features may vary by plan or UI—use it as an operational playbook, not a UI map.
Resource without ritual
The promised resource, no comment required
A. The 25-Term Glossary (grouped by what problem it solves)
Note: Different apps/platforms label features differently. Treat these terms as functional concepts.
1) Model (e.g., Opus / Sonnet): The specific “brain” you select. Use larger models for complex reasoning and critical copy; smaller/faster ones for drafts, formatting, and iteration.
2) Token: The unit of text cost/limit. Your biggest levers: shorten inputs, reuse context via projects, and request structured outputs.
3) Context Window: How much text the model can “hold” in a single conversation. Use summaries, outlines, and attachments strategically.
4) System Instruction: Highest-priority instruction (rules, tone, boundaries). Use to lock style guidelines, compliance rules, and “definition of done.”
5) Developer Instruction: Process and tool-use guidance (how to work). Use to enforce steps like “ask 3 clarifying questions before drafting.”
6) User Prompt: The task request. Keep it specific with constraints, audience, format, length.
7) Role Prompting: Assigning a role (“act as…”). Useful for perspectives and specialized checklists—don’t rely on it for factual authority.
8) Prompt Template: A reusable prompt with variables. Your fastest route to consistent outputs.
9) Few-shot Examples: Showing 1–5 examples of the desired output. Best for style mimicry and formatting consistency.
10) Constraints: Hard requirements (word count, forbidden claims, tone, reading level). Put these early and repeat at the end.
11) Project: A persistent workspace for a domain (client, brand, product). Use to centralize specs, tone, FAQs, and reusable assets.
12) Memory: Long-lived preferences or facts (when available). Use sparingly: stable preferences only (voice, role, repeating constraints), not transient tasks.
13) Knowledge Base / Files: Documents you attach or store for reference. Use to ground outputs in your sources (brand guide, offer, testimonials).
14) Retrieval: Pulling relevant snippets from your stored docs. Use when you have many documents; ask for citations/quotes from the files.
15) Citations (internal): Pointing to where in your provided docs a claim came from. Ask for “quote + file name + section” to reduce hallucinations.
16) Artifact: A structured, reusable output (doc, table, code, spec, template). Use when you want something you can copy/paste into tools.
17) Structured Output (JSON/CSV): Machine-friendly format. Use for automation, content calendars, CRM imports.
18) Tool Use / Actions: Having the assistant call tools (where supported). Use for workflows; otherwise simulate with checklists.
19) Workflow: A repeatable sequence of steps (inputs → processing → outputs). Use to reduce tokens and rework.
20) Agent / Assistant: A persona with a bounded job (e.g., “Content Strategist,” “Editor,” “Repurposer”). Use multiple agents to reduce cognitive load.
21) Extended Thinking: Slow/reflective mode for planning, tradeoffs, and complex synthesis. Use for strategy, positioning, system design; avoid for simple formatting.
22) Critic Pass / Self-Review: A second pass focused on errors, clarity, and constraints. Always request for important deliverables.
23) Verification / Reality Check: The step where the model flags uncertain claims and asks for sources. Use for anything factual, legal, medical, financial.
24) Temperature (Creativity): Higher = more variation; lower = more deterministic. Use low for brand consistency; higher for ideation.
25) Guardrails: Safety and policy boundaries + your own constraints (no competitor bashing, no made-up case studies). Use to protect brand trust.
Quick decision rule:
If you need strategy or synthesis → Extended Thinking + Artifact.
If you need repeatability → Prompt Template + Few-shot examples + Structured output.
If you need consistency across weeks/clients → Project + constraints + critic pass.
If you need accuracy from your materials → Files/Knowledge base + retrieval + internal citations.
B. The “Right Tool, Right Moment” Decision Framework (fast routing)
Use this 6-question router before you type a long prompt.
1) What is the deliverable?
Doc/page/email/thread? → Artifact (formatted sections)
Calendar/database? → Structured output (CSV/JSON)
Reusable workflow? → Prompt template + checklist
2) What matters most?
Accuracy to your assets → Attach files + ask for quotes/citations
Speed/volume → Smaller/faster model + strong template
Differentiation/strategy → Stronger model + extended thinking
3) How stable is the context?
Stable (brand, offer) → Put in Project + (optional) Memory
One-off campaign → Keep in the prompt + attach only needed docs
4) How risky is the output?
High risk (claims, pricing, legal) → Verification step + “flag uncertainties” + require sources
Low risk (captions, formatting) → Iterate quickly
5) How many variants do you need?
Many variants → Ask for a matrix (angles × hooks × CTAs)
One polished piece → Ask for 2 drafts + a final merged version
6) What’s the stop condition?
Define “Definition of Done”: length, CTA, audience, tone, proof points, banned phrases, formatting.
Copy-ready routing prompt:
"I need a [DELIVERABLE]. Priority is [accuracy/speed/originality]. Use my constraints below and produce an Artifact with [FORMAT]. If any claim is uncertain, flag it and ask me for a source. Constraints: [LIST]. Definition of done: [LIST]."
C. System #1 — The 60-Min Weekly Content Engine (7 days from one brief)
Goal: Generate a week of content without wasting tokens.
Inputs (15 min):
Audience: who, what they want, what they fear
Offer: what you sell + one core promise
Proof: 3 testimonials, 3 results, 3 differentiators
Topics: 3 pains, 3 desires, 3 objections
Workflow (30 min):
Step 1 — Angle bank (10 min)
Ask for 30 angles in a table:
Columns: Angle, Core insight, Hook line, Ideal format (post/carousel/email), CTA.
Step 2 — Build the weekly plan (10 min)
Ask for a 7-day calendar:
Day, objective (awareness/consideration/conversion), topic, hook, structure, CTA, repurpose notes.
Step 3 — Draft packages (10 min)
For each day, request:
LinkedIn post (120–220 words)
5 headline options
1 strong CTA variant
3 repurpose snippets (tweet-size)
Quality control:
Run a Critic Pass: clarity, specificity, proof, reading ease, banned phrases.
Copy-ready master prompt (paste as a template):
"You are my Content System. Use my brand and offer details below. Produce:
(1) 30 angles table,
(2) a 7-day calendar,
(3) drafts for Day 1–7 with 5 hooks each,
(4) a critic pass checklist with fixes.
Constraints: no vague claims, no invented metrics, no ‘game-changing’, keep tone [X], include 1 concrete example per post.
My details: Audience=[…], Offer=[…], Proof=[…], Differentiators=[…], Topics=[…]."
D. System #2 — Brand-Consistent Visuals (without “random AI style drift”)
If your tools support image generation: the core is a strict brand spec + a reusable layout system.
Brand Visual Spec (fill this once):
Brand adjectives (3): [e.g., minimal, premium, friendly]
Color palette (HEX): Primary [#…], Secondary [#…], Accent [#…]
Typography: Headline [font], Body [font], fallback [font]
Layout rules: margin/padding, corner radius, icon style
Imagery: photo vs illustration, grain/no grain, lighting style
Do-not list: forbidden colors, gimmicks, clutter, stock clichés
Reusable layout system (pick 3 templates):
Template A — “Big claim + 3 bullets” (square)
Top: hook (6–10 words)
Middle: 3 bullets (max 7 words each)
Bottom: logo/handle
Template B — “Process diagram” (landscape)
5-step horizontal flow with icons
Template C — “Checklist card” (story)
Title + 7 checkboxes
Prompt structure for visuals:
1) “Design brief” (brand spec + layout template)
2) “Content” (the exact text to place)
3) “Rendering constraints” (clean grid, high contrast, readable text, no extra words)
Copy-ready prompt (works even if you’re generating via another tool):
"Create a [FORMAT: 1080x1080] graphic using this Brand Visual Spec: [paste]. Use Template A. Text to include exactly:
Headline: ‘[hook]’
Bullets: ‘[b1]’; ‘[b2]’; ‘[b3]’
Footer: ‘[handle]’
Constraints: minimalist, high legibility, consistent spacing, no extra elements, no additional text."
E. System #3 — The “Launch-in-a-Day” Mini Machine (emails + posts + page)
Goal: Deploy a simple launch sequence with coherence across assets.
Inputs:
Offer: promise, price (or “book a call”), guarantees, constraints
Audience: who, pain, desired outcome
Proof: 3 proof points (no invented numbers)
Objections: top 5
Outputs (one coherent set):
1) Sales page (simple):
Hero (promise + who it’s for)
Problem agitation
Solution mechanism (your method)
What’s included
Proof
FAQ (objections)
CTA
2) Email sequence (5 emails):
E1: Announcement + story
E2: Problem deep dive + new belief
E3: Proof + case/story
E4: Objections + FAQ
E5: Last call (ethical urgency)
3) Social assets:
1 long-form LinkedIn post
1 carousel outline (8 slides)
10 short hooks
Copy-ready launch prompt:
"Build a coherent launch kit in one voice. Output as an Artifact with sections for: sales page, 5-email sequence, 1 LinkedIn post, 8-slide carousel outline, 10 hooks. Use only the proof points I provide; do not invent metrics. Audience=[…]. Offer=[…]. Proof=[…]. Objections=[…]. Tone=[…]. CTA=[…]."
F. Token-Saving + Quality Pattern (the practical stuff people skip)
Token savers:
Ask for an outline first, then approve, then draft.
Reuse a Project brief instead of re-pasting brand info.
Request tables/JSON for bulk ideation; expand only the winners.
Cap outputs: “Give me 10, not 50.”
Quality boosters:
Require examples: “Include 1 concrete example per section.”
Add a critic pass: “List the top 7 weaknesses and rewrite.”
Add a compliance pass: “Flag any claim that needs sourcing.”
Two-pass template:
Pass 1: "Propose structure + key points + assumptions/questions."
Pass 2: "Draft + critic pass + final revision."
G. (Optional) Infographic Spec You Can Generate as a One-Page Reference
If you want a single-image cheat sheet, generate a 1-page infographic with:
Title: “Claude Power-User: 25 Terms + When to Use Them”
Four quadrants: (1) Models & Cost, (2) Context & Persistence, (3) Outputs & Automation, (4) Quality & Safety
Each term: 1-line definition + “Use when…” micro-tag
Footer: “Router: Deliverable → Priority → Risk → Done criteria”
Text blocks (copy-ready):
Quadrant 1 (Models & Cost): Model, Opus, Sonnet, Token, Context Window, Temperature
Quadrant 2 (Context & Persistence): Project, Memory, Knowledge Base/Files, Retrieval, Citations, Guardrails
Quadrant 3 (Outputs & Automation): Artifact, Structured Output, Prompt Template, Few-shot Examples, Workflow, Tool Use/Actions
Quadrant 4 (Quality & Safety): Extended Thinking, Critic Pass, Verification/Reality Check, Constraints, System Instruction, Developer Instruction