[{"data":1,"prerenderedAt":1043},["ShallowReactive",2],{"blog-matt-pocock-ai-driven-software-engineering":3,"blog-surround-matt-pocock-ai-driven-software-engineering":1036},{"id":4,"title":5,"body":6,"date":1018,"description":1019,"draft":1020,"extension":1021,"featured":1020,"image":1022,"meta":1023,"navigation":1024,"path":1025,"seo":1026,"slug":1027,"stem":1028,"tags":1029,"updated":1034,"__hash__":1035},"blog\u002Fblog\u002FMatt Pocock ai-driven SE methodology note.md","Matt Pocock 的 AI 驱动软件工程方法论",{"type":7,"value":8,"toc":993},"minimark",[9,13,21,24,42,45,48,53,57,84,91,97,107,110,113,118,211,225,228,325,361,364,396,400,403,437,440,522,525,565,568,630,634,676,680,739,742,750,753,764,767,773,776,808,812,815,832,835,838,841,846,849,852,884,887,891,937,943,946,949,966,969,972,989],[10,11,12],"p",{},"最近，需要负责启动一个新的 App 项目。项目一开始没有完整的产品文档，只有老板一些比较零散的想法。我和负责 UI 设计的同学需要从头推动 MVP 落地，但在实现过程中，我们对同一个功能的理解有时并不一致。等到设计或开发已经往前走了一段，才发现需要回头修改，花了不少时间。",[10,14,15,16,20],{},"后来我在这个项目里尝试了 Matt Skills：从 ",[17,18,19],"code",{},"\u002Fask-matt"," 判断当前工作该进入哪条流程，到功能规划，再到按 Ticket 实施和交付。它帮助我把原本容易留在讨论里的细节逐步说清楚，并留下后续工作可以对照的依据。在随后的 AI Agent 驱动开发中，我没有再遇到因需求细节约束不清、Coding Agent 实现偏了而重新返工的情况。",[10,22,23],{},"这篇文章会整理我对这套方法的理解、它怎样帮助项目推进，以及如何把这些 Skills 引入自己的项目；同时也留作我开发时的速查手册。",[25,26,27,39],"note",{},[10,28,29],{},[30,31,35],"span",{"className":32},[33,34],"mb-2","block",[36,37,38],"strong",{},"核心观点",[10,40,41],{},"AI 并没有让软件工程基本功过时。需求澄清、领域建模、任务切分、测试、代码审查和上下文管理，决定了 AI Agent 能否稳定地交付复杂软件。",[10,43,44],{},"我把 Matt 的 Skills 理解为一套软件工程工作流路由系统：根据当前工作的状态选择合适入口，并在阶段边界留下可验证、可交接的工程产物。",[10,46,47],{},"这套方法串起了以下工作环节：",[10,49,50],{},[36,51,52],{},"问题 → 决策 → 文档 → Ticket → 实现 → 验证。",[54,55,56],"h2",{"id":56},"快速开始",[58,59,64],"pre",{"className":60,"code":61,"language":62,"meta":63,"style":63},"language-shell shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","npx skills@latest add mattpocock\u002Fskills\n","shell","",[17,65,66],{"__ignoreMap":63},[30,67,70,74,78,81],{"class":68,"line":69},"line",1,[30,71,73],{"class":72},"sBMFI","npx",[30,75,77],{"class":76},"sfazB"," skills@latest",[30,79,80],{"class":76}," add",[30,82,83],{"class":76}," mattpocock\u002Fskills\n",[10,85,86],{},[87,88],"img",{"alt":89,"src":90},"Matt Skills 工作流：从仓库初始化、任务分流和功能规划，到 Ticket 实施与交付","\u002Fimages\u002Fblog\u002Fmatt-pocock-ai-driven-software-engineering\u002Fskills-workflow.png",[10,92,93],{},[94,95,96],"a",{"href":90},"查看完整尺寸的流程图",[10,98,99,100,103,104,106],{},"正式使用前，先运行 ",[17,101,102],{},"\u002Fsetup-matt-pocock-skills"," 配置仓库；不确定下一步时，使用 ",[17,105,19],{}," 进行路由。",[54,108,109],{"id":109},"整体使用模型",[10,111,112],{},"这套方法包含一条“想法到交付”的主流程、若干特殊入口，以及贯穿全过程的领域和代码设计能力。",[114,115,117],"h3",{"id":116},"主流程从想法到交付","主流程：从想法到交付",[119,120,121,136,164,188,205],"ol",{},[122,123,124,127,128,131,132,135],"li",{},[36,125,126],{},"澄清目标","：在代码仓库中使用 ",[17,129,130],{},"\u002Fgrill-with-docs","；没有工作目录时使用 ",[17,133,134],{},"\u002Fgrill-me","。",[122,137,138,141,142],{},[36,139,140],{},"消除不确定性","：\n",[143,144,145,152,158],"ul",{},[122,146,147,148,151],{},"外部事实交给 ",[17,149,150],{},"\u002Fresearch","；",[122,153,154,155,151],{},"必须运行代码或观察 UI 的问题交给 ",[17,156,157],{},"\u002Fprototype",[122,159,160,161,135],{},"只有客户、同事或领域专家能回答的问题交给 ",[17,162,163],{},"\u002Fto-questionnaire",[122,165,166,141,169],{},[36,167,168],{},"按工作规模分流",[143,170,171,177],{},[122,172,173,174,151],{},"小任务可以在当前上下文中直接进入 ",[17,175,176],{},"\u002Fimplement",[122,178,179,180,183,184,187],{},"多会话任务先通过 ",[17,181,182],{},"\u002Fto-spec"," 形成正式规格，再由 ",[17,185,186],{},"\u002Fto-tickets"," 拆成纵向切片。",[122,189,190,193,194,196,197,200,201,204],{},[36,191,192],{},"实现与验证","：每个 Ticket 独立执行 ",[17,195,176],{},"，内部使用 ",[17,198,199],{},"\u002Ftdd"," 推进，最后通过 ",[17,202,203],{},"\u002Fcode-review"," 检查 Standards 与 Spec。",[122,206,207,210],{},[36,208,209],{},"提交与交付","：项目级检查通过后再提交变更，并把未完成事项放回 Ticket，而不是遗留在聊天记录里。",[212,213,214,222],"tip",{},[10,215,216],{},[30,217,219],{"className":218},[33,34],[36,220,221],{},"为什么要拆成纵向切片",[10,223,224],{},"Ticket 不应简单地按“前端、后端、数据库”横向分工，而应尽量形成能够端到端验证的 tracer bullet。这样每一步都可以独立证明价值和正确性。",[114,226,227],{"id":227},"特殊入口",[229,230,231,247],"table",{},[232,233,234],"thead",{},[235,236,237,241,244],"tr",{},[238,239,240],"th",{},"当前情况",[238,242,243],{},"使用的 Skill",[238,245,246],{},"后续流向",[248,249,250,266,282,297,312],"tbody",{},[235,251,252,256,261],{},[253,254,255],"td",{},"收到未经整理的 Bug、需求或 PR",[253,257,258],{},[17,259,260],{},"\u002Ftriage",[253,262,263,264],{},"形成 Agent-ready Ticket 后进入 ",[17,265,176],{},[235,267,268,271,276],{},[253,269,270],{},"遇到难以复现、难以定位的 Bug",[253,272,273],{},[17,274,275],{},"\u002Fdiagnosing-bugs",[253,277,278,279,281],{},"建立反馈循环，再通过 ",[17,280,199],{}," 修复",[235,283,284,287,292],{},[253,285,286],{},"面对一次会话无法规划的大型目标",[253,288,289],{},[17,290,291],{},"\u002Fwayfinder",[253,293,294,295],{},"逐个解决决策 Ticket，再进入 ",[17,296,182],{},[235,298,299,302,307],{},[253,300,301],{},"发现模块边界差、修改成本高",[253,303,304],{},[17,305,306],{},"\u002Fimprove-codebase-architecture",[253,308,309,310],{},"形成改进想法，再进入 ",[17,311,130],{},[235,313,314,317,322],{},[253,315,316],{},"正在解决 Merge\u002FRebase 冲突",[253,318,319],{},[17,320,321],{},"\u002Fresolving-merge-conflicts",[253,323,324],{},"按双方原始意图完成冲突解决",[326,327,328,336],"warning",{},[10,329,330],{},[30,331,333],{"className":332},[33,34],[36,334,335],{},"容易误用的边界",[143,337,338,346,351,356],{},[122,339,340,342,343,345],{},[17,341,260],{}," 只处理外部进入的原始工作；",[17,344,186],{}," 生成的 Ticket 已经是 Agent-ready。",[122,347,348,350],{},[17,349,291],{}," 负责消除大型目标中的决策迷雾，本身不负责交付代码。",[122,352,353,355],{},[17,354,157],{}," 只回答一个设计问题，不应自然演变成未经审查的生产实现。",[122,357,358,360],{},[17,359,150],{}," 提供事实和证据，但不会代替人做产品决策。",[114,362,363],{"id":363},"贯穿流程的基础能力",[143,365,366,372,378,384,390],{},[122,367,368,371],{},[17,369,370],{},"domain-modeling"," 维护统一的领域语言，避免同一个词在不同模块中表达不同含义；",[122,373,374,377],{},[17,375,376],{},"codebase-design"," 使用深模块、接口、接缝和局部性等概念设计代码结构；",[122,379,380,383],{},[17,381,382],{},"handoff"," 在跨会话、跨目录或跨协作者时生成可移交的上下文；",[122,385,386,389],{},[17,387,388],{},"wizard"," 把必须由人执行的控制台、凭据或迁移步骤整理成可重复流程；",[122,391,392,395],{},[17,393,394],{},"wait-what"," 在解释没有讲清楚时，用当前项目的领域语言重新说明。",[54,397,399],{"id":398},"skill-速查","Skill 速查",[114,401,402],{"id":402},"入口与环境配置",[229,404,405,415],{},[232,406,407],{},[235,408,409,412],{},[238,410,411],{},"Skill",[238,413,414],{},"一句话用途",[248,416,417,427],{},[235,418,419,424],{},[253,420,421],{},[17,422,423],{},"ask-matt",[253,425,426],{},"Skill 导航器。根据当前工作状态，帮你选择应该进入哪条 Skill 流程。",[235,428,429,434],{},[253,430,431],{},[17,432,433],{},"setup-matt-pocock-skills",[253,435,436],{},"项目初始化工具。为仓库配置 Issue Tracker、Triage 标签和领域文档布局。",[114,438,439],{"id":439},"需求澄清与大型规划",[229,441,442,450],{},[232,443,444],{},[235,445,446,448],{},[238,447,411],{},[238,449,414],{},[248,451,452,462,472,482,492,502,512],{},[235,453,454,459],{},[253,455,456],{},[17,457,458],{},"grilling",[253,460,461],{},"通过分轮决策树采访，把计划中的所有隐含问题逐项问清楚。",[235,463,464,469],{},[253,465,466],{},[17,467,468],{},"grill-me",[253,470,471],{},"在没有项目工作区时进行一次不保存文档的需求或方案采访。",[235,473,474,479],{},[253,475,476],{},[17,477,478],{},"grill-with-docs",[253,480,481],{},"在仓库中澄清方案，并同步维护领域词汇和必要 ADR。",[235,483,484,489],{},[253,485,486],{},[17,487,488],{},"wayfinder",[253,490,491],{},"把无法在一次会话中想清楚的大型目标组织成决策地图，逐步消除不确定性。",[235,493,494,499],{},[253,495,496],{},[17,497,498],{},"research",[253,500,501],{},"基于官方文档、标准和源代码研究外部事实，并将结论写成带引用的文档。",[235,503,504,509],{},[253,505,506],{},[17,507,508],{},"prototype",[253,510,511],{},"用可丢弃的运行代码回答一个仅靠讨论无法确定的设计问题。",[235,513,514,519],{},[253,515,516],{},[17,517,518],{},"to-questionnaire",[253,520,521],{},"把只有外部人员才能回答的知识缺口整理成针对性问卷。",[114,523,524],{"id":524},"领域和架构设计",[229,526,527,535],{},[232,528,529],{},[235,530,531,533],{},[238,532,411],{},[238,534,414],{},[248,536,537,546,555],{},[235,538,539,543],{},[253,540,541],{},[17,542,370],{},[253,544,545],{},"统一领域术语、澄清业务对象边界，并在必要时记录 ADR。",[235,547,548,552],{},[253,549,550],{},[17,551,376],{},[253,553,554],{},"用深模块、接口、接缝和局部性等概念设计易维护、易测试的代码结构。",[235,556,557,562],{},[253,558,559],{},[17,560,561],{},"improve-codebase-architecture",[253,563,564],{},"扫描代码库中的架构摩擦，找出值得深化模块或重构的机会。",[114,566,567],{"id":567},"规格与实施",[229,569,570,578],{},[232,571,572],{},[235,573,574,576],{},[238,575,411],{},[238,577,414],{},[248,579,580,590,600,610,620],{},[235,581,582,587],{},[253,583,584],{},[17,585,586],{},"to-spec",[253,588,589],{},"将已经讨论清楚的决定综合成正式、可实施的 Spec，不再发起新采访。",[235,591,592,597],{},[253,593,594],{},[17,595,596],{},"to-tickets",[253,598,599],{},"将 Spec 拆成带阻塞关系、可独立验收的纵向切片 Ticket。",[235,601,602,607],{},[253,603,604],{},[17,605,606],{},"implement",[253,608,609],{},"按 Spec 或 Ticket 完成实现、验证和交付。",[235,611,612,617],{},[253,613,614],{},[17,615,616],{},"tdd",[253,618,619],{},"使用红—绿—重构循环，以可观察行为驱动代码实现。",[235,621,622,627],{},[253,623,624],{},[17,625,626],{},"code-review",[253,628,629],{},"从固定基点分别检查代码是否符合仓库规范以及是否满足 Spec。",[114,631,633],{"id":632},"请求故障与代码维护","请求、故障与代码维护",[229,635,636,644],{},[232,637,638],{},[235,639,640,642],{},[238,641,411],{},[238,643,414],{},[248,645,646,656,666],{},[235,647,648,653],{},[253,649,650],{},[17,651,652],{},"triage",[253,654,655],{},"将外部 Bug、需求和 PR 整理、验证并推进成 Agent-ready 工作。",[235,657,658,663],{},[253,659,660],{},[17,661,662],{},"diagnosing-bugs",[253,664,665],{},"先建立能稳定复现问题的反馈循环，再定位根因并补充回归测试。",[235,667,668,673],{},[253,669,670],{},[17,671,672],{},"resolving-merge-conflicts",[253,674,675],{},"根据两边变更的原始意图逐个解决 Merge 或 Rebase 冲突。",[114,677,679],{"id":678},"上下文人机协作与知识维护","上下文、人机协作与知识维护",[229,681,682,690],{},[232,683,684],{},[235,685,686,688],{},[238,687,411],{},[238,689,414],{},[248,691,692,701,710,719,729],{},[235,693,694,698],{},[253,695,696],{},[17,697,382],{},[253,699,700],{},"把当前上下文压缩成可供另一会话、目录或协作者接手的临时文档。",[235,702,703,707],{},[253,704,705],{},[17,706,388],{},[253,708,709],{},"为必须由人操作的控制台、凭据、迁移或切换流程生成交互式 Bash 向导。",[235,711,712,716],{},[253,713,714],{},[17,715,394],{},[253,717,718],{},"当上一段解释没有讲明白时，使用项目领域语言重新简明解释。",[235,720,721,726],{},[253,722,723],{},[17,724,725],{},"teach",[253,727,728],{},"在工作区中建立可持续、多轮次的课程、参考资料和学习记录。",[235,730,731,736],{},[253,732,733],{},[17,734,735],{},"writing-for-agents",[253,737,738],{},"指导如何编写稳定、明确、可被 Agent 正确消费的 Skill 和 Agent 文档。",[54,740,741],{"id":741},"仓库初始化",[58,743,748],{"className":744,"code":746,"language":747,"meta":63},[745],"language-text","\u002Fsetup-matt-pocock-skills\n","text",[17,749,746],{"__ignoreMap":63},[10,751,752],{},"初始化回答三个问题：",[143,754,755,758,761],{},[122,756,757],{},"这个项目在哪里管理需求和 tickets？",[122,759,760],{},"项目使用什么 triage 状态语言？",[122,762,763],{},"Agent 应该从哪里读取领域知识和架构决策？",[10,765,766],{},"典型产物：",[58,768,771],{"className":769,"code":770,"language":747,"meta":63},[745],"project\u002F\n├── AGENTS.md 或 CLAUDE.md\n├── CONTEXT.md                     按需创建\n├── docs\u002F\n│   ├── agents\u002F\n│   │   ├── issue-tracker.md\n│   │   ├── domain.md\n│   │   └── triage-labels.md        安装 triage 时才有\n│   └── adr\u002F\n│       └── 0001-*.md              有重要决策时才创建\n└── src\u002F\n",[17,772,770],{"__ignoreMap":63},[10,774,775],{},"其中：",[143,777,778,784,790,796,802],{},[122,779,780,783],{},[17,781,782],{},"docs\u002Fagents\u002Fissue-tracker.md"," 是“工作发布到哪里”的操作约定；",[122,785,786,789],{},[17,787,788],{},"docs\u002Fagents\u002Fdomain.md"," 是 Agent 阅读领域文档的规则；",[122,791,792,795],{},[17,793,794],{},"docs\u002Fagents\u002Ftriage-labels.md"," 是通用状态和实际 Tracker 标签之间的映射；",[122,797,798,801],{},[17,799,800],{},"CONTEXT.md"," 是稳定、共享的领域词汇表；",[122,803,804,807],{},[17,805,806],{},"docs\u002Fadr\u002F"," 保存少量重要、难以逆转的架构决策。",[114,809,811],{"id":810},"issue-tracker","Issue Tracker",[10,813,814],{},"决定 spec 和 ticket 保存在哪里：",[143,816,817,820,823,829],{},[122,818,819],{},"GitHub Issues",[122,821,822],{},"GitLab Issues",[122,824,825,826],{},"本地 Markdown：",[17,827,828],{},".scratch\u002F\u003Cfeature>\u002F",[122,830,831],{},"Linear、Jira 或其他自定义工作流",[54,833,834],{"id":834},"上下文管理也是工程设计",[10,836,837],{},"在 AI 驱动的软件工程中，上下文是一种有限资源。",[10,839,840],{},"规划阶段最好保持一段连续上下文：",[10,842,843],{},[17,844,845],{},"grilling → research\u002Fprototype → to-spec → to-tickets",[10,847,848],{},"这些步骤共享同一套问题、事实和决策。进入实施阶段后，每个 Ticket 则应该从干净上下文开始，只依赖 Spec、Ticket、领域文档和当前代码。",[10,850,851],{},"在阶段边界，可以按以下顺序判断：",[119,853,854,860,866,872,878],{},[122,855,856,859],{},[36,857,858],{},"Continue","：当前上下文仍然清晰，直接继续；",[122,861,862,865],{},[36,863,864],{},"Clear","：后续工作不再需要当前上下文；",[122,867,868,871],{},[36,869,870],{},"Handoff","：需要跨目录、跨会话或交给其他协作者；",[122,873,874,877],{},[36,875,876],{},"Subagent","：把边界明确的支线任务交给独立上下文；",[122,879,880,883],{},[36,881,882],{},"Compact","：会话接近 smart zone 上限时压缩上下文。",[10,885,886],{},"关键不是频繁清理上下文，而是在正确的阶段边界处理它。规划尚未形成稳定产物时过早清空，会丢失重要推理；实现不同 Ticket 时持续携带旧上下文，又会积累大量无关信息。",[54,888,890],{"id":889},"人与-agent-的职责边界","人与 Agent 的职责边界",[229,892,893,903],{},[232,894,895],{},[235,896,897,900],{},[238,898,899],{},"人负责",[238,901,902],{},"Agent 负责",[248,904,905,913,921,929],{},[235,906,907,910],{},[253,908,909],{},"业务目标、价值判断和产品取舍",[253,911,912],{},"发现未决问题并组织讨论",[235,914,915,918],{},[253,916,917],{},"确认产品范围和验收标准",[253,919,920],{},"调查事实、阅读代码并生成证据",[235,922,923,926],{},[253,924,925],{},"批准不可逆或高风险决策",[253,927,928],{},"维护 Spec、Ticket、测试和文档",[235,930,931,934],{},[253,932,933],{},"提供凭据并完成必须人工操作的步骤",[253,935,936],{},"按 Ticket 实现、验证和审查代码",[10,938,939,942],{},[17,940,941],{},"\u002Fwizard"," 用于真正需要人参与的步骤，例如配置凭据、操作第三方控制台或执行切换流程。Agent 能安全完成的事情不应推给人；必须由人判断或授权的事情，也不应由 Agent 擅自决定。",[54,944,945],{"id":945},"我的理解",[10,947,948],{},"Matt 的方法论不是让 Agent 完全替代工程师，而是把优秀工程师原本隐性的工作方式显式化：",[143,950,951,954,957,960,963],{},[122,952,953],{},"先建立共享语言，再讨论方案；",[122,955,956],{},"先消除关键不确定性，再投入生产实现；",[122,958,959],{},"用文档和 Ticket 跨越上下文边界；",[122,961,962],{},"用测试、审查和证据约束 Agent 的输出；",[122,964,965],{},"让人保留产品判断和高风险决策权。",[10,967,968],{},"AI 提高的是执行速度，工程方法决定的是方向、质量和可持续性。",[54,970,971],{"id":971},"参考资料",[143,973,974,982],{},[122,975,976],{},[94,977,981],{"href":978,"rel":979},"https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills",[980],"nofollow","Matt Pocock Skills",[122,983,984],{},[94,985,988],{"href":986,"rel":987},"https:\u002F\u002Fzhuanlan.zhihu.com\u002Fp\u002F2032512098626954988",[980],"软件基本功没死，它在 AI 时代变得更值钱了",[990,991,992],"style",{},"html pre.shiki code .sBMFI, html code.shiki .sBMFI{--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":63,"searchDepth":994,"depth":994,"links":995},2,[996,997,1003,1011,1014,1015,1016,1017],{"id":56,"depth":994,"text":56},{"id":109,"depth":994,"text":109,"children":998},[999,1001,1002],{"id":116,"depth":1000,"text":117},3,{"id":227,"depth":1000,"text":227},{"id":363,"depth":1000,"text":363},{"id":398,"depth":994,"text":399,"children":1004},[1005,1006,1007,1008,1009,1010],{"id":402,"depth":1000,"text":402},{"id":439,"depth":1000,"text":439},{"id":524,"depth":1000,"text":524},{"id":567,"depth":1000,"text":567},{"id":632,"depth":1000,"text":633},{"id":678,"depth":1000,"text":679},{"id":741,"depth":994,"text":741,"children":1012},[1013],{"id":810,"depth":1000,"text":811},{"id":834,"depth":994,"text":834},{"id":889,"depth":994,"text":890},{"id":945,"depth":994,"text":945},{"id":971,"depth":994,"text":971},"2026-09-15","从实习项目中的需求澄清与返工经历出发，整理 Matt Skills 从想法到交付的工作流、Skill 速查、仓库初始化与上下文管理方法。",false,"md",null,{},true,"\u002Fblog\u002Fmatt-pocock-ai-driven-se-methodology-note",{"title":5,"description":1019},"matt-pocock-ai-driven-software-engineering","blog\u002FMatt Pocock ai-driven SE methodology note",[1030,1031,1032,1033],"ai","software-engineering","agent","methodology","2026-10-27","TcGF-4A_8gbszvDJ39ltMKB8LjvrRyyHinRlzndAH1w",[1037,1022],{"title":1038,"path":1039,"stem":1040,"description":1041,"slug":1042},"博客写作示例：Markdown、MDC 与组件","\u002Fblog\u002Fhello-nuxt","blog\u002Fhello-nuxt","当前博客支持的 Markdown 排版、MDC 属性和文章组件示例，按用途查找并参考对应写法","hello-nuxt",1793095680154]