MicroMagnet Factory — Terminology
MicroMagnet-Specific Terms
| Term | Means | NOT |
|---|---|---|
| MicroMagnet | A free AI product that solves one tiny problem completely | Lead magnet, freebie, opt-in, download, resource |
| Splinter | The tiny persistent problem the MicroMagnet solves — describable in one sentence, 1-3 hours without AI, core skill action under 2 minutes | Pain point, challenge, obstacle (too vague) |
| Factory | This kit — the production system that stamps out MicroMagnets | Framework, methodology, system |
| Pre-AI precedent | The paid product/service this MicroMagnet replaces | Competitor, alternative |
| The Gap | The adjacent problem the MicroMagnet deliberately leaves unsolved — the one the CTA destination addresses | The limitation, the downside, the caveat |
| Nano | A single-step extraction of the MicroMagnet's highest-value move, shipped as a standalone asset for DM drops and re-engagement. No CTA. Works without running the parent MicroMagnet. | Teaser, preview, sampler |
| Niche version | The splinter framed for one specific practice type | Example, persona, case study |
| Universal version | The same splinter translated for any sub-$500K solo professional services practitioner | Generic framing, broad audience |
| Both positioning | A MicroMagnet built for both Niche and Universal framings in one pass, producing doubled outputs | A/B test, variation |
| Audience-stage match | The check that the target practitioner, at their actual stage, feels this splinter today — not as a future problem | Persona fit, audience targeting |
| Source-driven intake | Starting from specific source material (conversation, memo, op-ed) instead of audience theory | Content mining, extraction |
| Mode (source mode) | One of four source classifications: client conversation, own thinking, op-ed, undistilled content | Type, category |
| Layer separation | The rule that shipped MicroMagnets strip internal scaffolding (Core Principle, Rules section, embedded QC, What Makes This Different) — those stay in the kit, not in the prospect-facing skill | Simplification, trimming |
Inherited Terms (from Skill Build Kit)
| Term | Means | NOT |
|---|---|---|
| Skill | A Claude .md file the user uploads and runs | App, tool, bot, GPT, template, prompt |
| Run | What the user does with the skill | Use, try, test, execute |
| Paste | How the user provides input | Upload, import, enter, input |
| Install | Adding the skill to Claude (one-time) | Set up, configure, onboard |
| Trigger phrase | The natural language command that activates the skill | Prompt, command, instruction |
| Core principle | The one operating rule that drives output quality (lives in the Kit, not in the shipped skill) | Philosophy, approach, methodology |
| Practice | The user's business | Company, firm (OK occasionally), business (too generic) |
| Practice owner | The person we're talking to | Founder, entrepreneur, solopreneur, business owner |
Skill File Voice (Prospect-Facing Shipped Output)
The shipped skill file speaks to the prospect in plain, direct language. It is not an internal tool document.
- Use "you" and direct commands. "Paste your..." / "Get back..."
- Concrete outcomes, not process language. "Turn your rough description into a posted-ready LinkedIn About section" — not "The skill evaluates the input and generates an optimized output."
- Active, short sentences that land on the concrete thing.
- Match the voice anchor files named in Config.
- Rules-oriented where Claude is the audience (in The Method section) — constraints stated as rules.
- No hedging — "Do this" not "You might want to consider."
The Method section is instructional to Claude. The surrounding framing is instructional to the prospect. Keep them distinct.
Quick-Start Guide Voice
Same as Skill Build Kit:
- Casual and brief
- Step-numbered
- Assumption-free
- Tips from real testing
Forbidden Constructions
Skill File (prospect-facing framing)
| Don't Write | Write Instead |
|---|---|
| "This skill will help you..." | State what it does: "Produces a [output] from [input]" |
| "The skill will evaluate your input..." | "Paste your [input]. Get back [output]." |
| "Consider including..." | "Include [thing]." |
| "For best results..." | State the rule directly |
| "The skill leverages..." | State the mechanism directly |
Quick-Start Guide
| Don't Write | Write Instead |
|---|---|
| "Welcome to your new skill!" | "You just got a free Claude skill. Here's how to use it." |
| "For optimal performance..." | "[Practical tip]." |
| "Please ensure you have..." | "What You Need: [list]" |
Output (What the Skill Produces)
| Don't Write | Write Instead |
|---|---|
| "Not because X. Because Y." | Kill the reversal. State the point directly. |
| "Here's the thing." | Cut it. Start with the thing. |
| "[Statement]. And that's [judgment]." | Cut the judgment. The statement stands alone. |
| Forced parallelism | Let each line carry its own weight. |
| Three-beat lists for rhythm | Vary the count. Pick the right number, not the rhythmic one. |
| Mirrored two-beats ("X fast. Y faster.") | Pick one beat. Land on the stronger word. |
| Adverbs | Cut them. The verb does the work. |
| Numbers as words | Use digits. "3" not "three." |
Trademark Rule
- Framework name gets ™ on first use and on every heading where it appears. "The 3-Touch Reset™," "The Wrong-Fit Filter™," "The Carry Map™."
- Step names inside the framework do NOT get ™. "The Triage," "The Reason Check," "The Scope Test" — plain.
This keeps the visual signal of ownership on the framework name without over-claiming on every sub-component.