Borrowing it
Nothing to install: this file belongs to chihebnabil/lovable-boilerplate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chihebnabil/lovable-boilerplate/main/.github/instructions/design.instructions.mdgit clone --depth 1 https://github.com/chihebnabil/lovable-boilerplateWrote 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.
[](https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/design)<a href="https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/design"><img src="https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/design/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.
<a href="https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/design"><img src="https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.04058 | $0.04058 |
| Opus 5.5 | $0.01623 | $0.01623 |
| Sonnet 5.5 | $0.00812 | $0.00812 |
| Haiku 4.5 | $0.00406 | $0.00406 |
Grade A, and why
lovable-boilerplate design.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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System Guidelines
CRITICAL DESIGN RULES
NEVER CREATE:
- Poor accessibility - must maintain 4.5:1 contrast ratio minimum
- Generic designs - always adapt to target industry/audience
- Template-like layouts - create unique, custom-crafted interfaces
- Static interfaces - include sophisticated micro-interactions
- Default grays (slate-400, gray-500) - use rich, intentional color palettes
ALWAYS CREATE:
- Industry-appropriate design - adapt colors/typography to target audience
- Premium visual hierarchy - sophisticated use of scale, contrast, spacing
- Accessible interfaces - WCAG 2.1 AA compliant (4.5:1 text contrast)
- Mobile-first responsive - progressive enhancement approach
- Purposeful animations - enhance usability, not just decoration
Core Design Philosophy
Every interface must feel like it was crafted by a top-tier design agency.
- Emotional Impact First: Ask "Does this make users stop and say 'wow'?"
- Sophisticated Hierarchy: Use contrast, scale, and spacing strategically
- Purposeful Motion: Every animation should enhance usability
- Breathing Room: Generous whitespace creates luxury feel
- Cohesive Visual Story: Design choices should work together harmoniously
- Unique Visual Identity: Design should feel custom-crafted, never template-like
- Industry-Appropriate Design: Visual language should match the target audience and use case
- Color Psychology: Use colors intentionally to evoke the right emotions and associations
Visual Quality Standards
NEVER CREATE:
- Generic card grids with default shadows
- Plain white backgrounds with black text
- Basic hover states (simple color changes)
- Template-like layouts
- Uniform spacing everywhere
- Overuse of default Tailwind grays without intention
- Static, lifeless interfaces
- Color choices without consideration for brand or industry context
ALWAYS CREATE:
- Dynamic, engaging compositions with visual flow
- Rich, intentional color palettes that serve the design purpose
- Sophisticated micro-interactions
- Asymmetrical layouts that guide the eye
- Varied spacing that creates rhythm
- High contrast, accessible text combinations
- Interactive, responsive designs with personality
- Color schemes that enhance the user experience and brand message
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.
- 1mo ago First seen · 384 lines · 4,058 tokens per session scan A a20358d7147a
lovable-boilerplate design.instructions.md is an instructions file published in the GitHub repository chihebnabil/lovable-boilerplate (65 stars, last pushed today), licensed MIT. It adds 4,058 tokens to every session, about $0.0162 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-30.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.