lovable-boilerplate: Instructions file for GitHub Copilot

.github/instructions/components.instructions.md

lovable-boilerplate components.instructions.md is an instructions file for GitHub Copilot from chihebnabil/lovable-boilerplate. It costs 391 tokens per session, scanned A, original, MIT.

Coding rules for organizing React interface components in a Lovable boilerplate project. React components are reusable pieces of an application's user interface.

In plain words
What is it for?
They specify where UI, shared, and feature components belong, require wrappers instead of direct edits to shadcn/ui components, and set reuse, documentation, composition, and size guidelines.
Why use it?
They prevent shared interface pieces from being changed inconsistently or becoming large, difficult-to-maintain components.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

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

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/chihebnabil/lovable-boilerplate/main/.github/instructions/components.instructions.md
Clone the repo
git clone --depth 1 https://github.com/chihebnabil/lovable-boilerplate

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 lovable-boilerplate components.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/components/github.svg)](https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/components)
Your own site
<a href="https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/components"><img src="https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/components/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 lovable-boilerplate components.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/components"><img src="https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/components.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 391 This file is loaded in full into every session.
When invoked 391 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.00391 $0.00391
Opus 5.5 $0.00156 $0.00156
Sonnet 5.5 $0.00078 $0.00078
Haiku 4.5 $0.00039 $0.00039

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

Security

Grade A, and why

lovable-boilerplate components.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.

.github/instructions/components.instructions.md · 57 lines

What it actually says

Component-Specific Guidelines

COMPONENT ARCHITECTURE RULES

UI Components (src/components/ui/)

  • READ-ONLY: Never modify shadcn/ui components directly
  • EXTEND: Create wrapper components in src/components/common/
  • COMPOSE: Build complex UI by combining multiple ui components

Common Components (src/components/common/)

  • REUSABLE: Components used across multiple features
  • GENERIC: Should accept flexible props for different use cases
  • DOCUMENTED: Include clear prop interfaces and examples

Feature Components (src/components/features/)

  • SPECIFIC: Components tied to particular business features
  • COMPOSED: Build from smaller ui and common components
  • SINGLE PURPOSE: One feature concern per component

Component Size Limits

// GOOD: Focused, single-purpose component (20-80 lines)
const UserCard = ({ user, onEdit }: UserCardProps) => (
  <Card className="p-4">
    <Avatar src={user.avatar} />
    <div>
      <h3>{user.name}</h3>
      <p>{user.email}</p>
      <Button onClick={() => onEdit(user.id)}>Edit</Button>
    </div>
  </Card>
)

// BAD: Monolithic component over 100 lines
const UserManagement = () => {
  // 200+ lines mixing multiple concerns
}

Component Composition Patterns

// PERFECT: Composition over monoliths
const DashboardPage = () => (
  <PageLayout>
    <DashboardHeader />
    <DashboardMetrics />
    <DashboardCharts />
    <DashboardActivity />
  </PageLayout>
)

// Each sub-component is 20-80 lines and focused
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. 1mo ago First seen · 57 lines · 391 tokens per session scan A fac308c818ed

Subscribe to this mod's changes

lovable-boilerplate components.instructions.md is an instructions file published in the GitHub repository chihebnabil/lovable-boilerplate (65 stars, last pushed today), licensed MIT. It adds 391 tokens to every session, about $0.0016 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.

Related

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).

microsoft/vscode · 9,715 tokens

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,581 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens