daisyui: Instructions file for GitHub Copilot

.github/instructions/code_generation.instructions.md

daisyui code_generation.instructions.md is an instructions file for GitHub Copilot from saadeghi/daisyui. It costs 755 tokens per session, scanned C, original, MIT.

Code-writing rules for the daisyUI project, including checking official documentation and existing examples before changing code.

In plain words
What is it for?
Use them when generating code, fixing a specific issue, researching library usage, or refactoring while preserving existing behavior.
Why use it?
They reduce syntax errors, guessed APIs, unrelated edits, and accidental behavior changes.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is saadeghi/daisyui's own configuration. It tells GitHub Copilot how to work on daisyui 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 daisyui configures →

About the project

daisyUI is a library of ready-made interface components built for Tailwind CSS, a utility-based system for styling web pages. It helps web developers assemble consistent buttons, forms, navigation, and other UI elements. The catalogue entries provide add-ons for working with this component library.

saadeghi/daisyui · 42,302 stars · on GitHub · daisyui.com

Reuse

Borrowing it

Nothing to install: this file belongs to saadeghi/daisyui. 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/saadeghi/daisyui/master/.github/instructions/code_generation.instructions.md
Clone the repo
git clone --depth 1 https://github.com/saadeghi/daisyui

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 daisyui code_generation.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/saadeghi/daisyui/code_generation.svg)](https://agentmods.dev/instructions/saadeghi/daisyui/code_generation)
Your own site
<a href="https://agentmods.dev/instructions/saadeghi/daisyui/code_generation"><img src="https://agentmods.dev/badge/instructions/saadeghi/daisyui/code_generation.svg" alt="Measured on agentmods" height="20"></a>
Per session 755 This file is loaded in full into every session.
When invoked 755 The same file — it is already loaded in full.
Security scan C 1 finding. 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.00755 $0.00755
Opus 5 $0.00378 $0.00378
Sonnet 5 $0.00151 $0.00151
Haiku 4.5 $0.00076 $0.00076

Measured 7d ago against content hash af9146071c38, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade C, and why

daisyui code_generation.instructions.md scanned grade C with 1 finding 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 7d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- Never run dangerous commands like rm -rf, etc before asking
.github/instructions/code_generation.instructions.md · 74 lines

How it starts

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

Code Generation Rules

General rules

  • Never ever break the code syntax
  • If you are asked to write code, only write the code, do not add any explanations unless necessary
  • do not make up answers. For code, always search the docs and write code based on that
  • If you're not sure about the syntax Use Context7 MCP server

Finding information

  • Use Context7 MCP server to find information about packages, libraries, and languages. Context7 MCP server provides up-to-date and accurate information
  • Search official documentation if needed
  • You can search into related files to find patterns and examples

Writing code

  • Do not guess, do not hallucinate, write code based on the information and facts you have, if you don't have enough information, ask for more information
  • Be careful about the syntax, always double check it
  • If you're asked to fix a specific issue, only fix that issue, do not change anything else unless necessary
  • Do not randomly change indentation, formatting, or style of existing code unless asked
  • If you're asked to refactor code, make sure to keep the same functionality and behavior
  • Latest features of the languages and libraries are preferred

Code style

  • Use latest version of packages, languages, and libraries
  • Always write small, pure functions that do one thing only. avoid side effects, avoid large functions if possible
  • Always use best practices and latest standards
  • Prioritize performance security, clean code, readability and accessibility
  • Use early returns to reduce nesting

Security

  • Never ever delete files before asking
  • Never run dangerous commands like rm -rf, etc before asking
  • Do not include any sensitive information such as API keys, passwords, or personal data in the code
  • If you're adding console logs for debugging, make sure to remove them after you're done

HTML

  • When writing HTML, ensure semantic tags are used appropriately
  • Ensure proper indentation and formatting for readability
  • Prioritize accessibility by using ARIA roles and properties where necessary

Read the full file on GitHub · 74 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. 7d ago First seen · 74 lines · 755 tokens per session scan C af9146071c38

Subscribe to this mod's changes

daisyui code_generation.instructions.md is an instructions file published in the GitHub repository saadeghi/daisyui (42,302 stars, last pushed 3d ago), licensed MIT. It adds 755 tokens to every session, about $0.0038 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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

next.js AGENTS.md

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

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

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

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

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,469 tokens

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