What is design-system global.instructions.md?

Project instructions for testing packages in the Iress Design System, a Yarn monorepo containing related components, tokens, and tools. They list commands for all tests, affected packages, individual packages, and individual test files.

Running the full test suite, testing only changed packages, testing a named workspace, running one test file, and producing coverage reports.

They make it clear which test command to use and remind agents to wait for tests to finish. This avoids confusing normal startup delay with failure and avoids accidentally leaving development processes running.

design-system global.instructions.md — Instructions file by iress

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/iress/design-system/global

Clone the repo

git clone --depth 1 https://github.com/iress/design-system

Made for: GitHub Copilot.

Per session 853 This file is loaded in full into every session.

When invoked 853 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.

Model	Per session	Once invoked
Fable 5	$0.00853	$0.00853
Opus 5	$0.00426	$0.00426
Sonnet 5	$0.00171	$0.00171
Haiku 4.5	$0.00085	$0.00085

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

Security

Grade A, and why

design-system global.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 2d ago.

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/global.instructions.md · 122 lines

How it starts

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

Package dependencies:

@iress-oss/ids-components depends on:
- @iress-oss/ids-tokens

Test Commands

Run all tests

yarn test          # All packages
yarn test:affected # Affected packages only

Run tests for specific packages

yarn test:components
yarn test:storybook-addon
yarn test:tokens

Run single test files

# Most common approach
yarn test:components Button.test.tsx

# Direct workspace commands (recommended)
yarn workspace @iress-oss/ids-components run test:coverage Button.test.tsx

Important for AI Assistants

When running tests via run_in_terminal:

Always use isBackground=false for test commands
WAIT PATIENTLY for tests to start up and complete (can take 30 seconds or more)
Do not cancel or make additional tool calls until you see completion messages
Test startup has overhead - the delay is normal, not a failure
Look for final completion messages before proceeding with other actions

Development modes

yarn test:coverage         # Run tests with coverage reporting
yarn workspace @iress-oss/ids-components run test:coverage Button.test.tsx --watch

# Verbose output
yarn vitest run --reporter=verbose

Important: Ensure your vitest.config.ts (or equivalent Vitest config file) includes reporters: ['verbose'] in the configuration. This is required for compatibility with yarn workspace test commands and to ensure proper output formatting.

Note: Test files must be in the project's src/ directory (e.g., packages/components/src/Button.test.tsx)

File Organization

For detailed file organization principles covering implementation and test files, see file-organization.instructions.md.

Quick Reference

Implementation Files (.ts/.tsx):

Imports → Types/Interfaces → Constants → Helper Functions → Main Exports

Test Files (.test.ts/.test.tsx):

Imports → Mocks → Constants/Test Data → Helper Functions → Test Suites

Read the full file on GitHub · 122 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.

2d ago First seen · 122 lines · 853 tokens per session scan A e36348d7a325

Subscribe to this mod's changes

design-system global.instructions.md is an instructions file published in the GitHub repository iress/design-system (1 stars, last pushed 7d ago), licensed Apache-2.0. It adds 853 tokens to every session, about $0.0043 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-31.

Testing

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

design-system global.instructions.md