Agent skill

Aesthetic Usability Effect

by hashgraph-online in hashgraph-online/awesome-codex-plugins

A skill your agent uses when the design's perceived quality affects whether users will tolerate friction, give the product a chance, or judge it as well-made — which is most consumer-facing…

Apache-2.0Auto-check passedFrontend & Design

Install Aesthetic Usability Effect

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill aesthetic-usability-effect -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins aesthetic-usability-effect --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/HDeibler/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/aesthetic-usability-effect .claude/skills/aesthetic-usability-effect && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
aesthetic-usability-effect
GitHub stars
1.3k
Token cost
~3.9k tokens
SKILL.md length
1,819 words
Files
2 (incl. references)
Skills in repo
714
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when the design's perceived quality affects whether users will tolerate friction, give the product a chance, or judge it as well-made — which is most consumer-facing…

  • Works in 5 steps: Default to a polished baseline → Spend on type, color, and spacing first → Eliminate the obvious → …
  • The designs perceived quality affects whether users will tolerate friction
  • SKILL.md covers Definition (in our own words), Origins and research lineage, Why this principle matters and When to apply, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Aesthetic Usability Effect is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill when the design's perceived quality affects whether users will tolerate friction, give the product a chance, or judge it as well-made — which is most consumer-facing surfaces, marketing, onboarding, first-run, and any moment where an unfamiliar user is forming a quick judgment. Trigger when designing landing pages, sign-up flows, first-time UX, app store screenshots, demo videos, sales decks, or any surface where the user's first impression matters and friction is unavoidable. Also trigger when…

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/research-and-cases.md`).

It sits in Frontend & Design, covering UX design, Landing pages and Sales enablement. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

  • The designs perceived quality affects whether users will tolerate friction
  • Give the product a chance
  • Judge it as well-made — which is most consumer-facing surfaces
  • Any moment where an unfamiliar user is forming a quick judgment

Example prompts

  • “polish”
  • “should we ship the spartan version or invest in design?”
  • “/aesthetic-usability-effect”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Default to a polished baseline
  2. Spend on type, color, and spacing first
  3. Eliminate the obvious
  4. Invest in micro-moments
  5. Photography and illustration matter

What it can do on your machine

Read from SKILL.md and the folder at commit 9e7b281. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are html).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Aesthetic Usability Effect loads about 3.9k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 169 tokens; SKILL.md has 1,819 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~169
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 9e7b281, republished under its Apache-2.0 licence (© hashgraph-online). 1,819 words, ~3,896 tokens.

Download SKILL.mdSave it as .claude/skills/aesthetic-usability-effect/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
aesthetic-usability-effect
description
Use this skill when the design's perceived quality affects whether users will tolerate friction, give the product a chance, or judge it as well-made — which is most consumer-facing surfaces, marketing, onboarding, first-run, and any moment where an unfamiliar user is forming a quick judgment. Trigger when designing landing pages, sign-up flows, first-time UX, app store screenshots, demo videos, sales decks, or any surface where the user's first impression matters and friction is unavoidable. Also trigger when defending why "polish" matters on a working product, or when the user asks "should we ship the spartan version or invest in design?"

Aesthetic-Usability Effect

The Aesthetic-Usability Effect is the empirical finding that users perceive aesthetically pleasing designs as easier to use — even when objectively measured usability is identical or worse. Beauty buys patience: users tolerate friction in beautiful interfaces and abandon ugly ones over the same friction.

Definition (in our own words)

When users encounter a design they find visually appealing, they (1) judge it as more usable than they would judge an objectively-equivalent unattractive design, (2) tolerate more friction before abandoning, (3) attribute usability problems to themselves ("I must be doing it wrong") rather than to the system, and (4) report higher satisfaction with the experience overall. This is not a temporary halo; it persists across the early phase of using a product, and only erodes once concrete usability failures stack up beyond the patience the aesthetic earned.

Origins and research lineage

  • Kurosu and Kashimura (1995), working with ATM interfaces, reported that subjects rated aesthetically-pleasing layouts as more usable, even when their actual usability scored similarly to less attractive alternatives. The finding was striking enough to launch a research line.
  • Tractinsky (1997) replicated the effect with Israeli ATM users, demonstrating that the relationship was not culture-specific.
  • Lavie and Tractinsky (2004) developed instruments to measure perceived aesthetics along two dimensions ("classical" — order, clarity, symmetry — and "expressive" — creativity, originality, fascination), and showed that classical aesthetics in particular correlate strongly with perceived usability.
  • Norman (2004) in Emotional Design proposed a theoretical mechanism: positive affect broadens cognitive flexibility, making users more tolerant of difficulty. Negative affect narrows focus and exaggerates problems.
  • Sonderegger & Sauer (2010) showed the effect persists in longitudinal use, though it diminishes as users accumulate genuine usability data.

Why this principle matters

A design is rarely judged in a vacuum. The user has options, attention is finite, and patience for new tools is short. The aesthetic-usability effect is one of the strongest determinants of whether the user will give the product a chance long enough to discover its actual usability. A product that is functionally great but visually rough will lose users to a product that is functionally adequate but visually appealing — for the same task, with the same user.

The effect is most decisive at:

  • First impression (the first 5–15 seconds with a new product).
  • Friction moments (any time the user hits a snag — they're more forgiving on a beautiful product).
  • Comparison contexts (the user is choosing between options).

The effect is least decisive in:

  • Habitual professional use (users who've been using a tool daily for years care little about polish — they care that it doesn't break).
  • High-stakes operations where reliability dominates (medical, aerospace, financial trading).

When to apply

  • Marketing and landing pages. Where every visitor is making a snap judgment.
  • Onboarding and first-run. Where the user has no commitment yet.
  • App store screenshots, demo videos, sales decks. Where the design is the product to the viewer.
  • Pricing and conversion surfaces. Where the aesthetic affects perceived quality and willingness to pay.
  • Empty states and celebration moments. Where polish carries meaning.

Restated: any time the user is choosing whether to engage, beauty matters disproportionately.

When NOT to apply

  • As a substitute for usability. The aesthetic-usability effect tilts perception, but it doesn't repair actual usability failures. A beautiful form that's confusing to fill in will frustrate users — they'll just blame themselves at first, and the product later.
  • In sustained-use professional tools. The traders, the developers, the ICU nurses, the air-traffic controllers — they've used your tool for thousands of hours. Polish is decoration; reliability is everything.
  • When polish steals from clarity. A "beautiful" design that obscures the next step, hides important information behind subtle cues, or applies aesthetic conventions inappropriate to the task is worse than a plain one. Beauty must serve the function, not compete with it.
  • When the user is in a stressful or emotional context. Beauty matters less when the user is panicking about a payment failure or trying to recover from data loss; clarity matters more.

What "aesthetic" means in this context

The Lavie/Tractinsky distinction is useful:

  • Classical aesthetics — order, clarity, symmetry, alignment, restraint, proportion. The aesthetic of a well-tailored suit, a Helvetica-set Swiss poster, a clean industrial product. This dimension correlates most strongly with perceived usability. Designs that score high on classical aesthetics feel "professional" and "competent."
  • Expressive aesthetics — creativity, originality, special effects, personality. The aesthetic of a striking illustration, a memorable animation, a bold brand voice. This dimension correlates more weakly with perceived usability but more strongly with perceived attractiveness and emotional connection.

For most software UI, classical aesthetics are the higher-leverage investment. They work without straining; they age well; they don't compete with content. Expressive aesthetics are powerful in moments (a hero illustration, a launch animation) but draining in sustained surfaces.

How to invest in aesthetic-usability

Concrete moves that buy the aesthetic-usability effect without trading off actual usability:

1. Default to a polished baseline

Use a credible UI library (Radix, Material, shadcn/ui, Carbon, Polaris) rather than building primitives from scratch. The default styling of these libraries is calibrated for classical aesthetics — proportions, spacing, type, contrast — and represents thousands of designer-hours of refinement.

A spartan in-house framework signals "engineered, not designed" — even when the engineering is excellent.

2. Spend on type, color, and spacing first

The fastest way to lift perceived quality:

  • Type: a quality typeface (Inter, IBM Plex, Söhne, system stack), a clear scale, generous leading, restrained weights.
  • Color: a thoughtful palette with neutrals as the workhorse and color as accent. Avoid flat-default-grey for everything; tint neutrals slightly toward the brand.
  • Spacing: a consistent rhythmic scale (Fibonacci-like progression), generous whitespace, deliberate proximity.

These three carry more perceived-quality weight than any single visual flourish.

3. Eliminate the obvious

Rough edges erode the aesthetic-usability effect quickly:

  • Misaligned elements.
  • Inconsistent spacing.
  • Mismatched type weights for the same role.
  • Off-color status badges.
  • Loading states that flash or jitter.
  • Text that breaks into single-word last lines.
  • Images at wrong aspect ratios that get squished.

A polished design isn't one with more features; it's one with fewer rough edges.

4. Invest in micro-moments

Small, well-crafted moments compound:

  • A satisfying focus ring animation.
  • A quick fade-in on content load (not a slow elaborate cascade).
  • A success toast with a tasteful check icon.
  • A loading skeleton that approximates the final layout.

These moments are individually inexpensive and collectively communicate care. Avoid heavy motion or "look at me" effects — restraint reads as confident.

5. Photography and illustration matter

If your product has hero imagery, screenshots, or illustrations, their quality affects perceived professionalism more than almost any other element. A great photograph or illustration on a mediocre layout outperforms a great layout with stock-photo cliché. If the budget exists for one investment in a marketing surface, this is often the right place.

Show full SKILL.md (705 more words)Show less

Worked examples

Example 1: a sign-up form with rough edges (anti-pattern)
html
<form>
  <h1 style="font-family: Arial; font-size: 24px;">Sign up</h1>
  <p>Enter your details.</p>
  <input type="text" placeholder="Name" style="border: 1px solid #888; padding: 4px;" />
  <input type="email" placeholder="Email" style="border: 1px solid #888; padding: 4px; margin-top: 5px;" />
  <input type="password" placeholder="Password" style="border: 1px solid #888; padding: 4px; margin-top: 5px;" />
  <button style="background: blue; color: white; border: 0; padding: 6px 12px; margin-top: 10px;">Submit</button>
</form>

Functionally complete. Aesthetically rough: default-stack font, thin grey borders, inconsistent margins, a saturated-blue submit button with no proportion to the form. The user judges the product as amateur and brings less patience to whatever comes next.

Example 2: same form, polished baseline
html
<style>
  body { font-family: 'Inter', system-ui; color: hsl(0 0% 12%); }
  .signup { max-width: 400px; padding: 2rem; display: grid; gap: 1.5rem; }
  .signup h1 { font-size: 1.5rem; font-weight: 600; }
  .signup p { color: hsl(0 0% 45%); margin-top: -1rem; }
  .field { display: grid; gap: 0.375rem; }
  .field label { font-size: 0.875rem; font-weight: 500; }
  .field input {
    height: 2.5rem; padding: 0 0.75rem;
    border: 1px solid hsl(0 0% 88%);
    border-radius: 0.375rem;
    font-size: 0.875rem;
  }
  .field input:focus-visible {
    outline: 2px solid hsl(220 90% 50%);
    outline-offset: 1px;
    border-color: transparent;
  }
  .submit {
    height: 2.5rem; padding: 0 1.25rem;
    background: hsl(0 0% 12%); color: white;
    border: 0; border-radius: 0.375rem;
    font-size: 0.875rem; font-weight: 500;
    cursor: pointer;
  }
  .submit:hover { background: hsl(0 0% 25%); }
</style>

<form class="signup">
  <div>
    <h1>Create your account</h1>
    <p>One minute and you're in.</p>
  </div>
  <div class="field">
    <label for="name">Full name</label>
    <input id="name" type="text" />
  </div>
  <div class="field">
    <label for="email">Email</label>
    <input id="email" type="email" />
  </div>
  <div class="field">
    <label for="password">Password</label>
    <input id="password" type="password" />
  </div>
  <button class="submit">Create account</button>
</form>

Same fields, same actions, same flow. The polish — type, color, spacing, focus ring, label placement — is what shifts perception. Users on the second form will tolerate the same login problem as a hiccup; users on the first will conclude the product is broken.

Example 3: dashboard polish

A bare-data-table dashboard versus the same data with: tabular numerals in numeric columns, consistent right-alignment, a quiet hairline between rows, a sticky header with subtle blur on scroll, and a thoughtful empty state when filters return no results. None of these change what the dashboard does. All of them shift whether the user feels they're using a precise tool or a duct-taped one.

Anti-patterns

  • Polish-as-substitute. A beautiful interface that hides what the user actually needs to do. The aesthetic earns initial trust; the broken flow squanders it within a session or two.
  • Imitation polish. Adopting visual conventions without understanding (drop shadows everywhere, gradients on every button, oversized icons in tinted squares). Reads as cargo-culted and ages quickly.
  • Inconsistent polish. A polished sign-up flow leading to a 1998-era settings page. Worse than uniformly plain — the contrast highlights the unpolished surface.
  • Polish at the cost of accessibility. Beautiful low-contrast text, gorgeous animation that triggers vestibular disorders, elegantly tiny tap targets. The beauty earns nothing if substantial users can't use it.
  • Aesthetic theater for serious tools. A dashboard for a hospital tracking critical patient metrics doesn't need delight animations; it needs clarity, correctness, and reliability. Polish for the sake of polish on serious tools reads as unserious.

Heuristics

  1. The 5-second test. Show the design to someone for 5 seconds, hide it, ask what they think the product does and what kind of company makes it. Their answer is heavily informed by the aesthetic-usability effect.
  2. The friction-tolerance test. Compare abandonment on a known friction point (e.g., email verification) across two design polish levels. The polished version typically loses fewer users to the same friction.
  3. The "would you trust this with money?" test. If the user would hesitate to enter payment info on this surface, polish is too low — even if functionality is fine.
  4. The detail audit. Pick 5 random elements (a form field, a button, a heading, a separator, a hover state). Are they consistent in size, weight, color, and spacing with the rest of the design? Inconsistencies erode perceived quality.

Trade-offs and warnings

  • Polish is not a strategy. It's an enabler. A product that succeeds on polish alone is rare; usually polish helps a sound product convert better at the margin.
  • Polish has diminishing returns. Going from rough to polished is enormous lift; going from polished to "ultra-premium" is small lift for big cost. Know where you are on the curve.
  • Polish ages. Heavy expressive aesthetics (gradients, glassmorphism, neumorphism, brutalism) tend to date quickly. Classical aesthetics age more gracefully because they rely on enduring visual fundamentals.
  • Polish must serve the audience. The aesthetic that earns trust from a B2B audience differs from the aesthetic that earns trust from a Gen Z consumer audience. Don't import an aesthetic from a domain whose codes don't match your users.
  • form-follows-function — beauty derived from function ages well; decorative beauty doesn't.
  • wabi-sabi — a counterpoint: imperfection can read as authentic, not unpolished, in some contexts.
  • hierarchy (perception) — strong hierarchy is a major component of "classical" aesthetic.
  • alignment and proximity (perception) — small alignment failures cost more than designers expect.
  • signal-to-noise-ratio (perception) — high SNR designs typically score high on classical aesthetics.
  • consistency (cognition) — perceived polish and perceived consistency are the same property in different language.

Final note

The aesthetic-usability effect is sometimes used to argue that "design doesn't matter as long as the function is there" or, conversely, "you can ship anything as long as it looks good." Both are wrong. The effect is a modulator: it amplifies the upside of good function and dampens the downside of friction. Build the function; invest in the polish; let the two compound.

© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/HDeibler/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/aesthetic-usability-effect of hashgraph-online/awesome-codex-plugins.

  • SKILL.md
  • references/research-and-cases.md

Open the folder on GitHubat commit 9e7b281

Compare with similar skills

Aesthetic Usability Effect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Aesthetic Usability Effect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Aesthetic Usability Effect this skillhashgraph-online/awesome-codex-plugins1.3k—~3.9kAutomated safety check: PassApache-2.0
App Preview Videodotnetdreamer/open-screenshot-generator125—~3.3kAutomated safety check: PassMIT
Impeccablebestofjs/bestofjs3.1k27 repos~2.6kAutomated safety check: PassMIT
Super UI UX Designsyahiidkamil/Software-Engineer-AI-Agent-Atlas401—~9kAutomated safety check: PassNone
Replica LaunchJakeschincariol/replica-skill1.2k—~1kAutomated safety check: PassMIT
Penpot Uiux Designgithub/awesome-copilot40k1 repos~3kAutomated safety check: PassMIT

Similar skills

  • App Preview Video

    dotnetdreamer/open-screenshot-generator

    Builds an App Store App Preview video (and a Play Store or landing page promo cut) from a screen recording of the app, using the open-screenshot-generator CLI (osg video): it starts from one of 20…

    125 GitHub stars~3.3k tokensUpdated yesterday
    MobileAuto-check passed
  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 27 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Super UI UX Design

    syahiidkamil/Software-Engineer-AI-Agent-Atlas

    Complete UI/UX design capability — a wiki-style knowledge map of design theory (UX laws, Nielsen heuristics, usability, visual hierarchy, typography, contrast/WCAG, design systems…

    401 GitHub stars~9k tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed
  • Replica Launch

    Jakeschincariol/replica-skill

    Writes the launch for an app clone: the landing page built on the positioning angle, pricing set against the original's public pricing and its users' complaints, and the App Store and Google Play…

    1.2k GitHub stars~1k tokensUpdated 6 days ago
    Frontend & DesignAuto-check passed
  • Penpot Uiux Design

    github/awesome-copilot

    Official

    Comprehensive guide for creating professional UI/UX designs in Penpot using MCP tools.

    40k GitHub starsUsed in 1 repo~3k tokens
    Frontend & DesignAuto-check passed
  • Product Skills

    alirezarezvani/claude-skills

    A skill your agent uses when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery…

    28k GitHub stars~2.6k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 714 skills in this repo
  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.3k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.3k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Calle

    hashgraph-online/awesome-codex-plugins

    Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.3k GitHub stars~618 tokensUpdated today
    Auto-check passed

Questions about Aesthetic Usability Effect

What does Aesthetic Usability Effect do?

A skill your agent uses when the design's perceived quality affects whether users will tolerate friction, give the product a chance, or judge it as well-made — which is most consumer-facing…. Aesthetic Usability Effect is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill when the design's perceived quality affects whether users will tolerate friction, give the product a chance, or judge it as well-made — which is most consumer-facing surfaces, marketing, onboarding, first-run, and any moment where an unfamiliar user is forming a quick judgment.

When should I use Aesthetic Usability Effect?

Aesthetic Usability Effect fits situations like: the designs perceived quality affects whether users will tolerate friction; give the product a chance; judge it as well-made — which is most consumer-facing surfaces; any moment where an unfamiliar user is forming a quick judgment.

How do I install Aesthetic Usability Effect in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill aesthetic-usability-effect -a claude-code`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/aesthetic-usability-effect in hashgraph-online/awesome-codex-plugins) into .claude/skills/aesthetic-usability-effect in your project. Claude Code loads it when a task matches its description.

How do I install Aesthetic Usability Effect in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill aesthetic-usability-effect -a codex`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/aesthetic-usability-effect in hashgraph-online/awesome-codex-plugins) into .agents/skills/aesthetic-usability-effect in your project. Codex loads it when a task matches its description.

Can I use Aesthetic Usability Effect in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill aesthetic-usability-effect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aesthetic-usability-effect, .gemini/skills/aesthetic-usability-effect, .github/skills/aesthetic-usability-effect and .opencode/skills/aesthetic-usability-effect in your project.

What does Aesthetic Usability Effect need to run?

SKILL.md names no scripts, command-line tools or credentials: Aesthetic Usability Effect is instructions for the agent only.

Does Aesthetic Usability Effect access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Aesthetic Usability Effect safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Aesthetic Usability Effect use?

Aesthetic Usability Effect is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Aesthetic Usability Effect use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Aesthetic Usability Effect?

Skills that share tags, products or a category with Aesthetic Usability Effect: App Preview Video (dotnetdreamer/open-screenshot-generator, 125 stars), Impeccable (bestofjs/bestofjs, 3.1k stars), Super UI UX Design (syahiidkamil/Software-Engineer-AI-Agent-Atlas, 401 stars) and Replica Launch (Jakeschincariol/replica-skill, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Aesthetic Usability Effect?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,255 GitHub stars. The repository holds 714 skills in this directory. The repository was last updated on October 9, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.