Token导航 LogoToken导航

Agent Skill · 前端设计

gsp-logo(普惠制标志)

gsp-logo 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

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

总安装 285周安装 12GitHub Stars 29下载 86核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jubscodes/get-shit-pretty --skill gsp-logo

这个 Skill 是做什么的

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

该技能用于 Logo 设计与品牌标识建议。适用于矢量图形生成、多尺寸适配与变体设计。可在多种宿主环境中调用,输出可编辑的设计稿参考。安装命令:npx skills add https://github.com/jubscodes/get-shit-pretty --skill gsp-logo。

建议遵循简洁易识别原则,并考虑黑白与单色应用场景。

来源仓库内路径:skills/gsp-logo

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jubscodes/get-shit-pretty --skill gsp-logo;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

gsp-logo 怎么安装?

在终端执行 npx skills add https://github.com/jubscodes/get-shit-pretty --skill gsp-logo。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

gsp-logo 支持哪些 AI 工具?

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

gsp-logo 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

gsp-logo 是免费的吗?

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

gsp-logo 用的人多吗?

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

gsp-logo 安全吗?

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

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

值得选的地方

  • 同时适配 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只读未明确通过
gsp-logo

普惠制标志 · 本页

28529只读未明确通过

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

SKILL.md 原文

This is a standalone composable skill. It works two ways:

  1. Standalone — user runs /gsp-logo directly for logo exploration
  2. As a building block — the creative-director invokes this during the branding diamond to produce logo-directions.md

A logo system is more than a mark — it's a flexible identity that works at every size (favicon to billboard), in every context (light, dark, monochrome), and in every variation (primary, secondary, icon, wordmark).

Input: Brand context (strategy, archetype, name) or user description Output: logo-directions.md chunk with 3 directions, each with concept, rationale, variations, and usage rules Agent: None — inline skill with structured questioning

<execution_context> @${CLAUDE_SKILL_DIR}/chunk-format.md </execution_context>

InputMode
/gsp-logo --enrichEnrich existing logo-directions.md
/gsp-logoInteractive — design logo directions

Enrich mode (--enrich)

Read existing {BRAND_PATH}/identity/logo-directions.md. For each direction, enrich with:

  • Detailed construction geometry (grid, proportions, key relationships)
  • Complete variation specs (primary, secondary, icon, wordmark, monochrome, reversed)
  • Clear space rules expressed as fraction of mark height
  • Minimum size calculations (full lockup vs icon breakpoint)
  • Don'ts with specific examples

Overwrite logo-directions.md with enriched version. Preserve the creative concepts and rationale.

Interactive/context mode

Check what's available:

  1. Within a brand — read {BRAND_PATH}/BRIEF.md, {BRAND_PATH}/strategy/archetype.md, {BRAND_PATH}/strategy/positioning.md, {BRAND_PATH}/identity/color-system.md if they exist. Use brand strategy to drive logo concepts.
  2. Within a project — read {PROJECT_PATH}/brand.ref → resolve brand → load above.
  3. Standalone — no brand context. Ask the user directly.

If brand context exists, skip to Step 2 (derive directions from strategy).

Step 1: Interactive mode (no brand context)

Gather logo direction through questions. One AskUserQuestion at a time:

  1. What's the brand name? (open-ended)
  2. What does the brand do, and for whom? (open-ended — infer personality)
  3. Logo energy — use AskUserQuestion:

- Bold & geometric — "strong shapes, confident, modern" - Elegant & refined — "thin strokes, classic, understated" - Playful & expressive — "organic, hand-crafted feel, personality" - Technical & precise — "grid-based, systematic, engineered" - Minimal & typographic — "the name IS the logo, pure type"

  1. Any existing marks or elements to consider? (open-ended — "no" is fine)

Step 2: Design 3 directions

Each direction must be a genuinely different approach — not three variations of the same idea:

Per direction, define:

  • Concept name — a memorable label (e.g., "The Architect", "Living Mark", "Pure Type")
  • Concept description — what the mark represents and why. 2-3 sentences max.
  • Strategic rationale — connects to brand archetype/positioning: "This direction expresses [strategy element] because..."
  • Mark type — wordmark, lettermark, symbol, combination mark, emblem, abstract
  • Construction — key geometric relationships, grid alignment, proportions
  • Variations:

- Primary (full lockup) - Secondary (compact/stacked) - Icon (standalone mark, works at 16px) - Wordmark (type only, no symbol) - Monochrome (single color) - Reversed (on dark backgrounds)

  • Clear space — minimum padding expressed as fraction of mark height (e.g., "0.5x mark height on all sides")
  • Minimum size — smallest size before the mark breaks down (e.g., "24px for full lockup, 16px for icon")
  • Don'ts — specific anti-patterns for this direction (stretching, recoloring, busy backgrounds, etc.)

Direction diversity

Ensure the 3 directions span different mark types. If one is a wordmark, another should be a symbol-based mark. If one is geometric, another should be organic. Give the user a real choice, not three flavors of the same thing.

Step 3: Write logo-directions.md

Resolve output path:

  • Within a brand: {BRAND_PATH}/identity/logo-directions.md
  • Within a project: {PROJECT_PATH}/references/logo-directions.md
  • Standalone: display output, offer to save

Write following chunk-format.md format. Target: 100-140 lines.

Structure:

# Logo Directions

> Phase: identity | Brand: {name} | Generated: {DATE}

---

## Direction 1: {Concept Name}

**Concept:** {description}
**Rationale:** {connects to strategy}
**Mark type:** {type}
**Construction:** {geometric relationships}

### Variations
{primary, secondary, icon, wordmark, monochrome, reversed}

### Usage Rules
- Clear space: {rule}
- Minimum size: {rule}
- Don'ts: {anti-patterns}

## Direction 2: {Concept Name}
{same structure}

## Direction 3: {Concept Name}
{same structure}

---

## Related
- [color-system.md](./color-system.md)
- [typography.md](./typography.md)

Step 4: Completion

Display summary:

  /gsp-logo — 3 directions defined

    1. {concept name}  {mark type} — {one-line concept}
    2. {concept name}  {mark type} — {one-line concept}
    3. {concept name}  {mark type} — {one-line concept}

Use AskUserQuestion:

  • Continue to identity — proceed with /gsp-brand-identity
  • Explore a direction — deep dive into one direction
  • Done — that's all

平台分布

Codex

34.3%
按下载量换算29

Claude

29.31%
按下载量换算25

Cursor

19.31%
按下载量换算17

Gemini CLI

8.89%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills