The CRAFT Framework: Creating AI Skills That Compound

craft-framework

How to build reusable AI skills that get smarter over time — turning one-off prompts into permanent capabilities.

C — Capture What You Need AI to Do

Define the task precisely. Vague goals make vague skills.

A skill starts with a clear problem statement. Not ‘help me with content’ but ‘take a news article URL, extract the key facts, and draft a 280-character tweet thread with a hook, 3 insights, and a CTA.’ The more precise your definition, the more reliable the skill. Document the full scope: What are all the possible inputs? What does a perfect output look like? What are the edge cases? What should the skill never do? Think of it like writing a job description for a very literal employee — if you leave something ambiguous, they’ll interpret it their own way.

Example

Skill definition template:
Name: Newsletter Quick Take Writer
Input: A news article URL + optional angle/spin
Output: 80-120 word summary with: headline, 2-3 sentence take, source attribution
Constraints: No speculation, no editorializing beyond the provided angle, always link to source
Edge cases: If URL is paywalled → use headline + available preview text. If article is > 3 months old → note the date prominently.

Pro Tip: Test your definition by explaining it to someone unfamiliar with the task. If they ask clarifying questions, those are gaps in your skill definition that need to be filled.

R — Research Best Practices

Study how experts do the task manually. Find the gold standard you’re replicating.

Before building a skill, study how the best humans do the task. If you’re building a skill to write LinkedIn posts, study the top 10 LinkedIn creators in your niche. What patterns do they use? What makes their hooks work? What’s their typical structure? Read documentation for any APIs or tools your skill will interact with. Understand the data formats, rate limits, and common pitfalls. If your skill generates emails, research email best practices — subject line length, preview text optimization, CTA placement. This research phase is where you collect the examples, templates, and rules that will make your skill exceptional instead of generic.

Example

Research checklist for a 'social media post writer' skill:
— Analyze 20 high-performing posts in the niche (save as examples)
— Document the hook patterns that get engagement (questions, bold claims, stories)
— Note platform-specific rules (X: 280 chars, LinkedIn: 3,000 chars, no hashtag spam)
— Identify what bad posts look like (save as negative examples)
— Review any brand voice guidelines or style guides

Pro Tip: Save your research as a reference document that lives alongside the skill. When you refine the skill later, this research gives you a baseline to return to.

A — Architect the Skill File

Structure your prompt with clear sections: context, instructions, examples, guard rails, output format.

A well-architected skill file has distinct sections that serve different purposes. Think of it like building a house — you need a foundation (context), walls (instructions), furniture (examples), safety features (guard rails), and a floor plan (output format). Use clear headers and formatting. The AI reads your skill file the same way a new employee reads a training manual — clear structure helps it follow instructions accurately.

Example

Skill file structure:
---
name: quick-take-writer
description: Writes newsletter quick takes from news URLs
---
# ROLE
You are a tech newsletter editor writing for a non-technical audience.

# PROCESS
1. Fetch the article content
2. Identify the single most newsworthy fact
3. Write headline (8 words max)
4. Write take (80-120 words)
5. Add source attribution

# EXAMPLES
[Good example here]
[Bad example here]

# GUARD RAILS
- Never speculate beyond what the article states
- Never use 'game-changing' or 'revolutionary'

# OUTPUT FORMAT
**[Headline]**
[Take]
Source: [publication]

Pro Tip: Version your skill files. Add a date or version number. When you make changes, you can always roll back to a version that worked if the new one regresses.

F — Feed It Examples and Edge Cases

Show the AI what great looks like — and what bad looks like. Examples beat instructions.

Examples are the most powerful tool in skill design. A single good example communicates more than a paragraph of instructions. Include 2-3 examples of ideal output and 1-2 examples of what to avoid (with explanations of why they’re bad). Edge cases are where skills break. What happens when the input is unusually long? Unusually short? In a different language? Missing key information? Formatted differently than expected? For each edge case, provide explicit instructions on how to handle it. Update your examples over time. When the skill produces exceptional output, add it to the examples. When it fails, add that failure (and the correction) as a negative example. Your skill gets smarter with every update.

Example

Example section of a skill:

GOOD EXAMPLE:
Input: [article about Apple launching a new chip]
Output: **Apple's New M5 Chip Targets AI Workloads**
Apple announced the M5 processor today, designed specifically for on-device AI tasks. The chip reportedly handles large language models 3x faster than the M4 while using 40% less power. This matters for anyone running local AI tools...
Source: The Verge

BAD EXAMPLE (and why):
'Apple just dropped a GAME-CHANGING new chip!!'
→ Why it's bad: Hype language, all caps, exclamation marks, no substance.

Pro Tip: The ‘golden ratio’ for examples: 3 positive examples showing range (different topics, different tones, different lengths), and 2 negative examples showing the most common failure modes.

T — Test, Break, and Refine

Throw weird inputs at it. Find where it fails. A skill isn’t done until it handles the unexpected.

Testing a skill means deliberately trying to break it. Give it inputs you didn’t design for. Feed it a 10,000-word article when you designed for 500-word ones. Give it an article in French. Give it a URL that 404s. Give it a topic outside its domain. See what happens. Keep a testing log: input, expected output, actual output, pass/fail. When something fails, diagnose why and update the skill file. Did it need a new guard rail? A better instruction? An example for that edge case? Make the fix, then test again. Refinement is ongoing, not one-time. Every time you use the skill in production, pay attention to output quality. When it slips, diagnose and update. After 10-20 refinement cycles, your skill will handle virtually anything you throw at it.

Example

Testing protocol:
Round 1: Happy path — 5 normal inputs you expect the skill to handle
Round 2: Edge cases — short input, long input, missing data, weird formatting
Round 3: Adversarial — inputs designed to confuse (ambiguous topics, conflicting info)
Round 4: Regression — re-run Round 1 to make sure fixes didn't break anything

Log format:
Input | Expected | Actual | Pass/Fail | Fix Applied

Pro Tip: Schedule quarterly skill reviews. Re-read the skill file with fresh eyes. You’ll spot instructions that made sense when you wrote them but are actually unclear or contradictory.

Key Takeaways

  • The framework: The CRAFT Framework — a step-by-step system you can apply immediately
  • Start small: Pick one task and apply the first step today
  • Compound effect: Each step builds on the last — the system gets more powerful with use
  • Works everywhere: Apply with ChatGPT, Claude, Gemini, or any AI tool
  • All frameworks: See our complete Framework System for the full AI mastery journey

Frequently Asked Questions

Do I need technical skills to use this framework?

No. Every step is designed for non-technical people. The examples use plain English and the tools recommended all have free tiers you can start with today.

Which AI tool should I use with this framework?

Any of them. The framework is tool-agnostic — it works with ChatGPT, Claude, Gemini, and any other AI assistant. Start with whichever you’re most comfortable with.

How long does it take to see results?

You’ll see improvement on your first use. The compound effect — where results get dramatically better — typically kicks in after 10-20 applications as your lessons file and examples accumulate.

Can I combine this with other Beginners in AI frameworks?

Yes — they’re designed to work together. See our complete framework system for how STACK, BUILD, ADAPT, THINK, CRAFT, and CRON form a full AI mastery journey.

Is this framework free?

The article and methodology are completely free. We also offer the frameworks as downloadable PDF guides with additional templates and worksheets.

How do I build a reusable AI skill or Custom GPT?

Use the CRAFT Framework: Capture what you need AI to do (precise task definition), Research best practices (study how experts do it manually), Architect the skill file (structure with Role, Process, Examples, Guard Rails, Output Format), Feed it examples and edge cases (show good AND bad output), and Test, break, and refine (deliberately try to break it). The skill file template with clear sections is what separates a reliable skill from a fragile one.

Free Download: Free AI Guides

Download our free, beautifully designed PDF guides to ChatGPT, Claude, Gemini, and Grok — plain English, no fluff.

Download Free →

How do I create a Claude Project that improves over time?

The CRAFT Framework teaches you to build AI skills that compound. The key is the ‘Feed It Examples’ step — every time your skill produces great output, add it as a positive example. Every time it fails, add the failure and correction as a negative example. After 10-20 refinement cycles, your Claude Project handles virtually any input you throw at it because it has seen and learned from real production data.

The The CRAFT Framework was developed by James Swierczewski at Beginners in AI. For more frameworks and practical AI guidance, subscribe to our free daily newsletter.

Sources

Want the full framework system?

Get all 6 frameworks as downloadable PDF guides from our free community, or explore each one on our frameworks page.

Get free AI tips delivered daily → Subscribe to Beginners in AI

You May Also Like

Sources

This article draws on official documentation, product pages, and industry reporting. Specific sources are linked inline throughout the text.

Last reviewed: April 2026

Get Smarter About AI Every Morning

Free daily newsletter — one story, one tool, one tip. Plain English, no jargon.

Free forever. Unsubscribe anytime.

Discover more from Beginners in AI

Subscribe now to keep reading and get access to the full archive.

Continue reading