[{"data":1,"prerenderedAt":1490},["ShallowReactive",2],{"search-docs":3,"doc-\u002Fai\u002Fprompt\u002Ftechniques":886},[4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,159,162,165,169,172,175,178,182,186,190,194,198,202,206,210,214,218,222,226,230,234,238,242,246,250,254,258,262,266,269,273,277,281,285,288,291,294,298,301,304,307,310,313,316,319,322,325,329,332,336,340,344,348,352,356,359,362,365,368,371,374,377,380,383,386,389,393,396,399,402,405,408,411,414,417,420,424,428,432,435,438,442,446,450,454,458,462,466,470,474,477,480,483,487,491,494,497,500,504,507,511,515,518,521,524,527,530,533,536,539,542,545,548,551,554,557,560,563,566,569,572,575,579,583,587,591,595,599,603,606,610,614,617,620,623,626,629,633,637,640,643,646,649,652,655,658,661,664,667,670,673,676,679,682,685,688,691,694,697,700,703,706,709,712,716,720,724,728,732,736,740,744,748,752,756,760,764,768,772,775,779,783,787,790,793,796,799,802,805,808,811,814,818,822,825,829,832,835,838,841,844,848,851,854,858,862,865,869,873,876,879,882],{"path":5,"title":6,"description":7},"\u002Fabout\u002Fauthor","作者相关","只想纯粹的做一个程序员...",{"path":9,"title":10,"description":11},"\u002Fabout\u002Fjourney","心路历程","",{"path":13,"title":14,"description":15},"\u002Fai\u002Fagent\u002Fframeworks","Agent 框架","主流 Agent 框架：LangChain、LlamaIndex、AutoGen、CrewAI",{"path":17,"title":18,"description":19},"\u002Fai\u002Fagent\u002Fhooks","Agent Hooks 与自动化","Claude Agent 的 Hooks 生命周期、事件类型、典型自动化场景",{"path":21,"title":22,"description":23},"\u002Fai\u002Fagent\u002Fintroduction","AI Agent 概述","AI Agent 核心概念：感知、规划、执行、记忆",{"path":25,"title":26,"description":27},"\u002Fai\u002Fagent\u002Fpractice","Agent 实战","AI Agent 实战：构建自主任务执行系统",{"path":29,"title":30,"description":31},"\u002Fai\u002Fagent\u002Fsdk","Claude Agent SDK 开发","使用 Claude Agent SDK 构建自定义 AI Agent：架构、API、生命周期",{"path":33,"title":34,"description":35},"\u002Fai\u002Fagent\u002Fsubagents","Subagents 子代理","用 Subagents 分解复杂任务、并发执行、隔离上下文",{"path":37,"title":38,"description":39},"\u002Fai\u002Fagent\u002Ftool-use","工具调用","AI Agent 工具调用：Function Calling、Tool Use 原理与实践",{"path":41,"title":42,"description":43},"\u002Fai\u002Ffundamentals\u002Fdeep-learning","深度学习入门","深度学习基础知识：前向传播、反向传播、损失函数、优化器",{"path":45,"title":46,"description":47},"\u002Fai\u002Ffundamentals\u002Fml-basics","机器学习基础","机器学习核心概念：监督学习、无监督学习、强化学习",{"path":49,"title":50,"description":51},"\u002Fai\u002Ffundamentals\u002Fneural-networks","神经网络原理","神经网络架构：CNN、RNN、注意力机制",{"path":53,"title":54,"description":55},"\u002Fai\u002Fgetting-started","AI 学习路线","AI 技术学习路线图，从基础到实战的完整指南",{"path":57,"title":58,"description":59},"\u002Fai\u002Fllm\u002Ffine-tuning","模型微调","大模型微调技术：LoRA、QLoRA、全量微调、RLHF",{"path":61,"title":62,"description":63},"\u002Fai\u002Fllm\u002Fintroduction","大模型概述","大语言模型发展历程、核心能力与主流模型对比",{"path":65,"title":66,"description":67},"\u002Fai\u002Fllm\u002Flocal-deploy","本地部署","大模型本地部署：Ollama、vLLM、llama.cpp",{"path":69,"title":70,"description":71},"\u002Fai\u002Fllm\u002Ftransformer","Transformer 架构","Transformer 架构详解：自注意力机制、位置编码、多头注意力",{"path":73,"title":74,"description":75},"\u002Fai\u002Fmcp\u002Fclient","MCP Client 开发","MCP Client 开发指南：连接、调用、集成",{"path":77,"title":78,"description":79},"\u002Fai\u002Fmcp\u002Fdebugging","MCP 调试与排错","MCP Server 开发与集成过程中的常见问题、日志分析、诊断工具",{"path":81,"title":82,"description":83},"\u002Fai\u002Fmcp\u002Fintroduction","MCP 概述","Model Context Protocol 协议概述：架构、核心概念、应用场景",{"path":85,"title":86,"description":87},"\u002Fai\u002Fmcp\u002Fserver","MCP Server 开发","MCP Server 开发指南：资源、工具、提示词的实现",{"path":89,"title":90,"description":91},"\u002Fai\u002Fmcp\u002Ftools","MCP Tools 深入","深入理解 MCP Tools：与 Resources\u002FPrompts 的差异、Schema 设计、Annotations 与权限控制",{"path":93,"title":94,"description":95},"\u002Fai\u002Fprompt\u002Fadvanced","高级 Prompt 模式","高级 Prompt 设计模式：Tree-of-Thought、自我反思、多轮对话策略",{"path":97,"title":98,"description":99},"\u002Fai\u002Fprompt\u002Fbasics","Prompt 基础","Prompt Engineering 入门：基本概念、角色设定、输出格式控制",{"path":101,"title":102,"description":103},"\u002Fai\u002Fprompt\u002Ftechniques","提示词技巧","常用提示词技巧：Few-shot、Chain-of-Thought、ReAct",{"path":105,"title":106,"description":107},"\u002Fai\u002Frag\u002Fembedding","文本嵌入","文本嵌入模型：Embedding 原理、模型选择、相似度计算",{"path":109,"title":110,"description":111},"\u002Fai\u002Frag\u002Fintroduction","RAG 概述","检索增强生成（RAG）架构原理、优势与应用场景",{"path":113,"title":114,"description":115},"\u002Fai\u002Frag\u002Fpractice","RAG 实战","RAG 应用实战：文档问答系统、知识库搭建",{"path":117,"title":118,"description":119},"\u002Fai\u002Frag\u002Fvector-database","向量数据库","主流向量数据库对比：Milvus、Pinecone、Chroma、Weaviate",{"path":121,"title":122,"description":123},"\u002Fai\u002Fskills\u002Fbest-practices","Skill 最佳实践","编写高质量 Skill 的设计原则、常见陷阱与优化技巧",{"path":125,"title":126,"description":127},"\u002Fai\u002Fskills\u002Fcreating","创建自定义 Skill","从零编写一个可被 Agent 自动发现和调用的 Skill",{"path":129,"title":130,"description":131},"\u002Fai\u002Fskills\u002Fintroduction","Agent Skills 概述","Claude Agent Skills 概念、工作原理、与 Tools\u002FMCP 的区别",{"path":133,"title":134,"description":135},"\u002Fgolang\u002Fadvanced\u002Fconcurrency","Go - 并发深入","深入理解 Go 并发编程的核心机制。",{"path":137,"title":138,"description":139},"\u002Fgolang\u002Fadvanced\u002Fgc","Go - 垃圾回收","理解 Go 的垃圾回收机制，掌握 GC 调优方法。",{"path":141,"title":142,"description":143},"\u002Fgolang\u002Fadvanced\u002Fgmp","Go - GMP 调度模型","GMP 是 Go 运行时调度器的核心模型，理解它对于编写高性能 Go 程序至关重要。",{"path":145,"title":146,"description":147},"\u002Fgolang\u002Fadvanced\u002Fgo-concurrency","Go - 并发编程","Go 的并发是其核心特性之一，通过 Goroutine 和 Channel 实现。",{"path":149,"title":150,"description":151},"\u002Fgolang\u002Fadvanced\u002Fmemory","Go - 内存模型","理解 Go 的内存分配机制和内存模型。",{"path":153,"title":154,"description":155},"\u002Fgolang\u002Fadvanced\u002Fprofiling","Go - 性能分析","掌握 Go 的性能分析工具：pprof、trace、benchmark。",{"path":157,"title":158,"description":11},"\u002Fgolang\u002Fcore\u002Fgo-basic","Go - 基础语法",{"path":160,"title":161,"description":11},"\u002Fgolang\u002Fcore\u002Fgo-composite","Go - 复合类型",{"path":163,"title":164,"description":11},"\u002Fgolang\u002Fcore\u002Fgo-control","Go - 流程控制",{"path":166,"title":167,"description":168},"\u002Fgolang\u002Fcore\u002Fgo-error","Go - 错误处理","Go 使用显式的错误返回值来处理错误，而不是异常机制。",{"path":170,"title":171,"description":11},"\u002Fgolang\u002Fcore\u002Fgo-function","Go - 函数",{"path":173,"title":174,"description":11},"\u002Fgolang\u002Fcore\u002Fgo-install","Go - 环境搭建",{"path":176,"title":177,"description":11},"\u002Fgolang\u002Fcore\u002Fgo-interface","Go - 接口",{"path":179,"title":180,"description":181},"\u002Fgolang\u002Fcore\u002Fgo-module","Go - 包管理","Go Modules 是 Go 1.11 引入的官方依赖管理方案，Go 1.16 后成为默认模式。",{"path":183,"title":184,"description":185},"\u002Fgolang\u002Fdistributed\u002Fgrpc","Go - gRPC","gRPC 是 Google 开发的高性能 RPC 框架，使用 Protocol Buffers 作为序列化协议。",{"path":187,"title":188,"description":189},"\u002Fgolang\u002Fdistributed\u002Fmicroservice","Go - 微服务","微服务架构的核心组件：服务发现、负载均衡、熔断降级。",{"path":191,"title":192,"description":193},"\u002Fgolang\u002Fdistributed\u002Fmq","Go - 消息队列","使用 Go 操作 Kafka 和 RabbitMQ。",{"path":195,"title":196,"description":197},"\u002Fgolang\u002Fdistributed\u002Fredis","Go - Redis","使用 go-redis 操作 Redis，实现缓存、分布式锁等功能。",{"path":199,"title":200,"description":201},"\u002Fgolang\u002Fengineering\u002Fconfig","Go - 配置管理","使用 viper 进行配置管理，支持多种配置格式和配置中心。",{"path":203,"title":204,"description":205},"\u002Fgolang\u002Fengineering\u002Fdocker","Go - Docker 部署","使用 Docker 容器化部署 Go 应用。",{"path":207,"title":208,"description":209},"\u002Fgolang\u002Fengineering\u002Fkubernetes","Go - Kubernetes 部署","在 Kubernetes 上部署和管理 Go 应用。",{"path":211,"title":212,"description":213},"\u002Fgolang\u002Fengineering\u002Flogging","Go - 日志系统","使用 zap 和 logrus 构建高性能结构化日志系统。",{"path":215,"title":216,"description":217},"\u002Fgolang\u002Fengineering\u002Ftesting","Go - 单元测试","Go 内置了强大的测试框架，掌握测试是编写高质量代码的基础。",{"path":219,"title":220,"description":221},"\u002Fgolang\u002Fstdlib\u002Fbufio","bufio","在 Go 语言中，bufio 包提供了带缓冲的 I\u002FO 操作，能够提高读写性能。以下是一些常用的 bufio 包 API 及其详细说明：",{"path":223,"title":224,"description":225},"\u002Fgolang\u002Fstdlib\u002Fcontainer","container","在Go语言标准库中，container 包提供了几种常用的数据结构实现，这些数据结构对于高效地管理和操作数据非常有用。以下是 container 包中主要的数据结构：",{"path":227,"title":228,"description":229},"\u002Fgolang\u002Fstdlib\u002Fcrypto","crypto","在 Go 语言中，crypto 包提供了一组用于加密和解密的功能。以下是一些常用的 crypto 包及其子包的 API 及其详细说明：",{"path":231,"title":232,"description":233},"\u002Fgolang\u002Fstdlib\u002Fencoding-csv","encoding\u002Fcsv","在 Go 语言中，encoding\u002Fcsv 包提供了对 CSV（逗号分隔值）文件进行读写的功能。以下是一些常用的 encoding\u002Fcsv 包的 API 及其详细说明：",{"path":235,"title":236,"description":237},"\u002Fgolang\u002Fstdlib\u002Fencoding-json","encoding\u002Fjson","在 Go 语言中，encoding\u002Fjson 包提供了对 JSON 数据进行编码和解码的功能。以下是一些常用的 encoding\u002Fjson 包的 API 及其详细说明：",{"path":239,"title":240,"description":241},"\u002Fgolang\u002Fstdlib\u002Fencoding-xml","encoding\u002Fxml","在 Go 语言中，encoding\u002Fxml 包提供了对 XML 数据进行编码和解码的功能。以下是一些常用的 encoding\u002Fxml 包的 API 及其详细说明：",{"path":243,"title":244,"description":245},"\u002Fgolang\u002Fstdlib\u002Fflag","flag","在Go语言中，flag 包是用于处理命令行参数的标准库，它提供了一种简单而直接的方式来解析和使用命令行参数。下面是关于 flag 包的一些基本介绍和常用功能：",{"path":247,"title":248,"description":249},"\u002Fgolang\u002Fstdlib\u002Ffmt","fmt","在 Go 语言的标准库中，fmt 包是非常重要的，它提供了处理格式化输入和输出的基本工具。以下是一些 fmt 包内常用的API：",{"path":251,"title":252,"description":253},"\u002Fgolang\u002Fstdlib\u002Fhttp","net\u002Fhttp","在 Go 语言中，net\u002Fhttp 包提供了用于构建 HTTP 客户端和服务器的强大工具。以下是一些常用的 net\u002Fhttp 包的 API 及其详细说明：",{"path":255,"title":256,"description":257},"\u002Fgolang\u002Fstdlib\u002Fio","io","在 Go 语言中，io 包提供了基本的输入输出功能。以下是一些常用的 io 包的 API 及其详细说明：",{"path":259,"title":260,"description":261},"\u002Fgolang\u002Fstdlib\u002Flog","log","在 Go 语言中，log 包提供了简单的日志记录功能。以下是一些常用的 log 包的 API 及其详细说明：",{"path":263,"title":264,"description":265},"\u002Fgolang\u002Fstdlib\u002Fmath","math","在 Go 语言中，math 包提供了基本的数学函数和常量。以下是一些常用的 math 包的 API 及其详细说明：",{"path":267,"title":268,"description":11},"\u002Fgolang\u002Fstdlib\u002Fnet","net",{"path":270,"title":271,"description":272},"\u002Fgolang\u002Fstdlib\u002Fos","os","在Go语言中，os 包是一个非常重要且常用的标准库，它提供了与操作系统交互的功能，包括文件操作、环境变量管理、进程管理等。下面是一些 os 包中常用的功能和API：",{"path":274,"title":275,"description":276},"\u002Fgolang\u002Fstdlib\u002Fsort","order","在 Go 语言中，sort 包提供了对切片和用户定义的集合进行排序的函数。它实现了常见的排序算法，如快速排序（Quicksort）和堆排序（Heapsort），并且为自定义集合提供了接口，使得用户可以根据特定的需求进行排序。",{"path":278,"title":279,"description":280},"\u002Fgolang\u002Fstdlib\u002Fstrconv","strconv","在 Go 语言中，strconv 包提供了字符串和基本数据类型之间的转换函数，例如将整数转换为字符串、字符串转换为整数，以及其他类型之间的转换。这些功能非常有用，特别是在处理用户输入或从外部数据源读取数据时。",{"path":282,"title":283,"description":284},"\u002Fgolang\u002Fstdlib\u002Ftime","time","在 Go 语言中，time 包提供了处理时间和日期的功能。以下是一些常用的 time 包的 API 及其详细说明：",{"path":286,"title":287,"description":11},"\u002Fgolang\u002Fweb\u002Fgin\u002Ferror","Gin - 错误处理",{"path":289,"title":290,"description":11},"\u002Fgolang\u002Fweb\u002Fgin\u002Ffile","Gin - 文件处理",{"path":292,"title":293,"description":11},"\u002Fgolang\u002Fweb\u002Fgin\u002Fmiddleware","Gin - 中间件",{"path":295,"title":296,"description":297},"\u002Fgolang\u002Fweb\u002Fgin\u002Fquickstart","Gin - 快速开始","Gin 是目前最流行的 Go Web 框架，以高性能和简洁 API 著称。",{"path":299,"title":300,"description":11},"\u002Fgolang\u002Fweb\u002Fgin\u002Frequest","Gin - 请求处理",{"path":302,"title":303,"description":11},"\u002Fgolang\u002Fweb\u002Fgin\u002Fresponse","Gin - 响应处理",{"path":305,"title":306,"description":11},"\u002Fgolang\u002Fweb\u002Fgin\u002Frouter","Gin - 路由",{"path":308,"title":309,"description":11},"\u002Fgolang\u002Fweb\u002Fgin\u002Fvalidation","Gin - 参数校验",{"path":311,"title":312,"description":11},"\u002Fgolang\u002Fweb\u002Fgorm\u002Fassociation","GORM - 关联关系",{"path":314,"title":315,"description":11},"\u002Fgolang\u002Fweb\u002Fgorm\u002Fcrud","GORM - CRUD 操作",{"path":317,"title":318,"description":11},"\u002Fgolang\u002Fweb\u002Fgorm\u002Fmodel","GORM - 模型定义",{"path":320,"title":321,"description":11},"\u002Fgolang\u002Fweb\u002Fgorm\u002Fperformance","GORM - 日志与性能",{"path":323,"title":324,"description":11},"\u002Fgolang\u002Fweb\u002Fgorm\u002Fquery","GORM - 高级查询",{"path":326,"title":327,"description":328},"\u002Fgolang\u002Fweb\u002Fgorm\u002Fquickstart","GORM - 快速开始","GORM 是 Go 语言最流行的 ORM 库，功能强大，使用简单。",{"path":330,"title":331,"description":11},"\u002Fgolang\u002Fweb\u002Fgorm\u002Ftransaction","GORM - 事务与 Hook",{"path":333,"title":334,"description":335},"\u002Finterview\u002Fbasic","计算机基础面经","本章节汇总了面试中常见的通用技术概念，不局限于特定语言或数据库，是考察技术内功的关键考点。",{"path":337,"title":338,"description":339},"\u002Finterview\u002Fgolang","Golang 面试题","Go 语言面试高频考点，覆盖基础语法、数据结构、并发编程、内存管理、GC、调度器等核心知识。",{"path":341,"title":342,"description":343},"\u002Finterview\u002Fk8s","Kubernetes 面试题","Kubernetes（K8s）面试高频考点，覆盖架构原理、核心资源、网络存储、调度策略、运维监控等核心知识。",{"path":345,"title":346,"description":347},"\u002Finterview\u002Fmysql","MySQL 面试题","MySQL 数据库面试高频考点，覆盖索引、事务、锁、优化、主从复制等核心知识。",{"path":349,"title":350,"description":351},"\u002Finterview\u002Fredis","Redis 面试题","Redis 面试高频考点，覆盖数据结构、持久化、集群、缓存一致性、性能优化等核心知识。",{"path":353,"title":354,"description":355},"\u002Finterview\u002Frocketmq","RocketMQ 面试题","RocketMQ 面试高频考点，覆盖消息模型、可靠性、顺序消息、事务消息、存储与高可用等核心知识。",{"path":357,"title":358,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Flist-arraylist","List - ArrayList 源码解析",{"path":360,"title":361,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Flist-linkedlist","List - LinkedList 源码解析",{"path":363,"title":364,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Flist-stack","List - Satck源码解析",{"path":366,"title":367,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Flist-vectore","List - Vector 源码解析",{"path":369,"title":370,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Fmap-hashmap","Map - HashMap 源码解析",{"path":372,"title":373,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Fmap-linkedhashmap","Map - LinkedHashMap 源码解析",{"path":375,"title":376,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Fmap-treemap","Map - TreeMap 源码解析",{"path":378,"title":379,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Fqueue-deque","Queue - Deque 接口解析",{"path":381,"title":382,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Fqueue-queue","Queue - Queue 接口解析",{"path":384,"title":385,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Fset-hashset","Set - HashSet源码解析",{"path":387,"title":388,"description":11},"\u002Fother\u002Fjava\u002Fcollection\u002Fset-linkedhashset","Set - LinkedHashSet 源码解析",{"path":390,"title":391,"description":392},"\u002Fother\u002Fjava\u002Fcollection\u002Fset-treeset","Set - TreeSet源码解析","TreeSet 是一个 Set 集合接口的实现类，与 HashSet 类似，其底层也是通过维护了一个 TreeMap 对象来封装了一些实现方法，故本篇不再对 TreeSet 的底层原理进行详细说明，仅对常用 API 做简单介绍，如需了解 TreeMap 的底层实现原理，请移步 Map - HashMap 源码解析",{"path":394,"title":395,"description":11},"\u002Fother\u002Fjava\u002Fcore\u002Fannotation","Java核心 - 注解",{"path":397,"title":398,"description":11},"\u002Fother\u002Fjava\u002Fcore\u002Fbasic-grammar","Java核心 - 基础语法",{"path":400,"title":401,"description":11},"\u002Fother\u002Fjava\u002Fcore\u002Fclass-and-object","Java核心 - 面向对象",{"path":403,"title":404,"description":11},"\u002Fother\u002Fjava\u002Fcore\u002Fcommon-classes","Java核心 - 常用类",{"path":406,"title":407,"description":11},"\u002Fother\u002Fjava\u002Fcore\u002Fexception","Java核心 - 异常处理",{"path":409,"title":410,"description":11},"\u002Fother\u002Fjava\u002Fcore\u002Fgenerics","Java核心 - 泛型",{"path":412,"title":413,"description":11},"\u002Fother\u002Fjava\u002Fcore\u002Fjdk-env-path","Java核心 - 环境搭建",{"path":415,"title":416,"description":11},"\u002Fother\u002Fjava\u002Fcore\u002Freflection","Java核心 - 反射",{"path":418,"title":419,"description":11},"\u002Fother\u002Fjava\u002Fcore\u002Fstring","Java核心 - String 字符串",{"path":421,"title":422,"description":423},"\u002Fother\u002Fjava\u002Fio\u002Fbuffer-stream","Java IO - 缓冲流","缓冲流是对基本流的包装，通过内置缓冲区减少系统调用次数，大幅提升读写效率。",{"path":425,"title":426,"description":427},"\u002Fother\u002Fjava\u002Fio\u002Fbyte-stream","Java IO - 字节流","字节流是 Java IO 中最基本的流类型，以字节（byte）为单位进行数据读写，可以处理任意类型的文件。",{"path":429,"title":430,"description":431},"\u002Fother\u002Fjava\u002Fio\u002Fchar-stream","Java IO - 字符流","字符流以字符为单位进行读写，专门用于处理文本文件。相比字节流，字符流能够正确处理字符编码，避免中文乱码问题。",{"path":433,"title":434,"description":11},"\u002Fother\u002Fjava\u002Fio\u002Ffile","Java IO - File 类",{"path":436,"title":437,"description":11},"\u002Fother\u002Fjava\u002Fio\u002Fio-stream-system","Java IO - IO流概述",{"path":439,"title":440,"description":441},"\u002Fother\u002Fjava\u002Fio\u002Fnio","Java IO - NIO","NIO（New IO）是 JDK 1.4 引入的新 IO 模型，提供了更高效的 IO 操作方式，支持非阻塞 IO 和多路复用。",{"path":443,"title":444,"description":445},"\u002Fother\u002Fjava\u002Fjvm\u002Fclass-loading","类加载机制","类加载机制是 JVM 将 .class 文件加载到内存，并对数据进行校验、转换解析和初始化，最终形成可被 JVM 直接使用的 Java 类型的过程。",{"path":447,"title":448,"description":449},"\u002Fother\u002Fjava\u002Fjvm\u002Fgarbage-collection","垃圾回收","垃圾回收（Garbage Collection，GC）是 JVM 自动管理内存的机制，负责回收不再使用的对象所占用的内存。",{"path":451,"title":452,"description":453},"\u002Fother\u002Fjava\u002Fjvm\u002Fjvm-memory","JVM 内存结构","JVM 在执行 Java 程序时，会把它管理的内存划分为若干个不同的数据区域。这些区域有各自的用途、创建和销毁时间。",{"path":455,"title":456,"description":457},"\u002Fother\u002Fjava\u002Fjvm\u002Fjvm-tuning","JVM 调优","JVM 调优是优化 Java 应用性能的重要手段，主要包括参数配置、性能监控和问题排查。",{"path":459,"title":460,"description":461},"\u002Fother\u002Fjava\u002Fthread\u002Fatomic","原子类","Java 原子类（Atomic Classes）提供了一种无锁的线程安全方式，基于 CAS（Compare-And-Swap）操作实现。",{"path":463,"title":464,"description":465},"\u002Fother\u002Fjava\u002Fthread\u002Fcompletable-future","CompletableFuture","CompletableFuture 是 JDK 8 引入的异步编程工具，实现了 Future 和 CompletionStage 接口，支持函数式编程和链式调用。",{"path":467,"title":468,"description":469},"\u002Fother\u002Fjava\u002Fthread\u002Fconcurrent-collections","并发集合","Java 并发包提供了多种线程安全的集合类，用于替代传统的同步集合（如 Collections.synchronizedList）。",{"path":471,"title":472,"description":473},"\u002Fother\u002Fjava\u002Fthread\u002Fconcurrent-utils","并发工具类","Java 并发包提供了多种实用的并发工具类，用于控制线程之间的协调与同步。",{"path":475,"title":476,"description":11},"\u002Fother\u002Fjava\u002Fthread\u002Fsynchronized-lock","同步机制",{"path":478,"title":479,"description":11},"\u002Fother\u002Fjava\u002Fthread\u002Fthread-basic","线程基础",{"path":481,"title":482,"description":11},"\u002Fother\u002Fjava\u002Fthread\u002Fthread-pool","线程池",{"path":484,"title":485,"description":486},"\u002Fother\u002Fspring-series\u002Fspring\u002Fannotations-beans","Spring - 基于注解管理Bean","从 Java 5 开始，Java 增加了对注解（Annotation）的支持，它是代码中的一种特殊标记，可以在编译、类加载和运行时被读取，执行相应的处理。开发人员可以通过注解在不改变原有代码和逻辑的情况下，在源代码中嵌入补充信息。",{"path":488,"title":489,"description":490},"\u002Fother\u002Fspring-series\u002Fspring\u002Fimplement-ioc","Spring - 原理手写IoC","Spring 框架的 IOC 是基于 Java 反射机制实现的，在学习手写 IoC 之前，你需要具备一定的 Java 反射相关的知识，参考本站内的 Java 教程。",{"path":492,"title":493,"description":11},"\u002Fother\u002Fspring-series\u002Fspring\u002Fintroduction-case","Spring - 入门案例",{"path":495,"title":496,"description":11},"\u002Fother\u002Fspring-series\u002Fspring\u002Fspring-aop","Spring - 面向切面AOP",{"path":498,"title":499,"description":11},"\u002Fother\u002Fspring-series\u002Fspring\u002Fspring-aot","Spring - AOT提前编译",{"path":501,"title":502,"description":503},"\u002Fother\u002Fspring-series\u002Fspring\u002Fspring-data-validation","Spring - 数据校验","在开发中，我们经常遇到参数校验的需求，比如用户注册的时候，要校验用户名不能为空、用户名长度不超过20个字符、手机号是合法的手机号格式等等。如果使用普通方式，我们会把校验的代码和真正的业务处理逻辑耦合在一起，而且如果未来要新增一种校验逻辑也需要在修改多个地方。而spring validation允许通过注解的方式来定义对象校验规则，把校验和业务逻辑分离开，让代码编写更加方便。Spring Validation其实就是对Hibernate Validator进一步的封装，方便在Spring中使用。",{"path":505,"title":506,"description":11},"\u002Fother\u002Fspring-series\u002Fspring\u002Fspring-i18n","Spring - 国际化i18n",{"path":508,"title":509,"description":510},"\u002Fother\u002Fspring-series\u002Fspring\u002Fspring-ioc","Spring - IOC容器","IoC 是 Inversion of Control 的简写，译为“控制反转”，它不是一门技术，而是一种设计思想，是一个重要的面向对象编程法则，能够指导我们如何设计出松耦合、更优良的程序。",{"path":512,"title":513,"description":514},"\u002Fother\u002Fspring-series\u002Fspring\u002Fspring-junit","Spring - 单元测试JUnit","在之前的测试方法中，几乎都能看到以下的两行代码：",{"path":516,"title":517,"description":11},"\u002Fother\u002Fspring-series\u002Fspring\u002Fspring-resources","Spring - 资源操作",{"path":519,"title":520,"description":11},"\u002Fother\u002Fspring-series\u002Fspring\u002Fspring-summarize","Spring - Spring概述",{"path":522,"title":523,"description":11},"\u002Fother\u002Fspring-series\u002Fspring\u002Fspring-transaction","Spring - 事务",{"path":525,"title":526,"description":11},"\u002Fother\u002Fspring-series\u002Fspring\u002Fxml-beans","Spring - 基于XML管理Bean",{"path":528,"title":529,"description":11},"\u002Fother\u002Fspring-series\u002Fspringboot\u002Fspringboot-config","SpringBoot - 配置详解",{"path":531,"title":532,"description":11},"\u002Fother\u002Fspring-series\u002Fspringboot\u002Fspringboot-data","SpringBoot - 数据访问",{"path":534,"title":535,"description":11},"\u002Fother\u002Fspring-series\u002Fspringboot\u002Fspringboot-quickstart","SpringBoot - 快速入门",{"path":537,"title":538,"description":11},"\u002Fother\u002Fspring-series\u002Fspringboot\u002Fspringboot-web","SpringBoot - Web 开发",{"path":540,"title":541,"description":11},"\u002Fother\u002Fspring-series\u002Fspringcloud\u002Fspringcloud-config","SpringCloud - 配置中心",{"path":543,"title":544,"description":11},"\u002Fother\u002Fspring-series\u002Fspringcloud\u002Fspringcloud-discovery","SpringCloud - 服务注册与发现",{"path":546,"title":547,"description":11},"\u002Fother\u002Fspring-series\u002Fspringcloud\u002Fspringcloud-feign","SpringCloud - 服务调用",{"path":549,"title":550,"description":11},"\u002Fother\u002Fspring-series\u002Fspringcloud\u002Fspringcloud-gateway","SpringCloud - 服务网关",{"path":552,"title":553,"description":11},"\u002Fother\u002Fspring-series\u002Fspringcloud\u002Fspringcloud-introduction","SpringCloud - 微服务概述",{"path":555,"title":556,"description":11},"\u002Fother\u002Fspring-series\u002Fspringcloud\u002Fspringcloud-sentinel","SpringCloud - 服务保护",{"path":558,"title":559,"description":11},"\u002Fother\u002Fspring-series\u002Fspringmvc\u002Fspringmvc-databind","SpringMVC - 数据绑定与转换",{"path":561,"title":562,"description":11},"\u002Fother\u002Fspring-series\u002Fspringmvc\u002Fspringmvc-exception","SpringMVC - 异常处理",{"path":564,"title":565,"description":11},"\u002Fother\u002Fspring-series\u002Fspringmvc\u002Fspringmvc-interceptor","SpringMVC - 拦截器",{"path":567,"title":568,"description":11},"\u002Fother\u002Fspring-series\u002Fspringmvc\u002Fspringmvc-introduction","SpringMVC - 简介与环境搭建",{"path":570,"title":571,"description":11},"\u002Fother\u002Fspring-series\u002Fspringmvc\u002Fspringmvc-request","SpringMVC - 请求处理",{"path":573,"title":574,"description":11},"\u002Fother\u002Fspring-series\u002Fspringmvc\u002Fspringmvc-response","SpringMVC - 响应处理",{"path":576,"title":577,"description":578},"\u002Fproject\u002Frocket-leaf\u002Farchitecture","项目架构","Rocket-Leaf 的目录结构、模块划分、数据流向，以及各层之间的依赖关系。",{"path":580,"title":581,"description":582},"\u002Fproject\u002Frocket-leaf\u002Fbackend-layers","后端分层设计","Rocket-Leaf 的 model \u002F rocketmq \u002F service 三层结构，以及服务之间的依赖关系与设计取舍。",{"path":584,"title":585,"description":586},"\u002Fproject\u002Frocket-leaf\u002Fclient-manager","RocketMQ 客户端管理器","AdminClientManager 的多客户端池、默认连接懒加载、自动重连重试的设计与实现。",{"path":588,"title":589,"description":590},"\u002Fproject\u002Frocket-leaf\u002Fencryption","连接信息加密存储","AES-256-GCM + SHA-256 字段级派生密钥的实现，以及如何在不破坏兼容性的前提下为历史明文数据做透明迁移。",{"path":592,"title":593,"description":594},"\u002Fproject\u002Frocket-leaf\u002Ffrontend","前端结构与类型绑定","React + Vite 目录组织、自动生成的 Wails 绑定、api 薄封装与自定义 hooks 的职责划分。",{"path":596,"title":597,"description":598},"\u002Fproject\u002Frocket-leaf","项目简介","Rocket-Leaf 是一款基于 Wails v3 构建的跨平台 RocketMQ 桌面管理客户端，Go 后端 + React 前端。本文档系列拆解它的架构与关键实现。",{"path":600,"title":601,"description":602},"\u002Fproject\u002Frocket-leaf\u002Fwails-v3","Wails v3 入门","Wails v3 的核心概念、Service 绑定机制，以及 Rocket-Leaf 是如何用它把 Go 后端和 React 前端打通的。",{"path":604,"title":605,"description":11},"\u002Ftutorials\u002Fcloud\u002Fdocker\u002Fdocker-basic","Docker - 入门基础",{"path":607,"title":608,"description":609},"\u002Ftutorials\u002Fcloud\u002Fdocker\u002Fdocker-compose","Docker - Compose","在部署应用时，常常使用到不止一个容器，那么在部署容器的时候就需要一个一个进行部署，这样的部署过程也相对来说比较繁琐复杂，也容易出问题，那么有没有一种更为简单的方法呢？",{"path":611,"title":612,"description":613},"\u002Ftutorials\u002Fcloud\u002Fdocker\u002Fdocker-container-connection","Docker - 容器互联","在上一个章节中我们学习了 Docker 容器的端口映射，可以将 Docker 容器和本地以及网络中的端口进行连接起来。",{"path":615,"title":616,"description":11},"\u002Ftutorials\u002Fcloud\u002Fdocker\u002Fdocker-dockerfile","Docker - Dockerfile",{"path":618,"title":619,"description":11},"\u002Ftutorials\u002Fcloud\u002Fdocker\u002Fdocker-helloworld","Docker - HelloWorld",{"path":621,"title":622,"description":11},"\u002Ftutorials\u002Fcloud\u002Fdocker\u002Fdocker-install","Docker - 安装",{"path":624,"title":625,"description":11},"\u002Ftutorials\u002Fcloud\u002Fdocker\u002Fdocker-introduce","Docker - 简介",{"path":627,"title":628,"description":11},"\u002Ftutorials\u002Fcloud\u002Fdocker\u002Fdocker-object","Docker - 镜像、容器、仓库",{"path":630,"title":631,"description":632},"\u002Ftutorials\u002Fcloud\u002Fdocker\u002Fdocker-warehouse","Docker - 仓库管理","仓库是集中存放资源的地方，代码仓库是存放代码的，那么Docker 中的仓库就是存放 Docker 镜像的。",{"path":634,"title":635,"description":636},"\u002Ftutorials\u002Fcloud\u002Fdocker\u002Fdocker-web-containers","Docker - WEB应用实例","在之前的章节中，仅对普通容器进行了演示，但在实际中常常使用到 Docker 容器中的 WEB 应用程序。",{"path":638,"title":639,"description":11},"\u002Ftutorials\u002Fcloud\u002Fkubernetes\u002Fk8s-config","Kubernetes - ConfigMap 与 Secret",{"path":641,"title":642,"description":11},"\u002Ftutorials\u002Fcloud\u002Fkubernetes\u002Fk8s-helm","Kubernetes - Helm 包管理",{"path":644,"title":645,"description":11},"\u002Ftutorials\u002Fcloud\u002Fkubernetes\u002Fk8s-install","Kubernetes - 集群安装",{"path":647,"title":648,"description":11},"\u002Ftutorials\u002Fcloud\u002Fkubernetes\u002Fk8s-introduction","Kubernetes - 简介与架构",{"path":650,"title":651,"description":11},"\u002Ftutorials\u002Fcloud\u002Fkubernetes\u002Fk8s-kubectl","Kubernetes - kubectl 命令行工具",{"path":653,"title":654,"description":11},"\u002Ftutorials\u002Fcloud\u002Fkubernetes\u002Fk8s-monitoring","Kubernetes - 监控与日志",{"path":656,"title":657,"description":11},"\u002Ftutorials\u002Fcloud\u002Fkubernetes\u002Fk8s-network-security","Kubernetes - 网络与安全",{"path":659,"title":660,"description":11},"\u002Ftutorials\u002Fcloud\u002Fkubernetes\u002Fk8s-service","Kubernetes - Service 与 Ingress",{"path":662,"title":663,"description":11},"\u002Ftutorials\u002Fcloud\u002Fkubernetes\u002Fk8s-storage","Kubernetes - 持久化存储",{"path":665,"title":666,"description":11},"\u002Ftutorials\u002Fcloud\u002Fkubernetes\u002Fk8s-workload","Kubernetes - 工作负载资源",{"path":668,"title":669,"description":11},"\u002Ftutorials\u002Fcloud\u002Flinux\u002Flinux-bash","Linux - Bash 基础语法",{"path":671,"title":672,"description":11},"\u002Ftutorials\u002Fcloud\u002Flinux\u002Flinux-file-directory","Linux - 文件与目录操作",{"path":674,"title":675,"description":11},"\u002Ftutorials\u002Fcloud\u002Flinux\u002Flinux-network","Linux - 网络配置",{"path":677,"title":678,"description":11},"\u002Ftutorials\u002Fcloud\u002Flinux\u002Flinux-package","Linux - 软件包管理",{"path":680,"title":681,"description":11},"\u002Ftutorials\u002Fcloud\u002Flinux\u002Flinux-process","Linux - 进程管理",{"path":683,"title":684,"description":11},"\u002Ftutorials\u002Fcloud\u002Flinux\u002Flinux-scripts","Linux - 常用脚本示例",{"path":686,"title":687,"description":11},"\u002Ftutorials\u002Fcloud\u002Flinux\u002Flinux-service","Linux - 服务管理",{"path":689,"title":690,"description":11},"\u002Ftutorials\u002Fcloud\u002Flinux\u002Flinux-user-permission","Linux - 用户与权限管理",{"path":692,"title":693,"description":11},"\u002Ftutorials\u002Fcloud\u002Fnginx\u002Fnginx-https","Nginx - HTTPS 配置",{"path":695,"title":696,"description":11},"\u002Ftutorials\u002Fcloud\u002Fnginx\u002Fnginx-install","Nginx - 安装与配置",{"path":698,"title":699,"description":11},"\u002Ftutorials\u002Fcloud\u002Fnginx\u002Fnginx-loadbalance","Nginx - 负载均衡",{"path":701,"title":702,"description":11},"\u002Ftutorials\u002Fcloud\u002Fnginx\u002Fnginx-optimization","Nginx - 性能优化",{"path":704,"title":705,"description":11},"\u002Ftutorials\u002Fcloud\u002Fnginx\u002Fnginx-proxy","Nginx - 反向代理",{"path":707,"title":708,"description":11},"\u002Ftutorials\u002Fcloud\u002Fnginx\u002Fnginx-static","Nginx - 静态资源服务",{"path":710,"title":711,"description":11},"\u002Ftutorials\u002Fcloud\u002Fnginx\u002Fnginx-vhost","Nginx - 虚拟主机配置",{"path":713,"title":714,"description":715},"\u002Ftutorials\u002Fdatabase\u002Fmysql\u002Fmysql-architecture","MySQL 高可用架构","主从复制、读写分离、分库分表。",{"path":717,"title":718,"description":719},"\u002Ftutorials\u002Fdatabase\u002Fmysql\u002Fmysql-index","MySQL 索引","索引是帮助 MySQL 高效获取数据的有序数据结构。",{"path":721,"title":722,"description":723},"\u002Ftutorials\u002Fdatabase\u002Fmysql\u002Fmysql-lock","MySQL 锁","锁用于解决并发访问时的数据一致性问题。",{"path":725,"title":726,"description":727},"\u002Ftutorials\u002Fdatabase\u002Fmysql\u002Fmysql-optimize","MySQL 性能优化","SQL 优化是后端开发必备技能。",{"path":729,"title":730,"description":731},"\u002Ftutorials\u002Fdatabase\u002Fmysql\u002Fmysql-transaction","MySQL 事务","事务是一组不可分割的操作，要么全部成功，要么全部失败。",{"path":733,"title":734,"description":735},"\u002Ftutorials\u002Fdatabase\u002Fmysql\u002Fsql-advanced","SQL 进阶","多表查询、子查询、函数、视图、存储过程。",{"path":737,"title":738,"description":739},"\u002Ftutorials\u002Fdatabase\u002Fmysql\u002Fsql-basic","SQL 基础","SQL（Structured Query Language）是操作关系型数据库的标准语言。",{"path":741,"title":742,"description":743},"\u002Ftutorials\u002Fdatabase\u002Fredis\u002Fredis-advanced","Redis 进阶功能","事务、发布订阅、Lua 脚本、Pipeline。",{"path":745,"title":746,"description":747},"\u002Ftutorials\u002Fdatabase\u002Fredis\u002Fredis-basic","Redis 基础","Redis 安装配置与基本命令。",{"path":749,"title":750,"description":751},"\u002Ftutorials\u002Fdatabase\u002Fredis\u002Fredis-cluster","Redis 高可用","主从复制、哨兵、Cluster 集群。",{"path":753,"title":754,"description":755},"\u002Ftutorials\u002Fdatabase\u002Fredis\u002Fredis-datatype","Redis 数据类型","Redis 5 种基本数据类型 + 4 种特殊类型。",{"path":757,"title":758,"description":759},"\u002Ftutorials\u002Fdatabase\u002Fredis\u002Fredis-optimize","Redis 性能优化","内存优化、缓存问题、最佳实践。",{"path":761,"title":762,"description":763},"\u002Ftutorials\u002Fdatabase\u002Fredis\u002Fredis-persistence","Redis 持久化","Redis 提供 RDB 和 AOF 两种持久化方式。",{"path":765,"title":766,"description":767},"\u002Ftutorials\u002Fdatabase\u002Fredis\u002Fredis-principle","Redis 底层原理","数据结构、线程模型、网络模型。",{"path":769,"title":770,"description":771},"\u002Ftutorials\u002Fdev-idea\u002Fdesign-patterns\u002Fbehaiver-patterns\u002Fobserver-pattern","观察者模式","观察者模式属于行为型模式，定义了对象之间的一对多的依赖关系，在这种模式中，当一个对象的状态发生变化时，所有依赖于它的对象都会得到通知，并且执行相关操作。观察者模式又被成为“发布—订阅模式”，即发布者发生改变后，会通知所有订阅者。",{"path":773,"title":774,"description":11},"\u002Ftutorials\u002Fdev-idea\u002Fdesign-patterns\u002Fcreate-patterns\u002Ffactory-pattern","工厂模式",{"path":776,"title":777,"description":778},"\u002Ftutorials\u002Fdev-idea\u002Fdesign-patterns\u002Fcreate-patterns\u002Fsingleton-pattern","单例模式","单例模式是最常用的设计模式之一，他可以保证在整个应用中，某个类只存在一个实例化对象，即全局使用到该类的只有一个对象，这种模式在需要限制某些类的实例数量时非常有用，通常全局只需要一个该对象即可，如一些配置文件映射对象、数据库连接对象等。",{"path":780,"title":781,"description":782},"\u002Ftutorials\u002Fdev-idea\u002Fdesign-patterns\u002Fstructural-patterns\u002Fadapter-pattern","适配器模式","适配器模式是一种结构型模式，可以将一个类的接口转换成客户端所期望的另一种接口，适配器模式可以帮助开发人员在不修改现有代码的情况下，将不兼容的类组合在一起。",{"path":784,"title":785,"description":786},"\u002Ftutorials\u002Fdev-tools\u002Fgit\u002Fgit-basic-operations","Git 创建版本库","在 Git 上创建版本库有两种方式，一种是直接拷贝远程 Git 仓库到本地，另外一种是我们自己创建本地的版本库。",{"path":788,"title":789,"description":11},"\u002Ftutorials\u002Fdev-tools\u002Fgit\u002Fgit-branch-manage","Git 分支管理",{"path":791,"title":792,"description":11},"\u002Ftutorials\u002Fdev-tools\u002Fgit\u002Fgit-content-operations","Git 仓库内容操作",{"path":794,"title":795,"description":11},"\u002Ftutorials\u002Fdev-tools\u002Fgit\u002Fgit-introduce-install","Git 介绍和安装",{"path":797,"title":798,"description":11},"\u002Ftutorials\u002Fdev-tools\u002Fgit\u002Fgit-remote-manage","Git 远程管理",{"path":800,"title":801,"description":11},"\u002Ftutorials\u002Fdev-tools\u002Fgit\u002Fgit-workspace-index-repo","Git 工作原理",{"path":803,"title":804,"description":11},"\u002Ftutorials\u002Fdev-tools\u002Fhomebrew","HomeBrew 教程",{"path":806,"title":807,"description":11},"\u002Ftutorials\u002Fdev-tools\u002Fidea\u002Fshortcuts","快捷键",{"path":809,"title":810,"description":11},"\u002Ftutorials\u002Fdev-tools\u002Fmaven\u002Fintroduce-install-config","Maven - 介绍、安装、配置",{"path":812,"title":813,"description":11},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Fbasic-knowledge","2. 基础知识",{"path":815,"title":816,"description":817},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Fcomponent-communication","9. 组件通信","在前面的章节内，介绍了 Vue 中最核心的内容——组件的介绍和使用，和 Java 等编程语言相反，组件并不近似于这些变成语言中的类，类可以通过类或者其实例化的对象来相互交互，但 Vue 组件之间的作用域是相互独立的，这就意味着不同组件之间的数据无法相互引用。",{"path":819,"title":820,"description":821},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Fcomputed","4. 计算属性","虽然直接在模板中使用表达式方便，但是如果在模板中添加很多逻辑，会让模板变的臃肿且难维护，耦合度较高。有没有一种简单的方式来实现呢？答案是有的。",{"path":823,"title":824,"description":11},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Fcreate-vue-project","1. 环境搭建及安装",{"path":826,"title":827,"description":828},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Flife-cycle","6. 生命周期","生命周期是指组件从创建、挂载、更新到销毁的整个过程中所经历的一系列阶段。在 Vue 中，每个组件都有自己的生命周期，可以通过生命周期钩子函数来监听和处理组件在不同阶段的行为和状态。",{"path":830,"title":831,"description":11},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Fother-api","10. 其他 API",{"path":833,"title":834,"description":11},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Fpinia","8. Pinia",{"path":836,"title":837,"description":11},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Frouter","7. 路由",{"path":839,"title":840,"description":11},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Ftemplate-grammar","3. 指令及模板语法",{"path":842,"title":843,"description":11},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Fvue3-new-component","11. Vue3 新组件",{"path":845,"title":846,"description":847},"\u002Ftutorials\u002Ffront-end\u002Fvue3\u002Fwatch","5. 监视","Watch 是 Vue 提供的一个用于监视响应式数据变化并执行相应操作的 API，能够对响应式数据的变化做出一些操作的功能。Vue3 中的 Watch 支持多种用法，包括监视响应式对象、ref 对象、数组、函数等。",{"path":849,"title":850,"description":11},"\u002Ftutorials\u002Fmq\u002Fkafka\u002Fkafka-introduction","Kafka 简介与安装",{"path":852,"title":853,"description":11},"\u002Ftutorials\u002Fmq\u002Fkafka\u002Fkafka-producer-consumer","Kafka 生产者与消费者",{"path":855,"title":856,"description":857},"\u002Ftutorials\u002Fmq\u002Fkafka\u002Fkafka-springboot","Spring Boot 整合 Kafka","Spring Kafka 提供了对 Apache Kafka 的便捷集成。",{"path":859,"title":860,"description":861},"\u002Ftutorials\u002Fmq\u002Frabbitmq\u002Frabbitmq-exchange","RabbitMQ Exchange 详解","Exchange（交换机）是 RabbitMQ 的核心组件，负责接收生产者发送的消息，并根据规则将消息路由到一个或多个队列。",{"path":863,"title":864,"description":11},"\u002Ftutorials\u002Fmq\u002Frabbitmq\u002Frabbitmq-introduction","RabbitMQ 简介与安装",{"path":866,"title":867,"description":868},"\u002Ftutorials\u002Fmq\u002Frabbitmq\u002Frabbitmq-reliability","RabbitMQ 消息可靠性","消息可靠性是消息队列的核心要求，RabbitMQ 提供了多种机制来保证消息不丢失。",{"path":870,"title":871,"description":872},"\u002Ftutorials\u002Fmq\u002Frabbitmq\u002Frabbitmq-springboot","Spring Boot 整合 RabbitMQ","Spring AMQP 提供了对 RabbitMQ 的便捷集成，大大简化了开发工作。",{"path":874,"title":875,"description":11},"\u002Ftutorials\u002Fmq\u002Frocketmq\u002Frocketmq-client","RocketMQ 客户端使用",{"path":877,"title":878,"description":11},"\u002Ftutorials\u002Fmq\u002Frocketmq\u002Frocketmq-concepts","RocketMQ 核心概念",{"path":880,"title":881,"description":11},"\u002Ftutorials\u002Fmq\u002Frocketmq\u002Frocketmq-installation","RocketMQ 安装部署",{"path":883,"title":884,"description":885},"\u002Ftutorials\u002Fmq\u002Frocketmq\u002Frocketmq-message-type","RocketMQ 消息类型","RocketMQ 支持多种消息类型，满足不同业务场景需求。",{"id":887,"title":102,"body":888,"description":103,"extension":1484,"meta":1485,"navigation":1486,"path":101,"seo":1487,"stem":1488,"__hash__":1489},"docs\u002Fai\u002Fprompt\u002Ftechniques.md",{"type":889,"value":890,"toc":1451},"minimark",[891,895,899,903,906,910,920,924,931,998,1002,1005,1011,1015,1019,1022,1026,1029,1035,1038,1044,1048,1051,1057,1061,1064,1070,1074,1078,1081,1087,1091,1094,1098,1104,1108,1114,1118,1122,1125,1131,1134,1138,1141,1144,1151,1154,1159,1165,1170,1176,1179,1182,1185,1277,1283,1287,1294,1297,1303,1306,1309,1405,1408,1442,1445,1448],[892,893,894],"h2",{"id":894},"概述",[896,897,898],"p",{},"在掌握了 Prompt 的基本结构之后，进一步学习具体的提示词技巧可以帮助你应对更复杂的任务。本文将介绍几种经过验证的、在实际开发中高频使用的提示词技巧，并通过对比帮助你选择合适的策略。",[892,900,902],{"id":901},"few-shot-prompting少样本提示","Few-shot Prompting（少样本提示）",[896,904,905],{},"Few-shot 是最直观的提示词技巧之一：通过提供少量输入-输出示例，让模型\"学会\"你期望的模式。",[907,908,909],"h3",{"id":909},"基本用法",[911,912,917],"pre",{"className":913,"code":915,"language":916,"meta":11},[914],"language-text","将以下 Go 函数签名转换为对应的接口定义。\n\n示例 1：\n输入：func GetUser(id int) (*User, error)\n输出：\ntype UserGetter interface {\n    GetUser(id int) (*User, error)\n}\n\n示例 2：\n输入：func SaveOrder(order *Order) error\n输出：\ntype OrderSaver interface {\n    SaveOrder(order *Order) error\n}\n\n请转换：\n输入：func DeleteComment(postID, commentID int) error\n","text",[918,919,915],"code",{"__ignoreMap":11},[907,921,923],{"id":922},"few-shot-的关键要点","Few-shot 的关键要点",[896,925,926,930],{},[927,928,929],"strong",{},"示例的质量比数量更重要。"," 以下是编写高质量示例的原则：",[932,933,934,950],"table",{},[935,936,937],"thead",{},[938,939,940,944,947],"tr",{},[941,942,943],"th",{},"原则",[941,945,946],{},"说明",[941,948,949],{},"示例",[951,952,953,965,976,987],"tbody",{},[938,954,955,959,962],{},[956,957,958],"td",{},"代表性",[956,960,961],{},"示例应覆盖不同的典型情况",[956,963,964],{},"包含有参数和无参数的函数",[938,966,967,970,973],{},[956,968,969],{},"一致性",[956,971,972],{},"所有示例格式必须统一",[956,974,975],{},"输入\u002F输出格式完全相同",[938,977,978,981,984],{},[956,979,980],{},"边界性",[956,982,983],{},"包含一个边界情况的示例",[956,985,986],{},"包含错误处理或空值的情况",[938,988,989,992,995],{},[956,990,991],{},"简洁性",[956,993,994],{},"示例不宜过于复杂",[956,996,997],{},"避免嵌套过深的示例",[907,999,1001],{"id":1000},"带标签的-few-shot","带标签的 Few-shot",[896,1003,1004],{},"为示例添加标签可以让模式更加明确：",[911,1006,1009],{"className":1007,"code":1008,"language":916,"meta":11},[914],"任务：为 Go 代码生成单行注释摘要。\n\n[代码]\nfunc (s *Server) Shutdown(ctx context.Context) error {\n    s.mu.Lock()\n    defer s.mu.Unlock()\n    s.closed = true\n    return s.listener.Close()\n}\n[摘要] 安全关闭服务器：加锁后标记关闭状态并关闭监听器。\n\n[代码]\nfunc retry(fn func() error, maxRetries int, delay time.Duration) error {\n    var err error\n    for i := 0; i \u003C maxRetries; i++ {\n        if err = fn(); err == nil {\n            return nil\n        }\n        time.Sleep(delay)\n    }\n    return fmt.Errorf(\"after %d retries: %w\", maxRetries, err)\n}\n[摘要] 带延迟的重试机制：执行函数最多 maxRetries 次，每次失败后等待 delay。\n\n[代码]\nfunc (c *Cache) Get(key string) (interface{}, bool) {\n    c.mu.RLock()\n    defer c.mu.RUnlock()\n    if item, ok := c.items[key]; ok && !item.IsExpired() {\n        return item.Value, true\n    }\n    return nil, false\n}\n[摘要]\n",[918,1010,1008],{"__ignoreMap":11},[1012,1013,1014],"tip",{},"\n当你发现模型无法仅通过文字描述理解你的需求时，Few-shot 是最简单有效的解决方案。2-3 个精心设计的示例胜过长段的文字说明。\n",[892,1016,1018],{"id":1017},"chain-of-thought链式思维","Chain-of-Thought（链式思维）",[896,1020,1021],{},"Chain-of-Thought（CoT）是一种引导模型进行逐步推理的技巧。对于需要逻辑推理、数学计算或多步分析的任务，CoT 可以显著提升准确率。",[907,1023,1025],{"id":1024},"基本-cot添加让我们逐步思考","基本 CoT：添加\"让我们逐步思考\"",[896,1027,1028],{},"最简单的 CoT 方式是在 Prompt 末尾添加引导语：",[911,1030,1033],{"className":1031,"code":1032,"language":916,"meta":11},[914],"以下 Go 代码存在一个并发 bug，请找出问题所在。\n让我们逐步分析：\n\nfunc counter() int {\n    count := 0\n    var wg sync.WaitGroup\n    for i := 0; i \u003C 1000; i++ {\n        wg.Add(1)\n        go func() {\n            defer wg.Done()\n            count++\n        }()\n    }\n    wg.Wait()\n    return count\n}\n",[918,1034,1032],{"__ignoreMap":11},[896,1036,1037],{},"模型会被引导进行如下推理：",[911,1039,1042],{"className":1040,"code":1041,"language":916,"meta":11},[914],"让我们逐步分析这段代码：\n\n1. 首先看整体结构：启动了 1000 个 goroutine，每个对 count 执行 +1 操作\n2. count 是一个共享变量，多个 goroutine 同时读写\n3. count++ 不是原子操作，它包含 读取 -> 加1 -> 写入 三个步骤\n4. 多个 goroutine 可能同时读取相同的值，导致写入被覆盖\n5. 结论：这是一个典型的数据竞争（data race）问题\n\n修复方案：使用 sync\u002Fatomic 包或 sync.Mutex 保护共享变量。\n",[918,1043,1041],{"__ignoreMap":11},[907,1045,1047],{"id":1046},"结构化-cot","结构化 CoT",[896,1049,1050],{},"对于更复杂的任务，可以预定义推理步骤：",[911,1052,1055],{"className":1053,"code":1054,"language":916,"meta":11},[914],"请诊断以下 Go 微服务的性能瓶颈，按以下步骤分析：\n\n步骤 1 - 识别热点：找出代码中可能成为瓶颈的操作\n步骤 2 - 评估影响：分析每个热点对整体性能的影响程度\n步骤 3 - 根因分析：找出导致瓶颈的根本原因\n步骤 4 - 优化方案：针对每个问题提出具体的优化措施\n步骤 5 - 优先级排序：按投入产出比排列优化任务\n\n代码如下：\n...\n",[918,1056,1054],{"__ignoreMap":11},[907,1058,1060],{"id":1059},"few-shot-cot","Few-shot CoT",[896,1062,1063],{},"将 Few-shot 与 CoT 结合，通过示例展示期望的推理过程：",[911,1065,1068],{"className":1066,"code":1067,"language":916,"meta":11},[914],"分析 Go 代码的时间复杂度。\n\n示例：\n代码：\nfunc twoSum(nums []int, target int) []int {\n    m := make(map[int]int)\n    for i, v := range nums {\n        if j, ok := m[target-v]; ok {\n            return []int{j, i}\n        }\n        m[v] = i\n    }\n    return nil\n}\n\n分析过程：\n1. 外层 for 循环遍历 nums 数组，执行 n 次\n2. 循环内的 map 查找操作 m[target-v] 平均时间复杂度 O(1)\n3. map 写入操作 m[v] = i 平均时间复杂度 O(1)\n4. 没有嵌套循环\n结论：时间复杂度 O(n)，空间复杂度 O(n)\n\n请分析以下代码：\nfunc findDuplicates(nums []int) []int {\n    sort.Ints(nums)\n    var result []int\n    for i := 1; i \u003C len(nums); i++ {\n        if nums[i] == nums[i-1] {\n            result = append(result, nums[i])\n        }\n    }\n    return result\n}\n",[918,1069,1067],{"__ignoreMap":11},[1071,1072,1073],"note",{},"\nCoT 特别适合以下类型的任务：代码调试、算法分析、系统设计评审、性能诊断。对于简单的任务（如格式转换、翻译），CoT 反而可能降低效率。\n",[892,1075,1077],{"id":1076},"逐步推理step-by-step-reasoning","逐步推理（Step-by-step Reasoning）",[896,1079,1080],{},"逐步推理是 CoT 的一种更严格的变体，它要求模型在每一步都给出明确的中间结果。",[911,1082,1085],{"className":1083,"code":1084,"language":916,"meta":11},[914],"请逐步执行以下代码审查，每一步给出具体发现：\n\n审查代码：[粘贴代码]\n\nStep 1: 安全性检查\n- 检查项：SQL 注入、XSS、敏感信息泄露\n- 发现：[列出具体问题]\n\nStep 2: 错误处理检查\n- 检查项：未处理的 error、panic 风险\n- 发现：[列出具体问题]\n\nStep 3: 并发安全检查\n- 检查项：数据竞争、死锁风险、goroutine 泄露\n- 发现：[列出具体问题]\n\nStep 4: 性能检查\n- 检查项：不必要的内存分配、N+1 查询、未使用缓存\n- 发现：[列出具体问题]\n\nStep 5: 总结\n- 严重问题：[列表]\n- 建议改进：[列表]\n- 优先级排序：[按严重程度排序]\n",[918,1086,1084],{"__ignoreMap":11},[892,1088,1090],{"id":1089},"react-模式reasoning-acting","ReAct 模式（Reasoning + Acting）",[896,1092,1093],{},"ReAct 模式结合了推理（Reasoning）和行动（Acting），让模型在解决问题时交替进行思考和操作。这种模式在需要模型与外部工具交互的场景中特别有效。",[907,1095,1097],{"id":1096},"react-的基本结构","ReAct 的基本结构",[911,1099,1102],{"className":1100,"code":1101,"language":916,"meta":11},[914],"你是一个 DevOps 助手，可以使用以下工具：\n- search_logs(keyword): 搜索服务日志\n- get_metrics(service, timerange): 获取服务监控指标\n- run_query(sql): 执行数据库查询\n\n问题：生产环境的订单服务响应时间突然增加到 5 秒以上，请排查原因。\n\n请按以下格式回答：\nThought: 思考下一步应该做什么\nAction: 使用哪个工具，传入什么参数\nObservation: 工具返回的结果\n...（重复以上过程直到找到答案）\nAnswer: 最终的结论和建议\n",[918,1103,1101],{"__ignoreMap":11},[907,1105,1107],{"id":1106},"react-执行过程示例","ReAct 执行过程示例",[911,1109,1112],{"className":1110,"code":1111,"language":916,"meta":11},[914],"Thought: 响应时间突增，首先应该查看是否有错误日志\nAction: search_logs(\"order-service ERROR last 1h\")\nObservation: 发现大量 \"connection timeout to mysql-primary\" 错误\n\nThought: 数据库连接超时，需要确认数据库的状态\nAction: get_metrics(\"mysql-primary\", \"last 2h\")\nObservation: CPU 使用率 95%，活跃连接数 500（上限 500）\n\nThought: 数据库连接池已满且 CPU 过高，可能存在慢查询\nAction: run_query(\"SELECT * FROM slow_log WHERE start_time > NOW() - INTERVAL 1 HOUR ORDER BY query_time DESC LIMIT 5\")\nObservation: 发现一个全表扫描查询，执行时间 45 秒，每分钟调用 200 次\n\nAnswer: 根本原因是一个缺少索引的全表扫描查询，它占满了数据库连接池并导致 CPU 过载。\n建议：\n1. 立即：为该查询涉及的 WHERE 条件字段添加索引\n2. 短期：增加连接池上限至 800 并设置查询超时\n3. 长期：启用慢查询监控报警\n",[918,1113,1111],{"__ignoreMap":11},[1115,1116,1117],"warning",{},"\nReAct 模式需要模型支持函数调用（Function Calling）或工具使用才能真正执行。在纯文本对话中，ReAct 只能作为思维框架模拟执行过程。\n",[892,1119,1121],{"id":1120},"self-consistency自洽性","Self-Consistency（自洽性）",[896,1123,1124],{},"Self-Consistency 技巧让模型对同一问题生成多条推理路径，然后取最一致的答案。在实际使用中，你可以通过提示词来模拟这个过程。",[911,1126,1129],{"className":1127,"code":1128,"language":916,"meta":11},[914],"请用三种不同的分析角度评估以下数据库 Schema 设计是否合理：\n\nSchema:\nCREATE TABLE orders (\n    id BIGINT PRIMARY KEY,\n    user_id BIGINT,\n    product_data JSON,\n    created_at TIMESTAMP\n);\n\n分析角度 1 - 范式化视角：\n[从数据库范式的角度分析]\n\n分析角度 2 - 查询性能视角：\n[从查询效率和索引的角度分析]\n\n分析角度 3 - 业务扩展视角：\n[从未来业务需求变化的角度分析]\n\n综合结论：\n[综合三个角度，给出最终建议]\n",[918,1130,1128],{"__ignoreMap":11},[1012,1132,1133],{},"\nSelf-Consistency 可以通过 API 的 `temperature` 参数配合实现：设置较高的 temperature 生成多个回答，然后取最一致的结果。这在需要高可靠性的场景中非常有用。\n",[892,1135,1137],{"id":1136},"prompt-chaining提示词链","Prompt Chaining（提示词链）",[896,1139,1140],{},"Prompt Chaining 将复杂任务分解为多个串联的 Prompt，每一步的输出作为下一步的输入。",[907,1142,1143],{"id":1143},"典型的链式流程",[911,1145,1149],{"className":1146,"code":1147,"language":916,"meta":1148},[914],"flowchart TD\n    P1[\"Prompt 1: 需求分析\u003Cbr\u002F>输出：功能列表\"]\n    P2[\"Prompt 2: 架构设计\u003Cbr\u002F>输出：模块划分和接口定义\"]\n    P3[\"Prompt 3: 代码实现\u003Cbr\u002F>输出：核心代码\"]\n    P4[\"Prompt 4: 代码审查\u003Cbr\u002F>输出：问题清单和修复建议\"]\n    P5[\"Prompt 5: 测试生成\u003Cbr\u002F>输出：单元测试代码\"]\n    P1 --> P2 --> P3 --> P4 --> P5\n","mermaid",[918,1150,1147],{"__ignoreMap":11},[907,1152,1153],{"id":1153},"实际示例",[896,1155,1156],{},[927,1157,1158],{},"第一步：分析需求",[911,1160,1163],{"className":1161,"code":1162,"language":916,"meta":11},[914],"分析以下需求并输出结构化的功能清单：\n\n需求：实现一个 Go 语言的 rate limiter（限流器），支持令牌桶和滑动窗口两种算法，\n提供 HTTP 中间件接口，支持按 IP 和按 API Key 限流。\n\n请输出 JSON 格式的功能清单，包含功能名、描述、优先级。\n",[918,1164,1162],{"__ignoreMap":11},[896,1166,1167],{},[927,1168,1169],{},"第二步：基于上一步输出进行设计",[911,1171,1174],{"className":1172,"code":1173,"language":916,"meta":11},[914],"基于以下功能清单，设计 Go 语言的包结构和核心接口：\n\n[粘贴第一步的输出]\n\n要求：\n- 遵循 Go 语言惯例的项目布局\n- 核心逻辑与 HTTP 层解耦\n- 接口设计支持未来扩展新的限流算法\n",[918,1175,1173],{"__ignoreMap":11},[892,1177,1178],{"id":1178},"分隔符的使用",[896,1180,1181],{},"合理使用分隔符可以让 Prompt 的结构更加清晰，减少模型的理解歧义。",[907,1183,1184],{"id":1184},"常用分隔符对比",[932,1186,1187,1199],{},[935,1188,1189],{},[938,1190,1191,1194,1197],{},[941,1192,1193],{},"分隔符",[941,1195,1196],{},"适用场景",[941,1198,949],{},[951,1200,1201,1217,1231,1247,1261],{},[938,1202,1203,1209,1212],{},[956,1204,1205,1208],{},[918,1206,1207],{},"\"\"\""," 三引号",[956,1210,1211],{},"包裹大段文本",[956,1213,1214],{},[918,1215,1216],{},"\"\"\"待翻译文本\"\"\"",[938,1218,1219,1225,1228],{},[956,1220,1221,1224],{},[918,1222,1223],{},"---"," 分割线",[956,1226,1227],{},"分隔不同部分",[956,1229,1230],{},"示例之间的分隔",[938,1232,1233,1239,1242],{},[956,1234,1235,1238],{},[918,1236,1237],{},"\u003Ctag>"," XML 标签",[956,1240,1241],{},"结构化数据标注",[956,1243,1244],{},[918,1245,1246],{},"\u003Ccode>...\u003C\u002Fcode>",[938,1248,1249,1255,1258],{},[956,1250,1251,1254],{},[918,1252,1253],{},"```"," 代码块",[956,1256,1257],{},"包裹代码片段",[956,1259,1260],{},"标准 Markdown 代码块",[938,1262,1263,1269,1272],{},[956,1264,1265,1268],{},[918,1266,1267],{},"###"," 标题标记",[956,1270,1271],{},"标识各段落主题",[956,1273,1274],{},[918,1275,1276],{},"### 任务描述",[911,1278,1281],{"className":1279,"code":1280,"language":916,"meta":11},[914],"请将 \u003Csource> 中的代码从 Python 重写为 Go，参考 \u003Cstyle> 中的代码风格。\n\n\u003Csource>\ndef fibonacci(n):\n    if n \u003C= 1:\n        return n\n    return fibonacci(n-1) + fibonacci(n-2)\n\u003C\u002Fsource>\n\n\u003Cstyle>\n\u002F\u002F 使用迭代而非递归\n\u002F\u002F 变量命名使用驼峰式\n\u002F\u002F 添加输入验证\n\u002F\u002F 使用 error 返回错误而非 panic\n\u003C\u002Fstyle>\n",[918,1282,1280],{"__ignoreMap":11},[892,1284,1286],{"id":1285},"否定提示negative-prompting","否定提示（Negative Prompting）",[896,1288,1289,1290,1293],{},"否定提示是指明确告知模型",[927,1291,1292],{},"不应该做什么","。虽然正向指令通常更有效，但在某些场景中否定提示是有益的补充。",[907,1295,1296],{"id":1296},"有效的否定提示用法",[911,1298,1301],{"className":1299,"code":1300,"language":916,"meta":11},[914],"为初学者解释 Go 的 channel 机制。\n\n要求：\n- 使用生活中的类比来解释概念\n- 提供可运行的示例代码\n\n限制：\n- 不要提及底层实现（hchan 结构体、sudog 等）\n- 不要涉及 select 语句（这是后续章节的内容）\n- 不要使用超过 20 行的代码示例\n",[918,1302,1300],{"__ignoreMap":11},[1071,1304,1305],{},"\n否定提示最佳的使用场景是划定内容边界——告诉模型哪些内容超出了当前讨论的范围，避免它过度展开。\n",[892,1307,1308],{"id":1308},"技巧对比与选择指南",[932,1310,1311,1327],{},[935,1312,1313],{},[938,1314,1315,1318,1321,1324],{},[941,1316,1317],{},"技巧",[941,1319,1320],{},"最佳场景",[941,1322,1323],{},"复杂度",[941,1325,1326],{},"Token 消耗",[951,1328,1329,1343,1355,1368,1380,1393],{},[938,1330,1331,1334,1337,1340],{},[956,1332,1333],{},"Few-shot",[956,1335,1336],{},"格式\u002F风格统一",[956,1338,1339],{},"低",[956,1341,1342],{},"中",[938,1344,1345,1348,1351,1353],{},[956,1346,1347],{},"CoT",[956,1349,1350],{},"推理\u002F分析任务",[956,1352,1342],{},[956,1354,1342],{},[938,1356,1357,1360,1363,1366],{},[956,1358,1359],{},"ReAct",[956,1361,1362],{},"工具交互\u002F排查",[956,1364,1365],{},"高",[956,1367,1365],{},[938,1369,1370,1373,1376,1378],{},[956,1371,1372],{},"Self-Consistency",[956,1374,1375],{},"高可靠性决策",[956,1377,1342],{},[956,1379,1365],{},[938,1381,1382,1385,1388,1390],{},[956,1383,1384],{},"Prompt Chaining",[956,1386,1387],{},"复杂多步任务",[956,1389,1365],{},[956,1391,1392],{},"分步消耗",[938,1394,1395,1398,1401,1403],{},[956,1396,1397],{},"否定提示",[956,1399,1400],{},"限定范围",[956,1402,1339],{},[956,1404,1339],{},[896,1406,1407],{},"选择技巧时的决策思路：",[1409,1410,1411,1418,1424,1430,1436],"ol",{},[1412,1413,1414,1417],"li",{},[927,1415,1416],{},"任务是否需要特定格式？"," 是 → Few-shot",[1412,1419,1420,1423],{},[927,1421,1422],{},"任务是否需要推理？"," 是 → CoT",[1412,1425,1426,1429],{},[927,1427,1428],{},"任务是否涉及外部工具？"," 是 → ReAct",[1412,1431,1432,1435],{},[927,1433,1434],{},"结果是否需要高可靠性？"," 是 → Self-Consistency",[1412,1437,1438,1441],{},[927,1439,1440],{},"任务是否可分解为多步？"," 是 → Prompt Chaining",[1012,1443,1444],{},"\n这些技巧并非互斥。在实际应用中，经常需要组合使用。例如，Few-shot CoT（用示例展示推理过程）、Prompt Chaining + CoT（每一步都使用链式思维）等组合都非常常见。\n",[892,1446,1447],{"id":1447},"小结",[896,1449,1450],{},"本文介绍的提示词技巧覆盖了绝大多数实际开发场景。关键在于理解每种技巧的适用条件，而不是机械地套用模板。随着实践经验的积累，你会逐渐形成自己的技巧组合策略，高效地完成各类任务。",{"title":11,"searchDepth":1452,"depth":1452,"links":1453},2,[1454,1455,1461,1466,1467,1471,1472,1476,1479,1482,1483],{"id":894,"depth":1452,"text":894},{"id":901,"depth":1452,"text":902,"children":1456},[1457,1459,1460],{"id":909,"depth":1458,"text":909},3,{"id":922,"depth":1458,"text":923},{"id":1000,"depth":1458,"text":1001},{"id":1017,"depth":1452,"text":1018,"children":1462},[1463,1464,1465],{"id":1024,"depth":1458,"text":1025},{"id":1046,"depth":1458,"text":1047},{"id":1059,"depth":1458,"text":1060},{"id":1076,"depth":1452,"text":1077},{"id":1089,"depth":1452,"text":1090,"children":1468},[1469,1470],{"id":1096,"depth":1458,"text":1097},{"id":1106,"depth":1458,"text":1107},{"id":1120,"depth":1452,"text":1121},{"id":1136,"depth":1452,"text":1137,"children":1473},[1474,1475],{"id":1143,"depth":1458,"text":1143},{"id":1153,"depth":1458,"text":1153},{"id":1178,"depth":1452,"text":1178,"children":1477},[1478],{"id":1184,"depth":1458,"text":1184},{"id":1285,"depth":1452,"text":1286,"children":1480},[1481],{"id":1296,"depth":1458,"text":1296},{"id":1308,"depth":1452,"text":1308},{"id":1447,"depth":1452,"text":1447},"md",{},true,{"title":102,"description":103},"ai\u002Fprompt\u002Ftechniques","mjX2_74jBsq-sX7qCh8Sl5fvoMd_rbT-OMNmOz95QWA",1775474635109]