Blueprint validate
Validate a blueprint against the survival-tested principles checklist: anthropometric clearances, modular grid conformance, daylight orientation, shearing-layer separation, open-system interfaces. Trigger: "review this floor plan", "is this layout sane", "principles check". NOT code-compliance certification.From its SKILL.md
npx -y skills add wjlgatech/design-anything --skill blueprint-validateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as CC-BY-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.7 KB, 323 tokens by cl100k_base, as published. Nobody here has run it
blueprint-validate
When to use
A floor plan, room layout, or building blueprint exists (image, IFC, or parametric source) and needs a principled review before deeper investment.
What it does
Walks principles/DESIGN_PRINCIPLES.md P1–P13 as a checklist against the
blueprint, scoring each as PASS / FAIL / NOT-MEASURED:
- Clearances vs Neufert-class tables (doors ≥ 800mm, corridors ≥ 900mm, counter work zones, stair geometry).
- Module grid: % of dimensions on the declared grid (target ≥ 90%).
- Daylight: every habitable room has an orientation-justified window.
- Layers: services accessible without demolishing structure.
- Open system: standard parts (windows/doors/fasteners) vs proprietary.
Example
Ask: "validate examples/planter against P2/P3" or hand a floor-plan image and the declared module (e.g. 100mm) and printer/process.
Verification (eval-with-teeth)
The report must list every principle with a verdict and evidence line; NOT-MEASURED items are excluded from the score and named in the summary — a blocking review cannot pass with unmeasured blocking items. An overall score with no per-item evidence is an invalid output.
Safety
This is a design review, not a permit document. Jurisdiction codes override everything here.
Cross-runtime
Prompt-only; no execution required.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.