Brief to blueprint
Any design intent in (text, picture) → execution-ready 3D blueprint out — construction- and 3D-print-verified. Game design · simulation · architecture (3DCP+AI) · interior · landscape.
npx -y skills add wjlgatech/design-anything --skill brief-to-blueprintAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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 author says it does
Copied from the file, not written here
Compile a messy design brief (text and/or picture) into a structured blueprint plan: target (print/construction/game), dimensions, constraints, applicable patterns, and the ready-gate it must pass. Trigger: "design me a ...", "turn this sketch into a model", "I want a 3D-printable ...". NOT for photoreal rendering or structural engineering sign-off.
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
2.1 KB, as published. Nobody here has run it
brief-to-blueprint
When to use
The user states a design intent in words or drops an image, and wants a path to a buildable artifact — not a mood board.
What it does
- Absorb the brief; reflect it back in ≤6 lines (object, target, size, material/process, must-haves). Never silently drop a stated constraint.
- Declare the target — 3D-print | construction | game/sim — and load the
matching gate spec from
pipeline/. - Retrieve patterns (skills/pattern-library) and constraint tables (anthropometrics, module grid, DfAM rules for the declared process).
- Emit the composition: deterministic parametric source (Python like
examples/planter/generate.py, OpenSCAD, or CadQuery) with the brief's parameters at the top — never an opaque mesh. - Gate it: generate geometry and run
pipeline/ready_gate.py. Iterate until READY or report the honest failure.
Example
# brief: "a desk planter, 120x80x60mm, 3mm walls, my printer is 220x220"
python3 examples/planter/generate.py out.stl
python3 pipeline/ready_gate.py out.stl --bed 220x220x250 --min-feature 3.0
Verification (eval-with-teeth)
Success may be declared ONLY when the gate exits 0:
python3 pipeline/ready_gate.py out.stl --min-feature <declared-wall> && echo VERIFIED
No gate pass ⇒ the skill reports NOT READY with the failing gate's evidence.
Safety
Outputs are design aids, not engineering certifications. Construction-target outputs must carry: "checklist ≠ structural engineer's stamp".
Cross-runtime
Pure prompts + stdlib Python; no runtime-specific APIs.