菜单
How to create reference documentation for complex coordinate systems and building constraints
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/csharpfritz/Aspire-Minecraft --skill architecture-documentation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
Manage Azure DevOps resources via CLI including projects, repos, pipelines, builds, pull requests, work items, artifacts, and service endpoints. Use when working with Azure DevOps, az commands, devops automation, CI/CD, or when user mentions Azure DevOps CLI.
Prevents subsystems from modifying blocks within placed building volumes using 3D bounding box clipping
Correctly place directional blocks (doors, levers, torches, signs, banners, stairs) in Minecraft via RCON
| name | architecture-documentation |
| description | How to create reference documentation for complex coordinate systems and building constraints |
| domain | documentation |
| confidence | low |
| source | earned |
When a project involves complex spatial logic (coordinate systems, layout algorithms, size constraints) or technical constraints (rate limits, API boundaries), create two complementary reference documents:
This skill applies when:
Document 1: Visual Architecture (docs/architecture-diagram.md)
Document 2: Constraints Reference (docs/[domain]-constraints.md)
Both documents should include:
Architecture diagrams:
Constraints:
Y=-59: Air (player walking level)
↑ Players walk here
│
Y=-60: █████████████████████ ← BaseY (grass block surface)
│ Structures place floors here
Why this works: Visual hierarchy shows relationships. Annotations explain purpose, not just labels.
col = index % 2 // Alternates 0, 1, 0, 1, ...
row = index / 2 // Increments every 2 resources: 0, 0, 1, 1, 2, 2, ...
x = BaseX + (col × 10) // Result: 10, 20, 10, 20, 10, 20, ...
Why this works: Formula + concrete results + inline comments. Reader sees pattern immediately.
### ⚠️ Critical Y-Level Rules
1. **Never place fences at `BaseY + 1`** — they will float one block above the ground.
2. **Paths must be at `BaseY - 1`** with grass cleared at `BaseY` — this makes them flush with the surrounding terrain.
Why this works: Emoji draws attention. "Never" is unambiguous. Explanation shows consequence of violation.
| Operation | Command Count | Estimated Time (at 10 cmd/sec) |
|-----------|---------------|--------------------------------|
| Single structure | ~15-20 commands | 1.5-2 seconds |
| 50-resource village | ~800-900 commands | 80-90 seconds |
Why this works: Concrete numbers. Shows scaling behavior. Helps users understand cost.
❌ Single monolithic document — hard to navigate, mixes "how it works" with "how to use it"
❌ Diagrams without numbers — "structures are spaced apart" is vague; "Spacing=10 blocks center-to-center" is precise
❌ Constants without source references — reader can't verify or update; always cite source file and line
❌ Rules without rationale — "Don't place fences at Y+1" → why? Add consequence: "they will float in the air"
❌ Examples without scaling limits — show 4-resource village working fine, hide that 50+ resources break
❌ Missing cross-references — constraints doc should point to architecture doc for visual explanations
❌ Stale examples — if constants change in code, docs break. Use grep to verify constants match.