cglt2026opc/opc-skills / skills/ai-super-individual
ai-super-individual
Verified基于《AI超级个体》帮助用户推进职业转型、专业能力变现、副业验证与一人公司经营。用于 OPC 能力诊断、定位、商业验证、获客交付及行动复盘,按需调用书中 21 个实战模块,并查找菜根智库资料、开展 OPC 市场/案例/政策研究与报告生成、城市/社区政策匹配及申报准备;支持职场AI任务设计、工作流与岗位助手配置、可复用资产沉淀。 支持GEO可见度自诊、私域销售漏斗、标准品封装与经营收入结构复盘。
references/modules/case-explorer/references/cases.json
View on GitHub{
"source": "AI超级个体-正文.pdf(2026-07-17 作者样)",
"cases": [
{
"id": "case-01",
"section": "1.1.1",
"chapter": "第一章 觉醒",
"title": "AI 到底替代了谁",
"keywords": ["AI替代", "技术判断", "问卷架构", "人机协作"],
"scenario": "执行能力被 AI 加速后,如何把价值转向业务理解、抽象、架构与协调",
"takeaway": "AI 优先替代可标准化执行,人的价值转向判断、组织与交付。"
},
{
"id": "case-02",
"section": "1.2.1",
"chapter": "第一章 觉醒",
"title": "很多人不是不努力,而是走错了路",
"keywords": ["职业路径", "能力贬值", "转型", "选择"],
"scenario": "努力投入旧能力却回报下降时,重新选择能力升级方向",
"takeaway": "方向错误时,增加投入只会放大路径依赖。"
},
{
"id": "case-03",
"section": "2.1.4",
"chapter": "第二章 蓄力",
"title": "我的三次职业转型,从技术人到全栈产品经理",
"keywords": ["职业转型", "产品思维", "全栈PM", "复合能力"],
"scenario": "技术执行者通过多次角色升级形成产品与业务判断",
"takeaway": "转型不是抛弃主业,而是在主业深度上叠加产品、业务与协作能力。"
},
{
"id": "case-04",
"section": "2.4.1",
"chapter": "第二章 蓄力",
"title": "0 代码一周上线,先做出看得见的结果",
"keywords": ["速赢", "零代码", "高频痛点", "可见成果"],
"scenario": "用短周期成果快速建立组织信任",
"takeaway": "先解决一个高频痛点,用可见结果赢得继续推进的空间。"
},
{
"id": "case-05",
"section": "2.4.2",
"chapter": "第二章 蓄力",
"title": "预算为 0,独立交付完整项目",
"keywords": ["完整闭环", "零预算", "AI补位", "量化价值"],
"scenario": "资源有限时借助 AI 独立承担需求到上线的完整链路",
"takeaway": "不必样样精通,但要能扛住闭环并对结果负责。"
},
{
"id": "case-06",
"section": "3.1.1",
"chapter": "第三章 赋能",
"title": "从 1 个到 6 个数字员工",
"keywords": ["数字员工", "企业赋能", "工作流", "AI落地"],
"scenario": "把个人提效扩展为多个可落地的组织工作流",
"takeaway": "AI 落地的关键是把真实需求翻译成可执行流程。"
},
{
"id": "case-07",
"section": "3.2.3",
"chapter": "第三章 赋能",
"title": "客户主动说“我要为你知识付费”",
"keywords": ["咨询", "知识付费", "判断价值", "首笔收入"],
"scenario": "专业判断第一次被客户用真实付款确认",
"takeaway": "客户为清除关键卡点和获得结果付费,而不是为知识数量付费。"
},
{
"id": "case-08",
"section": "3.3.3",
"chapter": "第三章 赋能",
"title": "2 个月,抖音小号通勤路上做到万粉",
"keywords": ["个人品牌", "短视频", "碎片时间", "内容验证"],
"scenario": "在主业之外用碎片时间验证专业内容和个人品牌",
"takeaway": "人设来自持续可验证的内容与结果,不是一次包装。"
},
{
"id": "case-09",
"section": "3.5.1",
"chapter": "第三章 赋能",
"title": "我曾试过传统创业,差点亏光了",
"keywords": ["创业失败", "轻资产", "风险", "副业验证"],
"scenario": "从重投入创业失败转向低风险的一人公司路径",
"takeaway": "先保现金流、验证需求和交付,再决定是否放大。"
},
{
"id": "case-10",
"section": "4.1.4",
"chapter": "第四章 建立",
"title": "从失败到重启:我的画布演变",
"keywords": ["商业模式画布", "轻路径", "资源缺口", "重启"],
"scenario": "用个人版商业模式画布把重资产路径改造成 OPC 路径",
"takeaway": "同样的方向,启动路径的轻重往往决定生意能否活下来。"
},
{
"id": "case-11",
"section": "4.4.1",
"chapter": "第四章 建立",
"title": "不等一切就绪,先验证有人买单",
"keywords": ["MVP", "真实付费", "需求验证", "最小闭环"],
"scenario": "在产品尚不完整时先验证真实客户、交付和付款",
"takeaway": "MVP 的可信证据是实际行为和真实付款,不是口头喜欢。"
},
{
"id": "case-12",
"section": "4.5.4",
"chapter": "第四章 建立",
"title": "一次谈话,从竞争对手成合伙人",
"keywords": ["合作", "竞争", "资源互补", "联盟"],
"scenario": "通过识别资源互补,把潜在竞争关系改造成合作关系",
"takeaway": "一人公司不是凡事亲自做,而是设计清楚的协作结构。"
},
{
"id": "case-13",
"section": "4.7",
"chapter": "第四章 建立",
"title": "首单交付:怎么赚到第一笔钱",
"keywords": ["首单", "真实交付", "第一笔收入", "复盘"],
"scenario": "从机会识别到完成一人公司的第一笔真实回款",
"takeaway": "先完成可交付、可回款的小闭环,再谈规模。"
},
{
"id": "case-14",
"section": "5.2.1",
"chapter": "第五章 运营",
"title": "做减法:那个飞到四川考察后放弃的项目",
"keywords": ["项目筛选", "做减法", "机会成本", "拒绝清单"],
"scenario": "面对看似诱人的项目,基于主航道和投入产出做放弃决策",
"takeaway": "经营能力也体现在知道哪些项目不该接。"
},
{
"id": "case-15",
"section": "5.5.2",
"chapter": "第五章 运营",
"title": "10 个项目后,我把自己变成了 SOP",
"keywords": ["SOP", "服务标准化", "AI化", "可复制交付"],
"scenario": "把多次项目经验沉淀为流程、模板、规则和 AI 工作流",
"takeaway": "先把业务拆成流程,再把流程做成模板,最后把模板交给 AI 跑。"
},
{
"id": "case-16",
"section": "6.1.4",
"chapter": "第六章 增长",
"title": "一次报价失败,让我彻底转变了收费逻辑",
"keywords": ["价值定价", "结果承诺", "报价", "客户目标"],
"scenario": "从按人天报价转向围绕客户结果和确定性定价",
"takeaway": "客户不买工时,而是购买结果与更高的确定性。"
},
{
"id": "case-17",
"section": "6.3.3",
"chapter": "第六章 增长",
"title": "一条腿走路有多危险",
"keywords": ["收入结构", "现金流", "多收入", "风险对冲"],
"scenario": "政策变化暴露单一业务线的现金流风险",
"takeaway": "多元收入应从主业务高频需求中长出,而不是四处分散。"
},
{
"id": "case-18",
"section": "6.4.4",
"chapter": "第六章 增长",
"title": "三次资源合作,拓宽多元业务渠道",
"keywords": ["资源合作", "交换结构", "渠道", "分润"],
"scenario": "通过客户、履约和运营资源交换拓展收入渠道",
"takeaway": "先看资源缺口,再设计交换结构,最后把收益机制写清楚。"
},
{
"id": "case-19",
"section": "7.1.1",
"chapter": "第七章 突破",
"title": "龙虾化身数字分身,自动跑完 324 份文档",
"keywords": ["数字分身", "文档自动化", "批处理", "工作流"],
"scenario": "让 AI 代理接管大批量重复文档处理流程",
"takeaway": "自动化从真实高频、规则清晰、结果可验收的任务开始。"
},
{
"id": "case-20",
"section": "7.1.2",
"chapter": "第七章 突破",
"title": "两人 + AI,一周跑出一个订单管理系统",
"keywords": ["AI开发", "订单系统", "极简团队", "一周交付"],
"scenario": "极简人力借助 AI 在短周期内完成可运行系统",
"takeaway": "AI 放大完整闭环能力,但业务判断与验收仍由人负责。"
},
{
"id": "case-21",
"section": "7.1.3",
"chapter": "第七章 突破",
"title": "选对工具,等于请一个“高级设计师”",
"keywords": ["AI设计", "工具选择", "视觉生成", "质量筛选"],
"scenario": "选择合适的专业工具压缩视觉生产和筛选时间",
"takeaway": "工具价值取决于是否嵌入可验收的工作流,而不是功能多少。"
},
{
"id": "case-22",
"section": "7.1.4",
"chapter": "第七章 突破",
"title": "用 Skills 赋能客户,让我看见了转型的方向",
"keywords": ["Skills", "知识封装", "客户赋能", "产品化"],
"scenario": "把专业方法封装为可被不同 Agent 调用的技能",
"takeaway": "可复用的判断、流程和模板可以从服务资产升级为技能产品。"
},
{
"id": "case-23",
"section": "7.2.3",
"chapter": "第七章 突破",
"title": "累到想招人,最终把 AI 工具用到极限",
"keywords": ["效率瓶颈", "招聘判断", "AI杠杆", "流程优化"],
"scenario": "业务压力上升时先判断应招人、自动化还是重构流程",
"takeaway": "扩张前先把现有工具、流程和自动化潜力用足。"
},
{
"id": "case-24",
"section": "7.2.5",
"chapter": "第七章 突破",
"title": "我亲历 5 亿项目的规模化失败教训",
"keywords": ["规模化", "失败", "重资产", "增长边界"],
"scenario": "从大型项目失败反思规模、组织和路径选择",
"takeaway": "规模不是天然正确,未经验证的放大会同步放大成本和风险。"
},
{
"id": "case-25",
"section": "7.4.1",
"chapter": "第七章 突破",
"title": "业务步入正轨后,我差点掉进重资产负重经营",
"keywords": ["重资产", "扩张陷阱", "现金储备", "系统债务"],
"scenario": "业务稳定后识别盲目扩张、固定成本和系统债务风险",
"takeaway": "增长跑通后仍要守住轻资产、现金储备和标准化底线。"
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |