ai-kit
AGENTS.md12 starsChanged 2 months agoMITView on GitHub
This repo's architecture, decisions, rules, specs and patterns live in .archcore/, reachable through the Archcore MCP tools. Consult them even on code you think you know — a decision or rule may already constrain it. A .archcore/ may also mount read-only global sources — shared, org-wide context not shown in the session-start list. list_documents / search_documents surface them alongside local docs, tagged source_kind: "global". When present, treat them as defaults a local doc can override — never edit or relate…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ivklgn/bag-of-skillsword for word, first seen Sep 4, 2026
Other versions1 project uses a version of this.
Word for word · 1
- ivklgn/bag-of-skills★ 12100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository22 other files it gives its agents.
- new-skillSkill
- review-and-releaseSkill
- 12-factor-appsSkill
- ask-meSkill
- audit-websiteSkill
- can-i-useSkill
- code-reviewerSkill
- compatibility-auditSkill
- explain-branch-changesSkill
- humanizer-ruSkill
- humanizerSkill
- jsdocSkill
- load-branch-changesSkill
- nextjs-developerSkill
- recapSkill
- reset-permissionsSkill
- review-golangSkill
- seo-auditSkill
- simplify-code-commentsSkill
- test-health-checkSkill
- update-golang-depsSkill
- update-node-depsSkill
The file
Files
<!-- archcore:start --> managed by `archcore init` — edit outside these markersArchcore — project context for this repo
This repo's architecture, decisions, rules, specs and patterns live in .archcore/,
reachable through the Archcore MCP tools. Consult them even on code you think you
know — a decision or rule may already constrain it.
- Touching this repo's real code or behavior → search first; read only what matches.
- A decision was made ("we'll use X", "from now on Y") → record it.
- A module / API / system has no doc — or a search comes back empty → capture it.
- Planning a feature or refactor → scope it against what's already decided.
A .archcore/ may also mount read-only global sources — shared, org-wide
context not shown in the session-start list. list_documents / search_documents
surface them alongside local docs, tagged source_kind: "global". When present,
treat them as defaults a local doc can override — never edit or relate to one.
The search is cheap — lean on it. Skip it only for turns this repo would have no opinion on: syntax trivia, throwaway snippets, pure mechanics.
<!-- archcore:end -->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.