Lore speaks your language
Until now, because the skills themselves are written in English, generated Lore artifacts tended to come out in English — even for users working in another language. This release fixes that.
What's new
Lore is now generated in YOUR language — content and filenames
Every Lore skill (create-area, create-project, save-to-lore, transmute-lore) now writes all generated content in the language you work in, and localizes the artifact filenames too: identidad.md, principios.md, FASES.md, proyectos/ are the Spanish canonical forms — in English they become identity.md, principles.md, PHASES.md, projects/. What stays fixed in every language:
- CLAUDE.md (a Claude Code convention), lore/ (the kit's own name), index.md, golden-paths.md
- Structure, relative-path depth, and confidence markers
- English terms of general technical use (workflow, commit, stack, scaffold…)
Consistency wins inside an existing corpus: established names are never mixed. save-to-lore matches the language your lore already uses, and create-project flags a language mismatch with its parent Area instead of silently diverging.
New: transmute-lore TRANSLATE mode
A third mode to standardize the language of an existing Lore:
standardize the language of the lore of "Legacy Frontend"
translate the lore of "Legacy Frontend" to Spanish
It inventories the current language of every artifact, presents a file-by-file plan behind the usual HARD-GATE — including artifact renames — then translates content, renames localizable files with git mv, and rewrites every affected link. Meaning-preserving, never a rewrite: no clue is added, removed, or reinterpreted. As always: clean git tree required, no auto-commit, you review the diff.
Docs
README, USAGE, REFERENCE, and MIGRATION guides (Spanish and English) updated to cover the language rule and the new TRANSLATE mode.
Upgrading
/plugin update lore@lore-plugin
No breaking changes — existing Lore corpora keep their current names and language until you explicitly run TRANSLATE on them.