Token导航 LogoToken导航

Agent Skill · 效率

style-guide-generator(风格指南生成器)

style-guide-generator 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

style-guide-generator 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描有提醒项,按安装量在效率类的 21,003 个 Skill 里排第 482。

总安装 86,344周安装 3,634GitHub Stars 2下载 30,235核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:style-guide-generator(风格指南生成器)
来源仓库:https://github.com/tomstools11/style-guide-generator
安装命令:
openclaw skills install style-guide-generator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install style-guide-generator

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

从 URL、屏幕截图和现有文档生成全面的网站风格指南和设计系统。当用户要求从网站、应用程序或现有材料创建风格指南、设计系统文档、品牌指南文档或设计规范时,请使用此技能。该技能可以按照行业标准的样式指南结构生成专业的 PDF 输出。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install style-guide-generator;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

style-guide-generator 怎么安装?

在终端执行 openclaw skills install style-guide-generator。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

style-guide-generator 支持哪些 AI 工具?

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

style-guide-generator 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

style-guide-generator 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

style-guide-generator 用的人多吗?

公开数据是累计安装 86,344 次,近一周安装 3,634 次,下载 30,235 次,GitHub 2 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

style-guide-generator 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

效率类 Skill 对比

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

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
style-guide-generator

风格指南生成器 · 本页

86,3442需要联网MIT-0有提醒

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

SKILL.md 原文

name
style-guide-generator
description
Generate comprehensive website style guides and design systems from URLs, screenshots, and existing documentation. Use this skill when users ask to create a style guide, design system documentation, brand guidelines document, or design specification from a website, app, or existing materials. This skill produces professional PDF outputs following industry-standard style guide structure.

Style Guide Generator

Overview

Generate professionally formatted website style guides and design systems by analyzing provided URLs, screenshots, uploaded files, and user requirements. Output comprehensive PDF documents that serve as the single source of truth for design and development teams.

Workflow Decision Tree

When a user requests a style guide, follow this decision tree:

  1. Gather Information

- If user provides URL → Use web_fetch to analyze the website - If user provides screenshots/images → Analyze visual elements - If user provides existing documentation → Extract and structure information - If user provides minimal information → Ask clarifying questions about brand, goals, and requirements

  1. Extract Design Elements

- Colors (primary, secondary, accent, text, background, success, warning, error) - Typography (fonts, weights, sizes, line heights) - Logo usage guidelines - Iconography style - Imagery preferences - UI component patterns - Layout and spacing systems - Accessibility requirements

  1. Structure Content

- Follow the standard template structure (see Template Structure section) - Organize extracted information into appropriate sections - Add mission/vision if provided or inferred - Document design principles - Create component specifications

  1. Generate PDF

- Use the PDF skill to create a professional document - Apply consistent formatting and typography - Include tables for color palettes, typography specs, and component states - Ensure accessibility with proper contrast ratios - Add version number and last updated date

Standard Template Structure

Every style guide should follow this professional structure (based on industry best practices):

1.0 Introduction

  • Version number and last updated date
  • Purpose and scope statement
  • Target audience (design and development teams)

1.1 Mission & Vision

  • Company mission statement
  • Company vision statement
  • Strategic positioning

1.2 Design Principles

  • 4-6 core principles that guide design decisions
  • Each principle with name and description
  • Examples: "Clarity Above All", "Empowerment Through Simplicity", "Consistency Builds Trust", "Human-Centered"

2.0 Brand Identity

2.1 Logo Usage
  • Primary logo specifications
  • Clear space requirements
  • Incorrect usage examples
  • Minimum size requirements
  • Color variations (full color, black, white)
2.2 Color Palette
  • Organized table with Role, Color Name, HEX, and RGB values
  • Primary colors (1-2)
  • Secondary colors (1-3)
  • Accent colors
  • Text colors
  • Background colors
  • System colors (Success, Warning, Error)
  • Accessibility notes for each color combination
2.3 Typography
  • Heading font specifications (H1, H2, H3)
  • Body text specifications
  • Caption/small text specifications
  • Font families, weights, sizes, and line heights in tabular format
  • Web font loading considerations
  • Fallback fonts
2.4 Iconography
  • Icon style guidelines (outlined, filled, line weight)
  • Grid system specifications
  • Size variants
  • Usage examples
  • Link to icon library
2.5 Imagery
  • Photography style guidelines
  • Illustration style guidelines
  • Image treatment specifications
  • Do's and don'ts
  • Quality requirements

3.0 Content Style Guide

3.1 Voice and Tone
  • Voice characteristics (consistent attributes)
  • Tone variations (how voice adapts to context)
  • Examples for different scenarios
3.2 Grammar and Mechanics
  • Punctuation rules
  • Capitalization standards
  • Voice preference (active/passive)
  • Number formatting
  • Date and time formatting

4.0 UI Components

4.1 Buttons
  • State variants (Primary, Secondary, Tertiary, Disabled)
  • Size variants
  • Usage guidelines
  • Code snippets (HTML/CSS)
  • Accessibility requirements
4.2 Forms
  • Input field specifications
  • Label positioning
  • Validation states
  • Required field indicators
  • Error message styling
  • Help text formatting
4.3 [Additional Components as needed]
  • Cards
  • Modals
  • Navigation
  • Tables
  • Alerts/Notifications
  • Tooltips
  • Badges
  • Progress indicators

5.0 Layout & Grid

  • Grid system specifications (columns, gutters)
  • Responsive breakpoints
  • Spacing scale (base unit and multipliers)
  • Container widths
  • Margin and padding conventions

6.0 Accessibility (A11y)

  • WCAG compliance level (2.1 AA standard)
  • Color contrast requirements
  • Alt text guidelines
  • Keyboard navigation standards
  • Screen reader considerations
  • Focus indicators

7.0 Resources

  • Links to design files (Figma, Sketch, Adobe XD)
  • Icon library location
  • Illustration library location
  • Font files repository
  • Code repository
  • Additional documentation

8.0 Changelog

  • Version history with dates
  • Changes summary for each version

Information Extraction Process

When analyzing provided materials, extract the following systematically:

From URLs/Websites:

  1. Fetch the website using web_fetch
  2. Analyze HTML/CSS for:

- Color values (background-color, color properties) - Font families and typography (font-family, font-size, font-weight) - Spacing patterns (margin, padding values) - Component structures

  1. Take note of:

- Visual hierarchy - Button styles and states - Form element treatments - Navigation patterns - Responsive behavior (if observable)

From Screenshots/Images:

  1. Identify color palette using visual analysis
  2. Determine typography hierarchy
  3. Note spacing and layout patterns
  4. Identify UI component variants
  5. Observe design principles in practice

From Existing Documentation:

  1. Extract mission/vision statements
  2. Gather existing brand guidelines
  3. Collect color specifications
  4. Document current typography standards
  5. Note any existing component libraries

Creating Professional Tables

Use well-formatted tables for specifications. Example formats:

Color Palette Table:

| Role       | Color       | HEX     | RGB           |
|------------|-------------|---------|---------------|
| Primary    | Brand Blue  | #378DFF | 55, 141, 255  |
| Secondary  | Light Blue  | #A5CAFF | 165, 202, 255 |

Typography Table:

| Element | Font Family | Weight  | Size (px) | Line Height |
|---------|-------------|---------|-----------|-------------|
| H1      | Inter       | Bold    | 48        | 1.2         |
| H2      | Inter       | Bold    | 36        | 1.3         |
| Body    | Inter       | Regular | 16        | 1.5         |

Button States Table:

| State     | Appearance              | Usage                          |
|-----------|-------------------------|--------------------------------|
| Primary   | Solid fill, primary     | Main call to action on a page  |
| Secondary | Outline, primary color  | Secondary actions              |
| Tertiary  | Text only              | Less important actions         |

PDF Generation Best Practices

  1. Professional Formatting:

- Use consistent heading hierarchy - Apply proper spacing between sections - Utilize tables for structured data - Include visual examples where possible

  1. Typography:

- Use professional fonts (Inter, Roboto, or system fonts) - Maintain consistent sizing hierarchy - Ensure sufficient line height for readability

  1. Color Usage:

- Show color swatches with hex codes - Ensure sufficient contrast for accessibility - Document color roles clearly

  1. Organization:

- Number sections clearly (1.0, 1.1, 2.0, etc.) - Include table of contents for longer guides - Use page breaks appropriately - Add page numbers

  1. Accessibility:

- Ensure document is screen-reader friendly - Use proper heading structure - Include alt text for images - Maintain minimum font size of 12pt

Handling Incomplete Information

When information is missing or unclear:

  1. Make Reasonable Inferences:

- Extract colors from provided screenshots - Infer typography from website analysis - Estimate spacing based on visual patterns

  1. Use Placeholders:

- "[Insert company mission statement]" for unknown content - "[Link to design files]" for unavailable resources - "Version 1.0" and current date as defaults

  1. Ask Clarifying Questions:

- "What is your company's mission statement?" - "Do you have existing brand colors or should I extract them from the website?" - "Are there specific accessibility requirements beyond WCAG 2.1 AA?"

  1. Provide Templates:

- Include example text for sections that need user input - Show format for content they should provide - Give guidance on what information would be ideal

Example User Interactions

Example 1: URL-Based Request User: "Create a style guide for my website at example.com" Process:

  1. Fetch website with web_fetch
  2. Analyze HTML/CSS for design system
  3. Extract colors, fonts, spacing
  4. Structure into standard template
  5. Generate professional PDF
  6. Provide download link

Example 2: Screenshot-Based Request User: "Here are screenshots of my app. Create a style guide." [uploads images] Process:

  1. Analyze images for visual elements
  2. Extract color palette
  3. Identify typography patterns
  4. Document component styles
  5. Fill in template structure
  6. Generate PDF with findings
  7. Provide download link

Example 3: Comprehensive Request User: "Create a style guide using my website URL, these brand colors [list], and our mission statement [text]" Process:

  1. Combine all provided information
  2. Fetch and analyze website
  3. Integrate provided brand elements
  4. Structure complete style guide
  5. Generate professional PDF
  6. Provide download link

Quality Checklist

Before delivering the style guide PDF, verify:

  • [ ] All sections are complete or marked as placeholders
  • [ ] Color palette includes HEX and RGB values
  • [ ] Typography specifications are detailed (family, weight, size, line height)
  • [ ] Tables are properly formatted and aligned
  • [ ] Accessibility requirements are documented
  • [ ] Version number and date are included
  • [ ] Resources section links are provided (even if placeholder)
  • [ ] Changelog is started with version 1.0
  • [ ] PDF is professionally formatted
  • [ ] Document is ready for team distribution

Resources

This skill uses the following bundled resources:

assets/template.pdf

The base template PDF that demonstrates the professional structure and formatting that all generated style guides should follow. This file serves as a reference for structure, section organization, and formatting standards.

scripts/analyze_website.py

Python script to extract design system information from websites, including colors, typography, and component patterns. Can be used to automatically gather design specifications from live URLs.

references/design_system_examples.md

Reference document containing examples of well-structured design systems and style guides from leading companies. Use this for inspiration on content organization and presentation standards.

平台分布

OpenClaw

81.2%
按下载量换算24,551

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills