principle-never-block-on-the-human
WHEN progress awaits a human decision; NOT permission to exceed scope; continue authorized independent work and isolate the actual dependency.
- License 许可
- MIT
- 所属仓库
- mintuz/skills
- 最近更新
- 2026-11-11
- Stars
- ★ 35
- Forks
- 7
01 前言 Front Matter
- name
- principle-never-block-on-the-human
- description
- WHEN progress awaits a human decision; NOT permission to exceed scope; continue authorized independent work and isolate the actual dependency.
03 SKILL.md 正文
Never Block On The Human
Separate work needing missing facts or authority from work already authorized. Complete independent investigation, implementation, tests and reviewable preparation while the human is unavailable.
Choose routine implementation details within scope and state material assumptions. Ask narrowly for the fact or decision that blocks dependent work; keep that dependency pending. Silence and elapsed time never supply consent.
Reversibility does not override an explicit read-only request, protected data or unrelated work. Publishing, deployment, external messages and destructive changes need authority from the user or applicable instructions; do not repeatedly ask for authority already given.
Present the concrete result, evidence limits and remaining dependency. A plausible fix is still a hypothesis until tested. Preparation can continue without pretending missing access or production verification exists.
Distinct from: principle-stay-in-scope (an action may fall outside the grant), principle-state-the-scope (a broad or ambiguous request needs restating), principle-price-each-option (the ask offers the user a choice).
Done: only work that depends on the missing fact or decision waits, and the ask names that one fact or decision.
04 同仓库更多 Skills
xstate
WHEN React state changes in response to an external answer — async submit, in-flight or loading flags, retries, cancellation, polling, optimistic updates, stale responses — or to an interaction with an interruptible middle, such as a drag or a gesture; or WHEN building, reviewing, testing, or visualising XState 5 actors and @xstate/react integrations; NOT for a value one event sets completely, such as a text draft, a focus flag, or a plain open and closed toggle; models typed lifecycles and renders legal Mermaid stateDiagram-v2 charts.
web-design
WHEN refining UI layout, typography, color, or polish; NOT code implementation; provides concise principles for intentional, legible design.
tailwind
WHEN building design systems or component libraries with Tailwind CSS; covers design tokens, CVA patterns and dark mode.
refactoring
WHEN you need a plan to refactor, restructure, or clean up working code and the test result is known, either green or a recorded failing set; NOT for new feature delivery or any behavior change; reversible-baseline safety with prioritized improvements.
react
WHEN building or changing React components, pages, hooks, effects, or apps, including edits to existing components; NOT for test code (react-testing) or styling (css, tailwind); enforces scalable architecture, state management, API layer, performance patterns.
react-testing
WHEN testing React components/hooks/context with React Testing Library; NOT e2e; covers renderHook, providers, forms, and anti-patterns.