[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AVG2J86QEC2AJWDA1F4MPV":3,"skill-same:01M7AVG2J86QEC2AJWDA1F4MPV":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AVG2J86QEC2AJWDA1F4MPV","philosophy-of-software-design",null,"Design modules, review code, reduce complexity.","peterlau123\u002Fskills-you-need","peterlau123","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F19188200?v=4","01M7AV0Y55C30Y4E2TGRQ8X7WR","Sloth","01M7AV0Y5SNAJQ4E3FG1EEK8S4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fphilosophy-of-software-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fphilosophy-of-software-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: philosophy-of-software-design\ndescription: Design modules, review code, reduce complexity.\n---\n\n# A Philosophy of Software Design — 路由核心\n\n> 来源: John Ousterhout《A Philosophy of Software Design》(斯坦福 CS 190)\n> 核心论点: **软件设计的核心挑战是管理复杂性**。所有原则服务于一个目标：让系统容易理解和修改。\n> 元原则: 任何原则与\"是否真的降低复杂性\"冲突时，以后者为准（作者原意，勿教条）。\n\n---\n\n## 复杂性的三个症状（诊断入口）\n\n| 症状 | 含义 | 识别方法 |\n|---|---|---|\n| **变更放大** | 简单修改需改动多处代码 | 改一个功能要碰多少个文件\u002F方法？ |\n| **认知负荷** | 开发者必须吸收大量信息才能安全完成任务 | 完成任务要读多少不相关代码？⚠️ 行数少 ≠ 简单，有时更多代码反而更简单 |\n| **未知的未知** | 不清楚该改哪些代码 | 最危险——修改时\"不知道该看哪里\" |\n\n**根源**：依赖（无法独立理解\u002F修改）+ 晦涩（重要信息不明显）。\n**关键洞察**：复杂性是增量累积的——不是灾难性错误，而是成百上千个小决定堆积。必须零容忍。\n\n---\n\n## 15 条设计原则速查\n\n1. 复杂性是逐步增加的——必须处理小事情\n2. 能跑起来的代码不够\n3. 持续小额投资改善系统设计（10-20% 时间）\n4. 模块应该深\n5. 接口设计让最常见的用法最简单\n6. 简单接口 > 简单实现\n7. 通用模块更深（\"有点通用\"）\n8. 通用与专用代码分开\n9. 不同层应有不同抽象\n10. 把复杂性往下压\n11. 把错误（和特例）定义掉\n12. 设计两次\n13. 注释描述代码中不明显的内容\n14. 软件为易读而设计，不为易写\n15. 开发增量是抽象而非功能\n\n---\n\n## 14 个危险信号速查（评审检查表）\n\n| 危险信号 | 含义 |\n|---|---|\n| 浅模块 | 接口不比实现简单 |\n| 信息泄漏 | 一个设计决策反映在多个模块 |\n| 时间分解 | 结构基于执行顺序而非信息隐藏 |\n| 过度暴露 | API 强迫调用者为常用功能而了解不常用功能 |\n| 透传方法 | 方法只是把参数传给签名相似的另一方法 |\n| 重复 | 非平凡代码反复出现 |\n| 特殊-通用混合 | 专用代码未与通用代码分离 |\n| 联合方法 | 两方法依赖太强，不理解一个就无法理解另一个 |\n| 注释重复代码 | 注释内容从代码立即可见 |\n| 实现文档污染接口 | 接口注释描述用户不需要的实现细节 |\n| 含糊名称 | 名字无法传达有用信息 |\n| 难以取名 | 为实体找不到精确直观的名字（= 设计问题信号） |\n| 难以描述 | 完整文档必须很长 |\n| 非显而易见代码 | 行为\u002F含义不易理解 |\n\n---\n\n## 使用场景路由\n\n| 场景 | 加载内容 | 位置 |\n|---|---|---|\n| **写代码 \u002F 设计模块接口** | 深模块指南 + 错误处理哲学 + 注释命名 | `references\u002Fdeep-modules.md` + `references\u002Ferror-handling.md` + `references\u002Fcomments-and-naming.md` |\n| **代码评审** | 危险信号检查表（配合 code-review skill 的 Standards 轴） | `references\u002Fred-flags-checklist.md` |\n| **重构** | 深模块指南 + 修改现有代码原则 | `references\u002Fdeep-modules.md` |\n| **快速提醒** | 本文件的原则\u002F危险信号速查 | 本文件 |\n\n**与相邻 skill 的分工**：\n- 深模块词汇表（seam\u002Fadapter\u002Fleverage）→ 用 `codebase-design` skill（不重复建设）\n- 评审流程（双轴、sub-agent）→ 用 `code-review` skill\n- 本 skill 提供：**原则依据 + 独有哲学（错误处理\u002F注释\u002F命名）+ 危险信号检查表**\n\n## 边界与注意事项\n\n- 原则冲突时回到元原则：\"这个选择真的降低复杂性了吗？\"\n- 深模块 ≠ 类越大越好：同时检查接口是否真的简单\n- AI\u002FAgent 场景映射：AGENTS.md = \"把复杂性往下压\"（让 agent 用户简单）；repo-as-spec = 消除 unknown unknowns\n","# A Philosophy of Software Design — 路由核心\n\n> 来源: John Ousterhout《A Philosophy of Software Design》(斯坦福 CS 190)\n> 核心论点: **软件设计的核心挑战是管理复杂性**。所有原则服务于一个目标：让系统容易理解和修改。\n> 元原则: 任何原则与\"是否真的降低复杂性\"冲突时，以后者为准（作者原意，勿教条）。\n\n---\n\n## 复杂性的三个症状（诊断入口）\n\n| 症状 | 含义 | 识别方法 |\n|---|---|---|\n| **变更放大** | 简单修改需改动多处代码 | 改一个功能要碰多少个文件\u002F方法？ |\n| **认知负荷** | 开发者必须吸收大量信息才能安全完成任务 | 完成任务要读多少不相关代码？⚠️ 行数少 ≠ 简单，有时更多代码反而更简单 |\n| **未知的未知** | 不清楚该改哪些代码 | 最危险——修改时\"不知道该看哪里\" |\n\n**根源**：依赖（无法独立理解\u002F修改）+ 晦涩（重要信息不明显）。\n**关键洞察**：复杂性是增量累积的——不是灾难性错误，而是成百上千个小决定堆积。必须零容忍。\n\n---\n\n## 15 条设计原则速查\n\n1. 复杂性是逐步增加的——必须处理小事情\n2. 能跑起来的代码不够\n3. 持续小额投资改善系统设计（10-20% 时间）\n4. 模块应该深\n5. 接口设计让最常见的用法最简单\n6. 简单接口 > 简单实现\n7. 通用模块更深（\"有点通用\"）\n8. 通用与专用代码分开\n9. 不同层应有不同抽象\n10. 把复杂性往下压\n11. 把错误（和特例）定义掉\n12. 设计两次\n13. 注释描述代码中不明显的内容\n14. 软件为易读而设计，不为易写\n15. 开发增量是抽象而非功能\n\n---\n\n## 14 个危险信号速查（评审检查表）\n\n| 危险信号 | 含义 |\n|---|---|\n| 浅模块 | 接口不比实现简单 |\n| 信息泄漏 | 一个设计决策反映在多个模块 |\n| 时间分解 | 结构基于执行顺序而非信息隐藏 |\n| 过度暴露 | API 强迫调用者为常用功能而了解不常用功能 |\n| 透传方法 | 方法只是把参数传给签名相似的另一方法 |\n| 重复 | 非平凡代码反复出现 |\n| 特殊-通用混合 | 专用代码未与通用代码分离 |\n| 联合方法 | 两方法依赖太强，不理解一个就无法理解另一个 |\n| 注释重复代码 | 注释内容从代码立即可见 |\n| 实现文档污染接口 | 接口注释描述用户不需要的实现细节 |\n| 含糊名称 | 名字无法传达有用信息 |\n| 难以取名 | 为实体找不到精确直观的名字（= 设计问题信号） |\n| 难以描述 | 完整文档必须很长 |\n| 非显而易见代码 | 行为\u002F含义不易理解 |\n\n---\n\n## 使用场景路由\n\n| 场景 | 加载内容 | 位置 |\n|---|---|---|\n| **写代码 \u002F 设计模块接口** | 深模块指南 + 错误处理哲学 + 注释命名 | `references\u002Fdeep-modules.md` + `references\u002Ferror-handling.md` + `references\u002Fcomments-and-naming.md` |\n| **代码评审** | 危险信号检查表（配合 code-review skill 的 Standards 轴） | `references\u002Fred-flags-checklist.md` |\n| **重构** | 深模块指南 + 修改现有代码原则 | `references\u002Fdeep-modules.md` |\n| **快速提醒** | 本文件的原则\u002F危险信号速查 | 本文件 |\n\n**与相邻 skill 的分工**：\n- 深模块词汇表（seam\u002Fadapter\u002Fleverage）→ 用 `codebase-design` skill（不重复建设）\n- 评审流程（双轴、sub-agent）→ 用 `code-review` skill\n- 本 skill 提供：**原则依据 + 独有哲学（错误处理\u002F注释\u002F命名）+ 危险信号检查表**\n\n## 边界与注意事项\n\n- 原则冲突时回到元原则：\"这个选择真的降低复杂性了吗？\"\n- 深模块 ≠ 类越大越好：同时检查接口是否真的简单\n- AI\u002FAgent 场景映射：AGENTS.md = \"把复杂性往下压\"（让 agent 用户简单）；repo-as-spec = 消除 unknown unknowns\n",{"name":5,"description":7},"main","c0b220603dea88e986e5b31268098ef2f5b07fd0","software-development\u002Fphilosophy-of-software-design","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need","https:\u002F\u002Fgithub.com\u002Fpeterlau123","A software engineer in deep learning\r\n","2026-08-19 16:46:00",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add peterlau123\u002Fskills-you-need --skill philosophy-of-software-design",{"tool":38,"command":39},"bunx","bunx skills add peterlau123\u002Fskills-you-need --skill philosophy-of-software-design",{"tool":41,"command":42},"pnpm","pnpm dlx skills add peterlau123\u002Fskills-you-need --skill philosophy-of-software-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fphilosophy-of-software-design\u002FSKILL.md",true,[46,50,56,60,64],{"path":47,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":16},"LICENSE","许可证",1068,{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcomments-and-naming.md","REFERENCE","参考文档",3387,"https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fphilosophy-of-software-design\u002Freferences\u002Fcomments-and-naming.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fdeep-modules.md",4405,"https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fphilosophy-of-software-design\u002Freferences\u002Fdeep-modules.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Ferror-handling.md",2112,"https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fphilosophy-of-software-design\u002Freferences\u002Ferror-handling.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fred-flags-checklist.md",2277,"https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fphilosophy-of-software-design\u002Freferences\u002Fred-flags-checklist.md",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":20},"01M7AVH2D16QBRC8T2P6SVXSTS","jekyll-chirpy-blog","Use when editing the Jekyll\u002FChirpy blog or fixing mermaid.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fweb\u002Fjekyll-chirpy-blog\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":20},"01M7AVGYYFDK4GKCSNHBCP59Y6","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":20},"01M7AVGT9GAVB5EBKZ2616R27Z","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":20},"01M7AVGQ23T5EHRQP5GZ45KZC5","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":20},"01M7AVGKZ0ZD91ATKD9QB44E1B","simplify-code","Parallel 4-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":20},"01M7AVGFBR76BWQNG2X4CN5SQT","requesting-code-review","Pre-commit review: security scan, quality gates, auto-fix.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Frequesting-code-review\u002FSKILL.md",[],[]]