ChatGPT Claude Codex CLI Cohere Cursor DeepSeek Gemini GitHub Copilot GLM Grok Kimi Llama MiniMax Mistral OpenAI opencode Skill

deterministic-design

Render the UI and prove it's balanced + usable: a deterministic layout audit (centroid / optical-center / pixel-oracle balance via explicit math + annotated screenshot) plus a vision-judged Nielsen usability audit by a separate fresh-eyes judge. The measurement layer taste-only d

LLM Mart · 0 points · 20 views 40 listing impressions 0 install-command copies

#vision #verification #design

Virus-scanned Reviewed automatically before listing.

Full trust report

Download sickn33-agentic-awesome-skills-skills_deterministic-design-286166a.zip · 1 KB
Part of sickn33/agentic-awesome-skills — 427 skills
This skill couldn't be refreshed from GitHub on the last check — you're seeing the last imported snapshot.

Install

skills CLI npx skills add https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/deterministic-design
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install sickn33-agentic-awesome-skills@llmmart
Git git clone https://github.com/sickn33/agentic-awesome-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole sickn33/agentic-awesome-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

When to Use

Use to catch AI-generated UI that "looks off", is misaligned or centered-mush, or fails usability — when you need to PROVE a layout is balanced and usable instead of trusting the model's eye. Compose it with any taste/token design skill before reporting design "done".

Source: connerkward/deterministic-design-skill (MIT).

deterministic-design

Thesis: determinism beats AI randomness. A model can't trust its own eye on layout — so don't. Render the UI and measure it.

Two sub-skills (load as needed):

  • design-spatial — deterministic layout audit: explicit grid
    • 8-pt spacing, and layout-audit.js computes centroid / optical-center / pixel-oracle balance and draws an annotated screenshot. Numbers, not vibes. Plus a render-then- critique vision loop.
  • design-ux — usability audit: scores the rendered UI against Nielsen's 10 + interaction heuristics via a SEPARATE fresh-eyes judge → prioritized fix list.

This improves existing design skills (including the default Anthropic one) by adding the layer they lack — it doesn't just advise on taste, it renders, measures, and judges the output. Composable with any design skill.

In central this lives as a subdir of ckw-design; it publishes separately as deterministic-design-skill (its own distribution) via publish-skill. One of the two flagship narratives — the determinism one; its sibling is human-in-the-loop (lookdev).

Limitations

  • Layout metrics and vision-judged audits catch many spatial and usability failures, but they are not a substitute for product judgment or user testing.
  • The workflow requires a rendered UI or screenshot; it cannot validate components that have not been built or captured.
  • Automated scoring can miss brand nuance, copy tone, accessibility needs, and domain-specific user expectations.
Files (agentic-awesome-skills)
  • SKILL.md 2.7 KB
    ---
    name: deterministic-design
    description: "Render the UI and prove it's balanced + usable: a deterministic layout audit (centroid / optical-center / pixel-oracle balance via explicit math + annotated screenshot) plus a vision-judged Nielsen usability audit by a separate fresh-eyes judge. The measurement layer taste-only design skills lack."
    risk: safe
    source: community
    source_type: community
    source_repo: connerkward/deterministic-design-skill
    date_added: "2026-06-16"
    author: Conner K Ward
    license: MIT
    tags:
      - design
      - layout
      - usability
      - audit
      - verification
      - vision
    tools:
      - claude-code
      - antigravity
      - cursor
      - gemini-cli
      - codex-cli
    ---
    ## When to Use
    
    Use to catch AI-generated UI that "looks off", is misaligned or centered-mush, or fails usability — when you need to PROVE a layout is balanced and usable instead of trusting the model's eye. Compose it with any taste/token design skill before reporting design "done".
    
    _Source: [connerkward/deterministic-design-skill](https://github.com/connerkward/deterministic-design-skill) (MIT)._
    
    # deterministic-design
    
    Thesis: **determinism beats AI randomness.** A model can't trust its own eye on layout — so
    don't. Render the UI and *measure* it.
    
    Two sub-skills (load as needed):
    - **[design-spatial](https://github.com/connerkward/deterministic-design-skill/blob/main/design-spatial/SKILL.md)** — deterministic layout audit: explicit grid
      + 8-pt spacing, and `layout-audit.js` computes centroid / optical-center / pixel-oracle
      balance and draws an annotated screenshot. **Numbers, not vibes.** Plus a render-then-
      critique vision loop.
    - **[design-ux](https://github.com/connerkward/deterministic-design-skill/blob/main/design-ux/SKILL.md)** — usability audit: scores the rendered UI against
      Nielsen's 10 + interaction heuristics via a SEPARATE fresh-eyes judge → prioritized fix list.
    
    This **improves** existing design skills (including the default Anthropic one) by adding the
    layer they lack — it doesn't just advise on taste, it renders, measures, and judges the
    output. Composable with any design skill.
    
    In central this lives as a subdir of ckw-design; it **publishes separately** as
    `deterministic-design-skill` (its own distribution) via publish-skill. One of the two
    flagship narratives — the *determinism* one; its sibling is human-in-the-loop (lookdev).
    
    ## Limitations
    
    - Layout metrics and vision-judged audits catch many spatial and usability failures, but they are not a substitute for product judgment or user testing.
    - The workflow requires a rendered UI or screenshot; it cannot validate components that have not been built or captured.
    - Automated scoring can miss brand nuance, copy tone, accessibility needs, and domain-specific user expectations.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related