Folio Assistant Core

SkillPackage

theming

https://litlfred.github.io/folio-assistant/cat-harness/package/theming

JSON-LD · in graph cat-harness.jsonld ·

nametheming
version0.1.0
descriptionTheming, split on PIPELINE STAGE first (intake -> declaration -> generation -> contrast), with producer/consumer as the direction each stage faces and per-artefact specialisation last. The owner chose that axis on 2026-09-20 — "1 + 2, then specialized to 3" — and the ordering matters more than the names: going artefact-first would duplicate intake and contrast into every surface, which is the shape that put the scrim rule in one skill's prose and let it be rediscovered rather than read. TWO SESSIONS BUILT THIS PACKAGE INDEPENDENTLY and the merge kept both halves: this LOCATION and the relocation of create-sticky-note, site-presentation-assets and theme-art-intake out of folio-core came from one; the stage split, the theme:sheet visualiser and the documentation entry came from the other, which had put them in a top-level cat-harness/theming/. The location here won on evidence rather than on arriving first — bean lps0 measured that kg-audit's skillFiles() walks a hardcoded skills/, so a top-level topical directory silently drops its skills out of skill QA, and theme-art-intake would have lost the sidecar it has here. Beans 1hvo, lps0.
pathskills/ui/theming
hasManifesttrue
declaresSkillSite presentation assets — the node is the source, the stylesheet is a rendering
https://litlfred.github.io/folio-assistant/cat-harness/skill/site-presentation-assets
Theme art intake
https://litlfred.github.io/folio-assistant/cat-harness/skill/theme-art-intake
Theming, split on the stage it fails at
https://litlfred.github.io/folio-assistant/cat-harness/skill/theming
providesCapability
requiresCapability
inSubgraphskills
https://litlfred.github.io/folio-assistant/cat-harness/directory/skills