canopy
CLAUDE.md5 starsChanged 7 months agoApache-2.0View on GitHub
This project follows the BossUI standard: refined minimalism with subtle depth. Clean surfaces, purposeful shadows, smooth transitions. Not sterile, not flashy. Use CSS variables and Tailwind design tokens exclusively: NEVER use bg-white, bg-gray-100, text-gray-500, border-gray-200, or any other hardcoded color. Always use tokens that respect dark/light mode. Exception: the SVG canvas uses raw hex values for geometry (stroke colors, fill) because SVG doesn't support Tailwind classes — this is acceptable. Always include dark mode variants: Glassmorphism for overlays: bg-card/80 backdrop-blur-sm…
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
14 rules. About 0 are common, 11 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Use CSS variables and Tailwind design tokens exclusively:
- Very specific: line 39
NEVER: use bg-white, bg-gray-100, text-gray-500, border-gray-200, or any other hardcoded color.
- Distinctive: line 45
Always include dark mode variants:
- Distinctive: line 78
Never jarring — smooth width/opacity changes only
- Distinctive: line 105
Do NOT auto-commit — only commit when explicitly asked
- Distinctive: line 106
Do NOT open or refresh the browser
- Very specific: line 107
Always use cn() for conditional class merging
- Very specific: line 108
Use shrink-0 on icons to prevent squishing
- Distinctive: line 110
No emojis in UI unless explicitly requested
- Distinctive: line 113
No hardcoded colors anywhere in TSX/CSS (SVG geometry is the only exception)
- Distinctive: line 114
No inconsistent border radii within the same context
- Distinctive: line 115
No shadows without purpose
- Distinctive: line 116
No new patterns when existing ones apply
- Distinctive: line 117
No mixing button/input styles within the same view
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
git-visualizer — Project Rules
Stack
- Next.js 16 App Router, TypeScript, Tailwind CSS
- SVG-based branch map canvas (custom, no React Flow)
- GitHub REST API v3 via server components + API routes
GITHUB_PATenv var for authentication
Key Files
components/BranchMap.tsx— main SVG canvas, all layout constants at toplib/github.ts— all GitHub API wrapperstypes/index.ts— shared TypeScript typesapp/repo/[owner]/[repo]/page.tsx— server component, initial data fetchapp/api/commits/route.ts— paginated commit history API routeapp/globals.css— global styles including custom scrollbar
Design System — BossUI Principles
This project follows the BossUI standard: refined minimalism with subtle depth. Clean surfaces, purposeful shadows, smooth transitions. Not sterile, not flashy.
Color Tokens — NEVER hardcode colors
Use CSS variables and Tailwind design tokens exclusively:
bg-background /* base app background */
bg-card /* elevated surfaces, panels */
bg-muted /* subtle differentiation, hover states */
bg-muted/30 /* very subtle backgrounds */
bg-primary/10 /* selection/active states */
text-foreground /* primary text */
text-muted-foreground /* secondary, labels, timestamps */
border-border /* standard borders */
border-border/50 /* subtle borders */
hover:bg-accent
hover:bg-mutedNEVER use bg-white, bg-gray-100, text-gray-500, border-gray-200, or any other hardcoded color. Always use tokens that respect dark/light mode.
Exception: the SVG canvas uses raw hex values for geometry (stroke colors, fill) because SVG doesn't support Tailwind classes — this is acceptable.
Status Colors
Always include dark mode variants:
/* Success */ bg-green-50 dark:bg-green-900/20 text-green-600 dark:text-green-400
/* Warning */ bg-amber-50 dark:bg-amber-900/20 text-amber-600 dark:text-amber-400
/* Error */ bg-red-50 dark:bg-red-900/20 text-red-600 dark:text-red-400
/* Info */ bg-blue-50 dark:bg-blue-900/20 text-blue-600 dark:text-blue-400Typography
- Page titles:
text-lg font-semibold - Section headers:
text-sm font-medium - Body:
text-sm - Metadata/labels:
text-xs - Section labels:
text-[10px] uppercase tracking-wide text-muted-foreground font-medium
Spacing & Shape
- Page padding:
max-w-7xl mx-auto px-6 pt-6 - Card padding:
p-4orpx-4 py-2.5for compact items - Gaps:
gap-4for grids,gap-2for tight lists - Border radius:
rounded-2xlfor major containers,rounded-xlfor cards,rounded-lgfor buttons/inputs
Shadows — use sparingly
shadow-sm /* subtle elevation — inputs, floating buttons */
shadow-inner /* inset depth — empty states */
shadow-lg /* modals, dropdowns */Glassmorphism for overlays: bg-card/80 backdrop-blur-sm rounded-2xl border shadow-sm
Motion
- Sidebar/panel collapse:
transition-all duration-300 ease-in-out - Hover states:
transition-colors - Never jarring — smooth width/opacity changes only
Component Patterns
Cards/tiles:
<div className="rounded-xl border p-4 bg-card hover:shadow-sm transition-colors cursor-pointer">Empty states:
<div className="h-full bg-muted/30 shadow-inner rounded-xl flex items-center justify-center">
<div className="text-center">
<p className="text-sm text-muted-foreground">Message here</p>
</div>
</div>Nav items:
<div className={cn(
'flex items-center gap-3 px-3 py-2.5 rounded-lg transition-colors',
isActive ? 'bg-primary/10 text-primary' : 'text-muted-foreground hover:bg-accent'
)}>Workflow Rules
- Do NOT auto-commit — only commit when explicitly asked
- Do NOT open or refresh the browser
- Always use
cn()for conditional class merging - Use
shrink-0on icons to prevent squishing - Include hover/active states on all interactive elements
- No emojis in UI unless explicitly requested
Anti-Patterns
- No hardcoded colors anywhere in TSX/CSS (SVG geometry is the only exception)
- No inconsistent border radii within the same context
- No shadows without purpose
- No new patterns when existing ones apply
- No mixing button/input styles within the same view
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

