deconstruct

自媒体 / 新媒体 思考方法 爆款拆解对标结构 1 文件 EN 原文

逆向拆成功作品。直接用于我们对标爆款

Reverse-engineer why a finished piece of work succeeds and extract what transfers to your own — rules, a checklist, and a first exercise.

说明语言:英文

来源coolTheWorldevolution-skills ↗ 查看原文件 ↗版权归原作者,请遵循原仓库许可
安装
npx skills add https://github.com/coolTheWorld/evolution-skills --skill deconstruct

需要已安装 skills CLI。也可以直接从源仓库 clone。

在星云中查看 ↗
SKILL.md 原文

Admiring a finished work teaches nothing; the lessons sit in the choices its maker made and never wrote down. Deconstruct the exemplar to recover those choices, then keep only what is transferable to the user's own work.

Write in the language the user writes in.

1. Take in the exemplar and the goal

The user supplies two things: the exemplar (a product page, webpage, plan, process doc, dashboard, or other finished work) and what they want to learn from it. If either is missing, ask one question for it and stop.

When the exemplar is a URL, fetch it with WebFetch and work from the fetched page; when the fetch returns nothing usable, ask the user to paste the content and stop.

Hold the learning goal as the filter for every later step: the same page deconstructed for "how it sells" and for "how it organises information" yields different rules.

Done when the full exemplar is in hand and the learning goal is stated in one sentence you can test a rule against.

2. Name the problem it solves

Open with one sentence: what problem this work solves, and for whom. Describe the problem from the audience's side ("lets a first-time visitor decide in thirty seconds whether the tool fits"); "a SaaS landing page" names a category, not a problem.

Done when the sentence names the problem and the person who has it, and contains no feature of the artifact.

3. Deconstruct why it works

Reverse-engineer the exemplar through four lenses, each backed by something you can point to in the artifact:

Where a lens needs context the artifact does not carry (who made it, what the ordinary version looks like), look it up with WebSearch rather than guess.

Done when each of the four lenses has a finding tied to evidence from the exemplar, and the quality-gap lens names the ordinary version it was measured against.

4. Sort transferable from case-specific

Sort the findings into patterns that transfer and details that fit only this case. A pattern is transferable when it would still hold with a different audience, medium and subject; a detail is case-specific when it depends on this maker's brand, resources, domain or moment.

Name the case-specific details as fully as the transferable patterns; they tell the user what to leave out of their own version.

Done when every finding from step 3 sits in exactly one of the two piles.

5. Deliver

Deliver in this order: the problem sentence, the deconstruction under its five lenses (four from step 3, the sort from step 4), and then:

Done when the output runs in that order, the rules number three to five, every checklist item is checkable, and the exercise names one rule and one concrete thing to make.

同类技能
cross-domainfact-checkfirst-principlesmin-experimentsteelmantwo-axis-researchtwo-layer-explain
本页内容来自开源项目 coolTheWorld, 版权归原作者所有。
本站仅作技能索引与分享,所有 Skill 版权归其原作者所有。