· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →TryHand Co., Ltd v1.4.0
Build production-ready UX
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Build this application UI with production UX contracts.
Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 20, 2026.
From the marketplace listing
Adds durable design context, cross-screen behavioral consistency, resilient interaction states, accessibility, localization, and verification to frontend implementation workflows.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: frontend-design description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. license: Complete terms in LICENSE.txt --- # Frontend Design Approach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. This client has already rejected proposals that felt templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take one real aesthetic risk you can justify. ## Ground it in the subject If the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. If there's any information in your memory about the human's preferences, context about what they're building, or designs you've made before – use that as a hint. The subject's own world, its materials, instruments, artifacts, and vernacular, is where distinctive choices come from. Build with the brief's real content and subject matter throughout. ## Design principles For web designs, the hero is a thesis. Open with the most characteristic thing in the subject's world, in whatever form makes sense for it: a headline, an image, an animation, a live demo, an interactive moment. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the template answer, only use if that's truly the best option. Typography carries the personality of the page. Pair the display and body faces deliberately, not the same families you would reach for on any other project, and set a clear type scale with intentional weights, widths, and spacing. Make the type treatment itself a memorable part of the design, not a neutral delivery vehicle for the content. Structure is information. Structural devices, numbering, eyebrows, dividers, labels, should encode something true about the content, not decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence - like a real process or a typed timeline where order carries information the reader needs. Question if choices like numbered markers actually make sense before incorporating them. Leverage motion deliberately. Think about where and if animation can serve the subject: a page-load sequence, a scroll-triggered reveal, hover micro-interactions, ambient atmosphere. An orchestrated moment usually lands harder than scattered effects; choose what the direction calls for. However, sometimes less is more, and extra animation contributes to the feeling that the design is AI-generated. Match complexity to the vision. Maximalist directions need elaborate execution; minimal directions need precision in spacing, type, and detail. Elegance is executing the chosen vision well. Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance. ## Process: brainstorm, explore, plan, critique, build, critique again For calibration: AI-generated design right now clusters around three looks: (1) a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta accent; (2) a near-black background with a single bright acid-green or vermilion accent; (3) a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns. All three are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, includi
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 2 — file references are metadata, not package contents.
---
name: frontend-design-premium
description: Production UX and durable design-context layer that must be used together with the upstream frontend-design skill when building, modifying, reviewing, or refactoring application UI. Use for dashboards, admin tools, SaaS screens, forms, tables, CRUD flows, multi-screen apps, design systems, localized products, Japan-market products, and Japanese-facing UI—even when the request only says “build”, “implement”, or names one screen. Proactively creates or maintains project DESIGN.md taste context, enforces cross-screen behavioral consistency, resilient interaction states, localization, Japan-native market/content/visual routing, layout stability, accessibility, and verification.
metadata:
compatibility: Requires the separately installed frontend-design Agent Skill. Python 3 is optional for bundled resolver and validation scripts.
author: frontend-design-premium contributors
version: "1.4.0"
upstream-skill: frontend-design
upstream-tested:
revision: "2026-02 — initial compatibility"
digest: "1608ea77fbb6fc30d13a97d12cfa8ebf31358d40f0dd97beed24829d6b3f45dd"
tested-with-premium: "1.4.0"
compatibility-policy:
strict-on-release: true
warn-on-untested: true
---
# Frontend Design Premium
Treat `frontend-design` as the visual-design base, project-root `DESIGN.md` as durable taste memory, and this skill as the production-behavior contract. Deliver a UI that is distinctive, operationally coherent, and consistent across future screens and agent sessions.
When this skill is used from a Pilot repository, also follow
`references/pilot-review.md` for pull-request finding levels and pass criteria.
## 0. Load the upstream skill first
This is composition, not a fork. The Agent Skills standard has no `extends` field, so enforce inheritance at runtime:
1. Load and follow the installed skill named `frontend-design` before planning or coding. Use the harness's native Skill mechanism when available.
2. If native skill loading is unavailable, locate it with `python <this-skill-dir>/scripts/resolve_frontend_design.py --print-path`, then read that `SKILL.md` completely.
3. Do not rely on a copied excerpt of upstream instructions. Loading the installed file is what keeps this skill aligned when `frontend-design` is upgraded.
4. If the dependency cannot be found, stop and report the missing `frontend-design` installation instead of silently approximating it.
> **Compatibility note:** This skill records a tested upstream content digest in its frontmatter (`upstream-tested.digest`).
> The resolver (`resolve_frontend_design.py --status`) reports one of five states: `MATCH`, `UNTESTED`, `MISSING`,
> `UNTRUSTED`, or `INCOMPATIBLE`. During interactive use, `UNTESTED` warns and continues. Release/CI validation
> (`validate_skill.py --strict`) fails unless the installed upstream is `MATCH`. The resolver never auto-downloads
> or upgrades upstream. See `VERSIONING.md` for the upgrade workflow.
Apply both skills. Upstream owns subject-specific aesthetic direction; this skill owns product behavior, consistency, safety, accessibility, and verification. Explicit business rules and an established project contract win. Never trade away accessibility, data safety, or cross-screen consistency for a visual flourish.
## 0a. Register gate — product/admin vs marketing landing page
Before reading any reference, classify the target:
- **Product / admin / SaaS / dashboard / forms / CRUD / tool:** premium behavior wins. You will read all relevant references, establish DESIGN.md, enforce consistency contracts, verify interaction states, and follow the full workflow below.
- **Marketing landing page / brand site / content site / one-shot hero:** upstream `frontend-design` owns the creative direction. This premium skill adds accessibility, layout stability, scrollbar, and reduced-motion rules from §4. Do **not** force UX-CONTRACT.md, consistency-system.md, data-entry-patterns.md, async-resilience.mPreview of the first 4,000 characters. Read full instructions →
Referenced files: 31 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 20, 2026.
plugins_6a7039f8e9708191bde88207b1919bf4
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.