← Back to Skills Marketplace
wpank

Frontend Design

by wpank · GitHub ↗ · v1.0.0
cross-platform ✓ Security Clean
830
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install frontend-design-guidelines
Description
Create distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Focuses on creative direction and memorable design choices.
README (SKILL.md)

Frontend Design

Create memorable frontend interfaces that stand out from generic AI-generated aesthetics through bold creative choices.

See also: ui-design for fundamentals (typography, color, spacing), web-design for CSS patterns.

Installation

OpenClaw / Moltbot / Clawbot

npx clawhub@latest install frontend-design

WHAT This Skill Does

Guides creation of visually distinctive web interfaces by:

  • Establishing a bold aesthetic direction before coding
  • Making intentional typography, color, and spatial choices
  • Implementing motion and micro-interactions that delight
  • Avoiding the predictable patterns that mark AI-generated UIs

WHEN To Use

  • Building a new component, page, or web application
  • Creating landing pages, marketing sites, or product UIs
  • Redesigning interfaces to be more memorable
  • Any frontend work where visual impact matters

KEYWORDS

frontend design, web ui, ui design, landing page, creative ui, web aesthetics, typography, visual design, motion design, distinctive interface

Design Thinking Process

Before writing code, commit to an aesthetic direction:

1. Understand Context

  • Purpose: What problem does this interface solve?
  • Audience: Who uses it and what do they expect?
  • Constraints: Framework, performance, accessibility requirements

2. Choose a Bold Direction

Pick an extreme aesthetic — mediocrity is forgettable:

Direction Characteristics
Brutally Minimal Stark, essential, nothing extra
Maximalist Chaos Dense, layered, overwhelming intentionally
Retro-Futuristic Blends vintage aesthetics with modern tech
Organic/Natural Soft, flowing, nature-inspired
Luxury/Refined Premium materials, subtle elegance
Playful/Toy-like Fun, approachable, bright
Editorial/Magazine Type-forward, grid-based
Brutalist/Raw Exposed structure, anti-design
Art Deco/Geometric Bold shapes, symmetry, ornament
Industrial/Utilitarian Function-forward, robust

3. Identify the Memorable Element

What single thing will someone remember about this interface? Commit to it.

Aesthetic Guidelines

Typography

NEVER use generic fonts:

  • Arial, Helvetica, system-ui
  • Inter, Roboto (unless highly intentional)

DO choose distinctive fonts:

  • Pair a characterful display font with a refined body font
  • Explore: Space Grotesk, Clash Display, Cabinet Grotesk, Satoshi, General Sans, Instrument Serif, Fraunces, Newsreader
/* Example pairing */
--font-display: 'Clash Display', sans-serif;
--font-body: 'Satoshi', sans-serif;

Color & Theme

  • Commit to a cohesive palette — don't hedge with safe choices
  • Dominant + accent outperforms evenly-distributed colors
  • Use CSS variables for consistency
  • Avoid purple gradients on white (the "AI default")
:root {
  --color-bg: #0a0a0a;
  --color-surface: #141414;
  --color-text: #fafafa;
  --color-accent: #ff4d00;
  --color-muted: #666666;
}

Spatial Composition

Break expectations:

  • Asymmetry over perfect balance
  • Overlap elements intentionally
  • Diagonal flow or unconventional layouts
  • Generous negative space OR controlled density — not middle ground
  • Grid-breaking elements that draw attention

Motion & Interaction

Focus on high-impact moments:

  • Page load: Staggered reveals with animation-delay
  • Scroll-triggered animations that surprise
  • Hover states with personality
  • Prefer CSS animations for HTML; Motion library for React
/* Staggered entrance */
.card { animation: fadeUp 0.6s ease-out backwards; }
.card:nth-child(1) { animation-delay: 0.1s; }
.card:nth-child(2) { animation-delay: 0.2s; }
.card:nth-child(3) { animation-delay: 0.3s; }

@keyframes fadeUp {
  from { opacity: 0; transform: translateY(20px); }
  to { opacity: 1; transform: translateY(0); }
}

Backgrounds & Atmosphere

Create depth and atmosphere:

  • Gradient meshes and multi-stop gradients
  • Noise textures and grain overlays
  • Geometric patterns or subtle grids
  • Layered transparencies
  • Dramatic shadows or complete flatness
  • Custom cursors for interactive elements

Implementation Principles

Match Complexity to Vision

  • Maximalist vision → elaborate code with extensive animations
  • Minimalist vision → restraint, precision, perfect spacing
  • Elegance = executing the vision well, not adding more

Vary Between Generations

Never converge on patterns:

  • Alternate light/dark themes
  • Use different font families each time
  • Explore different aesthetic directions
  • Each design should feel unique

NEVER Do

  1. NEVER use generic font families (Inter, Roboto, Arial, system fonts)
  2. NEVER use purple gradients on white backgrounds — the "AI aesthetic"
  3. NEVER use predictable, cookie-cutter layouts
  4. NEVER skip the design thinking phase — understand before building
  5. NEVER hedge with safe, middle-ground aesthetics — commit to a direction
  6. NEVER forget that distinctive design requires distinctive code
  7. NEVER converge on the same patterns across generations — vary intentionally
  8. NEVER add complexity without purpose — minimalism and maximalism both require intention
Usage Guidance
This is an instruction-only design guideline and appears coherent and low-risk: it asks for nothing sensitive and contains only style/process guidance and small CSS examples. Before installing or copying any files from the referenced GitHub path or running the README's npx commands, verify the source repository and prefer official release URLs. Also consider: (1) license — the files include an Apache 2.0 license; (2) practical impacts — some 'NEVER use' rules (e.g., avoiding system fonts) are stylistic and could affect accessibility or compatibility, so review for your project's needs; (3) font usage may require separate font licenses. If you plan to run any install commands fetched from remote servers, audit those commands first. Overall, no security red flags in the skill content itself.
Capability Analysis
Type: OpenClaw Skill Name: frontend-design-guidelines Version: 1.0.0 The skill bundle contains metadata, a standard Apache 2.0 license, and documentation (`SKILL.md`, `README.md`) for an AI agent focused on frontend design. The `SKILL.md` file, which serves as instructions for the AI agent, provides detailed guidance on design principles, typography, color, and layout, all aimed at achieving distinctive visual interfaces. There are no instructions for the agent to perform malicious actions such as data exfiltration, unauthorized command execution, or prompt injection against the user. Installation instructions in `README.md` involve standard package manager commands and local file copies, without any suspicious external fetches or execution patterns. All content aligns with the stated purpose and lacks any indicators of malicious intent or significant vulnerabilities.
Capability Assessment
Purpose & Capability
The name/description (distinctive frontend design guidance) matches the contents of SKILL.md and README. The skill is purely prescriptive design guidance and does not ask for unrelated capabilities or credentials.
Instruction Scope
SKILL.md contains only design process, CSS examples, and aesthetic rules. It does not instruct the agent to read system files, access environment variables, post data to external endpoints, or run shell commands. No scope creep detected.
Install Mechanism
There is no formal install spec in the registry metadata and no code files to run, so risk from installation is low. README contains example install/copy commands (npx clawhub install, npx add with a GitHub tree URL, copying from ~/.ai-skills) — these are informational only. The 'npx add https://github.com/.../tree/...' line is non-standard (npx typically expects a package or git repo URL) and should be treated as documentation rather than an authoritative install source; exercise normal caution before running arbitrary install commands from an unknown source.
Credentials
The skill declares no required environment variables, credentials, or config paths and SKILL.md does not reference any secrets or system credentials. Requested environment access is proportional (none).
Persistence & Privilege
Flags are default (always: false, user-invocable: true, model invocation allowed). The skill does not request persistent presence or modify other skills or system-wide settings. Autonomous invocation is allowed by default but is not coupled with any sensitive capabilities here.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install frontend-design-guidelines
  3. After installation, invoke the skill by name or use /frontend-design-guidelines
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of the skill. - Added complete documentation (README.md) outlining installation, usage, creative process, and aesthetic guidelines for designing distinctive, production-grade frontend interfaces.
Metadata
Slug frontend-design-guidelines
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Frontend Design?

Create distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Focuses on creative direction and memorable design choices. It is an AI Agent Skill for Claude Code / OpenClaw, with 830 downloads so far.

How do I install Frontend Design?

Run "/install frontend-design-guidelines" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Frontend Design free?

Yes, Frontend Design is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Frontend Design support?

Frontend Design is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Frontend Design?

It is built and maintained by wpank (@wpank); the current version is v1.0.0.

💬 Comments