guidance-measurement
Guidance-complexity measurement tooling and usage notes. Use when running or maintaining the guidance measurement script and related deterministic analysis assets for issue #360. DO NOT USE FOR: changing D10 ceiling rules or prompt-facing guidance policy, which remain in agent prompts.
- License 许可
- MIT
- 最近更新
- 2026-08-16
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- guidance-measurement
- description
- Guidance-complexity measurement tooling and usage notes. Use when running or maintaining the guidance measurement script and related deterministic analysis assets for issue #360. DO NOT USE FOR: changing D10 ceiling rules or prompt-facing guidance policy, which remain in agent prompts.
02 资源文件 2
03 SKILL.md 正文
Guidance Measurement
This skill owns deterministic tooling for measuring guidance complexity without moving the D10 ceiling rules themselves out of agent prompts.
Purpose
- Describe the measurement domain for issue #360
- Provide the stable home for measurement scripts under
scripts/ - Keep tooling separate from prompt-owned guidance rules
Contents
scripts/contains the guidance measurement CLI wrapper and core implementation- Future supporting assets should stay next to this skill only if they are measurement-specific
Boundary
- The D10 ceiling and prompt guidance rules stay in agent prompts and are not migrated here
- This skill is only for measurement and deterministic analysis support
Gotchas
| Trigger | Gotcha | Fix |
|---|---|---|
| Moving guidance tooling | The measurement script gets confused with the prompt-owned D10 rule set | Keep measurement code here and leave the actual ceiling rules in agent prompts |
04 同仓库更多 Skills
webapp-testing
Playwright end-to-end testing guidance for web apps, with practical patterns and setup steps. Use when creating or improving browser-based E2E coverage, test stability, and CI execution. DO NOT USE FOR: React component tests (use ui-testing), canvas game interaction (use browser-canvas-testing), TDD workflow (use test-driven-development), debugging failures (use systematic-debugging), or randomized property tests (use property-based-testing).
verification-before-completion
Evidence-based verification checklist before marking work complete. Use before PRs, releases, marking tickets done, or any "I'm finished" declaration; also when naming a baseline commit for a differential suite claim, when designing a mutation campaign or red-run evidence, when making an absence claim, a universal claim, or a one-time demonstration offered as a standing guarantee, when attributing a measurement or claiming a sweep or verification loop is complete, and when stating what a check or a CI suite will do about a change. DO NOT USE FOR: post-merge cleanup or archival (use post-pr-review) or processing GitHub review comments (use code-review-intake).
validation-methodology
Reusable validation and review methodology for staged validation, failure triage, and prosecution-depth setup. Use when running validation ladders, triaging failures, or executing adversarial review passes. DO NOT USE FOR: CE Gate orchestration, specialist dispatch ownership, or step execution flow (keep those in Code-Conductor).
upstream-onboarding
Shared opening-phase protocol for upstream agents (Experience-Owner, Solution-Designer, Issue-Planner) and Code-Conductor when invoked on an existing GitHub issue. Renders a scaled context brief and runs a standards check on inherited work at each phase boundary. Use when a user-invocable agent receives a request referencing an existing GitHub issue and must load solution-authoring and upstream-onboarding at the opening phase. DO NOT USE FOR: subagent dispatches (which already operate within an assessed session context); post-merge review (use post-pr-review); research or non-tree subagents.
ui-testing
Resilient React component testing strategies focusing on user behavior. Use when writing or reviewing component-level React tests, fixing flaky component tests, or establishing React testing patterns. DO NOT USE FOR: Playwright E2E tests (use webapp-testing), canvas game interaction (use browser-canvas-testing), TDD workflow (use test-driven-development), debugging failures (use systematic-debugging), UI component design (use frontend-design), or randomized property tests (use property-based-testing).
ui-iteration
Reusable screenshot-driven UI polish workflow for iterative visual refinement. Use when improving layout, hierarchy, spacing, feedback, or Tailwind-based presentation through repeated review-and-adjust passes. DO NOT USE FOR: functional bug fixing, accessibility-only audits, or major redesign strategy work (use Code-Smith or frontend-design).