[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDMG4ZFZ4MMJS16G08E2G9":3,"skill-same:01M7FDMG4ZFZ4MMJS16G08E2G9":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7FDMG4ZFZ4MMJS16G08E2G9","adk-architecture",null,"Explains how the ADK runtime fits together: the node and graph execution model, Context and Event flow, checkpoint and resume, tracing, and the rules governing the public API surface. Use when answering \"how does X work\" about ADK internals, tracing where an event or a piece of state comes from, deciding where a new capability belongs, reviewing a change to BaseNode, Workflow, Runner, Agent, Event or Context, working out why a node re-ran or stayed waiting after a resume, or judging whether a change breaks the public API. Don't use for assembling an agent from existing pieces (use adk-agent-builder), diagnosing one failing run or test (use adk-debug), or formatting and naming conventions (use adk-style).","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: adk-architecture\ndescription: >-\n  Explains how the ADK runtime fits together: the node and graph execution\n  model, Context and Event flow, checkpoint and resume, tracing, and the rules\n  governing the public API surface. Use when answering \"how does X work\" about\n  ADK internals, tracing where an event or a piece of state comes from,\n  deciding where a new capability belongs, reviewing a change to BaseNode,\n  Workflow, Runner, Agent, Event or Context, working out why a node re-ran or\n  stayed waiting after a resume, or judging whether a change breaks the public\n  API. Don't use for assembling an agent from existing pieces (use\n  adk-agent-builder), diagnosing one failing run or test (use adk-debug), or\n  formatting and naming conventions (use adk-style).\n---\n\n# ADK Architecture\n\nThe runtime is a graph of nodes. `BaseNode` is the unit of execution.\n`Workflow` is a node that schedules other nodes along declared edges.\n`NodeRunner` executes exactly one node. `Runner` owns the invocation and the\nsession. Agents are nodes too — `BaseAgent` extends `BaseNode`.\n\nA node communicates with its parent through a per-execution `Context`, and\nwith the session through `Event`s it yields. Those are two separate channels:\n`ctx` carries the result upward, events carry persistence and streaming.\n\nRead the source before relying on any signature here. These notes drift; the\ncode does not. Paths below are relative to `src\u002Fgoogle\u002Fadk\u002F`.\n\n## Pick a reference\n\n| Question | Reference |\n|---|---|\n| What must a node implement? What may it yield? Which config fields exist? | [BaseNode](references\u002Finterface-base-node.md) |\n| How does the graph schedule nodes, dedup dynamic children, propagate interrupts? | [Workflow](references\u002Finterface-workflow.md) |\n| How does a caller start an invocation? | [Runner](references\u002Finterface-runner.md) |\n| What is `Agent`, and which methods do I call on it? | [Agent](references\u002Finterface-agent.md) |\n| I am subclassing an agent — what do I override? | [BaseAgent](references\u002Finterface-base-agent.md) |\n| What is on an `Event`, and what may I assume about its lifetime? | [Event](references\u002Finterface-event.md) |\n| What does a node read and write on `ctx`? | [Context](references\u002Farchitecture-context.md) |\n| Who creates the child Context, stamps events, retries, catches errors? | [NodeRunner](references\u002Farchitecture-node-runner.md) |\n| Why are Runner, NodeRunner and Workflow three separate things? | [Runner roles](references\u002Farchitecture-runner-roles.md) |\n| How does a human-in-the-loop pause and resume work for one node? | [Checkpoint and resume](references\u002Farchitecture-checkpoint-resume.md) |\n| How does a whole workflow survive a pause, and what does `is_resumable` change? | [Workflow resumability](references\u002Farchitecture-workflow-resumability.md) |\n| How are spans created, and what attributes do they carry? | [Observability](references\u002Farchitecture-observability.md) |\n| Why does the model not see the raw event log? | [LLM context orchestration](references\u002Farchitecture-llm-context-orchestration.md) |\n| Is this change a breaking change? Where does a new export belong? | [API principles](references\u002Fapi-principles.md) |\n\n## Where the code lives\n\n| Concept | Module |\n|---|---|\n| `BaseNode`, `START` | `workflow\u002F_base_node.py` |\n| `Workflow`, `_LoopState` | `workflow\u002F_workflow.py` |\n| `Graph`, edge compilation | `workflow\u002F_graph.py` |\n| `NodeRunner` | `workflow\u002F_node_runner.py` |\n| `DynamicNodeScheduler` | `workflow\u002F_dynamic_node_scheduler.py` |\n| `ReplayManager` (resume scan) | `workflow\u002Futils\u002F_replay_manager.py` |\n| `NodeInterruptedError`, `NodeTimeoutError` | `workflow\u002F_errors.py` |\n| `Context`, `ctx.run_node()` | `agents\u002Fcontext.py` |\n| `ReadonlyContext` | `agents\u002Freadonly_context.py` |\n| `InvocationContext` | `agents\u002Finvocation_context.py` |\n| `BaseAgent`, `LlmAgent` (aliased `Agent`) | `agents\u002Fbase_agent.py`, `agents\u002Fllm_agent.py` |\n| `Event`, `NodeInfo` | `events\u002Fevent.py` |\n| `EventActions` | `events\u002Fevent_actions.py` |\n| Branch paths (`parent.child@1`) | `events\u002F_branch_path.py` |\n| Node paths (`wf@1\u002Fchild@2`) | `events\u002F_node_path_builder.py` |\n| `Runner`, `InMemoryRunner` | `runners.py` |\n| `LiveRequestQueue`, `LiveRequest` | `live\u002Flive_request_queue.py` |\n| Node spans, `TelemetryContext` | `telemetry\u002Fnode_tracing.py` |\n| `ResumabilityConfig` | `apps\u002F_configs.py` |\n\nEverything under `workflow\u002F` is a leading-underscore module. Treat those names\nas internal — they can change without a major version bump, so a change there\nis not automatically a breaking change.\n","# ADK Architecture\n\nThe runtime is a graph of nodes. `BaseNode` is the unit of execution.\n`Workflow` is a node that schedules other nodes along declared edges.\n`NodeRunner` executes exactly one node. `Runner` owns the invocation and the\nsession. Agents are nodes too — `BaseAgent` extends `BaseNode`.\n\nA node communicates with its parent through a per-execution `Context`, and\nwith the session through `Event`s it yields. Those are two separate channels:\n`ctx` carries the result upward, events carry persistence and streaming.\n\nRead the source before relying on any signature here. These notes drift; the\ncode does not. Paths below are relative to `src\u002Fgoogle\u002Fadk\u002F`.\n\n## Pick a reference\n\n| Question | Reference |\n|---|---|\n| What must a node implement? What may it yield? Which config fields exist? | [BaseNode](references\u002Finterface-base-node.md) |\n| How does the graph schedule nodes, dedup dynamic children, propagate interrupts? | [Workflow](references\u002Finterface-workflow.md) |\n| How does a caller start an invocation? | [Runner](references\u002Finterface-runner.md) |\n| What is `Agent`, and which methods do I call on it? | [Agent](references\u002Finterface-agent.md) |\n| I am subclassing an agent — what do I override? | [BaseAgent](references\u002Finterface-base-agent.md) |\n| What is on an `Event`, and what may I assume about its lifetime? | [Event](references\u002Finterface-event.md) |\n| What does a node read and write on `ctx`? | [Context](references\u002Farchitecture-context.md) |\n| Who creates the child Context, stamps events, retries, catches errors? | [NodeRunner](references\u002Farchitecture-node-runner.md) |\n| Why are Runner, NodeRunner and Workflow three separate things? | [Runner roles](references\u002Farchitecture-runner-roles.md) |\n| How does a human-in-the-loop pause and resume work for one node? | [Checkpoint and resume](references\u002Farchitecture-checkpoint-resume.md) |\n| How does a whole workflow survive a pause, and what does `is_resumable` change? | [Workflow resumability](references\u002Farchitecture-workflow-resumability.md) |\n| How are spans created, and what attributes do they carry? | [Observability](references\u002Farchitecture-observability.md) |\n| Why does the model not see the raw event log? | [LLM context orchestration](references\u002Farchitecture-llm-context-orchestration.md) |\n| Is this change a breaking change? Where does a new export belong? | [API principles](references\u002Fapi-principles.md) |\n\n## Where the code lives\n\n| Concept | Module |\n|---|---|\n| `BaseNode`, `START` | `workflow\u002F_base_node.py` |\n| `Workflow`, `_LoopState` | `workflow\u002F_workflow.py` |\n| `Graph`, edge compilation | `workflow\u002F_graph.py` |\n| `NodeRunner` | `workflow\u002F_node_runner.py` |\n| `DynamicNodeScheduler` | `workflow\u002F_dynamic_node_scheduler.py` |\n| `ReplayManager` (resume scan) | `workflow\u002Futils\u002F_replay_manager.py` |\n| `NodeInterruptedError`, `NodeTimeoutError` | `workflow\u002F_errors.py` |\n| `Context`, `ctx.run_node()` | `agents\u002Fcontext.py` |\n| `ReadonlyContext` | `agents\u002Freadonly_context.py` |\n| `InvocationContext` | `agents\u002Finvocation_context.py` |\n| `BaseAgent`, `LlmAgent` (aliased `Agent`) | `agents\u002Fbase_agent.py`, `agents\u002Fllm_agent.py` |\n| `Event`, `NodeInfo` | `events\u002Fevent.py` |\n| `EventActions` | `events\u002Fevent_actions.py` |\n| Branch paths (`parent.child@1`) | `events\u002F_branch_path.py` |\n| Node paths (`wf@1\u002Fchild@2`) | `events\u002F_node_path_builder.py` |\n| `Runner`, `InMemoryRunner` | `runners.py` |\n| `LiveRequestQueue`, `LiveRequest` | `live\u002Flive_request_queue.py` |\n| Node spans, `TelemetryContext` | `telemetry\u002Fnode_tracing.py` |\n| `ResumabilityConfig` | `apps\u002F_configs.py` |\n\nEverything under `workflow\u002F` is a leading-underscore module. Treat those names\nas internal — they can change without a major version bump, so a change there\nis not automatically a breaking change.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","07-后端与架构\u002Fadk-architecture",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill adk-architecture",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill adk-architecture",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill adk-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84,88,92,96,100],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fapi-principles.md","REFERENCE","参考文档",1951,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Fapi-principles.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Farchitecture-checkpoint-resume.md",2650,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Farchitecture-checkpoint-resume.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Farchitecture-context.md",4280,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Farchitecture-context.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Farchitecture-llm-context-orchestration.md",1956,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Farchitecture-llm-context-orchestration.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Farchitecture-node-runner.md",4527,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Farchitecture-node-runner.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Farchitecture-observability.md",3656,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Farchitecture-observability.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Farchitecture-runner-roles.md",452,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Farchitecture-runner-roles.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Farchitecture-workflow-resumability.md",7872,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Farchitecture-workflow-resumability.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Finterface-agent.md",2024,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Finterface-agent.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Finterface-base-agent.md",2087,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Finterface-base-agent.md",{"path":89,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Finterface-base-node.md",5009,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Finterface-base-node.md",{"path":93,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Finterface-event.md",3022,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Finterface-event.md",{"path":97,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Finterface-runner.md",1765,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Finterface-runner.md",{"path":101,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Finterface-workflow.md",12854,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fadk-architecture\u002Freferences\u002Finterface-workflow.md",[105,112,117,124,131,138],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":113,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]