repo-architecture
Skill1k starsChanged 11 days agoMITView on GitHub
Cross-cutting architecture reference for the eslint-plugin-boundaries monorepo — the dependency graph between packages and the Nx target graph. Load before designing or reviewing anything that spans more than one project.
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
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 32
Run pnpm nx graph to see the live dependency graph rather than trusting this table if it's unclear whether it's stale.
- Very specific: line 38
Only eslint-plugin and eslint-plugin-e2e make lint depend on their own build.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
eslint-plugin-boundaries repository architecture
This is a pnpm + Nx monorepo publishing @boundaries/elements, @boundaries/eslint-plugin, and the jsboundaries.dev documentation website. Its architecture is defined by each project's AGENTS.md plus this cross-cutting reference, not by convention alone.
Where the rules live
The map of where each kind of rule lives is in the root AGENTS.md; read the AGENTS.md of the project you touch. eslint-plugin and website lint-enforce their own layering (their eslint.config.mjs, ground truth over prose); elements' layering is described in its AGENTS.md.
Component map
| Directory | Nx project | Publishes | Role |
packages/elements | elements | @boundaries/elements | Element descriptors and matchers — the classification engine eslint-plugin builds rules on |
packages/eslint-plugin | eslint-plugin | @boundaries/eslint-plugin | The ESLint plugin itself: rules, settings parsing, messages |
packages/website | website | (deployed, not published) | Docusaurus site for jsboundaries.dev; versioning in its AGENTS.md |
examples/typescript | example-typescript | (not published) | Minimal TypeScript project consuming the plugin, built against current source |
examples/oxlint-integration | example-oxlint-integration | (not published) | Demonstrates pairing the plugin with Oxlint |
support/eslint-config | eslint-config | @boundaries/repo-eslint-config | Shared ESLint flat config every project's eslint.config.* composes |
support/cspell-config | cspell-config | @boundaries/repo-cspell-config | Shared cspell config every project's cspell.config.* composes |
test/eslint-plugin-e2e | eslint-plugin-e2e | (not published) | Plain-Node end-to-end suite against the built plugin |
Dependency graph and direction
elementshas no in-repo dependencies.eslint-plugindepends on it for classification.eslint-plugin-e2e, bothexamples/*andwebsitedepend on the builteslint-plugin(via Nx'sdependsOn: ["build"]/["^build"]and aworkspace:dependency, never a published version).support/eslint-configandsupport/cspell-configare depended on by every project viaimplicitDependenciesin eachproject.json, and via each project's ownlint/check:spelltarget depending on that support package'seslint:config/cspell:configtarget.websiteis downstream ofeslint-pluginconceptually (it documents the plugin's current API and versions its docs alongside plugin releases) and lints its ownsrc/with it, so itslintbuildseslint-pluginfirst — keeppackages/website/docs/rules/in sync witheslint-pluginchanges manually.- Run
pnpm nx graphto see the live dependency graph rather than trusting this table if it's unclear whether it's stale.
Nx target graph
The standardized target names are listed in the root AGENTS.md ("Commands"). They get common defaults from nx.json's targetDefaults and are overridden per-project in project.json only where a project's needs diverge; .agents/rules/nx-project-config.md covers that override mechanism and why it matters for caching.
Only eslint-plugin and eslint-plugin-e2e make lint depend on their own build; each project's AGENTS.md says why.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- garrytan/gbrain★ 31ksame name
- JatinBhargava/repo-architecture-skill★ 9same name
- Kaushik2210/gitVisualise★ 1same 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- boundaries-architectSkill
- create-architectural-decision-recordSkill
- create-issueSkill
- create-prSkill
- documentation-writerSkill
- releaseSkill
- review-prSkill
- unit-testingSkill
- write-planSkill
- writing-styleSkill
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.