blueprint-document-reference
- Repo stars 0
- License NOASSERTION
- Author updated Live
- Author repo blueprints-learn.zh-Hans
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @AdobeDocs · NOASSERTION
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: blueprint-document-reference
description: 在此存储库中创建或编辑Blueprint文档时使用此技能。 Blueprint是可重复的实施,用于解决已确定的业务问题,包括架构图、技术注意事项以及相关Adobe Experience Lea…
category: other
runtime: no special runtime
---
# blueprint-document-reference output preview
## PART A: Task fit
- Use case: 在此存储库中创建或编辑Blueprint文档时使用此技能。 Blueprint是可重复的实施,用于解决已确定的业务问题,包括架构图、技术注意事项以及相关Adobe Experience League文档的链接。 每个Blueprint页面都应遵循此结构。 仅包括适用的部分。 title: [Short descriptive title] runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “何时应用 / 快速参考 / 文档模板” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “在此存储库中创建或编辑Blueprint文档时使用此技能。 Blueprint是可重复的实施,用于解决已确定的业务问题,包括架构图、技术注意事项以及相关Adobe Experience League文档的链接。 每个Blueprint页面都应遵循此结构。 仅包括适用的部分。 title: [Short descriptive title] runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “何时应用 / 快速参考 / 文档模板” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “何时应用 / 快速参考 / 文档模板”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: blueprint-document-reference
description: 在此存储库中创建或编辑Blueprint文档时使用此技能。 Blueprint是可重复的实施,用于解决已确定的业务问题,包括架构图、技术注意事项以及相关Adobe Experience Lea…
category: other
source: AdobeDocs/blueprints-learn.zh-Hans
---
# blueprint-document-reference
## When to use
- 在此存储库中创建或编辑Blueprint文档时使用此技能。 Blueprint是可重复的实施,用于解决已确定的业务问题,包括架构图、技术注意事项以及相关Adobe Experience League文档的链接。 每个Blueprint页…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “何时应用 / 快速参考 / 文档模板” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "blueprint-document-reference" {
input -> user goal + target files + boundaries + acceptance criteria
context -> 何时应用 / 快速参考 / 文档模板
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Blueprint文档引用
在此存储库中创建或编辑Blueprint文档时使用此技能。 Blueprint是可重复的实施,用于解决已确定的业务问题,包括架构图、技术注意事项以及相关Adobe Experience League文档的链接。
何时应用
- 创建新的Blueprint文档或Blueprint概述页面
- 在现有Blueprint中添加或重新构建区域
- 链接或引用Adobe Experience League文档
- 将新内容与Blueprint约定(前件、标题、图表)对齐
快速参考
- 文档目的: Blueprint提供系统和数据流架构,以显示Adobe Experience Platform和应用程序的集成方式。 它们是视觉和技术性的,而不是营销性的。
- 节:使用模板中的标准节;仅在不适用时省略(请参阅reference.md)。
- Experience League:首选链接到Experience League以获取产品文档、API、护栏和教程。 使用完整的URL;有关URL模式和格式,请参阅reference.md。
- 存储库结构: Blueprint位于
help/blueprints/下。 添加或移动Blueprint页面时更新help/blueprints/TOC.md。
文档模板
每个Blueprint页面都应遵循此结构。 仅包括适用的部分。
---
title: [Short descriptive title]
description: "[One sentence: what this blueprint shows and why it matters.]"
solution: [Product name, e.g. Real-Time Customer Data Platform, Journey Optimizer]
exl-id: [UUID - if this is already popultated keep it as is. Disregard and remove this field if it is a new blueprint as blank values will be rejected by the publishing flow. If the field and value are not present, it will be auto-generated as part of the Experience League publishing flow]
---
# [H1 - same as title or expanded]
[1–3 paragraphs: what the blueprint covers, key capabilities, and who it’s for.]
## Applications
* [Product 1]
* [Product 2]
## Use cases
* [Use case 1]
* [Use case 2]
## Prerequisites
[Bullets or short paragraphs: required products, config, or setup.]
## Architecture Diagram
<img src="[path to SVG/image]" alt="[Descriptive alt]" style="width:90%; border:1px solid #4a4a4a" class="modal-image" />
## Guardrails
[Link to Experience League guardrails and any blueprint-specific limits.]
## Implementation patterns
[Optional: named patterns with bullets.]
## Implementation steps
1. [Step with link to Experience League where relevant]
2. ...
## Implementation considerations
[Optional: identity, performance, security, etc.]
## Related documentation
[Grouped links to Experience League: product docs, APIs, tutorials.]
对于概述页面或中心页面,请使用较短的结构:简介、用例(或选项卡)、架构图像、方案/阵列表、先决条件、护栏、相关文档。 有关示例,请参阅help/blueprints/中的现有概述。
Frontmatter
| 字段 | 必填 | 注释 |
|---|---|---|
title |
是 | 短;按Adobe样式使用[!DNL Product Name]作为产品名称 |
description |
是 | 一个句子;用于搜索和卡片 |
solution |
是 | 主要产品(例如Real-Time Customer Data Platform、Journey Optimizer) |
exl-id |
是 | UUID;留空则创建新页面 |
doc-type |
概述 | 将overview-page用于主Blueprint概述页面 |
kt |
可选 | 知识库文章ID(如果已链接) |
引用Adobe Experience League
- 何时链接:链接到Experience League,获取产品文档、API引用、护栏、教程和配置步骤。 不要重复冗长的过程;摘要和链接。
- URL格式:使用完整的URL。 首选
https://experienceleague.adobe.com/docs/?lang=zh-Hans...或https://experienceleague.adobe.com/zh-hans/docs/...。 对于开发人员文档,https://developer.adobe.com/...也有效。 - 链接文本:使用描述性文本(例如,“[创建架构] (url)”,而不是“单击此处”)。 对于链接文本中的产品名称,请酌情使用
[!DNL Product Name]。 - 相关文档部分:使用“相关文档”部分结束Blueprint并按类别对链接进行分组(例如,目标配置、SDK文档、配置文件和分段、教程)。
有关详细的URL模式、链接分组和示例,请参阅reference.md。
提交前清单
- Frontmatter具有
title、description、solution、exl-id - H1匹配或适当扩展标题
- [ ]架构图显示和替换文本描述性
- [ ]实施步骤链接到Experience League,过程位于此处
- [ ]护栏部分链接到官方的Experience League护栏文档
- [ ]相关文档部分包含相关的Experience League链接
- [ ]个新页面或移动页面反映在
help/blueprints/TOC.md中
其他资源
- 完整模板和部分注释: reference.md
- 现有Blueprint:
help/blueprints/(例如audience-activation/real-time-lookup.md,customer-journeys/journey-optimizer/journey-optimizer-overview.md) - 目录和导航:
help/blueprints/TOC.md
Decide Fit First
Design Intent
How To Use It
Boundaries And Review