signalproof-design

Define product information architecture, state semantics, and evidence-backed design acceptance criteria.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-design-docreo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signalproof-design
Source: https://github.com/docreo/Signalproof-Skills/tree/main/skills/signalproof-design
Command: npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-design-docreo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product redesigns often blur operational meaning, hide technical evidence behind visual polish, or overwrite working baselines without governance. This Skill provides a governed contract for structuring product information architecture, state semantics, and acceptance evidence so design changes preserve product meaning and remain verifiable. ## Core Features & Use Cases - Information Architecture Definition: Establish workspaces, navigation, operational views, and technical/evidence depth proportionate to product scale. - Evidence-Backed State Semantics: Define explicit states such as HEALTHY, ATTENTION, DEGRADED, BLOCKED, and UNKNOWN tied to real product data sources, never treating UNKNOWN as healthy. - Governed Redesign Workflow: Protect known-working baselines, gate material redesigns behind candidate mockup review, and hand micro-polish and accessibility to dedicated specialists. - Use Case: When redesigning a monitoring dashboard, use this Skill to define the operational summary view, drill-down technical evidence, state definitions, identity asset slots, and a build handoff contract with an acceptance matrix before implementation begins. ## Quick Start Ask the AI to define the information architecture, state semantics, and acceptance evidence plan for a product redesign using the signalproof-design contract.

Frequently Asked Questions about signalproof-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a product dashboard with operational and technical views?▼

Define an operational view answering what is running, what changed, and what needs attention, then expose technical depth such as versions, dependencies, and provenance as drill-down evidence. Technical detail should explain operational summaries rather than contradict them.

What is the difference between information architecture and UI polish?▼

Information architecture defines workspaces, navigation, state semantics, and evidence access, which this Skill owns. Micro-layout, spacing, alignment, motion, and visual finish belong to a dedicated UI polish specialist, keeping each contract bounded.

How should health status states be defined in product design?▼

Use explicit states such as HEALTHY, ATTENTION, DEGRADED, BLOCKED, and UNKNOWN only when backed by real product evidence. UNKNOWN must never be represented as healthy, and important status should be textual and drillable to its evidence source.

When should a product redesign not proceed?▼

Stop when redesign would overwrite the only accepted baseline, state has no trustworthy source, mockup success is being treated as runtime acceptance, or a generic shared layout would materially harm the specific product workflow.

Does this Skill handle accessibility requirements?▼

No. Keyboard navigation, screen readers, contrast, reduced motion, and semantic accessibility are routed to a dedicated accessibility specialist. This Skill focuses on information architecture and state communication only.