neighbours
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
02 资源文件 7
- 参考文档evidence/rules/list.yml57 B
- 参考文档evidence/rules/subject.yml90 B
- 参考文档evidence/sgconfig.yml18 B
- 参考文档rulebook/steering.md50 B
- 参考文档rulebook/steering.rules.json410 B
- 参考文档scan-oracle.json341 B
- 参考文档skill-rules.config.json753 B
03 SKILL.md 正文
Intro.
- previous one
- previous two
Subject.
- following one
- following two
04 同仓库更多 Skills
smoke-fixture
暂无简介
demistify-explainer
Use when writing, editing, or checking Demistify markup: component syntax, attributes, nesting, layouts, Markdown/Mermaid islands, and data references.
examples
暂无简介
verification-design
Use when planning how a design project's requirements will be proven: for each requirement, the reference, the target and `verify-<app>` journey, a passing condition a wrong build fails, reused real-path tests and what stays unverified, after Program Design or when that plan is missing or stale. Not for observing or challenging a delivered claim (practices-verification), building journeys (practices-verification-maintenance), or regression tests.
practices-retrospective
Use when asked for a blameless retrospective, a look back, or lessons from a finished or bounded session or delivery: what helped, what hindered, what to preserve, or why an owner or review correction keeps recurring across sessions. Not for re-anchoring a shared model in the current conversation, diagnosing a current failure, collecting evidence alone, choosing which skills to create or merge, or maintaining a verification skill.
practices-research
Use when a task needs source gathering, prior-art research, current docs or web evidence, or memory, session-log, or saved-reader research before design, planning, review, or discussion can continue. Not for extracting unwritten owner meaning.