Pattern library
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 pattern-libraryAssembled 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
Retrieve applicable Alexander-style patterns (context/problem/solution) for a design brief BEFORE generating form — courtyard, light on two sides, entrance transition, prospect/refuge, six-foot balcony, and per-domain equivalents. Trigger: "what patterns apply", or invoked by brief-to-blueprint step 3.
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.6 KB, as published. Nobody here has run it
pattern-library
When to use
Before massing/layout generation for any architecture, interior, landscape, or game-level brief. Patterns are the generator's representation (principle P5).
What it does
- Parse the brief's context: climate zone, lot depth, privacy needs, program, play-type mix (for games: agôn/alea/mimicry/ilinx).
- Match against the pattern set in
principles/DESIGN_PRINCIPLES.mdand the 300-year digest (courtyard for deep plans, lightwell, entrance transition, prospect/refuge for both rooms and game arenas). - Return each match as context / problem / solution / source, plus explicit conflicts between selected patterns.
Example
"Brief: narrow 8m-wide row-house lot, hot-dry climate, family of 5" → courtyard (light/air/privacy in one move), thick-wall thermal mass, sheltered entrance transition.
Verification (eval-with-teeth)
Every returned pattern must cite its survival evidence (source + years in use)
from research/last300years/DIGEST.md. A pattern without lineage is an
invention, not a retrieval — label it PROPOSED, never mix it into the canon.
Safety
Patterns are priors, not mandates; site and code override.
Cross-runtime
Prompt-only.