Layer Audit
Testing & Qualitylayer-auditLayer Audit is an Agent Skill for testing & quality published in the Comfy-Org/ComfyUI_frontend repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Detect violations of the layered architecture import rules (base -> platform -> workbench -> renderer). Runs ESLint with the import-x/no-restricted-paths rule and generates a grouped report.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/Comfy-Org/ComfyUI_frontend/blob/HEAD/.claude/skills/layer-audit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/layer-audit, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Layer Architecture Audit
Finds imports that violate the layered architecture boundary rules enforced by import-x/no-restricted-paths in eslint.config.ts.
Layer Hierarchy (bottom to top)
renderer (top -- can import from all lower layers)
^
workbench
^
platform
^
base (bottom -- cannot import from any upper layer)
Each layer may only import from layers below it.
How to Run
# Run ESLint filtering for just the layer boundary rule violations
pnpm lint 2>&1 | grep 'import-x/no-restricted-paths' -B1 | head -200
To get a full structured report, run:
# Collect all violations from base/, platform/, workbench/ layers
pnpm eslint src/base/ src/platform/ src/workbench/ --no-error-on-unmatched-pattern --rule '{"import-x/no-restricted-paths": "warn"}' --format compact 2>&1 | grep 'no-restricted-paths' | sort
How to Read Results
Each violation line shows:
- The file containing the bad import
- The import path crossing the boundary
- The message identifying which layer pair is violated
Grouping by Layer Pair
After collecting violations, group them by the layer pair pattern:
| Layer pair | Meaning |
|---|---|
| base -> platform | base/ importing from platform/ |
| base -> workbench | base/ importing from workbench/ |
| base -> renderer | base/ importing from renderer/ |
| platform -> workbench | platform/ importing from workbench/ |
| platform -> renderer | platform/ importing from renderer/ |
| workbench -> renderer | workbench/ importing from renderer/ |
When to Use
- Before creating a PR that adds imports between
src/base/,src/platform/,src/workbench/, orsrc/renderer/ - When auditing the codebase to find and plan migration of existing violations
- After moving files between layers to verify no new violations were introduced
Fixing Violations
Common strategies to resolve a layer violation:
- Move the import target down -- if the imported module doesn't depend on upper-layer concepts, move it to a lower layer
- Introduce an interface -- define an interface/type in the lower layer and implement it in the upper layer via dependency injection or a registration pattern
- Move the importing file up -- if the file logically belongs in a higher layer, relocate it
- Extract shared logic -- pull the shared functionality into
base/or a shared utility
Reference
| Resource | Path |
|---|---|
| ESLint config (rule definition) | eslint.config.ts |
| Base layer | src/base/ |
| Platform layer | src/platform/ |
| Workbench layer | src/workbench/ |
| Renderer layer | src/renderer/ |