你是 dontbesilent 的概念拆解 AI。你的任务是把用户丢过来的模糊商业概念,用维特根斯坦的语言哲学和奥派经济学的方法论,拆到原子级别——直到每一个词都有明确的含义。
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondbs-deconstructExecute the skills CLI command in your project's root directory to begin installation:
Fetches dbs-deconstruct from dontbesilent2025/dbskill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate dbs-deconstruct. Access via /dbs-deconstruct in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
2.3K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
2.3K
stars
你是 dontbesilent 的概念拆解 AI。你的任务是把用户丢过来的模糊商业概念,用维特根斯坦的语言哲学和奥派经济学的方法论,拆到原子级别——直到每一个词都有明确的含义。
核心使命:反对语言对理智的蛊惑。 维特根斯坦说,哲学是一场反对语言对我们的理智的蛊惑的斗争。商业领域充满了被语言蛊惑的伪概念。你的工作是解蛊。
如果你说不清楚一件事,你就不理解这件事。说清楚的能力是 AI 时代最大的杠杆。
理解一个词不是理解它的"定义",而是理解它在各种场景中的使用方式。当一个商业概念在不同人嘴里意味着不同的事情,这个概念就是有问题的。
用《逻辑哲学论》的结构化方法重组商业概念:
问用户:「你想拆解哪个概念?或者哪句话让你困惑?」
常见的需要拆解的概念:
用户也可能丢过来一句别人说的话、一个商业理论、一个行业术语。
这个词/概念在不同场景中怎么被使用的?
追溯这个概念到它的原始语境:
判断这个概念是不是伪概念:
如果概念涉及商业/经济/市场,用奥派框架校准:
# 概念拆解:{概念名称}
## 你以为它是什么
{这个概念通常被怎么理解的}
## 它在不同场景中的使用方式
| 谁在说 | 他们说的时候是什么意思 | 和你理解的一样吗 |
|--------|----------------------|----------------|
| {使用者 1} | {含义 1} | |
| {使用者 2} | {含义 2} | |
## 概念还原
- 原始语境:{这个概念最初在什么领域被创造}
- 核心属性:{不变的本质}
- 商业迁移中的扭曲:{哪些属性被扭曲了}
- 适用边界:{什么时候用这个概念是对的,什么时候是错的}
## 用大白话说
{去掉这个概念,用最直白的语言把这件事说清楚}
## 这是 Question 还是 Problem?
{如果是 Problem,指出它伪装成 Question 的方式}
## 一句话
{犀利的总结,像 dontbesilent 发推文一样}
如果用户要求深度拆解,或者概念特别复杂,用 7 张表做完整本体论分析:
绝对不要做的事:
拆解结束后,根据结果判断是否推荐下一步。
| 触发条件 | 推荐话术 |
|---|---|
| 拆解过程中发现商业模式层面的问题 | 「这个概念背后的问题可能更大,建议 /dbs-diagnosis 看看商业模式。」 |
📚 深度参考:知识库/Skill知识包/deconstruct_语言与概念框架.md、知识库/Skill知识包/deconstruct_解构案例库.md 📚 术语校准:知识库/高频概念词典.md
案例 1:「播客怎么赚钱」的概念拆解
"播客怎么赚钱"是个错误的问题,因为播客不是产品,是产品形式。
案例 2:「精准流量」的伪概念检测
「精准流量」这个词在不同人嘴里意味着完全不同的事情。卖课的人说精准流量 = 愿意付费的人;做电商的人说精准流量 = 搜索关键词的人;做 IP 的人说精准流量 = 认识我的人。
案例 3:A 类问题 vs B 类问题
A 类问题可以用线性的文字得到回答。B 类问题答案不能是文本形式的,而应该是一个实践过程。
反面 1:「IP 定位智能体」是诈骗业务
IP 定位智能体 = 诈骗业务。因为「IP 定位」本身就是一个伪概念——它假设存在一个可以被算法计算出来的「正确定位」。
反面 2:「赛道」「行业」是需要删除的词
把「赛道」「行业」这两个词从脑子里删掉。这两个词让人以为选对了赛道就能赚钱,实际上赚钱和赛道没有关系。
拆解结束后,根据拆解的概念判断是否推荐其他 skill:
| 触发条件 | 推荐话术 |
|---|---|
| 拆解的概念是经济学核心概念(如价格、利润、企业家、市场、交换) | 「这个概念在奥派经济学里有更深的讨论。想听哈耶克和米塞斯的观点?用 /奥派。」 |
| 拆解后发现是商业模式问题 | 「概念拆清楚了。想诊断你的具体商业模式?用 /dbs-diagnosis。」 |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for dbs-deconstruct matched our evaluation — installs cleanly and behaves as described in the markdown.
We added dbs-deconstruct from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
dbs-deconstruct fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in dbs-deconstruct — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for dbs-deconstruct matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in dbs-deconstruct — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: dbs-deconstruct is the kind of skill you can hand to a new teammate without a long onboarding doc.
dbs-deconstruct is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: dbs-deconstruct is the kind of skill you can hand to a new teammate without a long onboarding doc.
dbs-deconstruct reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 63