Token导航 LogoToken导航TokenDH.com
前端设计只读github未标认证来源可访问许可证需确认审计通过

gsp-logo普惠制标志

Agent Skill

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

总安装

285

周安装

12

GitHub Stars

29

下载量

86
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

该技能用于 Logo 设计与品牌标识建议。

  • 适用于矢量图形生成、多尺寸适配与变体设计。
  • 可在多种宿主环境中调用,输出可编辑的设计稿参考。
  • 安装命令:npx skills add https://github.com/jubscodes/get-shit-pretty --skill gsp-logo。
  • 建议遵循简洁易识别原则,并考虑黑白与单色应用场景。

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

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