principle-fix-the-bar-first
WHEN comparing, racing, iterating on or reviewing candidates, existing or new; NOT for a gate that has already failed or for choosing which checks to run; records the selection criteria before evaluation and holds them after results.
- License 许可
- MIT
- 所属仓库
- mintuz/skills
- 最近更新
- 2026-11-13
- Stars
- ★ 35
- Forks
- 7
01 前言 Front Matter
- name
- principle-fix-the-bar-first
- description
- WHEN comparing, racing, iterating on or reviewing candidates, existing or new; NOT for a gate that has already failed or for choosing which checks to run; records the selection criteria before evaluation and holds them after results.
03 SKILL.md 正文
Fix the bar first
Decide how candidates will be judged before you see how any of them perform.
- Before generating, comparing, racing, iterating on or reviewing candidates, record the bar: a few concrete, gradeable criteria for success on this task, any thresholds, and the selection rule (first pass, rank all or best-of).
- Derive the criteria from the request, requirements or a supplied reference, never from a candidate. A draft, diff or proposal cannot define the bar it is judged against: when no independent bar exists, withhold the verdict and ask for one.
- Do not change criteria, weights, thresholds or the selection rule after seeing results. A preference that appears after results is a candidate for a future bar, recorded before the next evaluation runs, not a reason to re-score finished ones.
- When results were seen before any bar existed, ground the bar in sources written independently of the results and state that limitation in the verdict.
Distinct from: principle-never-weaken-a-check (an existing gate fails), principle-judge-with-fresh-eyes (who gives the verdict), principle-exhaust-the-design-space (whether to generate alternatives), principle-define-done (a completion criterion for one deliverable).
Done: criteria were recorded before evaluation began and were not altered after results.
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
USE WHEN writing, fixing or reviewing styling in a project that uses Tailwind CSS, even a one-class change or a request that does not name Tailwind: colours, focus rings, spacing, class names chosen by a prop, map or CVA variants, theme tokens and dark mode in the Tailwind stylesheet or tailwind.config, setup or upgrades (if unsure whether the project uses Tailwind, check package.json or the main stylesheet first); NOT WHEN writing plain CSS or Sass in a project without Tailwind; produces class names Tailwind can find, syntax for the installed major version, visible focus indicators, and no unrequested dependency or invented brand value.
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
USE WHEN changing the logic, data, props, state, Effects or rendered text of a React component, hook or page, even a one-line change; NOT WHEN the request is styling only (class names, Tailwind, CSS, dark mode, spacing, shadows) or tests only, or when it models submit, in-flight, loading, retry or failure states, even for a named React form (xstate covers that, including its React wiring); applies React 19 composition, state, Effect, structure, API and performance rules with only the project's installed libraries.
react-testing
USE WHEN writing, fixing or reviewing a React Testing Library test for a component, hook or context provider, even one small test, or when asked for an end-to-end journey inside a Vitest or React Testing Library suite; NOT WHEN changing the component itself (react), testing XState actors or @xstate/react (xstate), or writing a Playwright or Cypress test; covers renderHook, providers, async results, forms and false-pass anti-patterns, and declines end-to-end journeys with the testable slices.