review-architecture

A review guide for checking pull requests against pascalorg/editor’s architecture rules. A pull request is a proposed code change submitted for review before it is merged.

In plain words
What is it for?
Use it to review a pull request, branch, or current changes for correct package placement, component composition, renderer and system responsibilities, and proper use of project hooks.
Why use it?
It helps catch changes that cross package boundaries, use outdated dispatch methods, mix editor and viewer responsibilities, or break the project’s rules for new components.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/pascalorg/editor/review-architecture
Any agent
npx skills add pascalorg/editor --skill review-architecture
Clone the repo
git clone --depth 1 https://github.com/pascalorg/editor

Made for: Claude Code, Codex.

Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,111 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00097 $0.07111
Opus 5 $0.00048 $0.03556
Sonnet 5 $0.00019 $0.01422
Haiku 4.5 $0.00010 $0.00711

Measured 2d ago against content hash f9cf2ebe4c12, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

review-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/review-architecture/SKILL.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Architectural review for Pascal PRs. The user will provide a PR URL, branch name, or ask to review the current branch.

1. Load the rules (required — do not skip)

Read these before reviewing any diff. They are the source of truth, not your training data:

  • wiki/architecture/layers.md
  • wiki/architecture/systems.md — core systems vs viewer systems, what each may do
  • wiki/architecture/renderers.md — renderer responsibilities and prohibitions
  • wiki/architecture/tools.md — editor tools live only in apps/editor/components/tools/ or packages/nodes/src/<kind>/
  • wiki/architecture/viewer-isolation.md — viewer must stay editor-agnostic
  • wiki/architecture/node-definitions.md — the three-checkbox composition model (geometry / renderer / system)
  • wiki/architecture/plugin-authoring.md — public contract for external node packs

Required on every review. Read the remaining pages on demand when the diff touches their subject area:

  • wiki/architecture/selection-managers.md
  • wiki/architecture/scene-registry.md
  • wiki/architecture/spatial-queries.md
  • wiki/architecture/node-schemas.md
  • wiki/architecture/inspector-field-limits.md — no arbitrary min/max on dimension fields. Read whenever the diff adds or edits parametrics.ts, a kind panel.tsx, or <SliderControl> bounds.
  • wiki/architecture/events.md
  • wiki/architecture/interaction-scope.md — the interaction state machine + the unified snapping/modifier convention. Read whenever the diff touches a tool, a move-tool / selection / endpoint / reshape file, lib/interaction/**, lib/snapping-mode.ts, or use-interaction-scope.

If anything in the diff looks like a new dispatch surface or registry concept, also skim the live charter at plans/editor-node-registry.md (in the private-editor repo) — it owns the current contract and which kind sits at which migration stage.

2. Fetch the diff

# If the user gave a PR URL or number:
gh pr diff <pr-number-or-url>

# If reviewing the current branch:
git diff main...HEAD

Read the full file on GitHub · 180 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 180 lines · 97 tokens per session scan A f9cf2ebe4c12

Subscribe to this mod's changes

review-architecture is a skill published in the GitHub repository pascalorg/editor (21,769 stars, last pushed 4d ago), licensed MIT. It adds 97 tokens to every session and 7,111 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

fy_layout

Use when doing construction site layout planning with the FeiYang LightCAD platform — fence, lawn, foundation pit, road, prefab house 2D/3D modeling. FYLayout: construction site layout secondary development plugin for LightCAD/LightBIM.

znlgis/opengis-skills · 56 tokens

freecad

Use when doing parametric 3D CAD modeling, BIM/architectural design, FEM simulation, CAM toolpath generation, or robot simulation with Python scripting. FreeCAD: the leading open-source parametric 3D CAD with Sketcher, Part, PartDesign, Arch, CAM, and FEM workbenches.

znlgis/opengis-skills · 67 tokens

FluidCAD

Workflow and best practices for designing parts in FluidCAD through its MCP server. Use this skill whenever the user wants to model, design, or modify any part in FluidCAD, whenever they mention FluidCAD, a .fluid.js file, or ask for CAD/parametric modeling work that involves sketches, extrudes, cuts, fillets…

Fluid-CAD/FluidCAD · 131 tokens

FluidCAD-from-drawing

Turning a 2D engineering drawing into a parametric FluidCAD model. Use this skill whenever the user supplies a drawing, blueprint, dimension sheet, hand sketch, screenshot, PDF, or photo of a part and wants it modeled — "model this", "build this part", "make this in CAD", "here's the drawing". Trigger it alongside the…

Fluid-CAD/FluidCAD · 114 tokens

ara3d-sdk

Use when processing AEC/BIM 3D data in .NET 8 — mesh generation and transformation, SIMD-accelerated math, IFC/STEP/PLY to glTF/GLB/VIM conversion, plugin development. Ara3D-SDK: high-performance .NET 3D geometry and BIM library suite.

znlgis/opengis-skills · 70 tokens

elements

Use when generating building information models (BIM) programmatically in C#/.NET — wall, beam, column, floor creation, geometry kernel (BREP/CSG), glTF/IFC/JSON serialization, MEP systems, spatial grids. Hypar Elements: the smallest useful BIM — a cross-platform C# library for creating building elements without…

znlgis/opengis-skills · 81 tokens