design-system component-creation.instructions.md

Coding instructions for creating new version 6 components in the Iress Design System, a shared library of interface components. They define the required files, implementation structure, styles, examples, tests, and documentation.

In plain words
What is it for?
Use them when adding a new component, including its TypeScript React code, styling, Storybook examples, tests, exports, and documentation.
Why use it?
They give each component the same structure so it can be implemented, tested, demonstrated, and documented consistently.

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/iress/design-system/component-creation
Clone the repo
git clone --depth 1 https://github.com/iress/design-system

Made for: GitHub Copilot.

Per session 4,774 This file is loaded in full into every session.
When invoked 4,774 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.04774 $0.04774
Opus 5 $0.02387 $0.02387
Sonnet 5 $0.00955 $0.00955
Haiku 4.5 $0.00477 $0.00477

Measured yesterday against content hash 9c70f512f064, 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 component-creation.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/component-creation.instructions.md · 649 lines

How it starts

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

V6 Component Creation Guidelines

These guidelines ensure consistency and quality when creating new components in the design system.

File Structure Requirements

Each component must include exactly these files:

ComponentName/
├── index.ts                          # Exports
├── ComponentName.tsx                 # Main component
├── ComponentName.styles.ts           # Styling (CVA recipe)
├── ComponentName.stories.tsx         # Storybook stories
├── ComponentName.test.tsx            # Tests
└── ComponentName.docs.mdx            # Documentation
└── mocks/                            # (optional) Mock use cases for this component that cannot be represented in stories

Component Implementation (*.tsx)

Required Structure

import { propagateTestid } from '@helpers/utility/propagateTestid';
import { componentName } from './ComponentName.styles';
import { cx } from '@/styled-system/css';
import { styled } from '@/styled-system/jsx';
import { ReactNode, useMemo } from 'react';
import { IressStyledProps } from '@/types';
import { GlobalCSSClass } from '@/enums';

export interface IressComponentNameProps extends IressStyledProps {
  /**
   * Content of this component.
   */
  children?: ReactNode;

  /**
   * Additional props with detailed JSDoc comments.
   * Include default values, examples, and relationships to other props.
   */
  variant?: 'primary' | 'secondary';

  /**
   * Status of the component.
   * @default 'info'
   */
  status?: 'info' | 'success' | 'warning' | 'danger';
}

export const IressComponentName = ({
  children,
  className,
  variant,
  status = 'info',
  ...restProps
}: IressComponentNameProps) => {
  const classes = componentName({ variant, status });

  return (
    <styled.div
      className={cx(className, classes.root, GlobalCSSClass.ComponentName)}
      {...restProps}
    >
      {children}
    </styled.div>
  );
};

Key Requirements

  • Always use Iress prefix for component names (e.g., IressAlert, IressButton)
  • Extend existing props when appropriate (e.g., IressStyledProps, IressUnstyledProps, IressTextProps)
  • Include comprehensive JSDoc comments with defaults, examples, and relationships
  • Use cx() for className composition to merge custom and component classes
  • Add GlobalCSSClass enum for consistent global CSS class naming
  • Use propagateTestid() helper for nested testids when needed
  • Implement controlled/uncontrolled patterns with useControlledState hook when applicable
  • Do not import from @/main within the component file itself to ensure tree-shaking. Import from @/components/ComponentName instead.

Read the full file on GitHub · 649 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 · 649 lines · 4,774 tokens per session scan A 9c70f512f064

Subscribe to this mod's changes

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

Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

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

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens