hashgraph-online/awesome-codex-plugins / plugins/alpoxdev/hypercore/skills/hyper-design
hyper-design
Verified[Hyper] Use this skill when the user wants interface design work that must not look AI-generated - designing a new screen, page, or component, restyling an existing UI, building faux product UI for a hero, feature card, or demo, or auditing, cleaning, or verifying generic template patterns in an interface - driven by a written design direction, a numeric craft floor, static detection, and evidence-separated review, with briefs and reports saved under `.hyper/design/[slug]/`. Do not use it for backend or data work with no visual surface, accessibility-only or performance-only QA, brand strategy with no interface, or a reusable skill folder.
rules/evidence-and-severity.md
View on GitHub# Evidence and Severity
Read before a finding gets a disposition. This file owns the finding record, the evidence kinds, the confidence split, and the severity classes.
## Finding record
Every finding must include:
| Field | Requirement |
|---|---|
| `claim` | Observable statement, not a taste verdict |
| `risk` | What product, usability, identity, accessibility, or maintenance outcome may fail |
| `severity` | P0–P3 using the definitions below |
| `confidence` | `high`, `medium`, or `low` |
| `engine` | `text`, `css`, `markup`, `context`, `dom`, or `visual`; state whether it actually ran |
| `evidence kind` | `static-source`, explicit local context, rendered handoff, accessibility, behavior, or rationale |
| `detection confidence` | Certainty that the engine observed its signature |
| `remediation confidence` | Certainty that changing it preserves protected contracts |
| `exception status` | `not-checked`, `candidate`, or documented waiver; candidate remains reviewable |
| `cluster` | Generic-output prioritization group, never authorship evidence |
| `evidence` | File/line, DOM/CSS, screenshot/state, command result, brief, or source |
| `warrant` | Why the evidence supports this risk in this context |
| `recommendation` | `remove`, `replace`, `preserve`, `ask`, or `block`, with a bounded action |
| `verification` | Observable check needed after action |
| `caveat` | Exception, missing evidence, or false-positive risk |
## Severity
- `P0` blocking: prevents task completion or causes severe accessibility, behavior, security, or data-integrity failure.
- `P1` major: repeated high-impact AI pattern, confirmed WCAG AA failure, or serious responsive failure.
- `P2` minor: worthwhile improvement with a usable workaround and no blocked task.
- `P3` polish: refinement close to taste; never use it to justify broad automatic change.
## Confidence
- `high`: directly confirmed in source, DOM/CSS, or deterministic output.
- `medium`: strong heuristic with a plausible contextual exception.
- `low`: depends on screenshot interpretation, product intent, or subjective review.
High confidence in a source match does not imply high confidence that removal is correct. Record detection confidence separately from remediation judgment in prose when they differ.
## Evidence families
- `validator`: detector, schema, fixture, test, build, or CI output.
- `screenshot`: viewport/state capture or visual diff.
- `accessibility`: contrast, keyboard, semantics, reduced-motion evidence.
- `user`: persona evidence, cognitive walkthrough, or user test.
- `source`: brief, design system, standard, or documented practice.
- `rationale`: decision record, rejected alternative, owner, debt, or review trigger.
A static detector cannot establish actual contrast, visual hierarchy, usability, or user preference. A screenshot cannot prove semantic correctness, keyboard behavior, or all responsive states. State these limits in the finding and final report.
## Sources
> Claims checked 2026-09-21. No external source was used in this file.
The severity, confidence, and evidence-family definitions are this package's own. WCAG AA is named only as the `P1` severity anchor; no WCAG document is quoted or restated here.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |