More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Japanese interface ergonomics

    2

    Review any screen by 17 rules of Japanese ergonomics. Scores it out of 34, finds what makes it awkward and suggests fixes with code.

    Free

    2 usesSecurity scanned
    Japanese interface ergonomics

    Japanese interface ergonomics

    Example session with this skill installed

    Review this settings card: it has an 'Edit' icon next to the title, 12 separate toggle rows for notifications, and a 'Save' button that shows a 'Changes Saved' popup. Simplify it.

    • Read your context and instructions
    • Compiled the japanese interface ergonomics

    The interface is currently optimized for the grid rather than the user's focus, leading to a high cognitive load (14+ elements).

    24 of 34 points (Japanese Ergonomics Score)

    Ergonomic Review

    #BlockFindingNumberLawSwap
    1HeaderRedundant 'Edit' icon2 objects1Remove icon; make the title row itself the trigger.
    2Body12 toggle rhythms12 things14Group into 3 categories (Miegakure); use Oku to hide rare items.
    3FooterInstant popup transition0ms zone9Replace popup with a 300ms inline 'Saved' state with undo.

    Recommended Redesign

    1. The Entrance (Genkan)
    Reduce the initial view to three primary notification categories: "Critical," "Activity," and "Marketing." Each category is a single wide row.

    2. The Archetype (Super Normal)

    <!-- Replace individual switches with word-control chips -->
    <div style="display: flex; gap: 12px; padding: 12px 0;">
      <button aria-pressed="true" class="chip-active">Immediate</button>
      <button aria-pressed="false" class="chip-quiet">Daily Digest</button>
      <button aria-pressed="false" class="chip-quiet">Off</button>
    </div>
    

    3. The Result

    • Total elements: 14 → 6
    • Hit area: 24px icons → 48px category rows
    • Error potential: Removed "Save" requirement by using auto-save with a veranda (engawa) transition zone.

    Next steps

    1. Group the 12 notification types into the suggested three core categories.
    2. Implement the engawa transition for the save state to remove the modal popup.
    3. Test the "covered-icon" logic on the header to ensure the 'Edit' state is clear from text weight alone.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Why is one app easy to use while another feels like work? It's almost never the colour. It's how many fields you fill in, where the main button sits, whether you see the full price up front and whether a mistake can be undone.

    This skill turns the Japanese school of product design and architecture into 17 rules you can check with a yes-or-no question — no arguments about taste.

    Where the rules come from

    • Product design. Naoto Fukasawa's "without thought" and Super Normal; Shigeo Shingo's poka-yoke at Toyota.
    • The Japanese house and garden. The tatami module, engawa, genkan, miegakure, shakkei, Fumihiko Maki's oku.
    • Emptiness. Kenya Hara's "Designing Design" and MUJI's kore de ii — "this will do".

    What it does

    • Scores a screen out of 34 with numeric thresholds for every rule.
    • Returns a table: block · finding · number · rule · swap.
    • Suggests swaps from a library of 40+ before → after cases.
    • Knows recipes for 8 screen types: settings, forms and checkout, tables, dashboards, onboarding, navigation, mobile, empty states.
    • Returns corrected HTML and CSS.

    What the rules don't allow

    Hiding what people press, showing state by colour alone, pre-selecting paid options, cutting meaning for the sake of "clean".

    See all 17 rules on a live before/after checkout: https://claude.ai/artifact/XkMHXC54MaeaqCSZL7aKbK

    Free for personal and work projects.

    Does not generate images or icons. Focuses on structure and behavior, not brand aesthetics. Numeric audits require detailed descriptions or code of the existing UI. It doesn't override discoverability, contrast or keyboard access, and never justifies hiding controls or pre-selecting paid options.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    2 uses

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    The skill analyzes your interface against 17 specific rules derived from Japanese product design and architecture, providing a objective score out of 34, a detailed findings table, and ready-to-use HTML/CSS fixes.

    This skill is designed for any AI agent capable of processing images or code snippets, including Claude, ChatGPT, and specialized developer assistants that support vision or file analysis.

    You will receive the complete prompt logic containing the 17-rule framework, the library of 40+ 'before and after' design swaps, and specialized recipes for 8 different screen types including checkouts and dashboards.

    No complex setup is required; once you import the skill into your preferred AI agent, you can simply upload a screenshot or paste your frontend code to receive an immediate ergonomic audit.

    The skill includes specific 'recipes' for mobile, desktop, and web-based interfaces, ensuring the ergonomic rules are applied correctly regardless of the device or screen size.

    New in Frontend & Web Apps