# Create YAML Architecture Diagrams

Architecture teams need diagram YAML that is consistent, valid, and easy to maintain. This skill gives schemas, layout rules, examples, and troubleshooting guidance for diagram authoring.

## Install

```bash
npx skillstore add 7nohe/yaml-authoring
```

## Metadata

- Status: approved
- Slug: 7nohe-yaml-authoring
- Skillstore revision: r1
- Version status: missing
- Tree hash: aa082f7096a4b6152b05f6be3d7b5f4e1e6a9ab840eb4665fd11da48ccf69f50
- Author: 7nohe
- GitHub username: 7nohe
- License: MIT
- Repository: https://github.com/7nohe/figram/tree/main/.claude/skills/yaml-authoring
- Ref: c1fdca50ff516318f65fed0d7f9e82797c5171dc
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/7nohe-yaml-authoring
- Manifest: https://skillstore.pages.dev/api/skills/7nohe-yaml-authoring/manifest

## Capabilities

- Defines required document fields such as version, docId, nodes, and edges.
- Explains node layout rules, including auto-layout for child nodes.
- Lists supported infrastructure kind patterns for common cloud resources.
- Provides complete diagram examples for Lambda, API, database, and VPC patterns.
- Describes validation commands and common error fixes.

## Use Cases

- Draft cloud architecture diagrams: Create structured YAML for services, containers, edges, labels, and layout positions.
- Fix diagram validation errors: Diagnose missing fields, duplicate IDs, layout problems, and broken node references.
- Standardize architecture documentation: Use consistent node kinds, labels, comments, and nesting rules across diagram files.

## Prompt Templates

### Create a basic diagram

```
Create a YAML architecture diagram for [system]. Include version, docId, title, nodes, edges, labels, and simple layout coordinates.
```

### Add nested resources

```
Build a YAML diagram for [architecture]. Use VPC or subnet containers, parent relationships, and auto-layout for child resources where appropriate.
```

### Troubleshoot validation errors

```
Review this diagram YAML for validation issues: [paste YAML]. Explain each problem and provide corrected structure without changing the architecture intent.
```

### Refine a complex architecture

```
Improve this architecture diagram YAML for readability, unique IDs, clear labels, valid edges, nested containers, and maintainable layout: [paste YAML].
```

## Limitations

- Does not include an executable validator inside the skill package.
- Does not render diagrams or preview visual output by itself.
- Focuses on the documented diagram YAML format, not general YAML standards.
- Requires users to provide real architecture details and naming choices.

## Best Practices

- Use descriptive IDs that match the resource purpose.
- Keep top-level nodes positioned with explicit x and y values.
- Use parent relationships for resources inside VPC or subnet containers.

## Anti Patterns

- Do not reuse node or edge IDs across the same document.
- Do not specify only one coordinate for a positioned node.
- Do not create edges that reference missing node IDs.

## Security Audit

- Audited at: 2026-07-06T00:48:19.166\+00:00
- Summary: Static analysis flagged Markdown fences and inline backticks as Ruby or shell execution, but the skill is a documentation-only YAML authoring guide. No prompt injection, data exfiltration, destructive command, or hidden execution intent was found in SKILL.md.

## Stats

- Views: 265
- Downloads: 18
- Favorites: 0
- Popularity score: 0