wind tests.instructions.md

Testing instructions for the Wind Flutter project, including where tests belong, required setup, helper patterns, and lifecycle rules. Flutter is a framework for building apps with Dart.

In plain words
What is it for?
Use them when adding or reviewing parser and widget tests, matching test files to source files, clearing parser state, and wrapping widgets with the required theme.
Why use it?
They help keep tests organized and prevent false results caused by shared parser caches or incorrectly prepared widgets.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/fluttersdk/wind/tests
Clone the repo
git clone --depth 1 https://github.com/fluttersdk/wind

Made for: GitHub Copilot.

Per session 1,099 This file is loaded in full into every session.
When invoked 1,099 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01099 $0.01099
Opus 5 $0.00549 $0.00549
Sonnet 5 $0.00220 $0.00220
Haiku 4.5 $0.00110 $0.00110

Measured yesterday against content hash cf2218da7efd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

wind tests.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/tests.instructions.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test conventions (test/)

Layout mirror

test/ mirrors lib/src/ exactly. One production file → one test file:

  • lib/src/widgets/w_button.darttest/widgets/w_button_test.dart
  • lib/src/parser/parsers/padding_parser.darttest/parser/parsers/padding_parser_test.dart

For widgets with large surface area, sub-directory: test/widgets/w_div/spacing_test.dart, test/widgets/w_div/overflow_test.dart, etc. Mirror that under test/widgets/<name>/.

Required setUp

Parser tests + every widget test that pumps className-styled widgets:

setUp(() {
  WindParser.clearCache();
});

Skipping WindParser.clearCache() is the single biggest source of false-positive cross-test pollution. The parser cache persists between tests; a sibling test priming the cache makes the next test report PASS even when the production logic regressed.

Canonical helpers (duplicate per file, no shared extraction)

Widget tests define wrapWithTheme at the top:

Widget wrapWithTheme(Widget child) {
  return MaterialApp(
    home: WindTheme(
      data: WindThemeData(),
      child: Scaffold(body: child),
    ),
  );
}

Parser tests define createTestContext at the top with 7-8 named params:

WindContext createTestContext({
  bool isHovering = false,
  bool isFocused = false,
  bool isDisabled = false,
  String activeBreakpoint = 'md',
  Brightness brightness = Brightness.light,
  String platform = 'web',
  bool isMobile = false,
}) => WindContext(
      theme: testTheme,
      screenWidth: 400,
      screenHeight: 800,
      activeBreakpoint: activeBreakpoint,
      brightness: brightness,
      platform: platform,
      isMobile: isMobile,
      activeStates: {
        if (isHovering) 'hover',
        if (isFocused) 'focus',
        if (isDisabled) 'disabled',
      },
    );

Duplicate is intentional — keeps each file's helper trivially editable for local tweaks. Do not extract into test/test_utils.dart.

No mockito

Wind tests use NO mocking library. Fake via:

  • Constructor injection (WActionHandler(actions: {'foo': (args) => ...}, state: WDynamicState()))
  • Stub widgets that implement the contract
  • debugDefaultTargetPlatformOverride for Platform.is* paths (inside try/finally — reset is mandatory)

Read the full file on GitHub · 132 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 132 lines · 1,099 tokens per session scan A cf2218da7efd

Subscribe to this mod's changes

wind tests.instructions.md is an instructions file published in the GitHub repository fluttersdk/wind (33 stars, last pushed 2d ago), licensed MIT. It adds 1,099 tokens to every session, about $0.0055 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

mobile CLAUDE.md

Claude Code instructions for lichess-org/mobile, covering claude.md, project overview, development setup, initial setup and install dependencies.

lichess-org/mobile · 4,362 tokens

dart_agent_core AGENTS.md

Instructions for memex-lab/dart_agent_core, covering agents.md, common commands, transcript viewer cli (reads eval traces), two public libraries and architecture (big picture).

memex-lab/dart_agent_core · 1,450 tokens

sanad-agent AGENTS.md

Instructions for EastStarAI/sanad-agent, covering sanad agent repository contract, 1. documentation hierarchy, rules for ai agents and developers, 1.1. the strict separation pact and 1.2. the living project wiki & incremental documentation.

EastStarAI/sanad-agent · 3,115 tokens

terradart CLAUDE.md

Instructions for nozomi-koborinai/terradart: Use AGENTS.md as the shared project guide. Read CONTEXT.md for project vocabulary before design work.

nozomi-koborinai/terradart · 63 tokens

dart-sdk-skills AGENTS.md

Instructions for RandalSchwartz/dart-sdk-skills, covering ai agent developer handbook (agents.md), 🎯 repository purpose, 🔄 runbook 1: updating for new dart sdk releases, 🔄 runbook 2: updating for new flutter framework releases and 📏 quality & style guidelines.

RandalSchwartz/dart-sdk-skills · 736 tokens

dart-expert-skills copilot-instructions.md

Instructions for Poorgramer-Zack/dart-expert-skills, covering flutter skills repository - copilot instructions, repository overview, architecture, directory structure and skill structure.

Poorgramer-Zack/dart-expert-skills · 2,008 tokens