agentleFS
GCarin1GCarin1/Doctrina/.claude/skills/keep-docs-en-pt-parity/SKILL.md

keep-docs-en-pt-parity

Skill1 starsChanged 3 days agoMITView on GitHub

Keep docs/en and docs/pt as true mirrors — same files, same structure, EN as the source of truth. Use when: The task adds, renames, removes, or substantially edits any file under docs/.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never translate file paths, command names, code identifiers, fenced examples, or artifact status vocabulary (active, verified, Read-only).

    line 20
  2. Distinctive:

    Every PT file carries, right under its H1, the source note:

    line 25
  3. Very specific:

    Check yourself with the gates: doctrina validate warns on a missing EN↔PT counterpart, and node scripts/check-docs.js (also wired into …

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- doctrina:skill-export — generated from .doctrina/skills/keep-docs-en-pt-parity.md by `doctrina index rebuild`; edit that file, not this one. -->

Skill — keep-docs-en-pt-parity

When to use this skill

  • Adding a new documentation topic.
  • Editing an EN doc (the PT mirror must move in the same change).
  • Renaming or deleting a doc file.

Procedure

  1. EN is the source of truth; PT is a translation of EN, never the reverse. Author the EN change first, then mirror it into the PT file with the identical filename under docs/pt/.
  2. Never translate file paths, command names, code identifiers, fenced examples, or artifact status vocabulary (active, verified, Read-only). Headings that name commands stay in backticks exactly as in EN (## doctrina spec set <capability> stays untranslated) — the docs drift test parses them.
  3. Every PT file carries, right under its H1, the source note:

    Tradução da versão em inglês. O inglês é a fonte de verdade; este arquivo o segue.

  4. A new topic lands as a PAIR (EN + PT) in the same change, plus a sidebar entry in docs/en/_sidebar.md and docs/pt/_sidebar.md.
  5. Prose docs stay under the 250-line soft cap (.doctrina/specs/docs/spec.md); lookup references (cli-reference.md) are exempt — agents read them per-section.
  6. Check yourself with the gates: doctrina validate warns on a missing EN↔PT counterpart, and node scripts/check-docs.js (also wired into doctrina verify) checks parity, H1 shape, line caps, and the PT source note.
  7. The gates check SHAPE, not content: a PT bullet can say the opposite of its EN twin with the same line count. For an audit, compare per file what does not translate — the inline code spans (commands, flags, paths; placeholders such as <name>/<nome> normalised), the numbers, the link targets — and read every pair that differs. That is how "constitution deferred" (PT) against "shipped in 0.10.0" (EN), a table row that said a vague word for "8 personas", and an EN-only fact (cwd per verify check) were found in change 0228.
  8. The PT source note costs three lines, so a PT file runs into the 250-line cap before its EN twin. Rewrap the PT paragraphs that break short instead of cutting content, and diff the WORDS before and after (git show HEAD:<file> split on whitespace) to prove the rewrap changed none.
  9. A doc that walks a flow is checked by walking it: run its commands in order in a temporary directory, and keep the walk as a test when the flow matters (test/o-guia-de-ponta-a-ponta-roda-como-escrito.test.js). A Mermaid block is checked by rendering it (mermaid.render in a headless browser against the version docs/index.html loads) — counting node ids proves nothing about whether it parses.

Anti-patterns

  • "I'll translate it later": the file lands in EN only, the PT tree silently falls behind, and no reader of the PT docs ever learns the feature exists.
  • Translating a command heading (## doctrina search <termo> is fine in the body text, but the command word itself must remain search) — it breaks lookup and the heading-based drift test.
  • Writing new content directly in PT. If the content is worth having, it is worth having in the source language first.

Related material

  • .doctrina/specs/docs/spec.md — the docs capability contract.
  • scripts/check-docs.js — the executable shape check.
  • AGENTS.md — "Do NOT translate file paths, command names, or code identifiers."

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.