Create Saleor Package
saleor/apps
Scaffold a new shared package in the saleor-apps monorepo under ./packages/.
Cross-cutting architecture reference for the eslint-plugin-boundaries monorepo — the dependency graph between packages, the Nx target graph, and the release flow.
Install Repo Architecture
$ npx skills add javierbrea/eslint-plugin-boundaries --skill repo-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install javierbrea/eslint-plugin-boundaries repo-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/javierbrea/eslint-plugin-boundaries.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/repo-architecture .claude/skills/repo-architecture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "repo-architecture" agent skill from https://github.com/javierbrea/eslint-plugin-boundaries/tree/master/.agents/skills/repo-architecture into .claude/skills/repo-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/javierbrea/eslint-plugin-boundaries/tree/master/.agents/skills/repo-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add javierbrea/eslint-plugin-boundaries --skill repo-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install javierbrea/eslint-plugin-boundaries repo-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javierbrea/eslint-plugin-boundaries.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/repo-architecture .agents/skills/repo-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "repo-architecture" agent skill from https://github.com/javierbrea/eslint-plugin-boundaries/tree/master/.agents/skills/repo-architecture into .agents/skills/repo-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add javierbrea/eslint-plugin-boundaries --skill repo-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install javierbrea/eslint-plugin-boundaries repo-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javierbrea/eslint-plugin-boundaries.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/repo-architecture .cursor/skills/repo-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "repo-architecture" agent skill from https://github.com/javierbrea/eslint-plugin-boundaries/tree/master/.agents/skills/repo-architecture into .cursor/skills/repo-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/javierbrea/eslint-plugin-boundaries.git --path .agents/skills/repo-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add javierbrea/eslint-plugin-boundaries --skill repo-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install javierbrea/eslint-plugin-boundaries repo-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javierbrea/eslint-plugin-boundaries.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/repo-architecture .gemini/skills/repo-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "repo-architecture" agent skill from https://github.com/javierbrea/eslint-plugin-boundaries/tree/master/.agents/skills/repo-architecture into .gemini/skills/repo-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install javierbrea/eslint-plugin-boundaries repo-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add javierbrea/eslint-plugin-boundaries --skill repo-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/javierbrea/eslint-plugin-boundaries.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/repo-architecture .github/skills/repo-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "repo-architecture" agent skill from https://github.com/javierbrea/eslint-plugin-boundaries/tree/master/.agents/skills/repo-architecture into .github/skills/repo-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add javierbrea/eslint-plugin-boundaries --skill repo-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install javierbrea/eslint-plugin-boundaries repo-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javierbrea/eslint-plugin-boundaries.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/repo-architecture .opencode/skills/repo-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "repo-architecture" agent skill from https://github.com/javierbrea/eslint-plugin-boundaries/tree/master/.agents/skills/repo-architecture into .opencode/skills/repo-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "repo-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
repo-architecture- GitHub stars
- 997
- Token cost
- ~1.3k tokens
- SKILL.md length
- 570 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Cross-cutting architecture reference for the eslint-plugin-boundaries monorepo — the dependency graph between packages, the Nx target graph, and the release flow.
- Tasks that involve Linting and formatting
- SKILL.md covers Where the rules live, Component map, Dependency graph and direction and Nx target graph, plus 1 more section
- Calls pnpm
- Tasks that involve Monorepo tooling
What it does
Repo Architecture is an agent skill from javierbrea/eslint-plugin-boundaries. Cross-cutting architecture reference for the eslint-plugin-boundaries monorepo — the dependency graph between packages, the Nx target graph, and the release flow. Load before designing or reviewing anything that spans more than one project.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting and Monorepo tooling. It works with ESLint and TypeScript. The repository describes itself as: Enforce architectural boundaries in your JavaScript and TypeScript projects. The licence is MIT.
When your agent uses it
- Tasks that involve Linting and formatting
- Tasks that involve Monorepo tooling
Example prompts
- “/repo-architecture”
What it can do on your machine
Read from SKILL.md and the folder at commit 50f2d31. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Repo Architecture loads about 1.3k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 570 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from javierbrea/eslint-plugin-boundaries at commit 50f2d31, republished under its MIT licence (© javierbrea). 570 words, ~1,331 tokens.
Download SKILL.mdSave it as
.claude/skills/repo-architecture/SKILL.md (or your agent's skills folder).- name
- repo-architecture
- description
- Cross-cutting architecture reference for the eslint-plugin-boundaries monorepo — the dependency graph between packages, the Nx target graph, and the release flow. Load before designing or reviewing anything that spans more than one project.
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
<project>/AGENTS.mdis the source of truth for that project — everypackages/*,examples/*,support/*, andtest/*directory. Read the one(s) touching the area before making a judgment call.- Per-file conventions live in
.agents/rules/[rule-name].md. Read them when you need to know what's expected in a given file type — e.g..agents/rules/eslint-rule-authoring.mdwhen adding a rule toeslint-plugin. packages/eslint-plugin/eslint.config.mjsandpackages/elements/eslint.config.mjsare where each package's internal layering becomes mechanically enforced (both dogfoodeslint-plugin-boundarieson themselves) — treat them as ground truth over any prose description when the two disagree.- Long-form reference docs (per-rule documentation, ADRs) live in
docs/andpackages/website/docs/— non-normative companions: rules/skills win on disagreement.
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; version kept in lockstep with eslint-plugin |
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-e2eand bothexamples/*depend on the builteslint-plugin(via Nx'sdependsOn: ["build"]/["^build"], not 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) but has no Nx build dependency on it — 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.
Show full SKILL.md (212 more words)Show less
Nx target graph
Standardized target names (lint, check:types, check:spell, build, test:unit, test:mutation, test:e2e, check:all) are defined with common defaults in nx.json's targetDefaults, and overridden per-project in project.json only where a project's needs diverge — see .agents/rules/nx-project-config.md for what that override mechanism looks like and why it matters for caching.
The one non-obvious edge: eslint-plugin and elements both make their own lint target depend on build, because each dogfoods its own compiled output (eslint-local-rules.js requires ./dist/index.js) to lint its own source. A stale dist/ means a lint run's boundary checks are stale too — Nx handles this automatically via the dependsOn, but be aware of it when reasoning about why a lint result did or didn't change.
Release flow
Each package is versioned independently under semver — see .agents/rules/changelog-and-versioning.md. At a high level: release is the default PR base branch (PRs squash-merge into it); a maintainer periodically opens a PR from release to main (merge-commit strategy) to cut a release, tags each modified package as <package-name>-vX.Y.Z, and publication to npm happens automatically once a GitHub release is created. Full detail lives in .github/CONTRIBUTING.md.
Known inconsistency, not yet resolved: .github/CONTRIBUTING.md and nx.json's defaultBase disagree on the stable branch name (main vs master), and README.md/.github/PULL_REQUEST_TEMPLATE.md mostly link via master. Don't silently pick one when it matters — flag it.
© javierbrea, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/repo-architecture of javierbrea/eslint-plugin-boundaries.
Open the folder on GitHubat commit 50f2d31
Compare with similar skills
Repo Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Repo Architecture this skilljavierbrea/eslint-plugin-boundaries | 997 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Create Saleor Packagesaleor/apps | 162 | — | ~608 | Automated safety check: Pass | Custom licence | |
| Vscode MCP Architecturetjx666/vscode-mcp | 105 | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Typescript Tooling MigrationArize-ai/phoenix | 12k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| AntfuJetBrains/skills | 366 | 4 repos | ~1k | Automated safety check: Pass | None | |
| Monorepoavibebuilder/claude-prime | 120 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Vscode MCP Architecture
tjx666/vscode-mcp
VSCode MCP Bridge project architecture — current monorepo layout, IPC/EventDispatcher flow, per-workspace socket discovery, MCP/CLI adapters, tool filtering, and VSCode extension services.
Typescript Tooling Migration
Arize-ai/phoenix
Migrate or upgrade TypeScript tooling in the Phoenix monorepo.
- Official
Antfu
JetBrains/skills
Anthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects.
Monorepo
avibebuilder/claude-prime
MUST use for ANY query mentioning packages, monorepo, workspace, catalog, turbo, turborepo, or pnpm in a multi-package context.
- Official
Eslint Migrate Options
biomejs/biome
A skill your agent uses when biome migrate eslint must preserve configurable ESLint rule options through source-option models, Biome conversions, typed rule variants, and migration fixtures.
More from javierbrea/eslint-plugin-boundaries
Boundaries Architect
javierbrea/eslint-plugin-boundaries
Act as a software architect: analyze a repository's folder structure and cross-file import dependencies, detect its architectural pattern, design element/file boundaries with the user, and configure…
Review PR
javierbrea/eslint-plugin-boundaries
Review a GitHub pull request from three perspectives — functional fit against its linked issue, code correctness/quality, and architectural boundaries — then post a single GitHub review: one general…
Unit Testing
javierbrea/eslint-plugin-boundaries
Complete or maximize unit test coverage for a specific TypeScript file in this repo.
Create PR
javierbrea/eslint-plugin-boundaries
Create or update a GitHub pull request for the current branch from the repository's fixed PR template (.github/PULLREQUESTTEMPLATE.md) and the branch changes.
Related
Works with
Categories
Questions about Repo Architecture
What does Repo Architecture do?
Cross-cutting architecture reference for the eslint-plugin-boundaries monorepo — the dependency graph between packages, the Nx target graph, and the release flow. Repo Architecture is an agent skill from javierbrea/eslint-plugin-boundaries. Cross-cutting architecture reference for the eslint-plugin-boundaries monorepo — the dependency graph between packages, the Nx target graph, and the release flow.
When should I use Repo Architecture?
Repo Architecture fits situations like: tasks that involve Linting and formatting; tasks that involve Monorepo tooling.
How do I install Repo Architecture in Claude Code?
Run `npx skills add javierbrea/eslint-plugin-boundaries --skill repo-architecture -a claude-code`. Or copy the skill folder (.agents/skills/repo-architecture in javierbrea/eslint-plugin-boundaries) into .claude/skills/repo-architecture in your project. Claude Code loads it when a task matches its description.
How do I install Repo Architecture in Codex?
Run `npx skills add javierbrea/eslint-plugin-boundaries --skill repo-architecture -a codex`. Or copy the skill folder (.agents/skills/repo-architecture in javierbrea/eslint-plugin-boundaries) into .agents/skills/repo-architecture in your project. Codex loads it when a task matches its description.
Can I use Repo Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add javierbrea/eslint-plugin-boundaries --skill repo-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repo-architecture, .gemini/skills/repo-architecture, .github/skills/repo-architecture and .opencode/skills/repo-architecture in your project.
What does Repo Architecture need to run?
Going by SKILL.md and its folder, Repo Architecture needs the command-line tools its instructions call (pnpm).
Does Repo Architecture access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Repo Architecture safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Repo Architecture use?
Repo Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Repo Architecture use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Repo Architecture?
Skills that share tags, products or a category with Repo Architecture: Create Saleor Package (saleor/apps, 162 stars), Vscode MCP Architecture (tjx666/vscode-mcp, 105 stars), Typescript Tooling Migration (Arize-ai/phoenix, 12k stars) and Antfu (JetBrains/skills, 366 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Repo Architecture?
javierbrea (a GitHub user) maintains it in javierbrea/eslint-plugin-boundaries, which has 997 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.
Source: javierbrea/eslint-plugin-boundaries on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.