tekhne / biome-complete
AGENTS.md10 starsChanged 39 days agoMITView on GitHub
Complete Biome toolchain guidance covering configuration, linting rules, formatting, and migration from ESLint/Prettier. Configuration (config-): - references/config-biome-json.md - biome.json structure and schema - references/config-vcs.md - VCS integration and ignored files - references/config-project.md - Project organization and extends Linting Rules (linting-): - references/linting-rule-categories.md - Rule groups (correctness, style, etc.) - references/linting-severity.md - Error, warning, info severity levels - references/linting-ignoring.md - Disabling rules inline and in config - references/linting-recommended.md - Recommended rule sets Formatting (formatter-): - references/formatter-options.md - Indentation, quotes, line width…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository81 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/development/bun-development/AGENTS.mdAGENTS.md
- skills/development/commanderjs/AGENTS.mdAGENTS.md
- skills/documentation/markdown-authoring/AGENTS.mdAGENTS.md
- skills/package-mgmt/mise-complete/AGENTS.mdAGENTS.md
- skills/testing/bdd-testing/AGENTS.mdAGENTS.md
- agents-mdSkill
- cache-auditSkill
- context-radar-auditSkill
- create-contextSkill
- guided-interviewSkill
- handover-document-creatorSkill
- load-contextSkill
- pick-modelSkill
- pinSkill
- professional-honestySkill
- rules-managementSkill
- save-contextSkill
- session-reflectionSkill
- socratic-methodSkill
- vault-captureSkill
- vault-consolidateSkill
- vault-fetchSkill
- vault-searchSkill
- bird-fortune-political-satireSkill
- brooker-esque-media-satireSkill
- clarke-dawe-esqueSkill
- comedy-style-skill-generatorSkill
- cunk-esque-mockumentarySkill
- gervais-esque-cringe-satireSkill
- monty-python-esqueSkill
- pryor-esque-confessional-standupSkill
- rock-esque-observational-standupSkill
- biome-completeSkill
- bun-developmentSkill
- commanderjsSkill
- conventional-commitsSkill
- humanizerSkill
- journal-entry-importSkill
- markdown-authoringSkill
- mermaid-diagramsSkill
- plain-englishSkill
- professional-communicationSkill
- sop-structureSkill
- logql-generatorSkill
- mise-completeSkill
- context-indexSkill
- create-context-fileSkill
- follow-upSkill
- goal-trackerSkill
- nasa-pm-lessonsSkill
- plan-createSkill
- plan-executeSkill
- plan-reviewSkill
- risk-registerSkill
- tech-debtSkill
- tech-evaluationSkill
- blast-radiusSkill
- bridgeSkill
- challengeSkill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 18
Read SKILL.md to understand when to use Biome
- Distinctive: line 21
Start with config, then linting, then formatting
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
biome-complete
Overview
Complete Biome toolchain guidance covering configuration, linting rules, formatting, and migration from ESLint/Prettier.
Structure
biome-complete/
SKILL.md # Main navigation hub
AGENTS.md # This file - complete reference guide
references/ # Detailed reference files by categoryUsage
- Read
SKILL.mdto understand when to use Biome - Navigate to categories based on your task
- Load reference files on-demand
- Start with config, then linting, then formatting
Reference Categories
| Priority | Category | Impact | Prefix |
| 1 | Configuration | CRITICAL | config- |
| 2 | Linting Rules | HIGH | linting- |
| 3 | Formatting | HIGH | formatter- |
| 4 | Migration | MEDIUM | migration- |
Available References
Configuration (config-):
references/config-biome-json.md- biome.json structure and schemareferences/config-vcs.md- VCS integration and ignored filesreferences/config-project.md- Project organization and extends
Linting Rules (linting-):
references/linting-rule-categories.md- Rule groups (correctness, style, etc.)references/linting-severity.md- Error, warning, info severity levelsreferences/linting-ignoring.md- Disabling rules inline and in configreferences/linting-recommended.md- Recommended rule sets
Formatting (formatter-):
references/formatter-options.md- Indentation, quotes, line widthreferences/formatter-line-endings.md- CRLF vs LF configurationreferences/formatter-trailing-commas.md- Trailing comma optionsreferences/formatter-ignore.md- Ignoring files from formatting
Migration (migration-):
references/migration-from-eslint.md- ESLint to Biome migrationreferences/migration-from-prettier.md- Prettier to Biome migrationreferences/migration-gradual.md- Gradual adoption strategiesreferences/migration-config-mapping.md- Rule mapping reference
Consolidates 2 original skills: biome-configuration, biome-linting
15 reference files across 4 categories
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.

