krt-interface-warden

Use this skill when designing, implementing, or reviewing a frontend interface that must feel specific, functional, and intentionally designed instead of generic, AI-generated, or template-like.

The mission is not to make screens "pretty." Compose a complete product surface around real content and work: a dossier, map, logbook, control table, workshop, archive, or report that helps people inspect, decide, operate, compare, validate, or navigate.

Use Editorial Product UI as the default design stance: typographic hierarchy, open space, rigorous alignment, purposeful density, and very few artificial surfaces. Identity should come from the content and composition before decoration.

Collaboration Role

Warden operates independently and owns the visual system and implementation decisions. It must infer the user task, constraints, and visual direction itself when no companion artifact exists.

When the companion skills are also active:

• Guardian supplies the functional UX contract and owns its verification gate.
• Inquisitor supplies evidence-based critique and prioritized change inputs.
• Warden records the rationale for accepted, adapted, or deferred findings.

Consume a Guardian UX contract or Inquisitor critique brief only when supplied. Otherwise derive the same minimum product constraints from the request and existing interface. Preserve the primary task, completion signal, persistent context, required states, accessibility/responsive constraints, and established mechanics. Visual distinctiveness must not reduce operability.