Design skills only
Turn on what ships decks and images. Keep motion skills off this profile.
Theory lives in Harness 09
What a skill is, progressive disclosure, and hub scans are Open Harness 09. This module only filters the skill list for a design profile, studio, not VFX house.
A design profile that loads HyperFrames or Remotion skills will spend tokens deciding whether to animate a slide. That is the wrong failure mode for Course 02.
Harness 09: skills theory →| Keep / install for Design | Disable / Open Video later |
|---|---|
| Open Design, deck, frontend, brand, image helpers you use | HyperFrames, Remotion, Manim, video orchestrators |
| Export / PDF helpers if present | Full film / avatar pipelines |
Why filter before you feel pain
Every enabled skill is a candidate the model may load. Noise skills raise cost and produce “I made a motion brief” when you asked for a PPTX. Filtering is studio hygiene, not purism.
- One profile for static design; another later for motion if you need both.
- Name the skill in the prompt when you want it: “Use the Open Design skill; write under design-lab/.”
- If a skill rewrites brand outside DESIGN.md, disable it or pin your brand file first.
Audit steps (filter only)
skills-audit.md template
# skills-audit.md
Profile: [...]
Date: [...]
Enabled (design):
- name: why
Disabled (motion / noise):
- name: why
Proof run:
- skill: [...]
- file written: design-lab/[...]
A short skills-audit.md lists enabled design-related skills and explicitly disabled video/motion skills; you ran one task that named a design skill on purpose.
Stored on this device only, not sent anywhere.