fill-translations
Skill45k starsChanged todayMITView on GitHub
Fill missing Reactive Resume translations across all configured web and mobile locales using parallel subagents, then prove catalog completeness. Use for “fill translations”, “complete translations”, missing locale strings, or a request to ensure translations are complete before release. Cover existing gaps unrelated to the current task unless the user explicitly narrows scope. Do not activate for ordinary prose translation or a read-only audit that forbids edits.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Very specific: line 10
Run from the Reactive Resume checkout root.
- Very specific: line 14
Read GLOSSARY.md, both apps' lingui.config.ts, relevant package scripts, and apps/mobile/scripts/seed-locales.mjs.
- Distinctive: line 25
Run both missing checks, capturing each exit code and verbose findings even when one fails:
- Distinctive: line 48
After every web worker finishes, seed once from the parent:
- Distinctive: line 61
Run every gate below and record each result.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.
Files
Fill translations
Finish every active catalog entry, including older gaps outside the current feature. Preserve existing translations and unrelated work. Technical completeness and linguistic quality are separate claims.
Run from the Reactive Resume checkout root. Follow its AGENTS.md, command wrappers, and current package scripts. Commands below match its Lingui 6 workflow; inspect installed --help if flags change. Use existing dependencies; no translation service or new dependency is required.
Establish the baseline
- Read
GLOSSARY.md, both apps'lingui.config.ts, relevant package scripts, andapps/mobile/scripts/seed-locales.mjs. Derive locales, source locale, and pseudo-locale from current config rather than a fixed locale count. Currentlyzu-ZAis a generated pseudo-locale, not Zulu translation work. - Capture
git status --shortand the initial diff. Save copies of catalog bytes outside the checkout so preservation checks compare against current work, notHEAD. Record pre-existing compiled locale files too. Keep staged/unstaged changes intact; no reset, checkout, clean, commit, push, or release unless separately requested. Extract all source strings in both apps, sequentially, before dispatching workers:
pnpm --filter web lingui:extract pnpm --filter mobile lingui:extractThe root
lingui:extractcurrently covers web only. Web's script cleans obsolete entries and overwrites the source locale from source messages; mobile's script also seeds empty entries from web. These extraction changes are expected. Compare preservation of active nonempty target translations against the post-extraction baseline.Run both missing checks, capturing each exit code and verbose findings even when one fails:
pnpm --filter web exec lingui check missing --mode catalog --verbose pnpm --filter mobile exec lingui check missing --mode catalog --verboseInventory all missing entries by app and locale. Use installed
@lingui/format-pothrough the owning workspace for structured inventory/edits; empty-line regexes misread multiline messages, headers, contexts, and obsolete entries. Keep msgid, context, translator comments, and source references with each work item. If no entries are missing, continue to verification without spawning translation workers.
Translate in parallel
Complete web first, seed mobile again, then translate only remaining mobile gaps. This reuses shared strings and avoids duplicate or inconsistent work.
Assign disjoint whole locale files to workers. Keep a small bounded pool within available concurrency; balance by missing-entry count, group related locales where useful, and refill slots as workers finish. Never assign two writers to the same file, even for different messages. Give workers only missing messages plus relevant existing examples and source context instead of whole catalogs when possible.
Use the environment's delegated-task tools. In T3 Code, inspect orchestrator_capabilities and use delegate_task when inherited model options require it; preserve the current provider/model/options unless the user requests another selection. Use shared-checkout tasks for disjoint files: worktrees start from committed state and can omit current uncommitted source/catalog changes. Use native subagents where supported and appropriate. If delegation is unavailable, complete the same inventory sequentially and disclose that limitation. Do not create ordinary top-level conversations.
Give each worker this brief, substituting exact paths and entries:
Fill only empty active target translations in these owned files: [paths]. Work from this post-extraction inventory: [entries/counts]. Read
GLOSSARY.md, existing locale terminology, comments, and referenced UI when meaning is ambiguous. Translate natural interface language for each locale. Preserve IDs, contexts, source messages, existing nonempty translations, headers, references, and unrelated edits. Preserve named placeholders, ICU variable names/types, select keys, exact-number branches,otherbranches, plural#, numbered rich-text tag indexes/pairing, literal URLs/config identifiers, and brands. Adapt plural categories to the target language. Keep tags attached to their corresponding meaning when word order changes. Use the installed PO parser/serializer; review round-trip diffs. English copying is acceptable only for genuine shared words, brands, and literals, never to conceal a gap. You own translation edits only: no extraction, seeding, global formatting, compilation, commits, or cleanup. Other workers share this checkout. Return paths, filled counts, unresolved IDs, uncertainties, and checks actually run. Finish every assigned entry or identify the blocker; do not claim global completion.
The parent tracks completion against the inventory, reviews returned diffs/counts, and resolves failures. Worker summaries alone are insufficient evidence. Retry only failed files/entries; do not rerun successful batches.
After every web worker finishes, seed once from the parent:
pnpm --filter mobile exec node scripts/seed-locales.mjs
pnpm --filter mobile exec lingui check missing --mode catalog --verbosePartition remaining mobile gaps into disjoint files and apply the same workflow. Existing nonempty mobile translations remain authoritative. Finish all workers before shared commands run.
Verify completion
First compare parsed catalog changes with the post-extraction baseline: active IDs/contexts/source messages stay intact, existing nonempty target translations stay intact, and only missing translations are filled. Review newly added messages against original source. Compare placeholder and numbered-tag structure for every filled entry using parsed ICU/message structure, not brace regexes. Inspect installed Lingui parser utilities before using them; locale plural categories may legitimately differ. A syntactically valid message can still omit a variable, so compilation alone is insufficient. Review glossary-sensitive wording and suspicious source-identical translations.
Run every gate below and record each result. These commands are for the whole catalog, not changed locales or changed source files:
pnpm --filter web exec lingui check sync --clean --overwrite
pnpm --filter mobile exec lingui check sync --clean
pnpm --filter web exec lingui check missing --mode catalog --verbose
pnpm --filter mobile exec lingui check missing --mode catalog --verbose
pnpm --filter web exec lingui compile --strict
pnpm --filter mobile exec lingui compile --strict
pnpm pdf:translations
pnpm --filter @reactive-resume/tooling test locales/section-titles.test.ts
pnpm lint:agent
pnpm format:check
git diff --checkcheck sync proves catalogs reflect current source; an old but fully filled catalog is insufficient. --mode catalog proves each target catalog is filled before fallback. Default missing checks and compile --strict allow fallback and cannot replace it. Compilation adds ICU syntax/bundle validation. The tooling test must actually execute its tests; zero tests is not proof.
Compilation writes locale .js files. Before compiling, back up existing output bytes and record absent output paths. After checking, restore pre-existing outputs to those exact bytes and remove only files created by this invocation. Preserve outputs that were already untracked. If another process changes an output during verification, preserve its change and report the conflict instead of overwriting it. Retain generated PDF section-title and Present-label changes, since those are maintained artifacts. Inspect final status/diff against the initial baseline.
If synchronization fails, inspect source drift and re-extract from the parent after workers finish, seed again, translate new gaps, and repeat affected gates. If missing checks fail, continue filling. Repair translation-introduced syntax/placeholder errors. Report unrelated pre-existing failures separately; do not change lint policy, fallback config, source strings, or locale lists to manufacture a pass. Never pipe away exit codes or treat a partial, timed-out, or unrun check as passing.
Stop when all configured web and mobile catalogs are synchronized, all catalog-mode missing checks return zero, changed messages preserve their runtime structure, strict compilation and derived-artifact checks pass, and unrelated work remains intact. If a blocker prevents this, report exact outstanding app/locale/message counts and failed or unrun gates; do not claim completion.
Report
Keep the handoff short: entries filled by app and locale count; final missing counts; commands/checks that passed or failed; unresolved linguistic uncertainty. State whether native-language review occurred. Mention parallelism only if workers actually ran. A clean catalog proves technical completeness, not native-language quality, browser/native behavior, deployment, or release readiness. Leave changes uncommitted unless asked otherwise.
Trending
Quiet since September.about the whole repository
Who's talking about AmruthPillai/Reactive-Resume
- Amruth Pillai“Reactive Resume - Free & Open Source Resume Builder”YouTube · Mar 26, 2020 · 20k views
- How to Web Dev“Open Source Projects You Should Know #code #programming #coding #tech #ai #website #software”YouTube · Aug 7, 2026 · 9.2k views
- TekZoom“Construtor de Currículos React e VueJS Open Source e Grátis!”YouTube · Apr 1, 2020 · 2.2k views
- أسرار التاريخ القديم“اصنع سيرتك الذاتية في 30 ثانية بالذكاء الاصطناعي 📄🚀⚡️”YouTube · Apr 29, 2026 · 304 views
- GitHub Daily Trend AI Podcast“GitHub - AmruthPillai/Reactive-Resume: A one-of-a-kind resume builder that keeps your privacy in ...”YouTube · Sep 12, 2024 · 289 views
The biggest 5 of 91 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 91
Talked about on GitHub, Bluesky, YouTube, Hacker News and the web (91 times).
On GitHub · 50
- Jan 14, 2026A New Chapter for Reactive Resume — reactive-resume/reactive-resume87 reactions · 36 comments
- Oct 2, 2022[FEATURE] Promotion history — reactive-resume/reactive-resume8 reactions · 1 comment
- Apr 8, 2024Add Reactive Resume as a Service — coollabsio/coolify5 reactions · 1 comment
- Nov 25, 2022[FEATURE] Builder sections are not translatable — reactive-resume/reactive-resume3 reactions · 4 comments
- Sep 5, 2026feat(pdf): add opt-in German hyphenation — reactive-resume/reactive-resume2 reactions · 5 comments
45 more on GitHub
- Sep 5, 2026fix(pdf): respect requested font metrics when positioning text — reactive-resume/reactive-resume2 reactions · 3 comments
- Sep 5, 2026fix(builder): preserve explicit HTTP URLs — reactive-resume/reactive-resume2 reactions · 3 comments
- Aug 18, 2026fix(pdf): render emoji via a Noto Emoji script fallback — reactive-resume/reactive-resume2 reactions · 2 comments
- Jan 30, 2026[Bug] PDF export (still) adds spacing that affects layout and adds pages — reactive-resume/reactive-resume2 reactions · 2 comments
- Aug 27, 2025App request: Reactive resume — truenas/apps2 reactions · 7 comments
- May 25, 2025[Feature] Tutorial for editing the templates — reactive-resume/reactive-resume2 reactions · 1 comment
- Nov 14, 2024feat(templates): make main full-width if sidebar is empty — reactive-resume/reactive-resume2 reactions · 1 comment
- Feb 21, 2024[Bug] Linkedin import error — reactive-resume/reactive-resume2 reactions · 8 comments
- Dec 9, 2023[Bug] Disable new signups still not possible — reactive-resume/reactive-resume2 reactions · 7 comments
- Nov 27, 2023[Feature] Missing Castform template — reactive-resume/reactive-resume2 reactions · 2 comments
- Oct 16, 2023Just wanted to appreciate the effort! — xitanggg/open-resume2 reactions · 1 comment
- Aug 25, 2023[Bug] Unable to register / create account — reactive-resume/reactive-resume2 reactions · 11 comments
- Aug 15, 2023[Bug] PDF download does not work locally with docker compose — reactive-resume/reactive-resume2 reactions · 14 comments
- Sep 10, 2026chore: pin Node.js runtime and make root TS strict mode explicit — reactive-resume/reactive-resume1 reaction · 2 comments
- Sep 9, 2026fix(pdf): add marginTop to style of "section" in "Lapras" template — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 6, 2026docs: expand v5.3.0 changelog — reactive-resume/reactive-resume1 reaction · 4 comments
- Sep 6, 2026test: opt in preview export geometry E2E — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 6, 2026test: measure preview and export geometry — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 6, 2026feat(web): improve accessible resume outline — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 6, 2026test(pdf): characterize date layout geometry — reactive-resume/reactive-resume1 reaction · 2 comments
- Sep 6, 2026test(pdf): characterize safe item pagination boundary — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 6, 2026feat(resume): add per-section heading visibility — reactive-resume/reactive-resume1 reaction · 4 comments
- Sep 6, 2026test(e2e): scope imported table border geometry — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 6, 2026fix(editor): avoid unsafe clipboard parsing pattern — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 6, 2026fix(pdf): restore Gengar skill rating order — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 6, 2026feat(sharing): serve a configured public resume at root — reactive-resume/reactive-resume1 reaction · 4 comments
- Sep 6, 2026feat(resume): add skill keyword list presentation — reactive-resume/reactive-resume1 reaction · 4 comments
- Sep 6, 2026feat(builder): explain authored page overflow — reactive-resume/reactive-resume1 reaction · 5 comments
- Sep 6, 2026test(recovery): refresh hashes for picture fit default — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 6, 2026feat: add retired resume link notices — reactive-resume/reactive-resume1 reaction · 5 comments
- Sep 5, 2026docs: explain current AI tailoring workflow — reactive-resume/reactive-resume1 reaction · 4 comments
- Sep 5, 2026docs: record Unicode fixes and remaining issue actions — reactive-resume/reactive-resume1 reaction · 5 comments
- Sep 5, 2026fix(pdf): preserve authored Unicode spaces in rich text — reactive-resume/reactive-resume1 reaction · 4 comments
- Sep 5, 2026fix(pdf): keep ordered list markers clear of body text — reactive-resume/reactive-resume1 reaction · 4 comments
- Sep 5, 2026fix(builder): center preview in RTL interfaces — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 5, 2026fix(pdf): keep list markers with their first text fragment — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 5, 2026fix(pdf): preserve imported rich text without semantic descendants — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 5, 2026fix(stylesheet): allow gaps between level decorations — reactive-resume/reactive-resume1 reaction · 5 comments
- Sep 5, 2026fix(storage): support S3 buckets with object ACLs disabled — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 5, 2026feat: add compact resume view with session preferences — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 5, 2026fix: label remaining website and picture inputs — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 5, 2026fix: restore MCP OAuth registration and authorization — reactive-resume/reactive-resume1 reaction · 4 comments
- Sep 5, 2026docs: audit open issues and track resolution plan — reactive-resume/reactive-resume1 reaction · 4 comments
- Sep 5, 2026fix: remove empty custom sections and affected pages after moving items — reactive-resume/reactive-resume1 reaction · 3 comments
- Sep 5, 2026fix(email): preserve optional Nodemailer property types — reactive-resume/reactive-resume1 reaction · 3 comments
On Bluesky · 26
- Apr 27, 2025Vous cherchez un outil pour faire un CV interactif ? Reactive Resume est fait pour vous ; c'est un générateur de CV open source qui… — @ponceto91.bsky.social40 likes and reposts · 2 replies
- Jan 3, 2024Votre carrière vaut bien ça 👉👉 Reactive Resume : un outil Open Source pour la création de CV. github.com/AmruthPil... — @bearstech.com16 likes and reposts
- Apr 26, 2025📦 AmruthPillai / Reactive-Resume ⭐ 30,738 (+82) 🗒 TypeScript A one-of-a-kind resume builder that keeps your privacy in mind. Completely… — @github-trending.bsky.social10 likes and reposts
- Jan 16, 2025📦 AmruthPillai / Reactive-Resume ⭐ 27,398 (+51) 🗒 TypeScript A one-of-a-kind resume builder that keeps your privacy in mind. Completely… — @github-trending-js.bsky.social6 likes and reposts
- Nov 10, 2024🚀 Skyrocketing! 🚀 (200+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 24,065 (+378) 🗒 TypeScript A one-of-a-kind resume builder that… — @github-trending-js.bsky.social5 likes and reposts · 1 reply
21 more on Bluesky
- Apr 25, 2025📦 AmruthPillai / Reactive-Resume ⭐ 30,684 (+70) 🗒 TypeScript A one-of-a-kind resume builder that keeps your privacy in mind. Completely… — @github-trending-js.bsky.social4 likes and reposts
- Jan 24, 2025🚀 Skyrocketing! 🚀 (200+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 27,936 (+246) 🗒 TypeScript A one-of-a-kind resume builder that… — @github-trending-js.bsky.social4 likes and reposts · 1 reply
- Jan 14, 2025📦 AmruthPillai / Reactive-Resume ⭐ 27,051 (+22) 🗒 TypeScript A one-of-a-kind resume builder that keeps your privacy in mind. Completely… — @github-trending.bsky.social4 likes and reposts
- Jan 24, 2025🚀 Skyrocketing! 🚀 (200+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 27,935 (+246) 🗒 TypeScript A one-of-a-kind resume builder that… — @github-trending.bsky.social3 likes and reposts
- Jan 24, 2025github.com/AmruthPillai... #Ai #Resume #Cloud — @dajjaal.bsky.social3 likes and reposts
- Nov 10, 2024🚀 Skyrocketing! 🚀 (200+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 24,065 (+378) 🗒 TypeScript A one-of-a-kind resume builder that… — @github-trending.bsky.social2 likes and reposts · 1 reply
- Nov 24, 2023📦 AmruthPillai / Reactive-Resume ⭐ 12,942 (+87) 🗒 TypeScript A one-of-a-kind resume builder that keeps your privacy in mind. Completely… — @github-trending-js.bsky.social2 likes and reposts
- Apr 24, 2025https://github.com/AmruthPillai/Reactive-Resume — @tom-doerr.bsky.social1 likes and repost
- Sep 15, 2024🚀 Skyrocketing! 🚀 (200+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 22,685 (+240) 🗒 TypeScript A one-of-a-kind resume builder that… — @github-trending-js.bsky.social1 likes and repost · 1 reply
- Sep 11, 2024📦 AmruthPillai / Reactive-Resume ⭐ 21,918 (+40) 🗒 TypeScript A one-of-a-kind resume builder that keeps your privacy in mind. Completely… — @github-trending.bsky.social1 likes and repost
- Sep 11, 2024📦 AmruthPillai / Reactive-Resume ⭐ 21,918 (+40) 🗒 TypeScript A one-of-a-kind resume builder that keeps your privacy in mind. Completely… — @github-trending-js.bsky.social1 likes and repost
- Aug 8, 2024📦 AmruthPillai / Reactive-Resume ⭐ 21,107 (+61) 🗒 TypeScript A one-of-a-kind resume builder that keeps your privacy in mind. Completely… — @github-trending-js.bsky.social1 likes and repost
- May 22, 2024📦 AmruthPillai / Reactive-Resume ⭐ 20,249 (+50) 🗒 TypeScript A one-of-a-kind resume builder that keeps your privacy in mind. Completely… — @github-trending-js.bsky.social1 likes and repost
- Jan 25, 2024🚀 Skyrocketing! 🚀 (200+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 18,625 (+316) 🗒 TypeScript A one-of-a-kind resume builder that… — @github-trending-js.bsky.social1 likes and repost · 1 reply
- Dec 26, 2023🚀 Skyrocketing! 🚀 (200+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 15,606 (+284) 🗒 TypeScript A one-of-a-kind resume builder that… — @github-trending-js.bsky.social1 likes and repost · 1 reply
- Dec 23, 2023🚀 Skyrocketing! 🚀 (200+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 14,883 (+200) 🗒 TypeScript A one-of-a-kind resume builder that… — @github-trending.bsky.social1 likes and repost · 1 reply
- Jan 20, 2024🔥 Hot Repo! 🔥 (100+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 17,505 (+107) 🗒 TypeScript A one-of-a-kind resume builder that keeps… — @github-trending.bsky.social0 likes and reposts · 1 reply
- Jan 20, 2024🔥 Hot Repo! 🔥 (100+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 17,505 (+107) 🗒 TypeScript A one-of-a-kind resume builder that keeps… — @github-trending-js.bsky.social0 likes and reposts · 1 reply
- Dec 28, 2023🚀 Skyrocketing! 🚀 (200+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 15,993 (+392) 🗒 TypeScript A one-of-a-kind resume builder that… — @github-trending.bsky.social0 likes and reposts · 1 reply
- Dec 22, 2023🔥 Hot Repo! 🔥 (100+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 14,735 (+134) 🗒 TypeScript A one-of-a-kind resume builder that keeps… — @github-trending-js.bsky.social0 likes and reposts · 1 reply
- Nov 29, 2023🚀 Skyrocketing! 🚀 (200+ new stars) 📦 AmruthPillai / Reactive-Resume ⭐ 14,248 (+313) 🗒 TypeScript A one-of-a-kind resume builder that… — @github-trending-js.bsky.social0 likes and reposts · 1 reply
On YouTube · 11
- Mar 26, 2020Reactive Resume - Free & Open Source Resume Builder — Amruth Pillai20k views · 47 comments
- Aug 7, 2026Open Source Projects You Should Know #code #programming #coding #tech #ai #website #software — How to Web Dev9.2k views · 3 comments
- Apr 1, 2020Construtor de Currículos React e VueJS Open Source e Grátis! — TekZoom2.2k views · 12 comments
- Apr 29, 2026اصنع سيرتك الذاتية في 30 ثانية بالذكاء الاصطناعي 📄🚀⚡️ — أسرار التاريخ القديم304 views · 1 comment
- Sep 12, 2024GitHub - AmruthPillai/Reactive-Resume: A one-of-a-kind resume builder that keeps your privacy in ... — GitHub Daily Trend AI Podcast289 views
6 more on YouTube
- Sep 24, 2026Free Resume Builder, No Paywall — Open Source, 43k Stars (Reactive Resume) — CodeGlade159 views · 1 comment
- Sep 3, 2026Reactive Resume: free open-source resume builder you can self-host — Git Gems131 views
- Jan 10, 2025每日github项目分享——免费开源的简历设计平台 — JasonW_69 views
- Oct 28, 2021AmruthPillai/Reactive-Resume - Grource visualisation — Gourcer62 views
- Jul 14, 2026Build a Professional Resume for FREE 🤯 No Paywall (Reactive Resume) — OpenRepo42 views
- Sep 30, 2026Your Resume May Look Fine—but ATS Might Read It Wrong — Sealos12 views
On Hacker News · 3
- Jul 5, 2026Show HN: Reactive Resume v5 – free, private, self-hostable resume builder2 points
- Aug 28, 2024Reactive Resume2 points · 1 comment
- Apr 8, 2022Reactive-Resume: An open-source resume builder that keeps your privacy in mind2 points
On the web · 1
- Mar 21, 2024Resume Download issue #1821 — google.com
Other versions3 projects use a version of this.
Word for word · 2
- amruthpillai/reactive-resume★ 45k100% same
- reactive-resume/reactive-resume★ 45k100% same
Edited · 0
None found.
Wrote their own version · 1
- karakeep-app/karakeep★ 30ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

