intlayer
CLAUDE.md863 starsChanged 13 days agoApache-2.0View on GitHub
Doc are multilingual. If not explicitly mentioned, never use AI generation for translations using the scripts translate or review + MODE = 'apply'. Those will consume extra token no included in the plan. But you can use review + MODE = 'synthesis' | 'synthesis' to validate the doc consistency. If not mentioned, you should iterate doc by doc and translate manually each doc for each locale without using script.
In this repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/commit-message-guidelines.mdCursor rule
- intlayer-angularSkill
- intlayer-astroSkill
- intlayer-backendSkill
- intlayer-bundle-optimizationSkill
- intlayer-cliSkill
- intlayer-compatSkill
- intlayer-compilerSkill
- intlayer-configSkill
- intlayer-contentSkill
- intlayer-dev-toolsSkill
- intlayer-litSkill
- intlayer-markdownSkill
- intlayer-next-jsSkill
- intlayer-preactSkill
- intlayer-reactSkill
- intlayer-remixSkill
- intlayer-remote-contentSkill
- intlayer-solidSkill
- intlayer-svelteSkill
- intlayer-usageSkill
- intlayer-vanillaSkill
- intlayer-vueSkill
- intlayer-angularSkill
- intlayer-astroSkill
- intlayer-backendSkill
- intlayer-bundle-optimizationSkill
- intlayer-cliSkill
- intlayer-compatSkill
- intlayer-compilerSkill
- intlayer-configSkill
- intlayer-contentSkill
- intlayer-dev-toolsSkill
- intlayer-litSkill
- intlayer-markdownSkill
- intlayer-next-jsSkill
- intlayer-preactSkill
- intlayer-reactSkill
- intlayer-remixSkill
- intlayer-remote-contentSkill
- intlayer-solidSkill
- intlayer-svelteSkill
- intlayer-usageSkill
- intlayer-vanillaSkill
- intlayer-vueSkill
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
13 rules. About 0 are common, 10 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
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
- Very specific: line 3
Should focus on final user point of view.
- Distinctive: line 8
Should looks human written, keep everything concise as possible
- Distinctive: line 9
Should avoid commercial positioning
- Distinctive: line 14
Keep everything concise as possible
- Distinctive: line 15
Don't use '—' char, replace it by ',' to '.'
- Distinctive: line 17
All title, description and h1 should be studied for best SEO indexation
- Very specific: line 18
Always update updatedAt in front-matter after update
- Distinctive: line 19
Add <TOC> for long posts
- Distinctive: line 22
Avoid '---' to separate sections
- Distinctive: line 23
Add links to other benchmarks docs and links to other docs, compat adapters etc where possible
- Distinctive: line 25
Avoid distraction. Go straight to the point.
- Very specific: line 56
If not explicitly mentioned, never use AI generation for translations using the scripts translate or review + MODE = 'apply'.
- Distinctive: line 57
If not mentioned, you should iterate doc by doc and translate manually each doc for each locale without using script.
≈ “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
For docs:
- Should focus on final user point of view. Avoid mention of internal intlayer subtleties
- To add docs in website navbar, list it in
apps/website/src/components/DocPage/docData.content.ts
For blogs:
- Should looks human written, keep everything concise as possible
- Should avoid commercial positioning
- For blogs, list it in
apps/website/src/components/BlogPage/blogData.content.ts
For both:
- Keep everything concise as possible
- Don't use '—' char, replace it by ',' to '.'
- Reuse the front-matter format to seo and website indexation.
- All title, description and h1 should be studied for best SEO indexation
- Always update
updatedAtin front-matter after update - Add
<TOC>for long posts <Tabs>,<Step>,<Accordion>,<FAQ>where pertinent- Links between docs should be like (
https://github.com/aymericzip/intlayer/blob/main/docs/.../.md, no./.../.md, nohttps://intlayer.org/...) - Avoid '---' to separate sections
- Add links to other benchmarks docs and links to other docs, compat adapters etc where possible
- For translations check
docs/tools/prompts/CUSTOM_INSTRUCTIONS.md - Avoid distraction. Go straight to the point. Avoid long blog. Don't hesitate to remove part that are not relevant, duplicated, obsolete, or too verbose for the user
Doc are multilingual.
- ENGLISH
- SPANISH
- RUSSIAN
- JAPANESE
- FRENCH
- KOREAN
- CHINESE
- GERMAN
- ARABIC
- ITALIAN
- ENGLISH_UNITED_KINGDOM
- PORTUGUESE
- HINDI
- TURKISH
- POLISH
- INDONESIAN
- VIETNAMESE
- UKRAINIAN
- HEBREW_ISRAEL
Structure:
docs/docs/{locale}/**/*.mddocs/blog/{locale}/**/*.mddocs/frequent_questions/{locale}/**/*.mddocs/legal/{locale}/**/*.md
If not explicitly mentioned, never use AI generation for translations using the scripts translate or review + MODE = 'apply'. Those will consume extra token no included in the plan. But you can use review + MODE = 'synthesis' | 'synthesis' to validate the doc consistency.
If not mentioned, you should iterate doc by doc and translate manually each doc for each locale without using script.
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.

