Token导航 LogoToken导航

Agent Skill · 前端设计

frontend-design(前端设计)

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。

frontend-design 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为操作浏览器;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 473。

总安装 22,691周安装 955GitHub Stars 88下载 7,946核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:frontend-design(前端设计)
来源仓库:https://github.com/julianoczkowski/designer-skills
仓库路径:skills/frontend-design
安装命令:
npx skills add https://github.com/julianoczkowski/designer-skills --skill frontend-design
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/julianoczkowski/designer-skills --skill frontend-design

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

frontend-design 用于辅助前端页面、组件和样式开发,支持主流框架集成。适合生成或审查 React、Vue、Tailwind 等相关代码。通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。涉及页面改动时应配合本地预览和构建检查确认效果。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/frontend-design

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/julianoczkowski/designer-skills --skill fronte…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要操作浏览器,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

frontend-design 怎么安装?

在终端执行 npx skills add https://github.com/julianoczkowski/designer-skills --skill frontend-design。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

frontend-design 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

frontend-design 需要什么权限?

权限级别是操作浏览器。该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

frontend-design 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

frontend-design 用的人多吗?

公开数据是累计安装 22,691 次,近一周安装 955 次,下载 7,946 次,GitHub 88 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

frontend-design 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
frontend-design

前端设计 · 本页

22,69188操作浏览器未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

This skill guides creation of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic detail.

Example prompts

  • "Build the hero section from the brief"
  • "Create a card component in a Scandinavian style"
  • "I want this to feel like a Japanese magazine. Build the layout."
  • "Build the settings page. Use whatever style fits."

Before You Write Any Code

  1. Explore the existing codebase first. Scan specifically for:

- Component directories: components/, ui/, shared/ and list every component by name and its props/API - CSS variables / tokens: files named tokens.css, variables.css, theme.css, or :root declarations with custom properties - Tailwind config: tailwind.config.js or tailwind.config.ts, check theme.extend for custom values - UI framework themes: Material UI createTheme, Chakra extendTheme, shadcn globals.css and components.json - Storybook: .storybook/ directory or *.stories.* files indicating documented components - Font loading: Google Fonts links, @font-face declarations, font imports - Layout patterns: how existing pages handle grid, containers, breakpoints, and spacing - Package.json UI dependencies: tailwindcss, @mui/material, @chakra-ui/react, @radix-ui, lucide-react, framer-motion, etc. - If components exist that match or partially match what you need to build, extend or compose them. Do not create duplicates.

  1. Understand the context:

- What problem does this interface solve? Who uses it? - What is the intended emotional tone? - What are the hard constraints (framework, devices, performance, accessibility)?

  1. Commit to an aesthetic direction. Either the user names one (see philosophies below) or you choose one that fits the context. State your choice and why before writing code.

Aesthetic Philosophies

When the user names a philosophy or describes a vibe, use these as concrete implementation guides. Each philosophy defines typography, color, layout, spacing, motion, and detail treatment.

Dieter Rams (Functionalist)

Less but better. Every element earns its place. Nothing decorative without function.

  • Typography: Clean sans-serif (Helvetica Neue, Suisse Intl, Akkurat). Tight letterspacing on headings. Generous line height on body. One size scale, used strictly.
  • Color: Restrained. Monochromatic with a single functional accent. White or light grey backgrounds. Color is information, not decoration.
  • Layout: Strict grid. Clear functional hierarchy. Components aligned to a spatial system. No asymmetry for its own sake.
  • Spacing: Consistent, mathematical scale (4px/8px base). Generous padding. Breathing room between elements.
  • Motion: Minimal. Purposeful transitions only (state changes, reveals). No decorative animation.
  • Details: Subtle borders and dividers over shadows. Precise alignment. Rounded corners used sparingly and consistently.

Swiss / International Typographic

Objectivity through structure. The grid is sacred. Content is king.

  • Typography: Strong sans-serifs (Neue Haas Grotesk, Univers, Aktiv Grotesk). Dramatic scale contrast between headings and body. All-caps subheadings with generous letterspacing.
  • Color: High contrast. Black, white, and one primary color. Bold color blocks as compositional elements.
  • Layout: Rigid multi-column grid. Asymmetric balance. Text and image in dialogue. Alignment across elements is non-negotiable.
  • Spacing: Defined by the grid module. Gutters are part of the design, not afterthought.
  • Motion: Page transitions and scroll-triggered reveals that respect the grid. No playful bounce.
  • Details: Rules (horizontal lines) as structural elements. No gradients. No shadows. Flatness is the point.

Japanese Minimalism (Ma)

Negative space is content. Restraint communicates sophistication. Quiet over loud.

  • Typography: Thin-weight sans-serifs or elegant serifs (Noto Sans, Cormorant). Generous line height (1.8-2.0). Small body size with large whitespace margins.
  • Color: Muted naturals (warm greys, stone, sage, washi). Subtle tonal shifts over hard contrasts. Near-monochrome.
  • Layout: Asymmetric but balanced. Off-center content. Large empty areas are intentional. Content floats in space.
  • Spacing: Extreme whitespace. Padding and margins 2-3x what feels "normal." Elements breathe.
  • Motion: Slow, gentle fades (400-600ms). No bounce, no overshoot. Opacity transitions over position shifts.
  • Details: Hairline borders. Subtle texture (paper grain, linen). No sharp shadows. Soft, diffused effects.

Brutalist / Raw

Structure is visible. No polish. Anti-aesthetic is the aesthetic.

  • Typography: System fonts, monospace (JetBrains Mono, IBM Plex Mono, Courier), or aggressive display faces. Mixed sizes. Text as texture.
  • Color: Black and white primary. If color, it is raw and clashing (construction yellow, hazard orange, terminal green). No gradients.
  • Layout: Visible borders. Box model exposed. Stacked blocks. Deliberate roughness. Content first, beauty never.
  • Spacing: Tight or intentionally uneven. Padding that feels compressed.
  • Motion: None, or jarring (instant state changes, hard cuts). No easing.
  • Details: Visible outlines. Default browser form elements can be intentional. Text-only interfaces. No icons unless functional.

Scandinavian

Warmth plus restraint. Functional beauty. Accessible by default.

  • Typography: Rounded, friendly sans-serifs (Nunito, Poppins, Circular, Cera Pro). Medium weights. Comfortable reading sizes.
  • Color: Natural palette. Warm whites, soft blues, muted greens, clay. Pastel accents. No pure black (use charcoal).
  • Layout: Clean and open. Card-based. Rounded corners (8-12px). Comfortable, generous layouts.
  • Spacing: Generous but not extreme. Everything feels approachable and uncluttered.
  • Motion: Gentle, natural easing. Subtle hover lifts. Content that settles into place.
  • Details: Soft shadows (large blur, low opacity). Rounded elements. Warm undertones in greys. Illustration-friendly.

Art Deco / Geometric

Bold symmetry. Decorative precision. Statement and luxury.

  • Typography: Geometric display faces (Futura, Poiret One, Josefin Sans). All-caps headlines with extreme letterspacing. Serif body text for contrast.
  • Color: Rich and deep. Gold/champagne, emerald, navy, burgundy, black. Metallic accents (gold gradients, shimmer effects).
  • Layout: Symmetrical and centered. Strong vertical axis. Decorative frames and borders. Layered depth.
  • Spacing: Structured and formal. Padding is architectural.
  • Motion: Elegant reveals. Staggered entrance animations. Parallax depth.
  • Details: Geometric patterns (chevrons, sunbursts, fan shapes). Ornamental borders. Texture (marble, brushed metal). Statement typography at hero scale.

Neo-Memphis

Playful chaos. Anti-corporate. Shapes as characters.

  • Typography: Mix of weights and styles. Clashing fonts is intentional. Oversized headlines. Text at angles.
  • Color: Bold primaries and neons. Clashing combinations (pink and yellow, blue and orange). No muted tones. Flat color, no gradients.
  • Layout: Broken grid. Overlapping elements. Shapes (circles, triangles, squiggles) as compositional elements. Asymmetric on purpose.
  • Spacing: Dense in some areas, empty in others. Rhythm is irregular.
  • Motion: Bouncy, playful. Exaggerated hover effects. Elements that wiggle, rotate, or pop.
  • Details: Thick borders. Geometric shapes as decoration. Patterns (dots, dashes, zigzags). Drop shadows with hard edges and bright colors.

Editorial / Magazine

Content-led design. Typography does the heavy lifting. Every page is a spread.

  • Typography: Display serif for headlines (Playfair Display, Fraunces, Instrument Serif). Clean sans for body (DM Sans, Source Sans). Dramatic scale (hero headlines at 72-120px). Pull quotes. Drop caps.
  • Color: Minimal. Black and white with one accent. Color used editorially (to highlight, not decorate).
  • Layout: Strong column grid (3-5 columns). Full-bleed images. Text wrapping. Mixed column widths. Vertical rhythm.
  • Spacing: Generous margins. Tight leading on headlines, open on body. Whitespace as a compositional tool.
  • Motion: Scroll-triggered reveals. Parallax on images. Smooth page transitions.
  • Details: Thin rules as dividers. Caption typography. Issue/date metadata. Print-inspired details (folio numbers, running headers).

Implementation Guidelines

  • Typography: Choose distinctive fonts loaded via Google Fonts or CDN. Avoid generic defaults (Inter, Roboto, Arial, system fonts). Pair a display font with a body font.
  • Color: Use CSS variables for consistency. Dominant color with sharp accents outperforms safe, evenly-distributed palettes.
  • Motion: CSS transitions for HTML. Framer Motion / Motion library for React. Focus on high-impact moments (page load reveals, state changes) over scattered micro-interactions.
  • Spatial composition: Unexpected layouts earn attention. Asymmetry, overlap, diagonal flow, grid-breaking elements. Or, if the philosophy demands it, strict grids executed with precision.
  • Backgrounds and depth: Create atmosphere. Gradient meshes, noise textures, geometric patterns, layered transparencies, grain overlays. Match the chosen philosophy.

NEVER produce generic AI aesthetics: purple gradients on white, Inter font, predictable card grids, cookie-cutter component layouts. Every output should feel designed for its specific context.

Match implementation complexity to the aesthetic vision. A Dieter Rams interface is 50 lines of precise CSS. A Neo-Memphis interface is 300 lines of creative chaos. Both are correct.

Mobile-First

Build mobile layout first, then scale up. This is non-negotiable.

  • Start with a single-column layout at 375px width.
  • Add complexity at each breakpoint (min-width media queries, not max-width).
  • Touch targets must be at least 44x44px on mobile.
  • Body text must be at least 16px on mobile (prevents iOS zoom on input focus).
  • Navigation must have a mobile-specific pattern (hamburger, bottom tabs, or drawer). Do not rely on horizontal nav bars that overflow.
  • Test that line lengths stay comfortable (45-75 characters) at every breakpoint.

Dark Mode

If a design tokens file exists (from /design-tokens), use its dark mode palette. If not, generate dark mode support alongside the light theme.

  • Use CSS custom properties so switching themes means changing variable values, not rewriting components.
  • Support both prefers-color-scheme media query (system preference) and a [data-theme="dark"] attribute (manual toggle).
  • Do not simply invert colors. Dark backgrounds should be warm or cool to match the philosophy (warm charcoal for Scandinavian, cool slate for Swiss, near-black for Brutalist).
  • Reduce pure white text to off-white (e.g., #E5E5E5 or rgba(255,255,255,0.87)) to reduce eye strain.
  • Shadows in dark mode should be darker and more transparent, not the same values as light mode.
  • Accent colors may need lightness adjustments to maintain WCAG contrast ratios against dark backgrounds.
  • Include a prefers-reduced-motion media query for users who need it. Disable or simplify all animations and transitions within that query.

适合场景

01

前端页面设计

02

生成更有辨识度的 UI

03

避免模板化 AI 页面

04

需要统一视觉方向时

能力概览

能力 1

建立明确视觉方向

能力 2

约束排版、色彩、动效和空间布局

能力 3

提醒避免通用模板化设计

能力 4

要求生成可运行的前端实现

平台分布

Codex

38.15%
按下载量换算3,031

Claude

28.24%
按下载量换算2,244

Cursor

18.04%
按下载量换算1,433

Gemini CLI

8.68%
按下载量换算690

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills