ywc-architecture-invariants
(ywc) Validate an optional repository-root architecture-invariants.json contract and bounded normalized edge evidence. Triggers: "architecture invariants", "architecture boundary", "architecture contract", "boundary validation". Validation-only in v1; never executes verifier data. Do not use for: verifier execution, general architecture advisory or design trade-off judgment (use ywc-architect), or security review (use ywc-security-audit / ywc-security-engineer).
- License 许可
- MIT
- 最近更新
- 2026-11-08
- Stars
- ★ 8
- Forks
- 1
01 前言 Front Matter
- name
- ywc-architecture-invariants
- description
- (ywc) Validate an optional repository-root architecture-invariants.json contract and bounded normalized edge evidence. Triggers: "architecture invariants", "architecture boundary", "architecture contract", "boundary validation". Validation-only in v1; never executes verifier data. Do not use for: verifier execution, general architecture advisory or design trade-off judgment (use ywc-architect), or security review (use ywc-security-audit / ywc-security-engineer).
02 资源文件 9
- 参考文档agents/openai.yaml285 B
- 参考文档evals/evals.json3.6 KB
- 参考文档README.en.md270 B
- 参考文档README.es.md151 B
- 参考文档README.ja.md178 B
- 参考文档README.ko.md188 B
- 参考文档README.md178 B
- 参考文档README.zh.md133 B
- 参考文档references/contracts.md2.7 KB
03 SKILL.md 正文
ywc-architecture-invariants
Use the shared helper to validate the optional root architecture-invariants.json,
validate normalized evidence, and audit a bounded changed-path scope. The contract
is JSON-compatible and closed: unknown fields, unsafe paths, invalid globs,
ambiguous mappings, and incomplete coverage return NEEDS_CONTEXT.
Interface
ywc-architecture-invariants --mode draft --proposal <path> --output <path> --approve-write
ywc-architecture-invariants --mode validate [--manifest <path>]
ywc-architecture-invariants --mode audit --changed-path <path>... --evidence <path> [--manifest <path>]
V1 launches zero child processes and accepts no executable/verifier fields.
Omitted manifest discovery checks only the repository root. An absent discovered
manifest returns N/A — no architecture contract; an explicit missing or invalid
manifest never falls back. See references/contracts.md
for the exact schemas and verdict precedence.
04 同仓库更多 Skills
missing-frontmatter
暂无简介
malformed-frontmatter
暂无简介
fixture-501-fail
(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.
fixture-500-pass
(ywc) Use when aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa Do not use for x.
ywc-worktrees
(ywc) Use when creating, auditing, pruning, or resolving git worktrees for isolated task workspaces, whether delegated from an executor or used standalone. Triggers: "worktree 생성", "worktree audit", "worktree 정리", "worktree prune", "ywc-worktrees", "create worktree". Do not use for branch creation/deletion alone, PR creation (use ywc-create-pr), CI or merge delivery (use ywc-finish-branch), task orchestration (use ywc-sequential-executor or ywc-parallel-executor), or non-git isolation.
ywc-wayfinder
(ywc) Use when a large or uncertain change needs multi-session discovery with a deterministic local map and exactly one active ticket before planning or implementation. Triggers: "wayfinder", "길찾기", "discovery map", "multi-session discovery", "탐색 ticket", "経路整理", "探索マップ", "ywc-wayfinder". Do not use for ordinary planning (use ywc-plan), idea clarification (use ywc-brainstorm), direct implementation, or tracker/database writes outside the local Markdown map.