UX/UI design and accessibility audit -- name the user, task, and success criterion before any layout decision, enforce WCAG 2.2 AA as a constraint from the first sketch, walk the 10 Nielsen heuristics, and refuse patterns that defeat usability or research integrity.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Design
## Purpose
Decide what interface a user should encounter, why, and on what evidence. Three decision
types: the user task flow (who, what, success criterion, failure modes) before any visual
decision; the accessibility constraint envelope (WCAG 2.2 AA enforced from the first sketch,
not audited at the end); and the design-system consistency verdict (reuse a token/component,
or justify the exception). Not aesthetic preference -- the procedure below, applied in order.
## Procedure
1. **Name the user, the task, the success criterion, and the failure modes (Move 1).** A
specific user segment with a competency level (not "users"); a verb phrase with an outcome;
an observable/measurable success criterion; enumerated failure modes (input error, network
failure, screen-reader silence, keyboard focus lost, etc.). Do not propose a layout before
these four sentences exist.
2. **Calibrate stakes.** High: onboarding, checkout, critical flows, accessibility-critical
forms, error handling. Medium: settings, navigation, dashboards. Low: marketing pages,
internal admin tools for trained users. Record the classification and its criterion.
…
The line at the top of this page pins the label git:20260906.2f7c802, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_lavonxijsm7bmg2c
GET https://markdownregistry.com/api/v1/resolve?ref=cdeust/zetetic-team-subagents/design
GET https://markdownregistry.com/api/v1/blob/1625ba6c69448cf0611a2790d2b0d749b02c0054bcce899c786e1672214396c5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
cdeust/zetetic-team-subagents · plugins/zetetic-loop/skills/advisor-model/SKILL.md · Consult a separate model at a selected plan, fork, or completion decision while the current model retains execution…
cdeust/zetetic-team-subagents · plugins/zetetic-loop/skills/goal/SKILL.md · Compile a long-running objective into a persistent, host-neutral goal contract: one measurable end state, non-goals…
cdeust/zetetic-team-subagents · plugins/zetetic-loop/skills/plan/SKILL.md · Turn an active goal contract into an ordered plan where every step carries its own check, then verify the plan against…
cdeust/zetetic-team-subagents · plugins/zetetic-loop/skills/refine-goal/SKILL.md · After a verify-goal run, turn the ledger into the next iteration: tighten criteria that passed by accident, add the…
cdeust/zetetic-team-subagents · plugins/zetetic-loop/skills/verify-goal/SKILL.md · Run every acceptance criterion of a goal file as an external check, record the command, its exit code and an output…
cdeust/zetetic-team-subagents · plugins/zetetic-reasoning/skills/evidence-synthesis/SKILL.md · Synthesize multiple papers, benchmarks, interviews, reviews, or other sources into a defensible and qualified…
cdeust/zetetic-team-subagents · skills/boundary-design/SKILL.md · Draw the line where it costs least. Use for build-vs-buy calls, "where does this module/team/service boundary belong?"…
cdeust/zetetic-team-subagents · skills/causal-audit/SKILL.md · Correlation walked in; make it prove causation. Use when someone claims "X causes Y" from observational data, asks "did…
cdeust/zetetic-team-subagents · skills/decision-bias-check/SKILL.md · Audit the decision before it ships. Use for "are we sure about this?", high-stakes choices made on fast intuition…
cdeust/zetetic-team-subagents · skills/estimation/SKILL.md · Bound it before you build it. Use when a decision is blocked by "we don't have data", an estimate looks suspiciously…
jeremylongshore/tons-of-skills-marketplace · plugins/ai-agency/hyperflow/skills/design/SKILL.md · Use when the user wants the visual/experiential design of a product done systematically — a design system, a screen, a…
sethgammon/citadel · skills/design/SKILL.md · Generates and maintains a design manifest for visual consistency. In existing projects, reads current styles and…
adityaraj0421/naksha-studio · skills/design/SKILL.md · Assembles a virtual design team to produce production-quality UI, UX, visual, social media, email, and data output. A…
ericrisco/rsc-harness · skills/design/SKILL.md · Use when designing, polishing or auditing a web UI or landing page — visual concept, type/color/spacing/motion tokens…