Scoville Design Anti-AI-Slop
Make visual decisions from the subject and task. Composition foundations live
here; load specialists only for an open decision or a needed method.
Mode, authority and ownership
| Mode |
Work |
| Generate |
Develop the requested concept and artifact from supplied facts. |
| Critique |
Inspect and report read-only; do not redesign to satisfy a generation routine. |
| Repair |
Change only the authorised artifact, scope and shared consumers. Inherit valid settled decisions. |
Design owns concept, art direction, visual hierarchy, typography, composition,
spacing, responsive intent, corporate-design/visual-identity definition and critique. Preserve incumbent
systems and protected content. Corporate Identity strategy, culture, behaviour,
naming and verbal identity remain authorised upstream inputs. Never invent
facts, approval, rights, strategy or deliverables.
With optional active-applicable UI, Design defines and judges; that partner
implements framework/component mechanics, states, semantics, accessibility,
responsiveness and runtime proof. Use Coordination for an actual partner exchange
(including Scribe for wording fidelity). Never require or simulate another Skill;
without a partner, handle authorised work directly within the same ownership floors.
Finding another Skill in this family does not make it installed, active, applicable, or required. If that Skill is absent or inactive, ignore it. Do not require, install, simulate, or reimplement it. If it is active and applicable, let it handle only its stated concern while this Skill continues its own authorized work. An opt-out applies only to the Skill the user excluded, not to independently authorized work.
Family owners, in suite order:
scoville-brainstorm: deliberate divergence before selection.
scoville-research: source-backed research and synthesis.
scoville-code-anti-ai-slop: engineering scope, implementation, risk, and validation.
scoville-design-anti-ai-slop: visual definition, art direction, critique, and repair.
scoville-ui-anti-ai-slop: framework UI implementation, accessibility mechanics, and rendered proof.
scoville-scribe-anti-ai-slop: wording, terminology, meaning, and source fidelity.
scoville-plan: durable Plans, Work Items, Decisions, and lifecycle state.
scoville-handoff: active-work transfer.
Studio workflow
Working notes are not extra deliverables. Start with
concern | owner | decision/status | evidence; expand only material open fields.
Carry source authority, protected constraints and unknowns between phases.
Approval never means verification.
| Stage |
Action |
Continue when |
| Frame and route |
Establish purpose, audience, message, real content, medium, constraints and unknowns; inspect supplied work. Load specialists through the Direct expert index for decisions or methods needed now. |
Selected owners match their Load when scope. Typography may lead exploration; later checks alone do not require early specialist loading. |
| Explore or diagnose |
Explore subject-grounded ideas and visual treatments at comparable rough fidelity when direction is open. Otherwise locate concerns without reopening settled direction. |
Judge the rough's communication and character; choices may be provisional. A useful default or quiet utility direction is valid; a new mechanism is not required. |
| Consolidate |
Select the direction, then commit shared spatial values and type roles before extending repetition. |
Real-content fit supports the system; retain variants for a visible contribution to hierarchy, reading or overall character. |
| Execute |
Build, inspect or repair in authorised scope; mark placeholders and constructed material. |
The actual requested artifact is available for its owner's renderer. |
| Inspect |
With brief and constraints visible, record the whole's communication, hierarchy and character before consulting design rationale; in self-review defer justification, not knowledge. Then inspect material groups and native details and measure critical relations on that version. |
Reconcile rationale with the recorded observation; unsupported contradictions stay disputed, expressive departures use existing exception criteria. Local passes do not clear global findings. Both lanes cover critical relations or missing proof stays explicit. Screenshot creation is not viewing. |
| Resolve and deliver |
Identify successful character, classify the failure, repair the parent and rerender affected consumers/neighbours; repeat affected checks and view the final whole again. |
Required relations and material whole-view findings are resolved, or report a real authority/evidence/resource limit as partial. Removing useful expression without a supported cause is a regression; never erase a failed or omitted relation. |
After two coherent unsuccessful passes, reassess cause and method; continue while
evidence supports progress, change approach on repeated failure. There is no
one-correction cap, required cosmetic repair or render quota. A clean first
render can pass after applicable checks. Unknown evidence permits safe source
work but not dependent acceptance.
When concept is open, let a verified subject fact visibly shape a decision
(hierarchy, type, colour, image or motion); record fact → decision. If swapping
logo and nouns serves unrelated subjects unchanged, examine the mechanism.
Style is a domain, not a mode. Preserve useful character; novelty is not required.
At consolidation or inspection, if a device adds unrest or its contribution is
unclear, briefly compare the whole without it. Retain it when grouping, rhythm
or expression visibly benefits. Keep unrelated choices fixed; this is a targeted
probe, not a required test of every mark or a preference for fewer elements.
Composition: decide, bind, inspect
Apply this foundation in every Design task. Steps 1 and 2 guide exploration with
provisional choices; consolidate before extending repetition. Steps 3 through 6 govern
inspection and final acceptance, not advance paperwork for each rough variant.
Keep content and binding constraints throughout; address visible failures when
found. Early targeted checks may inform an uncertain direction. Small repairs
scope work to affected regions and shared consumers, without redesigning settled work.
- Order before coordinates. Establish entry, subordinate reads and action.
Group by meaning; use proximity, similarity, enclosure, connection and
continuity as potentially conflicting cues. Choose spacing by job:
within-group, between-group, section, caption and edge. Give negative space
a purpose (separate, frame, pace, focus); neither empty nor dense is inherently good.
- Commit a usable system. Derive axes, columns, spans, gutters and shared
values from real content, medium and incumbent systems. Place the longest
required unit and representative repeated unit before multiplying them.
Equal roles reuse values; variation needs a role, rhythm or optical reason.
Set type roles as a coupled size/weight/measure/leading system, not isolated
sizes. Grid choices can change after a fit check; no universal scale, ratio,
column count or font-size count applies.
- Discover before choosing checks. Map panels, text, artwork/icons and
nested/repeated groups. Include the entry, dominant recognizable object and
dense text group when present and material; inspect a title with any rule or
eyebrow that frames it. For a motif joining or interrupting a drawn rule, inspect
both outer junctions and internal gaps as one unit, against intended overlap
or separation. Observe grouping before measuring. Cross-check
editable source/layers, including visible use/image instances, not unused
definitions. Enclosed controls, repeated groups and elements near frame edges
each need a disposition. Include neighbours and both outside endpoints of
repeated rows/columns. An empty helper queue does not close this map.
- Bind each material relation. Use
object → actual region/anchor | intent + target + basis | owner | metric + view | status.
Start unverified. Basis is supplied, incumbent, measured, inferred,
provisional or unknown; unknown is not zero. Preserve candidates or reasoned
dispositions rather than selecting them again from memory. A DOM parent,
growing group box or nearest rectangle is not automatically an enclosure.
Follow every relevant nested drawn boundary. Enclosure, backdrop and bleed
are distinct roles. For repeated groups check internal rhythm and both
external anchors; if no common span applies, retain its visible/source basis.
- Match proof to intent. Declare axis and reference (edge, baseline,
geometric or optical centre) before measuring. A one-line button/pill/badge
starts with a centring hypothesis unless its system supports another
alignment. Text plus icon/arrow is one compound group. A minimum-inset pass
proves neither centring nor sufficient space. Inspect effective paint,
strokes, corners and glyph ink; boxes are not optical mass. Choose tolerances
from scale and precision before results, in one coordinate space. Preserve
target and local region through repair; a larger container cannot close the
original failure. If intent changes, retain the old result and explain the
supported new hypothesis.
- Reconcile the final artifact. Pair actual whole/detail visual observations
and suitable measured results for every critical relation on the same final
source/render version. Detail crops must derive from that render; identify
it in working evidence (use hashes when files are available). Recheck changed
regions and neighbours, including artwork when text fits. Retain every
candidate's final disposition; uncovered, stale or unsupported checks remain open.
Load the Composition methods index entry only when an open relationship
needs a detailed discovery/measurement procedure or a diagnostic comparison,
and the method's required input is available. Discovery may precede binding;
measurement follows it. Small repair, mark and critique labels alone do not
trigger it. Without suitable inputs, record the missing proof, not a pass.
Acceptance and repair
| Final visual and suitable metric evidence for a critical relation |
Status |
| Both pass compatibly on the same version/local relation |
pass |
| A failure with no material lane contradiction |
fail |
| Pass/fail contradiction or unsupported intentional-exception rationale |
disputed |
| Missing, stale, wrong-region or unsupported evidence |
unverified |
| Neither lane applies, with a supported reason |
not-applicable |
A preferred idea may fail in execution: judge visible type, composition and
image craft, not its explanation. Keep content, execution and preference distinct;
missing feedback is not agreement and independent disagreement stays visible.
Diagnose in order: content/requirement → semantic order → container/measure →
grid/span → scale/density → crop/source → local optical correction. Stop at the
first supported cause; repair its canonical owner and inspect consumers. Do not conceal
failures through clipping, blanket centring, more whitespace, smaller type or
one-column stacking. Revert or narrow regressions. Cause may be confirmed,
inferred or unknown.
At acceptance, an exception needs supported intent/gain, protected communication/access floors,
counterstructure, cost and a falsifying observation. Compare a fair conventional
control when challenged; keep non-intervention variables constant, allowing the
repair's declared dependent effects. A plausible story after the fact is not
evidence. Never reclassify user-rejected overflow as intentional bleed. Source,
rights, consent and production constraints cannot become aesthetic exceptions.
Ordinary local exceptions stay with their specialist; Critique handles a separate
multi-domain lifecycle or challenged cross-domain exception.
Route and read only what applies
Use the Direct expert index. General composition foundations never require another
module. Specialists retain their geometry: packaging faces, mark contours,
chart encodings, map topology, responsive pressure and fixed-media structure.
Independent concerns still route: label appearance does not alone select
Information, but a contradicted value-to-position relation does; Wayfinding
does not settle map geometry; Mark does not reopen Brand/Concept unless open.
Brand also owns an authored icon-family or stroke system outside identity work.
Revisit routing when a new concern appears; no fixed module-count/token gate.
Verify received coverage before applying a selected source: numbered lines,
total, received and missing intervals. Recover missing or cut-through lines,
including intact adjacent lines; reconcile each file separately. Keep conflicting
returns and source order. An end marker is not proof of a complete middle.
Use the optional source reader or an equivalent.
Its header contains recovery details when transport fails. If coverage cannot
be recovered, carry the dependent concern unverified. Headings do not unload
context; split phases only for actual task/capacity needs. User/provider limits
and authorisation remain binding.
Proof ceiling
Distinguish binding constraints, evidence-bounded rules, conventions, heuristics,
preferences and exceptions. Numeric advice needs its population, language/script,
medium, task and override basis; one study or starting value is no universal law.
Render proof covers inspected appearance only. It requires a host capability
through which the agent actually views the rendered artifact or its image, such
as an image-viewing tool, a screenshot that the agent can open, or a supplied
render. Creating a screenshot file, reading its bytes or metadata, or inspecting
source alone is not viewing. Without such a capability, record every visual-lane
result as unverified and state that limit. Syntax, runtime, accessibility,
user research, rights, provider and physical acceptance are separate lanes.
Check current standards, law, licences and living-community claims when required;
if unavailable, mark unverified and stop at that authority boundary.
Terms
- Module / expert / leaf: one linked reference and its domain role, not a subagent.
- Owner: the person/domain authorised to change a field's decision or status.
- Observer: reports attributed effects without changing another owner's decision.
- Falsifier: the observation that would overturn a judgment or exception.
- Control: a fair comparison preserving unrelated conditions.
- Claim ceiling: the strongest claim the observed evidence actually supports.
Expert routing
SKILL.md itself is the Core. Load expert references only through the exact
links in the Direct expert index, never through a guessed Core file or transitive sibling loads.
Core or an active module may also link an optional packaged tool in scripts/; read or
execute that exact tool when needed. This exception does not load other experts.
Core or an active module may similarly link an exact declared teaching source
or render in examples/. Inspect only that named asset when it can resolve the
current decision; an example is neither a hidden module nor proof of the result.
modules.yaml is non-routed packaging/evaluation metadata, not another runtime
router. Repository tooling generates this index from its labels and paths and
checks for drift before packaging; runtime routing remains here in SKILL.md.
This installed snapshot does not itself attest that those development checks ran.
Neither the metadata nor the repository tools are runtime load targets.
Module Sources: IDs and the non-routed source index are provenance, not load instructions.
Runtime rules remain local and offline except an actually required source check.
1---2name: scoville-design-anti-ai-slop3description: Develop, critique, or repair visual concepts and artifacts through art direction, typography, composition, visual systems, and information graphics. Use when visual definition or judgment is the task. For framework UI implementation use scoville-ui-anti-ai-slop, and for WordPress plugin-owned wp-admin pages use wordpress-backend-ui. Excludes mechanical edits, rendering-only work, backend work, and prose.4compatibility: "Any Agent Skills host that can read references/ and examples/. Visual inspection needs an image or screenshot viewer provided by the host; without one, render checks stay unverified. Optional scripts/read-source.py needs Python 3. Web access only for standards, licence or living-community checks. Developed for Codex and Claude Code; other hosts untested."5metadata:6 source: https://skillmd.com/skills/benjaminstelzer/scoville-design-anti-ai-slop7---89# Scoville Design Anti-AI-Slop1011Make visual decisions from the subject and task. Composition foundations live12here; load specialists only for an open decision or a needed method.1314## Mode, authority and ownership1516| Mode | Work |17| --- | --- |18| Generate | Develop the requested concept and artifact from supplied facts. |19| Critique | Inspect and report read-only; do not redesign to satisfy a generation routine. |20| Repair | Change only the authorised artifact, scope and shared consumers. Inherit valid settled decisions. |2122Design owns concept, art direction, visual hierarchy, typography, composition,23spacing, responsive intent, corporate-design/visual-identity definition and critique. Preserve incumbent24systems and protected content. Corporate Identity strategy, culture, behaviour,25naming and verbal identity remain authorised upstream inputs. Never invent26facts, approval, rights, strategy or deliverables.2728With optional active-applicable UI, Design defines and judges; that partner29implements framework/component mechanics, states, semantics, accessibility,30responsiveness and runtime proof. Use Coordination for an actual partner exchange31(including Scribe for wording fidelity). Never require or simulate another Skill;32without a partner, handle authorised work directly within the same ownership floors.3334Finding another Skill in this family does not make it installed, active, applicable, or required. If that Skill is absent or inactive, ignore it. Do not require, install, simulate, or reimplement it. If it is active and applicable, let it handle only its stated concern while this Skill continues its own authorized work. An opt-out applies only to the Skill the user excluded, not to independently authorized work.3536Family owners, in suite order:3738- `scoville-brainstorm`: deliberate divergence before selection.39- `scoville-research`: source-backed research and synthesis.40- `scoville-code-anti-ai-slop`: engineering scope, implementation, risk, and validation.41- `scoville-design-anti-ai-slop`: visual definition, art direction, critique, and repair.42- `scoville-ui-anti-ai-slop`: framework UI implementation, accessibility mechanics, and rendered proof.43- `scoville-scribe-anti-ai-slop`: wording, terminology, meaning, and source fidelity.44- `scoville-plan`: durable Plans, Work Items, Decisions, and lifecycle state.45- `scoville-handoff`: active-work transfer.4647## Studio workflow4849Working notes are not extra deliverables. Start with50`concern | owner | decision/status | evidence`; expand only material open fields.51Carry source authority, protected constraints and unknowns between phases.52Approval never means verification.5354| Stage | Action | Continue when |55| --- | --- | --- |56| Frame and route | Establish purpose, audience, message, real content, medium, constraints and unknowns; inspect supplied work. Load specialists through the [Direct expert index](references/direct-expert-index.md) for decisions or methods needed now. | Selected owners match their Load when scope. Typography may lead exploration; later checks alone do not require early specialist loading. |57| Explore or diagnose | Explore subject-grounded ideas and visual treatments at comparable rough fidelity when direction is open. Otherwise locate concerns without reopening settled direction. | Judge the rough's communication and character; choices may be provisional. A useful default or quiet utility direction is valid; a new mechanism is not required. |58| Consolidate | Select the direction, then commit shared spatial values and type roles before extending repetition. | Real-content fit supports the system; retain variants for a visible contribution to hierarchy, reading or overall character. |59| Execute | Build, inspect or repair in authorised scope; mark placeholders and constructed material. | The actual requested artifact is available for its owner's renderer. |60| Inspect | With brief and constraints visible, record the whole's communication, hierarchy and character before consulting design rationale; in self-review defer justification, not knowledge. Then inspect material groups and native details and measure critical relations on that version. | Reconcile rationale with the recorded observation; unsupported contradictions stay disputed, expressive departures use existing exception criteria. Local passes do not clear global findings. Both lanes cover critical relations or missing proof stays explicit. Screenshot creation is not viewing. |61| Resolve and deliver | Identify successful character, classify the failure, repair the parent and rerender affected consumers/neighbours; repeat affected checks and view the final whole again. | Required relations and material whole-view findings are resolved, or report a real authority/evidence/resource limit as partial. Removing useful expression without a supported cause is a regression; never erase a failed or omitted relation. |6263After two coherent unsuccessful passes, reassess cause and method; continue while64evidence supports progress, change approach on repeated failure. There is no65one-correction cap, required cosmetic repair or render quota. A clean first66render can pass after applicable checks. Unknown evidence permits safe source67work but not dependent acceptance.6869When concept is open, let a verified subject fact visibly shape a decision70(hierarchy, type, colour, image or motion); record fact → decision. If swapping71logo and nouns serves unrelated subjects unchanged, examine the mechanism.72Style is a domain, not a mode. Preserve useful character; novelty is not required.7374At consolidation or inspection, if a device adds unrest or its contribution is75unclear, briefly compare the whole without it. Retain it when grouping, rhythm76or expression visibly benefits. Keep unrelated choices fixed; this is a targeted77probe, not a required test of every mark or a preference for fewer elements.7879## Composition: decide, bind, inspect8081Apply this foundation in every Design task. Steps 1 and 2 guide exploration with82provisional choices; consolidate before extending repetition. Steps 3 through 6 govern83inspection and final acceptance, not advance paperwork for each rough variant.84Keep content and binding constraints throughout; address visible failures when85found. Early targeted checks may inform an uncertain direction. Small repairs86scope work to affected regions and shared consumers, without redesigning settled work.87881. **Order before coordinates.** Establish entry, subordinate reads and action.89 Group by meaning; use proximity, similarity, enclosure, connection and90 continuity as potentially conflicting cues. Choose spacing by job:91 within-group, between-group, section, caption and edge. Give negative space92 a purpose (separate, frame, pace, focus); neither empty nor dense is inherently good.932. **Commit a usable system.** Derive axes, columns, spans, gutters and shared94 values from real content, medium and incumbent systems. Place the longest95 required unit and representative repeated unit before multiplying them.96 Equal roles reuse values; variation needs a role, rhythm or optical reason.97 Set type roles as a coupled size/weight/measure/leading system, not isolated98 sizes. Grid choices can change after a fit check; no universal scale, ratio,99 column count or font-size count applies.1003. **Discover before choosing checks.** Map panels, text, artwork/icons and101 nested/repeated groups. Include the entry, dominant recognizable object and102 dense text group when present and material; inspect a title with any rule or103 eyebrow that frames it. For a motif joining or interrupting a drawn rule, inspect104 both outer junctions and internal gaps as one unit, against intended overlap105 or separation. Observe grouping before measuring. Cross-check106 editable source/layers, including visible use/image instances, not unused107 definitions. Enclosed controls, repeated groups and elements near frame edges108 each need a disposition. Include neighbours and both outside endpoints of109 repeated rows/columns. An empty helper queue does not close this map.1104. **Bind each material relation.** Use111 `object → actual region/anchor | intent + target + basis | owner | metric + view | status`.112 Start unverified. Basis is supplied, incumbent, measured, inferred,113 provisional or unknown; unknown is not zero. Preserve candidates or reasoned114 dispositions rather than selecting them again from memory. A DOM parent,115 growing group box or nearest rectangle is not automatically an enclosure.116 Follow every relevant nested drawn boundary. Enclosure, backdrop and bleed117 are distinct roles. For repeated groups check internal rhythm and both118 external anchors; if no common span applies, retain its visible/source basis.1195. **Match proof to intent.** Declare axis and reference (edge, baseline,120 geometric or optical centre) before measuring. A one-line button/pill/badge121 starts with a centring hypothesis unless its system supports another122 alignment. Text plus icon/arrow is one compound group. A minimum-inset pass123 proves neither centring nor sufficient space. Inspect effective paint,124 strokes, corners and glyph ink; boxes are not optical mass. Choose tolerances125 from scale and precision before results, in one coordinate space. Preserve126 target and local region through repair; a larger container cannot close the127 original failure. If intent changes, retain the old result and explain the128 supported new hypothesis.1296. **Reconcile the final artifact.** Pair actual whole/detail visual observations130 and suitable measured results for every critical relation on the same final131 source/render version. Detail crops must derive from that render; identify132 it in working evidence (use hashes when files are available). Recheck changed133 regions and neighbours, including artwork when text fits. Retain every134 candidate's final disposition; uncovered, stale or unsupported checks remain open.135136Load the **Composition methods** index entry only when an open relationship137needs a detailed discovery/measurement procedure or a diagnostic comparison,138and the method's required input is available. Discovery may precede binding;139measurement follows it. Small repair, mark and critique labels alone do not140trigger it. Without suitable inputs, record the missing proof, not a pass.141142## Acceptance and repair143144| Final visual and suitable metric evidence for a critical relation | Status |145| --- | --- |146| Both pass compatibly on the same version/local relation | pass |147| A failure with no material lane contradiction | fail |148| Pass/fail contradiction or unsupported intentional-exception rationale | disputed |149| Missing, stale, wrong-region or unsupported evidence | unverified |150| Neither lane applies, with a supported reason | not-applicable |151152A preferred idea may fail in execution: judge visible type, composition and153image craft, not its explanation. Keep content, execution and preference distinct;154missing feedback is not agreement and independent disagreement stays visible.155156Diagnose in order: content/requirement → semantic order → container/measure →157grid/span → scale/density → crop/source → local optical correction. Stop at the158first supported cause; repair its canonical owner and inspect consumers. Do not conceal159failures through clipping, blanket centring, more whitespace, smaller type or160one-column stacking. Revert or narrow regressions. Cause may be confirmed,161inferred or unknown.162163At acceptance, an exception needs supported intent/gain, protected communication/access floors,164counterstructure, cost and a falsifying observation. Compare a fair conventional165control when challenged; keep non-intervention variables constant, allowing the166repair's declared dependent effects. A plausible story after the fact is not167evidence. Never reclassify user-rejected overflow as intentional bleed. Source,168rights, consent and production constraints cannot become aesthetic exceptions.169Ordinary local exceptions stay with their specialist; Critique handles a separate170multi-domain lifecycle or challenged cross-domain exception.171172## Route and read only what applies173174Use the [Direct expert index](references/direct-expert-index.md). General composition foundations never require another175module. Specialists retain their geometry: packaging faces, mark contours,176chart encodings, map topology, responsive pressure and fixed-media structure.177Independent concerns still route: label appearance does not alone select178Information, but a contradicted value-to-position relation does; Wayfinding179does not settle map geometry; Mark does not reopen Brand/Concept unless open.180Brand also owns an authored icon-family or stroke system outside identity work.181Revisit routing when a new concern appears; no fixed module-count/token gate.182183Verify received coverage before applying a selected source: numbered lines,184total, received and missing intervals. Recover missing or cut-through lines,185including intact adjacent lines; reconcile each file separately. Keep conflicting186returns and source order. An end marker is not proof of a complete middle.187Use the optional [source reader](scripts/read-source.py) or an equivalent.188Its header contains recovery details when transport fails. If coverage cannot189be recovered, carry the dependent concern unverified. Headings do not unload190context; split phases only for actual task/capacity needs. User/provider limits191and authorisation remain binding.192193## Proof ceiling194195Distinguish binding constraints, evidence-bounded rules, conventions, heuristics,196preferences and exceptions. Numeric advice needs its population, language/script,197medium, task and override basis; one study or starting value is no universal law.198Render proof covers inspected appearance only. It requires a host capability199through which the agent actually views the rendered artifact or its image, such200as an image-viewing tool, a screenshot that the agent can open, or a supplied201render. Creating a screenshot file, reading its bytes or metadata, or inspecting202source alone is not viewing. Without such a capability, record every visual-lane203result as unverified and state that limit. Syntax, runtime, accessibility,204user research, rights, provider and physical acceptance are separate lanes.205Check current standards, law, licences and living-community claims when required;206if unavailable, mark unverified and stop at that authority boundary.207208209## Terms210211- **Module / expert / leaf:** one linked reference and its domain role, not a subagent.212- **Owner:** the person/domain authorised to change a field's decision or status.213- **Observer:** reports attributed effects without changing another owner's decision.214- **Falsifier:** the observation that would overturn a judgment or exception.215- **Control:** a fair comparison preserving unrelated conditions.216- **Claim ceiling:** the strongest claim the observed evidence actually supports.217218## Expert routing219220`SKILL.md` itself is the Core. Load expert references only through the exact221links in the [Direct expert index](references/direct-expert-index.md), never through a guessed Core file or transitive sibling loads.222Core or an active module may also link an optional packaged tool in `scripts/`; read or223execute that exact tool when needed. This exception does not load other experts.224Core or an active module may similarly link an exact declared teaching source225or render in `examples/`. Inspect only that named asset when it can resolve the226current decision; an example is neither a hidden module nor proof of the result.227`modules.yaml` is non-routed packaging/evaluation metadata, not another runtime228router. Repository tooling generates this index from its labels and paths and229checks for drift before packaging; runtime routing remains here in `SKILL.md`.230This installed snapshot does not itself attest that those development checks ran.231Neither the metadata nor the repository tools are runtime load targets.232Module `Sources:` IDs and the non-routed source index are provenance, not load instructions.233Runtime rules remain local and offline except an actually required source check.