搜索

PythonReactSEOPDF
GitHub Skill

azure-artifacts

Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7). USE FOR: generating any agent artifact, checking H2 structure compliance. DO NOT USE FOR: Azure resource configuration (use azure-defaults), Bicep/Terraform patterns (use bicep-patterns or terraform-patterns).

jonathan-vella☆ 147 仓库 Stars53 仓库 Forks

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。

查看来源 ↗使用指南

技能说明

Azure Artifacts Skill

Single source of truth for artifact template structures and styling. Per-step H2 definitions live in references/ — load only the step you are generating.


Artifact Generation Rules

Mandatory Compliance
Rule Requirement
Template skeleton Read step template from references/ and replicate
Exact text Use H2 text from templates verbatim
Exact order Required H2s appear in the order listed
Anchor rule Extra sections allowed ONLY after last required H2
No omissions Every H2 listed must appear in output
Attribution > Generated by {agent} agent | {YYYY-MM-DD}
DO / DON'T
  • DO: Read the step-specific template before generating
  • DO: Copy H2 text character-for-character (including emoji)
  • DO: Save all output to agent-output/{project}/
  • DON'T: Reorder H2 headings from the listed sequence
  • DON'T: Use placeholder text like "TBD" or "Insert here"
  • DON'T: Add custom H2 sections BEFORE the last required H2

Mandatory: Project README

Every project in agent-output/{project}/ MUST have a README.md.

After saving step artifact(s), update the README:

  1. Mark your step as complete in ## ✅ Workflow Progress
  2. Add artifact files to ## 📄 Generated Artifacts
  3. Update Last Updated date and progress bar percentage

Placeholder Syntax

All templates use single-brace {placeholder-name} syntax:

  • Lowercase, hyphen-separated: {project-name}, {monthly-cost}
  • No Mustache/Handlebars {{double-braces}}

Automated Validation

npm run lint:artifact-templates   # H2 order and required headings
npm run lint:h2-sync              # Template ↔ artifact sync
npm run validate:all              # All validators together

Quality Checklist

  • H2 headings match template exactly (text + order)
  • Attribution header present with agent name and date
  • No placeholder text ("TBD", "Insert here", "TODO")
  • File saved to agent-output/{project}/ with correct name

Reference Index

When generating a Step N artifact, read the corresponding template:

Reference When to Load
references/01-requirements-template.md Generating Step 1 requirements
references/02-architecture-template.md Generating Step 2 assessment or Step 3 cost estimate
references/04-plan-template.md Generating Step 4 plan, governance, or preflight
references/05-code-template.md Generating Step 5 implementation reference
references/06-deploy-template.md Generating Step 6 deployment summary
references/07-docs-template.md Generating Step 7 workload documentation
references/styling-standards.md Applying callouts, badges, emoji, navigation

使用示例

查看来源仓库中的使用示例与配置说明。

查看来源 ↗

来源历史

收录时间
2026-03-11
索引更新时间
2026-03-11
Branch
main

收录与同步日期属于本站记录。源码修改历史请查看来源仓库。

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!