算法艺术创作
algorithmic-art
通过代码和可调参数创作生成艺术与交互式视觉效果。
thought-leadership-writer【设计与创意】Write long-form thought leadership articles, opinion pieces, industry POV essays, and CEO/founder bylines using the Made to Stick SUCCESs framework (Chip and Dan Heath). Use when the user asks for a long-form article, executive byline, opinion piece, industry POV, manifesto, "explain our point of view on X", or wants to publish an authority-building …
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Writes long-form opinion pieces that establish authority and get shared. Uses the Made to Stick SUCCESs framework (Chip & Dan Heath, Made to Stick) to ensure every piece is memorable, not just well-written.
The core insight from Made to Stick: Ideas fail to stick not because they're wrong, but because they're abstract, predictable, and forgettable. The SUCCESs framework systematically fixes this. A thought leadership piece that checks all 6 conditions will be remembered, quoted, and shared. One that checks none will be read once and forgotten.
Apply all 6 conditions to every piece. Each one is a checklist item, not optional.
| Letter | Condition | The test | How to apply |
|---|---|---|---|
| S | Simple | Can you express the core idea in one sentence? | Find the lead - the single most important insight. Strip everything that doesn't serve it. |
| U | Unexpected | Does the piece break a pattern the reader expected? | Open by violating an assumption. Say the thing the reader didn't see coming. |
| C | Concrete | Are there specific people, places, objects, and numbers? | Replace abstract claims with tangible examples. "Activation rate stuck at 52%" not "low engagement". |
| C | Credible | Why should anyone believe this? | Use statistics, named examples, or an "anti-authority" (a customer or peer, not just the brand). |
| E | Emotional | Does the reader care? | Tap the "self-interest" trigger (this affects you) or the "identity" trigger (this is about who you are). |
| S | Stories | Is there a narrative? | Use a story - even a short one - to make the idea travel. People remember stories, not arguments. |
Made to Stick names one root cause for unstuck ideas. Once you know something, you cannot imagine not knowing it, so you write the summary of your insight rather than the thing that produced it. Every element of SUCCESs is a countermeasure to that one failure.
Practical test before you draft: hand the thesis sentence to someone outside the company. If they need a follow-up question to understand what it claims, the curse is active and the piece will read as abstract to everyone but the author.
Credible is the element most often skipped in B2B writing, usually because the author has no study to cite. The Heaths list several sources of credibility that are not statistics. Pick one deliberately rather than defaulting to a number you would have to invent.
| Technique | What it is | Use it when |
|---|---|---|
| Anti-authority | A source credible precisely because they have no incentive to say it: a customer, a skeptic, a competitor conceding a point | The brand claiming it would read as self-serving |
| Testable credential | An invitation for the reader to check for themselves: "look at your own funnel between step 6 and step 11" | The reader has the data on hand |
| Vivid detail | Specific, checkable texture that signals first-hand knowledge | The claim rests on the author having actually been there |
| Human-scale statistic | A number rescaled to something a person can picture | You have a real figure but it is too large to feel |
| Sinatra test | One example so strong it settles the question by itself | You have one undeniable case rather than many weak ones |
Rule: a human-scale statistic still needs a real underlying number. Rescaling is a presentation move, not a licence to estimate one. If there is no number, use anti-authority or a testable credential instead.
| Plot | Shape | Best for a piece that argues |
|---|---|---|
| Challenge | Someone faces an obstacle bigger than them and overcomes it | This is hard but doable, here is the proof |
| Connection | Someone bridges a gap between people or groups | The problem is really a misalignment between two functions |
| Creativity | Someone solves a problem in a way nobody expected | The conventional method is not the only method |
Pick the plot from the argument, not from whichever anecdote is nearest. A Challenge plot attached to a Creativity argument makes the piece feel effortful rather than surprising.
Read knowledge/brand/voice.md, knowledge/markets/positioning.md, knowledge/markets/competitors.md. Stop if voice is missing: "Run /brand-context first."
A weak thesis kills everything downstream. Before writing, run it through three tests:
Test 1 - Specificity. Can it be argued with?
Test 2 - Contestability. Would a reasonable person disagree?
Test 3 - Alignment. Does it reinforce knowledge/markets/positioning.md?
Score the thesis before proceeding. One point each:
| Point | Condition |
|---|---|
| 1 | A competent person in this industry could disagree with it in one sentence |
| 2 | It names a specific mechanism, metric, step or population, not a trend |
| 3 | The author has first-hand material that supports it, not just an opinion |
| 4 | It moves knowledge/markets/positioning.md forward rather than sideways |
Threshold: write at 3 or 4. At 2, propose 2-3 sharper versions and rewrite. At 0 or 1, stop and say the piece should not be written yet, because a thesis nobody can disagree with produces an article nobody can remember, and no amount of SUCCESs work at later steps rescues it.
If the thesis fails any test, propose 2-3 sharper versions before proceeding.
Complete this before writing:
SUCCESs pre-write for: [Working title]
S - SIMPLE (the core)
One-sentence core idea (not the title - the insight):
What gets cut if we had to strip 50% of the piece:
U - UNEXPECTED (the pattern break)
What does the reader expect to hear on this topic?
What's the unexpected angle or opening move?
First sentence candidate (the pattern-breaker):
C - CONCRETE (the specifics)
3 specific examples, numbers, or named cases to use:
1.
2.
3.
Any abstract claims that need a concrete replacement?
C - CREDIBLE (the proof)
Credibility technique chosen (anti-authority | testable credential | vivid detail |
human-scale statistic | Sinatra test):
Primary credibility source (stat, study, customer, or self-experience) and where it came from:
Anti-authority candidate (a peer, customer, or skeptic who validates the point):
What the reader might object to, and the counter:
E - EMOTIONAL (why they should care)
Self-interest angle: how does this affect the reader directly?
Identity angle: what does believing this say about who they are?
The "curse of knowledge" check: are we assuming context the reader doesn't have?
S - STORIES (the narrative)
Plot type chosen (challenge | connection | creativity), and why it matches the argument:
Opening story candidate (specific scene, not a parable):
Supporting anecdote (from knowledge/content-library/ or user input):
The moment of realization (the turn in the narrative):
Use this structure. Each section maps to SUCCESs elements.
## 1. Hook (150-200 words) [U + S + stories]
Open with the UNEXPECTED move. Options:
- A specific scene ("Last Tuesday, a Head of Growth showed me her dashboard...")
- A counterintuitive stat ("The average B2B trial has 11 onboarding steps. The best ones have 4.")
- A direct challenge to conventional wisdom ("Most companies are measuring the wrong metric.")
Rule: The thesis should appear by the end of the hook, or at the start of section 2.
Never open with "In today's..." / "As we all know..." / "It's no secret that..."
## 2. What everyone believes (200-300 words) [Credible]
Steelman the conventional wisdom. Be generous. Don't strawman.
- "The standard advice is X, and it's not wrong. It's just incomplete."
- Name real examples of the conventional approach being applied
## 3. Why it's wrong (or incomplete) (300-500 words) [Unexpected + Concrete + Credible]
The UNEXPECTED argument. Specific evidence.
- Name the cracks in the conventional approach
- Use concrete examples (named companies, specific numbers, real situations)
- "We've seen this in [X] clients. The pattern is..."
- The anti-authority: quote a peer, customer, or skeptic - not just the brand
## 4. The new model (400-600 words) [Simple + Concrete + Emotional]
The author's POV. This is where the SIMPLE core lives.
- Define new terms if needed (give the idea a name it can travel with)
- Show how the new model works with a CONCRETE example
- Tap EMOTIONAL: "Here's why this matters for you specifically"
- Include a framework, visual, or 3-part structure the reader can remember and repeat
## 5. What to do about it (200-400 words) [Concrete + Emotional + Stories]
Practical application. Not abstract implications.
- 3 specific actions the reader can take
- At least one they can take today or this week
- One supporting story from knowledge/content-library/ if available
## 6. Close (100-150 words) [Simple + Unexpected]
The quotable line. One sentence the reader will screenshot.
- Restate the core insight in its sharpest form
- Call to something: a belief, an action, a question
- The ending should feel inevitable in hindsight, not obvious from the start
Apply voice from knowledge/brand/voice.md. Rules:
S - Simple: [ ] Core idea expressible in one sentence
[ ] No paragraphs that don't serve the core idea
U - Unexpected: [ ] Opening breaks a pattern or assumption
[ ] Quote the sentence that contradicts what section 2 said everyone believes.
If no sentence does, the piece agrees with the conventional wisdom it set up
C - Concrete: [ ] At least 3 specific examples, each traceable to `knowledge/` or user input. Any example you could not source is marked `[SOURCE NEEDED]` in the draft, never written as fact
[ ] No abstract claim left without a concrete anchor
C - Credible: [ ] Primary credibility source present (stat, case study, or experience)
[ ] At least 1 "anti-authority" (peer/customer validates, not just the brand)
E - Emotional: [ ] Piece taps self-interest ("this affects you") or identity ("this is about who you are")
[ ] No "curse of knowledge" - doesn't assume context reader doesn't have
S - Stories: [ ] At least 1 narrative (specific scene with a beginning, middle, and turn)
[ ] Close has a line worth quoting or sharing
Sourcing: [ ] Every statistic, quote, company name and result is listed with its source.
Anything without one is `[SOURCE NEEDED: ...]` or `[NEEDS INPUT: ...]`
[ ] Every external link was fetched in this session and resolved
[ ] The credibility technique named in the pre-write is the one actually used
Voice checks:
[ ] Thesis appears before word 300
[ ] Voice matches knowledge/brand/voice.md
[ ] Zero em dashes and zero en dashes
[ ] Zero occurrences of: "In today's rapidly evolving landscape", "It's no secret
that", "At the end of the day", leverage, unlock, robust, seamless
[ ] Word count within 10% of the target
output/thought-leadership/<DD-MM-YYYY>-<slug>.md with frontmatter:
---
format: thought-leadership
framework: made-to-stick-success
thesis: <one-sentence claim>
author: <name or role>
target: <publication>
words: <count>
success-score: S/U/C/C/E/S checked
created: DD-MM-YYYY
---
/linkedin-post)| Most common failures | Fix |
|---|---|
| Piece is technically accurate but boring | Missing U (unexpected) and S (stories) |
| Piece makes big claims nobody believes | Missing C (credible) |
| Piece is smart but nobody shares it | Missing E (emotional) - reader doesn't see why it matters to them |
| Piece is interesting but hard to remember | Missing S (simple) - no single core idea |
| Piece is full of jargon and abstractions | Missing C (concrete) - no specific examples |
Do not draft, or do not hand over, and say which condition fired.
[NEEDS INPUT: the real figure].[APPROVAL NEEDED: <name>] and say it must not publish unconfirmed.knowledge/markets/positioning.md. Flag the conflict and ask which
one is meant to move. Publishing against your own position confuses the market twice.knowledge/markets/competitors.md. Route to the user before it goes anywhere.Ranked worst first. The first four block handover.
/linkedin-post for the short version, and for the distribution post once this publishes/newsletter-writer when the piece is an issue of a recurring publication with a fixed spine/content-writer when the piece is shorter than 1200 words or is really a marketing asset/copy-review to grade and tighten a draft the user already wrote/positioning-doc when the thesis keeps conflicting with the company's stated position/messaging-framework when the new model needs to become language the whole company uses/competitor-analyst before any piece that makes factual claims about named competitors/pr-pitch-writer when the goal is placement in a trade publication rather than owned publishing/content-repurposer after publishing, to turn the piece into posts, a talk and a thread/brand-context first, whenever knowledge/brand/voice.md does not exist yetThese are real limitations of this skill, and none can be settled from knowledge/. Ask the
user, or emit [NEEDS INPUT: <what>].
knowledge/ is current, and whether its original source still says
what the note says it said. Second-hand statistics drift, and this piece will be the third
hand.