lawn
CLAUDE.md690 starsChanged 5 months agoMITView on GitHub
Video review platform for creative teams. Built by Theo. Brutalist, typographic, minimal. The design should feel bold and direct—like a poster, not a dashboard. Prioritize clarity over decoration. Let typography and whitespace do the heavy lifting. This project uses Convex as its backend. When working on Convex code, always read convex/_generated/ai/guidelines.md first for important guidelines on how to correctly use Convex APIs and patterns. The file contains rules that override what you may have learned about Convex from training data.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- convex-create-componentSkill
- convex-migration-helperSkill
- convex-performance-auditSkill
- convex-quickstartSkill
- convex-setup-authSkill
- convexSkill
- convex-create-componentSkill
- convex-migration-helperSkill
- convex-performance-auditSkill
- convex-quickstartSkill
- convex-setup-authSkill
- convexSkill
The file
We split this CLAUDE.md into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Use size contrast dramatically—massive headlines with small supporting text
- Distinctive: line 50
Use bold typography to create hierarchy
- Distinctive: line 52
Keep interactions obvious and direct
- Distinctive: line 53
Use green sparingly as accent, not primary
- Distinctive: line 57
No gradients or shadows (except subtle where functional)
- Distinctive: line 58
No rounded corners on primary UI (square/sharp edges)
- Distinctive: line 59
No decorative icons—only functional ones
- Distinctive: line 60
Don't hide information behind hover states
- Very specific: line 66
When working on Convex code, always read convex/_generated/ai/guidelines.md first for important guidelines on how to correctly use Convex …
≈ “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
lawn
Video review platform for creative teams. Built by Theo.
Design Language
Philosophy
Brutalist, typographic, minimal. The design should feel bold and direct—like a poster, not a dashboard. Prioritize clarity over decoration. Let typography and whitespace do the heavy lifting.
Colors
- Background:
#f0f0e8(warm cream) - Text:
#1a1a1a(near-black) - Muted text:
#888888 - Primary accent:
#2d5a2d(deep forest green) - Accent hover:
#3a6a3a - Highlight:
#7cb87c(soft green for emphasis) - Borders:
#1a1a1a(strong) or#ccc(subtle) - Inverted sections:
#1a1a1abackground with#f0f0e8text
Typography
- Headings: Font-black (900 weight), tight tracking
- Body: Regular weight, clean and readable
- Monospace: For technical info, timestamps, stats
- Use size contrast dramatically—massive headlines with small supporting text
Borders & Spacing
- Strong 2px borders in
#1a1a1afor section dividers and cards - Generous padding (p-6 to p-8 typical)
- Clear visual hierarchy through spacing
Interactive Elements
- Buttons: Solid backgrounds with bold text, clear hover states
- Links: Underlines, not color-only differentiation
- Hover states: Background fills or color shifts, no subtle opacity changes
Component Patterns
- Cards: 2px black border, cream background, bold title
- Sections: Often alternate between cream and dark backgrounds
- Forms: Simple inputs with strong borders, no rounded corners or minimal
- Navigation: Minimal, text-based, appears on scroll when needed
Do's
- Use bold typography to create hierarchy
- Embrace whitespace
- Keep interactions obvious and direct
- Use green sparingly as accent, not primary
Don'ts
- No gradients or shadows (except subtle where functional)
- No rounded corners on primary UI (square/sharp edges)
- No decorative icons—only functional ones
- Don't hide information behind hover states
<!-- convex-ai-start -->This project uses Convex as its backend.
When working on Convex code, always read
convex/_generated/ai/guidelines.md first for important guidelines on
how to correctly use Convex APIs and patterns. The file contains rules that
override what you may have learned about Convex from training data.
Convex agent skills for common tasks can be installed by running
npx convex ai-files install.
<!-- convex-ai-end -->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.