ericrisco/rsc-harness / skills/flutter
flutter
VerifiedUse when building, structuring, testing or optimizing a Flutter app — feature-first layering, Riverpod 3 or Bloc, typed go_router, freezed models, a dio data layer, Material 3, jank hunting, widget/golden tests. Targets Flutter 3.44 / Dart 3.12. NOT React Native (that is `react-native`), NOT Compose Multiplatform (that is `compose-multiplatform`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.1 KB |
| evals/README.md | markdown | 2.3 KB |
| evals/cases.yaml | config | 5.6 KB |
| references/architecture-and-state.md | markdown | 16.4 KB |
| references/i18n-and-dependencies.md | markdown | 6.9 KB |
| references/performance.md | markdown | 10.2 KB |
| references/testing.md | markdown | 11.8 KB |
| references/ui-and-navigation.md | markdown | 12.3 KB |
| scripts/verify.shexecutable | script | 3.1 KB |
evals/README.md
View on GitHub# Eval harness — `flutter` skill
These evals are run by an **agent harness** (an LLM agent with the Skill tool), not a
pure shell script. `cases.yaml` is the fixture; this README is the run procedure. There
are three things to measure: **triggering** (should fire), **anti-triggering** (must not
fire), and **capability** (does the skill make the answer better).
## 1. Triggering accuracy
For each prompt in `should_trigger` and `should_not_trigger`:
1. Start a fresh agent session with **only the `flutter` skill** available in the catalog
(plus its named siblings present but not the subject — so routing is realistic).
2. Feed the prompt verbatim. Do **not** hint that a skill exists.
3. Observe whether the agent invokes the `flutter` skill.
4. Run **3–5 trials** per prompt (LLM routing is stochastic); record the fire rate.
Pass conditions:
- Every `should_trigger` prompt fires the skill in **≥ 90%** of trials.
- Every `should_not_trigger` prompt **does not** fire it in ≥ 90% of trials. For routes
with a named sibling, the agent should prefer that sibling (or correctly defer when
`route_to: none`).
A single near-miss leaking into the skill is a harder failure than a missed trigger —
investigate the description boundary before shipping.
## 2. Capability uplift (with vs without)
For each `capability` scenario:
1. **Without skill:** run the scenario in a clean session, no `flutter` skill loaded.
Capture the answer.
2. **With skill:** run the same prompt with the `flutter` skill loaded.
3. Grade both answers against the scenario's `must_include` checklist — one point per
bullet that is concretely present (not just gestured at).
4. Use 3 trials each side; average the coverage.
Pass conditions:
- **With** the skill: `must_include` coverage **≥ 80%**.
- The skill produces a **measurable uplift**: with-skill coverage should beat without-skill
by a clear margin (target **≥ +25 percentage points**). If a baseline model already
scores high without the skill, the scenario is too easy — tighten `must_include`.
## 3. Reporting
Record per prompt: fire rate, trials, pass/fail. Per scenario: with/without coverage and
delta. The harness passes overall when triggering ≥ 90% on both sets **and** every
capability scenario clears the 80% bar with positive uplift.
## Counts
- `should_trigger`: 7
- `should_not_trigger`: 6
- `capability`: 2
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |