vuestrata: Skill for Claude Code

.github/skills/i-critique/SKILL.md

i-critique is a skill for Claude Code from boussadjra/vuestrata. It costs 32 tokens per session (1,142 once invoked), scanned A, a copy of critique, MIT.

A user-experience review of an interface, focusing on how clearly it guides people and how well its structure and visual design support their goals.

In plain words
What is it for?
Use it to assess visual hierarchy, information architecture, emotional impact, primary actions, and signs of formulaic AI-generated design, with feedback for improvements.
Why use it?
It exposes confusing hierarchy, unclear actions, weak information structure, and generic design choices that may make a product harder to use.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is boussadjra/vuestrata's own configuration. It tells Claude Code how to work on vuestrata itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vuestrata configures →

Reuse

Borrowing it

Nothing to install: this file belongs to boussadjra/vuestrata. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/boussadjra/vuestrata/main/.github/skills/i-critique/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/boussadjra/vuestrata

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for i-critique

README.md
[![agentmods](https://agentmods.dev/badge/skills/boussadjra/vuestrata/i-critique/github.svg)](https://agentmods.dev/skills/boussadjra/vuestrata/i-critique)
Your own site
<a href="https://agentmods.dev/skills/boussadjra/vuestrata/i-critique"><img src="https://agentmods.dev/badge/skills/boussadjra/vuestrata/i-critique/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for i-critique

Your own site · 80×15
<a href="https://agentmods.dev/skills/boussadjra/vuestrata/i-critique"><img src="https://agentmods.dev/badge/skills/boussadjra/vuestrata/i-critique.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,142 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.01142
Opus 5.5 $0.00013 $0.00457
Sonnet 5.5 $0.00006 $0.00228
Haiku 4.5 $0.00003 $0.00114

Measured 2mo ago against content hash 7e5351706734, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

i-critique scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

92% identical to critique — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/skills/i-critique/SKILL.md · 134 lines

How it starts

The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Conduct a holistic design critique, evaluating whether the interface actually works—not just technically, but as a designed experience. Think like a design director giving feedback.

First: Use the i-frontend-design skill for design principles and anti-patterns.

Design Critique

Evaluate the interface across these dimensions:

1. AI Slop Detection (CRITICAL)

This is the most important check. Does this look like every other AI-generated interface from 2024-2025?

Review the design against ALL the DON'T guidelines in the i-frontend-design skill—they are the fingerprints of AI-generated work. Check for the AI color palette, gradient text, dark mode with glowing accents, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells.

The test: If you showed this to someone and said "AI made this," would they believe you immediately? If yes, that's the problem.

2. Visual Hierarchy

  • Does the eye flow to the most important element first?
  • Is there a clear primary action? Can you spot it in 2 seconds?
  • Do size, color, and position communicate importance correctly?
  • Is there visual competition between elements that should have different weights?

3. Information Architecture

  • Is the structure intuitive? Would a new user understand the organization?
  • Is related content grouped logically?
  • Are there too many choices at once? (cognitive overload)
  • Is the navigation clear and predictable?

4. Emotional Resonance

  • What emotion does this interface evoke? Is that intentional?
  • Does it match the brand personality?
  • Does it feel trustworthy, approachable, premium, playful—whatever it should feel?
  • Would the target user feel "this is for me"?

5. Discoverability & Affordance

  • Are interactive elements obviously interactive?
  • Would a user know what to do without instructions?
  • Are hover/focus states providing useful feedback?
  • Are there hidden features that should be more visible?

6. Composition & Balance

Read the full file on GitHub · 134 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 134 lines · 32 tokens per session scan A 7e5351706734

Subscribe to this mod's changes

i-critique is a skill published in the GitHub repository boussadjra/vuestrata (111 stars, last pushed 11d ago), licensed MIT. It adds 32 tokens to every session and 1,142 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to critique, differing in 32 lines, and is treated as a copy.

Related

i-critique compared with skills from other repositories

i-critique next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
i-critiqueboussadjra/vuestrataSkill11111d agoMITA32Claude Code
magic-uimagicuidesign/magicuiSkill23kyesterdayMITA56Claude Code, Codex
tuturuuu-satellite-app-uxtutur3u/platformSkill54todayApache-2.0A25Codex
frontend-engineerbuiphucminhtam/forgewrightSkill496d agononeA55Claude Code
frontend-designbartstc/vite-ts-react-templateSkill12313d agoMITA43Claude Code, Codex
beuistarc007/ui-componentsSkill1.9kyesterdayMITA81Claude Code, Codex
beui-prostarc007/ui-componentsSkill1.9kyesterdayMITA85Claude Code, Codex