Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions construct.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@ schema_version: 3
name: Artisan
slug: artisan
version: 1.0.0
description: "Turns 'this feels off' into an engineering specification. Decomposes interfaces into structure, motion, and material β€” oklch deltas, spring constants, spacing rhythms. Craft precedes judgment."
short_description: "Taste made measurable"
description: "Turns 'this feels off' into a design specification. Breaks down UI into color, animation, and spacing β€” then gives you the exact values. 14 skills covering design feedback analysis, animation patterns, component architecture, and accessibility audits."
short_description: "Turn UI feel into design specs"
domain:
- design
author: 0xHoneyJar
Expand Down Expand Up @@ -56,6 +56,17 @@ events:
consumes:
- event: forge.observer.canvas_created
description: "Observer canvases inform taste token decisions"
capabilities:
model_tier: sonnet
danger_level: moderate
effort_hint: medium
downgrade_allowed: false
execution_hint: sequential
requires:
native_runtime: true
tool_calling: true
thinking_traces: false
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Advertise required thinking traces at construct level

If the 037/Echelon pipeline now gates construct admission on construct.yaml capabilities, this top-level thinking_traces: false will misclassify Artisan as runnable on trace-less runtimes even though /envisioning-direction explicitly requires traces in skills/envisioning-direction/index.yaml:55-59. In that environment the construct will be accepted, but invoking that skill will fail or be silently degraded because the pack metadata under-reports one of its contained skills' hard requirements.

Useful? React with πŸ‘Β / πŸ‘Ž.

vision: false
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Mark the construct as vision-capable

Several shipped skills declare vision: true (skills/iterating-visuals/index.yaml:56-60, skills/decomposing-feel/index.yaml:54-58, skills/styling-material/index.yaml:50-54, and skills/surveying-patterns/index.yaml:50-54), so publishing the pack-level manifest with vision: false under-advertises a hard runtime dependency. Any scheduler that trusts only construct.yaml can now place Artisan on a non-vision model, after which those screenshot- and image-based workflows are guaranteed to be unavailable even though the construct was accepted.

Useful? React with πŸ‘Β / πŸ‘Ž.

type: skill-pack
composition_paths:
reads:
Expand Down
Loading