design-system: Instructions file for GitHub Copilot

.github/instructions/file-organization.instructions.md

design-system file-organization.instructions.md is an instructions file for GitHub Copilot from iress/design-system. It costs 1,068 tokens per session, scanned A, original, Apache-2.0.

Coding instructions for arranging TypeScript implementation files and their test files in the Iress Design System. TypeScript is a programming language commonly used for JavaScript applications.

In plain words
What is it for?
Use them when writing or reviewing .ts, .tsx, .test.ts, and .test.tsx files in the design-system repository.
Why use it?
They make related code easier to scan and maintain by keeping imports, types, constants, helper functions, and public functions in a predictable order.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is iress/design-system's own configuration. It tells GitHub Copilot how to work on design-system itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything design-system configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { internalUtil } from '../utils';.

Reuse

Borrowing it

Nothing to install: this file belongs to iress/design-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/iress/design-system/main/.github/instructions/file-organization.instructions.md
Clone the repo
git clone --depth 1 https://github.com/iress/design-system

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-system file-organization.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/iress/design-system/file-organization/github.svg)](https://agentmods.dev/instructions/iress/design-system/file-organization)
Your own site
<a href="https://agentmods.dev/instructions/iress/design-system/file-organization"><img src="https://agentmods.dev/badge/instructions/iress/design-system/file-organization/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-system file-organization.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/iress/design-system/file-organization"><img src="https://agentmods.dev/badge/instructions/iress/design-system/file-organization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,068 This file is loaded in full into every session.
When invoked 1,068 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01068 $0.01068
Opus 5.5 $0.00427 $0.00427
Sonnet 5.5 $0.00214 $0.00214
Haiku 4.5 $0.00107 $0.00107

Measured 2mo ago against content hash c69e6cb8374c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-system file-organization.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 2mo 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/file-organization.instructions.md · 159 lines

How it starts

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

File Organization Principles

Implementation Files (.ts/.tsx)

Organize implementation files in this order for better readability and maintainability:

// 1. Imports (external dependencies first, then internal)
import { externalLib } from 'external-package';
import { internalUtil } from '../utils';

// 2. Types and Interfaces (public API)
export interface PublicData {
  // Public types that consumers need
}

type InternalType = {
  // Internal types for implementation
};

// 3. Constants and Configuration
const CONFIG_VALUE = 'constant';
const REGEX_PATTERN = /pattern/;

// 4. Helper Functions (private implementation details)
const helperFunction = () => {
  // Internal utility functions
};

// 5. Main Exported Functions (primary public API)
export const mainFunction = () => {
  // Primary public functions
};

Key Principles:

  • Public types first - What consumers need to import/use
  • Constants grouped together - Configuration and static values
  • Helper functions grouped together - Private implementation details
  • Main exports last - Primary public API
  • Separate concerns - Clear boundaries between public and private code

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

Organize test files in this order for clarity and proper setup:

// 1. Imports
import { describe, it, expect, vi } from 'vitest';
import { functionToTest, type TypeToTest } from './moduleToTest';

// 2. Mocks (global setup that affects module loading)
vi.mock('external-dependency', () => ({
  // Mock implementation
}));

// 3. Constants and Test Data
const TEST_DATA = {
  // Static test data
};

const EXPECTED_VALUES = ['value1', 'value2'];

// 4. Helper Functions (test utilities)
const createTestInstance = () => {
  // Test setup helpers
};

const validateStructure = (item: TypeToTest) => {
  // Validation helpers
};

// 5. Test Suites (actual test execution)
describe('functionToTest', () => {
  // Test cases
});

Key Principles:

  • Mocks immediately after imports - They're hoisted anyway and affect module loading
  • Constants before helpers - Static configuration before dynamic utilities
  • Helper functions before tests - Setup utilities before test execution
  • Test suites last - Actual test execution comes after all setup

Read the full file on GitHub · 159 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. 2mo ago First seen · 159 lines · 1,068 tokens per session scan A c69e6cb8374c

Subscribe to this mod's changes

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

Related

design-system file-organization.instructions.md compared with instructions from other repositories

design-system file-organization.instructions.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
design-system file-organization.instructions.mdiress/design-systemInstructions file12d agoApache-2.0A1,068GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode