What is lovable-boilerplate development.instructions.md?

A set of project instructions for building and shipping a React website with Vite, TypeScript, and related tools. It defines the commands, coding structure, and checks expected before release.

Use it to run the development server, build the site, check code quality, preview the production build, and review accessibility and responsive behavior before shipping.

It gives an agent consistent project rules and helps prevent common release problems such as lint errors, broken mobile layouts, poor color contrast, and browser warnings.

How chihebnabil/lovable-boilerplate configures GitHub Copilot

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/development.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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/development/github.svg)](https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/development)

Your own site

<a href="https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/development"><img src="https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/development/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/development"><img src="https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,060 This file is loaded in full into every session.

When invoked 2,060 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.

Model	Per session	Once invoked
Fable 5.1	$0.02060	$0.02060
Opus 5.5	$0.00824	$0.00824
Sonnet 5.5	$0.00412	$0.00412
Haiku 4.5	$0.00206	$0.00206

Measured 1mo ago against content hash c937c00e9b86, 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 development.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/development.instructions.md · 265 lines

How it starts

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

Development Workflow & Commands

ESSENTIAL COMMANDS

npm run dev          # Start development server (port 8080)
npm run build        # Production build
npm run lint         # Run ESLint - MUST pass before shipping
npm run preview      # Preview production build locally
npm install          # Install dependencies

CRITICAL WORKFLOW RULES

BEFORE SHIPPING:

Run npm run lint and fix all issues
Test responsive design on mobile/desktop
Verify accessibility contrast ratios
Ensure no console errors in browser

NEVER SHIP:

Code with ESLint errors
Untested responsive layouts
Poor accessibility (contrast violations)
Console errors or warnings

Framework Stack

React 18.3.1 with TypeScript for UI
Vite 5.4.1 as build tool with SWC for fast compilation
shadcn/ui component library built on Radix UI primitives
Tailwind CSS 3.4.11 for styling with custom design system
React Router DOM v6 for client-side routing
TanStack Query for server state management
Supabase 2.80.0 for backend, authentication, and database
React Hook Form + Zod for form handling and validation

Development Commands

Core Development

npm run dev - Start development server on port 8080
npm run build - Create production build
npm run build:dev - Create development build
npm run lint - Run ESLint linter
npm run preview - Preview production build locally

Package Management

npm install - Install dependencies (or use bun install for faster installs)

Key Architecture Patterns

Import Aliases (configured in vite.config.ts)

@/ maps to ./src/
@/components for components
@/lib for utilities
@/hooks for custom hooks
@/integrations/supabase for Supabase client and types

Routing Structure

Routes are defined in src/App.tsx. Add new routes above the catch-all * route:

<Routes>
  <Route path="/" element={<Index />} />
  {/* ADD NEW ROUTES HERE */}
  <Route path="*" element={<NotFound />} />
</Routes>

Read the full file on GitHub · 265 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.

1mo ago First seen · 265 lines · 2,060 tokens per session scan A c937c00e9b86

Subscribe to this mod's changes

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

Frontend Languages React TypeScript boilerplate copilot copilot-enabled lovable lovable-dev

plan-forge frontend.instructions.md

TypeScript frontend patterns — React, component architecture, state management.

srnichols/plan-forge · 1,485 tokens

create-trimble-app typescript.instructions.md

Instructions for julianoczkowski/create-trimble-app, covering typescript patterns for modus components, event type casting, common event types, component ref types and modal ref pattern.

julianoczkowski/create-trimble-app · 583 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 · 9,715 tokens

lovable-boilerplate: Instructions file for GitHub Copilot