Skip to main content

NeonInk Validation Checklist

This checklist validates design-system adoption readiness under NeonInk. SFDS suite conformance for NeonInk is tracked by NeonInk.manifest.toml and the NeonInk Suite Map.

  • Project declares NeonInk or a sub-contract in its manifest.
  • Palette usage preserves semantic roles.
  • Theme behavior is documented.
  • Component patterns match existing NeonInk guidance.
  • Desktop app surfaces define panel, list, tool, and health/repair state behavior when applicable.
  • Icon usage is semantic and does not rely on color alone.
  • Glow is reserved for active, verified, caution, critical, or focus states.
  • Dense views remain readable without oversized type or decorative effects.
  • Generated assets include provenance when applicable.
  • SESM metadata is used for SVG assets when semantic embedding is needed — see NeonInk's Relationship to SESM.