20:"$Sreact.view_transition" 21:I[9754,["/_next/static/chunks/2qcf_o2xotudn.js","/_next/static/chunks/1gyqeidjm5eoa.js","/_next/static/chunks/0_fjnxc4tt_l_.js","/_next/static/chunks/1ymt1shyhmu-4.js","/_next/static/chunks/3kv2zf0i7s2wc.js","/_next/static/chunks/1ucasf31l8j2v.js","/_next/static/chunks/0yj6_8vip2oqy.js","/_next/static/chunks/2l5xdnifczg1b.js","/_next/static/chunks/192kgs9v_t14j.js","/_next/static/chunks/0z6pw0v5c_lx5.js","/_next/static/chunks/08r60e6icmtkc.js","/_next/static/chunks/3trx6c0i7_x-3.js","/_next/static/chunks/40sro5bzp9bi_.js","/_next/static/chunks/1wgf3tk38y6cf.js"],"ProjectDetail"] 22:T92cd, Claude Code 最佳实践 · 从手感编码到代理工程

claude-code-best-practice

从手感编码,
到代理工程。
练习,让 Claude 更完美。

这份仓库把 Claude Code 的核心概念串联成一条有序的交接流程：子代理、命令、技能、工作流、钩子、MCP 服务器、插件、设置、记忆——每一次交接，都把一次性的“手感”请求,转化为编排好的工程管线。

作者 shanraisshan 仓库 claude-code-best-practice 语言 HTML 许可 MIT 方向 学习 · 构建 · 评估

EDITION 1 · LOT 2026-08-17 · DRAFT PLATE 03

01 · 交接流程

一次“手感”请求,
如何走成一条管线

“从手感编码到代理工程”，真正的分水岭不在于工具,而在于交接的顺序。A 一个含糊的偏好交给 子代理 去拆解，把结果传给命令定型，再由技能拧成可复用的动作。

每一步的出端口,都恰好接住下一步的入端口。流程有序,工程才可重复。

02 · 站点图

九个站点,各有各的职责

这不是功能清单,而是横向排开的一组站点。每个节点都有一条入端口、一条出端口,指向下一站。站点学会了职责,整条线的含义才成立。

子代理 subagent

把大任务拆给专注的工人,分而治之。

命令 command

把常用动作定型为可唤起的短指令。

技能 skill

把知识封装成可复用的操作手册。

工作流 workflow

按顺序编排多次交接,形成完整流程。

钩子 hook

在关键节点挂起动作,自动触发。

MCP 服务器

把模型接上外部工具与数据。

插件 plugin

以最小改动扩展能力边界。

设置 settings

把偏好钉在配置上,保持稳定。

记忆 memory

跨会话保留上下文,越用越准。

入端口　接通上一站出端口　送往下一站活动交接

03 · 工作流编排

把交接,编排成可执行的工程

仓库提供了编排工作流的实现示例——例如天气编排器命令,把“查天气”这种一次性的请求,编排成多次有序的交接,而不是零散的手工操作。

当交接有了顺序,工程就有了节奏。

备注 · 站点名按与官方文档一致的英文标注,中文注释仅作阅读辅助。

04 · 命令与技能的跳转

短指令与可复用动作

命令负责“叫得顺口”，技能负责“做得标准”。命令像一次短跳,技能像一张落地的路线图。两者配合,手感请求才不至于每次从头来过。

命令 command

把常用操作定型为短指令,降低调用成本
适合高频、一次次重复的动作
仓库收录了命令使用与编写示例

技能 skill

把知识封装成可复用的操作手册
适合需要上下文与步骤的复杂动作
仓库提供了技能集合的整理

05 · 钩子与上下文

在关键节点,挂上自动动作

钩子在流程的关键节点自动触发;记忆把跨会话的上下文一路带下去。二者让管线在正确时机自行推进,而不是每步都要人工伸手。

提示 · 上下文随交接一路携带,不在每次调用时重新解释。

06 · 跨模型桥接

交接,可以跨过不同模型

仓库还整理跨模型的工作流——把交接从单一模型的管线,延伸到多模型的协同。站点之间不再是紧巴巴的一条线,而是可以跨越的桥。

这也是它与作者的一线实践紧密相连的地方:文档、社区、课程相互串联。

备注 · 仓库把官方文档、社区热帖与视频/播客整理进同一张采集表,方便对比研读。

继续练习,
让线一直延伸下去

“练习,让 Claude 更完美。” 读文档只是起点,真正把管线跑起来、把交接走顺,才完成从手感编码到代理工程的一跃。虚线从这里继续延伸,等待你的下一步。

前往仓库并开始连到作者

MIT 许可 · 公开采集 · 图 01–06 全部为板面注记,无截图、无终端、无模拟画面

23:T90ee, Claude Code Best Practice · From Vibe Coding to Agentic Engineering

claude-code-best-practice

From vibe coding
to agentic engineering.
Practice makes Claude perfect.

A conductor's line for agentic workflows. This repository threads the core concepts of Claude Code — subagents, commands, skills, workflows, hooks, MCP servers, plugins, settings, memory — into an ordered chain of handoffs that turns a one-shot "vibe" ask into an orchestrated engineering pipeline.

Author shanraisshan Repo claude-code-best-practice Language HTML License MIT Intent learn · build · evaluate

EDITION 1 · LOT 2026-08-17 · DRAFT PLATE 03

01 · The Handoff Line

How one "vibe ask" becomes a pipeline

The real divide between vibe coding and agentic engineering is order, not tools. A loose preference goes to a subagent to be decomposed, lands on a command to be pinned down, and is hardened into a reusable move by a skill.

Every out-port meets the next station's in-port. Keep the order and the work becomes repeatable.

02 · Station Map

Nine stations, each with a job

This is not a feature list — it is a row of stations on the drafting plate. Every node carries one in-port and one out-port, aimed at the next station. Once each station knows its job, the whole line means something.

Subagent

Hand a large task to a focused worker and divide and conquer.

Command

Pin repeated moves into short, callable directives.

Skill

Wrap knowledge into a reusable operating manual.

Workflow

Sequence several handoffs into one complete flow.

Hook

Attach an action at a key node and fire it automatically.

MCP Server

Connect the model to external tools and data.

Plugin

Extend the boundary with the smallest possible change.

Settings

Peg preferences into config so things stay stable.

Memory

Carry context across sessions and get sharper each time.

in-port — from the previous station out-port — on to the next station active handoff

03 · Workflow Orchestration

Arrange the handoffs into a runnable build

This repository ships orchestration workflow examples — such as a weather orchestrator command — that turn a one-off "get the weather" ask into a number of ordered handoffs instead of loose manual steps.

Once the handoffs have an order, the build has a rhythm.

Note · station names follow the official docs; commentary stays descriptive, never fabricated.

04 · Command & Skill Hops

Short calls and reusable moves

Commands carry the feel of a quick call; skills carry the standard of a practiced route. Commands are a short hop, skills a laid-out map. Together they keep a vibe-ask from being rebuilt from scratch every time.

Command

Pins repeated operations into short directives and lowers the cost of a call
Suits high-frequency, repeated actions
Repo curates command usage and authoring examples

Skill

Wraps knowledge into a reusable operating manual
Suits complex actions that need context and steps
Repo organizes skill collections for pick-up use

05 · Hooks & Context

Fire automatic moves at the key nodes

Hooks fire automatically at critical points along the flow; memory carries cross-session context the whole way down. Together they let the pipeline advance at the right moment instead of waiting on a manual nudge at every step.

Tip · context rides along the line, never re-explained at each call.

06 · Cross-Model Bridges

Handoffs can span more than one model

The repo also curates cross-model workflows — extending the handoff line beyond a single engine into multi-model cooperation. Stations no longer sit on one tight rail; they reach across a bridge.

It is also where the repo links to the author's live practice: docs, community and courses threaded into one field guide.

Note · the repo threads official docs, community hot posts and video/podcast links into one collection for side-by-side study.

Keep practicing —
let the line keep running

"Practice makes Claude perfect." Reading the docs is only the start. Running the pipeline and walking the handoffs is what completes the leap from vibe coding to agentic engineering. The dashed continuation exits here, waiting for your next move.

Open the repo and start Reach the author

MIT licensed · public collection · FIGS 01–06 are plate annotations — no screenshots, no terminal, no mock-up surfaces

a:[["$","$20",null,{"enter":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-enter","default":"none"},"exit":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-exit","default":"none"},"update":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-update","default":"none"},"default":"none","children":["$","$L21","cmsn449bo00101s16ahrdt7el:zh-CN:beautified",{"project":{"id":"cmsn449bo00101s16ahrdt7el","slug":"shanraisshan-claude-code-best-practice","name":"claude-code-best-practice","description":"Claude Code 最佳实践与实现指南","authorName":"shanraisshan","authorVerification":{"verified":false,"verifiedAt":null},"category":"development_tools","subcategory":"data_ai_tools","experienceUrl":"https://linkedin.com/in/shanraisshan","qualityScore":90,"featured":false,"officialSite":null,"views":{"original":{"available":true},"official":{"available":false,"reason":"disabled_by_policy"},"beautified":{"available":true,"reason":null},"defaultView":"beautified"},"beautifiedView":{"revisionId":"cmt2zh2te01iz6271d41alczy","kind":"artifact","artifact":{"schemaVersion":"localized-static-html-v4","kind":"static_html","locales":["zh-CN","en"],"defaultLocale":"zh-CN","documents":{"zh-CN":"$22","en":"$23"},"designDirections":{"schemaVersion":"dodot-design-directions-v1","directions":[{"id":"dir-refinement-loop","name":"Refinement Loop","projectMetaphor":"'Practice makes claude perfect' as a continuous refinement loop: raw 'vibe coding' passes through repeated practice passes until it compresses into stable 'agentic engineering'. Every concept in the repo is a pass that tightens the loop.","signatureVisual":"A set of concentric, slightly eccentric rings that read as a spiral being squeezed tighter; the loose, wobbling outer ring labeled with a fuzzy 'vibe' weight graduates inward to a crisp single knot at the center. Each of the repo's concepts sits on a ring as a tick marker.","heroGeometry":"Off-center concentric rings/elliptical orbits converging to a tight central node, drawn as continuous stroked paths with a coarse outer pass and progressively finer inner passes.","sectionSequence":["problem_transition","practice_passes","concept_landscape","workflow_orchestration","community_scale","where_to_start"],"surfaceModel":"Paper-field: each surface sits as a physical card lying on a flat graph-paper-like ground, with rings peeking from behind cards. Stacking depth communicates how many practice passes a concept has undergone; fewer passes = lighter ink, more passes = heavier ink.","palette":"Warm paper beige background, ink charcoal text, a single accent of 'refined amber' for the inner compressed knot, muted clay for the coarse outer ring, off-white for card surfaces.","typography":"A high-contrast serif display for the transition headline paired with a neutral grotesque for structured concept labels; monospace numerals for the pass-count markers.","desktopComposition":"Left-bleed hero: the rings spiral anchored on the left, headline and CTA stacked on the right. Sections alternate a full-width 'pass band' divider with a two-column 'concept on one side, nearby outer ring on the other' rhythm that visually tightens as the page descends toward the center concept.","mobileTransformation":"Rings become a single vertical spiral that the page scrolls down into; each section is a horizontal swipe-through pass, with the center knot pinned at the bottom as an anchor that the final section lands on.","mediaStrategy":"No product media. Use observable 'pass-count' labels and small derived loop diagrams as content; no screenshots, no browser/terminal shells, no remote imagery.","forbiddenPatterns":["three side-by-side metric cards","editor or terminal shell frames","decorative glow or particle field substituted for the ring motif","feature-card wall that would accept any project copy"],"compositionFingerprint":"concentric-squeezing-spiral-with-counted-passes"},{"id":"dir-practice-tree","name":"Tree of Practice","projectMetaphor":"'From vibe coding to agentic engineering' is a growing tree whose single trunk is practice and whose branches are the concept families (subagents, commands, skills, workflows, hooks, MCP servers, plugins, settings, memory); reading the repo is climbing from the trunk to the canopy.","signatureVisual":"A schematic tree built as a rooted branching diagram: one trunk labeled 'practice', nine branch families tagged with the core concepts, and leaf nodes as individual tips/examples. Branch thickness encodes how many examples a family carries.","heroGeometry":"A structural root-to-canopy branch network starting from one baseline trunk at the bottom-left and branching asymmetrically upward, drawn as strokes with rounded joints and visible parent/child connections.","sectionSequence":["concept_families","example_leaves","workflow_orchestration","cross_model_links","skill_and_agent_collections","community_roots","start_climbing"],"surfaceModel":"Living-growth: sections are horizontal canopy layers that nest leaves (example chips) directly on each branch; surfaces emit slight organic rounding but stay flat, reading as cut wood panels rather than rounded software cards.","palette":"Deep forest-green panel ground, light bark paper text panels, a single sap-green accent for the trunk/practice, muted moss for older families and brighter lime for the freshest added tips.","typography":"A geometric rounded sans for family headers, a small mono for leaf/example ids, and a light humanist serif for section narration text for contrast against the structured tree.","desktopComposition":"Hero is a left-anchored trunk with the canopy bleeding off the right edge; below, the page reads top-down as 'root → trunk → first branches → canopy', each section a new branch level revealed horizontally, with a sparse one-column narrative lane along one side.","mobileTransformation":"The tree rotates to a vertical trunk you walk up: sections scroll bottom-to-top as you climb branches; on narrow screens the narrative lane collapses into brief inline captions beside each branch so the climb stays the primary motion.","mediaStrategy":"No media. Branch thickness and leaf-count chips carry all evidence; no screenshots, no placeholder frame, no remote image.","forbiddenPatterns":["terminal/editor shell","generic 3-card KPI row","decorative grid background standing in for the tree structure","unrelated logo wall or fake testimonial"],"compositionFingerprint":"rooted-branch-tree-with-thickness-encoding"},{"id":"dir-orchestration-flowline","name":"Orchestration Flowline","projectMetaphor":"The repo is a conductor's line for agentic workflows: concepts are stations (subagent → command → skill → workflow → hook → MCP) linked into handoffs that convert a one-shot 'vibe' ask into an orchestrated engineering pipeline.","signatureVisual":"A continuous directed flowline that travels horizontally and vertically through the page connecting concept stations; each station is a node with an in-port and out-port, and the line's direction literally shows the handoff/order of operations.","heroGeometry":"A single continuous path that enters from the left, snakes through stations, and exits off the right as a dashed continuation, built from quarter-turn arcs and straight segments to suggest an ordered pipeline.","sectionSequence":["handoff_flow","station_map","workflow_orchestration","command_and_skill_hops","hooks_and_context","cross_model_bridges","continue_practicing"],"surfaceModel":"Blueprint plate: a dark drafting plate as the ground, station cards acting as bolted-on modules that the line passes through, with thin registration/annotation rails beneath explaining each handoff.","palette":"Indigo-blue drafting plate ground, white chalk line work, a single signal-orange accent for the active handoff, muted teal for in-port and slate for out-port annotations.","typography":"Condensed all-caps heading in a blueprint sans, small mono annotations along the flow rails, and a readable grotesque for body, so the flow notation stays legible.","desktopComposition":"Hero is the full flowline crossing the viewport; each section then takes one segment of the line and enlarges it as a left-to-right rail with story copy above and the rail below, ending on a section that opens the line out to the reader as a continuation.","mobileTransformation":"The line re-composes into a vertical spine: stations stack in order and the flowline becomes a stitched path running down the screen, with side handoff notes; the dashed continuation exits off the bottom edge inviting the next scroll.","mediaStrategy":"No media; the flowline itself and the in-port/out-port notation are the content. No screenshots, no terminal shell, no remote imagery.","forbiddenPatterns":["browser or terminal shell framing","three-column metric wall","flat centered slogan hero without structural visual","decorative grid as a substitute for the flow spine"],"compositionFingerprint":"directed-flowline-with-station-handoffs"}],"selectedDirectionId":"dir-orchestration-flowline","selectionRationale":"The project's mechanism is explicitly about converting 'vibe coding' into 'agentic engineering' through orchestrated handoffs between concepts (subagents, commands, skills, workflows, hooks, MCP servers). The orchestration-flowline speaks directly to this: a directed pipeline of passed handoffs is the truest expression of how the repo's concepts compose (claim evidence includes 'orchestration workflow examples' and 'workflows'). It offers an evidence-driven section order (handoff → stations → orchestration → bridging) rather than a marketing order, yields a signature visual that is mechanism-derived and reproducible without media, and its blueprint surface model maximizes contrast against the other two organic directions (refinement loop and practice tree), lowering similarity risk."},"designBrief":{"schemaVersion":"dodot-design-brief-v1","selectedDirectionId":"dir-orchestration-flowline","projectMetaphor":"The repo is a conductor's line for agentic workflows: concepts are stations (subagent → command → skill → workflow → hook → MCP) linked into handoffs that convert a one-shot 'vibe' ask into an orchestrated engineering pipeline.","signatureVisual":"A continuous directed flowline that travels horizontally and vertically through the page connecting concept stations; each station is a node with an in-port and out-port, and the line's direction literally shows the handoff/order of operations.","compositionFingerprint":"directed-flowline-with-station-handoffs","heroGeometry":"A single continuous path that enters from the left, snakes through stations, and exits off the right as a dashed continuation, built from quarter-turn arcs and straight segments to suggest an ordered pipeline.","sectionSequence":["handoff_flow","station_map","workflow_orchestration","command_and_skill_hops","hooks_and_context","cross_model_bridges","continue_practicing"],"surfaceModel":"Blueprint plate: a dark drafting plate as the ground, station cards acting as bolted-on modules that the line passes through, with thin registration/annotation rails beneath explaining each handoff.","palette":"Indigo-blue drafting plate ground, white chalk line work, a single signal-orange accent for the active handoff, muted teal for in-port and slate for out-port annotations.","typography":"Condensed all-caps heading in a blueprint sans, small mono annotations along the flow rails, and a readable grotesque for body, so the flow notation stays legible.","desktopComposition":"Hero is the full flowline crossing the viewport; each section then takes one segment of the line and enlarges it as a left-to-right rail with story copy above and the rail below, ending on a section that opens the line out to the reader as a continuation.","mobileTransformation":"The line re-composes into a vertical spine: stations stack in order and the flowline becomes a stitched path running down the screen, with side handoff notes; the dashed continuation exits off the bottom edge inviting the next scroll.","mediaStrategy":"No media; the flowline itself and the in-port/out-port notation are the content. No screenshots, no terminal shell, no remote imagery.","evidencePlan":["Render the concept stations only for facts present in material.json: subagents, commands, skills, workflows, hooks, MCP servers, plugins, settings, memory","Annotate station_handoffs using the verified claim that the repo 'provides orchestration workflow examples' without inventing specific command names","Show 'practice makes claude perfect' and 'from vibe coding to agentic engineering' as the flowline's start and exit labels since they are direct description quotes"],"localeContract":{"zh-CN":"同一份构图与章节顺序；文案与文字密度保持中文自然。流程线仍然从'手感编码'通向'代理工程'，站点名用中英标注保持一致。","en":"Same composition and section order; copy and text density stay natural for English. The flowline still runs from 'vibe coding' to 'agentic engineering', with stations labeled consistently."},"forbiddenPatterns":["browser or terminal shell framing","three-column metric wall or three KPI cards","flat centered slogan hero without a structural visual","decorative grid/glow/particle field as a substitute for the flow spine","fake tabs, inputs, controls, logos, or testimonials","desktop columns merely stacked on mobile without recomposition"]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"approved","summary":"独立复核源码确认页面忠实实现所选方向 dir-orchestration-flowline：连续有向交接线贯穿 hero 与各 rail 剖面，站点带 in/out 端口与蓝图板面（深靛蓝底、粉笔白线、信号橙活动交接），7 节序列与 Brief 完全一致，签名视觉真实存在，9 个站点名全部来源于 material.json 的概念事实。特别核实：en 与 zh-CN 的收尾 continue_practicing 节均包含纵向虚线延续元素 $\"GitHub$
"}]},"userIntents":[{"slug":"build_software","label":"构建或改进软件","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"from vibe coding to agentic engineering - practice makes claude perfect"}]},{"slug":"automate_work","label":"自动化工作流程","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"from vibe coding to agentic engineering - practice makes claude perfect"}]},{"slug":"create_content","label":"创作内容或设计","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"from vibe coding to agentic engineering - practice makes claude perfect"}]},{"slug":"analyze_data","label":"分析与理解数据","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"from vibe coding to agentic engineering - practice makes claude perfect"}]},{"slug":"learn_explore","label":"学习与探索","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"from vibe coding to agentic engineering - practice makes claude perfect"}]}],"readme":{"headings":["claude-code-best-practice","🧠 CONCEPTS","🔥 Hot"," $\"Orchestration$ ","⚙️ DEVELOPMENT WORKFLOWS","Others","🔀 CROSS-MODEL WORKFLOWS","🧰 SKILL COLLECTIONS","🤖 AGENT COLLECTIONS","💡 TIPS AND TRICKS (83)","Tips from Claude code CLI binary","🎬 VIDEOS / PODCASTS","🔔 SUBSCRIBE","☠️ STARTUPS / BUSINESSES","🤔 [Does code matter?](https://github.com/shanraisshan/agentic-engineering)","REPORTS"," $\"How$ ","Star History","Other Repos","Developed by"],"commands":[]},"changeSet":[{"field":"repository","beforeHash":"e6f93880465122c65b3af69e4898b757697b66a3dd1177c51125c48a44ef172e","afterHash":"3a650d9666784bede602039e96a6e9aeb26e5ecbd7bcf0bafa2e9758ab08a367"}]},"publishedAt":"2026-08-10T10:55:53.405Z","updatedAt":"2026-08-21T13:26:53.585Z","summary":{"id":"cmt2zh2t401iv6271c0vzipa7","projectType":"other","oneLine":"Claude Code 最佳实践与实现指南","overview":"这是一个面向 Claude Code 用户的实践指南仓库，系统整理了子代理、命令、技能、工作流、钩子、MCP 服务器、插件、设置、记忆等核心概念的最佳实践，并提供了对应的实现示例。适合希望从 vibe coding 进阶到 agentic engineering 的开发者，帮助提升 AI 辅助编程的效率与质量。","highlights":["覆盖核心概念","含实现示例","链接官方文档","社区资源丰富"],"bestFor":["Claude Code 用户","想提升 AI 编程效率的开发者","学习 agentic engineering 的人"],"caveats":["部分内容依赖外部链接","未提供完整安装步骤","示例可能需适配个人环境"],"categorySuggestion":"development_tools","subcategorySuggestion":"developer_resources","lifecycleStages":["idea_requirements","product_design","frontend","backend_data"],"audienceIntents":["learn","build","evaluate"],"confidence":0.85,"evidence":[{"claim":"该仓库提供 Claude Code 的实践指南，涵盖子代理、命令、技能、工作流、钩子、MCP 服务器、插件、设置、记忆等概念。","sourceType":"readme","locator":"https://github.com/shanraisshan/claude-code-best-practice"},{"claim":"仓库包含最佳实践文档和实现示例，例如子代理、命令、技能、MCP、设置等。","sourceType":"readme","locator":"https://github.com/shanraisshan/claude-code-best-practice"},{"claim":"仓库提供了编排工作流示例，如天气编排器命令。","sourceType":"readme","locator":"https://github.com/shanraisshan/claude-code-best-practice"},{"claim":"仓库包含指向官方文档和社区资源的链接，如 Boris Cherny 的推文和 Claude Code 文档。","sourceType":"readme","locator":"https://github.com/shanraisshan/claude-code-best-practice"}],"publishedAt":"2026-08-17T14:26:00.454Z"},"github":{"url":"https://github.com/shanraisshan/claude-code-best-practice","ownerAvatarUrl":"https://avatars.githubusercontent.com/u/11731897?v=4","starsCount":64610,"forksCount":6418,"language":"HTML","syncedAt":"2026-08-17T13:39:00.063Z","license":"MIT","defaultBranch":"main","archived":false,"disabled":false,"lastChangedAt":"2026-08-17T06:47:54.000Z","missing":false},"tags":[{"name":"Vibe coding","slug":"vibe-coding","verification":"verified","evidenceUrl":"https://github.com/shanraisshan/claude-code-best-practice","evidenceExcerpt":"GitHub topic: vibe-coding"}],"updates":[]},"entryPoint":"discovery","claim":{"state":"unclaimed","verified":false},"initialView":"beautified","community":{"viewer":null,"state":{"likesCount":0,"creativeCount":0,"followersCount":0,"commentsCount":0,"liked":false,"creative":false,"followed":false},"comments":{"comments":[],"nextCursor":null}}}]}],"$L24"]

一次“手感”请求,如何走成一条管线

九个站点,各有各的职责

子代理 subagent

命令 command

技能 skill

工作流 workflow

钩子 hook

MCP 服务器

插件 plugin

设置 settings

记忆 memory

把交接,编排成可执行的工程

短指令与可复用动作

命令 command

技能 skill

在关键节点,挂上自动动作

交接,可以跨过不同模型

继续练习,让线一直延伸下去

How one "vibe ask" becomes a pipeline

Nine stations, each with a job

Subagent

Command

Skill

Workflow

Hook

MCP Server

Plugin

Settings

Memory

Arrange the handoffs into a runnable build

Short calls and reusable moves

Command

Skill

Fire automatic moves at the key nodes

Handoffs can span more than one model

Keep practicing —let the line keep running

一次“手感”请求,
如何走成一条管线

继续练习,
让线一直延伸下去

Keep practicing —
let the line keep running