UI review profile

This profile uses UI Skills as optional review context, not as a runtime library or a second design authority. site/DESIGN.md remains the source of truth for information architecture, component behavior, copy, tokens, and visual direction; AGENTS.md remains the source of truth for working boundaries and verification.

The reviewed upstream CLI version is ui-skills@0.2.4 as observed on 2026-08-06. Start with its router, then retrieve only the smallest skill it selects rather than importing the registry or installing it as a project dependency:

npx ui-skills@0.2.4 start
npx ui-skills@0.2.4 categories
npx ui-skills@0.2.4 list --category <category>
npx ui-skills@0.2.4 get <routed-skill>

categories and list are inspection tools when the router needs a narrower choice; they are not a reason to preload several skills. Registry contents can change without this repository changing, so do not encode one fixed set as an automatic bundle.

When to use each skill

• fixing-accessibility is a strong candidate for a reader-visible component or style change. Check semantic elements, accessible names, keyboard operation, visible focus, text contrast, and motion preferences where motion exists.
• fixing-metadata is a strong candidate when changing public routes, canonical URLs, indexing, sitemap/RSS behavior, unlisted pages, social metadata, or preview-only surfaces.
• frontend-ui-engineering is a strong candidate for component boundaries, repeated patterns, responsive behavior, and design-token reuse. Treat its framework examples as illustrations rather than prescribed code.
• improve-ui is useful for a read-only audit against the product’s own design evidence. Its output is a prioritized plan, not permission to modify this repository or a replacement for site/DESIGN.md.
• fixing-motion-performance is relevant only when adding or materially changing animation or transition behavior. Emergence deliberately uses very little motion.

These names document the compatible candidates present in the reviewed registry, not a command sequence that overrides the router.

Do not apply baseline-ui or create-design-md wholesale. Their generic defaults can introduce a competing design contract and assume Tailwind, React-oriented component primitives, or animation packages that this site does not use.

Quartz adapter

Translate upstream recommendations through these project rules:

• use Quartz v5 and Preact-native component patterns already present in the repository,
• translate utility-class examples into the existing SCSS and CSS custom properties,
• do not add Tailwind, shadcn, Radix, React Aria, motion/react, cn(), or another component/token system solely to follow an example,
• extend the tokens in quartz/styles/custom.scss only when a genuinely reusable semantic value is missing,
• keep component-owned .emergence-* DOM styles with that component; keep route shell, Quartz internals, and authored-Markdown styling in custom.scss, and
• preserve the site’s flat editorial direction: no decorative gradients, glow, shadows, excessive rounding, category colors, or motion without a specific approved need.

Verification

The skill text is review guidance, not proof that the implementation works. Before completion:

1. run npm run check and npm run build from site/,
2. inspect the actual built route rather than reasoning from SCSS alone,
3. verify light and dark modes at desktop and mobile widths,
4. exercise links, Search, theme, reader mode, disclosure controls, and keyboard focus relevant to the change,
5. confirm public-route changes against HTML output, static/contentIndex.json, sitemap.xml, and RSS, and
6. keep source changes, local build state, Git lifecycle state, and deployment state as separate claims.

Recheck the upstream version and skill text before intentionally upgrading this profile; registry contents can change independently of this repository.