<< All versions
Skill v1.0.1
currentAutomated scan100/100jubscodes/get-shit-pretty/gsp-help
+3 new
──Details
PublishedJune 16, 2026 at 11:42 PM
Content Hashsha256:00aed03da43276b6...
Git SHA5754ce8c44cd
Bump Typepatch
──Files
Files (1 file, 5.3 KB)
SKILL.md5.3 KBactive
SKILL.md · 130 lines · 5.3 KB
version: "1.0.1" name: gsp-help description: Show all skills user-invocable: true
<objective> Display the complete GSP skill reference as plain text.
Output ONLY the reference content below. Do NOT add:
- Project-specific analysis
- File context or git status
- Next-step suggestions
- Any commentary beyond the reference
</objective>
<process>
Version
GSP version: !cat ${CLAUDE_SKILL_DIR}/../../VERSION 2>/dev/null || echo "0.4.3"
Output the reference
Output the following as plain text. Use Unicode characters (───, ◇, ├──, └──, │, →) for visual structure.
Skill names are left-padded with 4 spaces. Descriptions start at column 27 (4 indent + 23 max skill name width).
/gsp- ◇◇ v{VERSION}skill reference─── Getting Started ──────────────────/gsp-start start here — picks up where you left off/gsp-help this skill reference/gsp-progress how pretty are we?─── Branding ─────────────────────────/gsp-brand-brief define your brand through guided Q&A/gsp-brand-research research your market and audience/gsp-brand-strategy define positioning, personality, voice and messaging/gsp-brand-identity create visual identity/gsp-brand-guidelines build design system tokens and components/gsp-brand-sync sync brand to match a project's shipped state/gsp-brand-refine tweak brand tokens mid-project without re-running identity/gsp-brand-audit audit existing brand before evolving (optional)─── Project ──────────────────────────/gsp-project-brief scope what you're building/gsp-project-research research UX patterns and approaches/gsp-project-design design screens and flows/gsp-project-critique critique designs + accessibility audit/gsp-project-build implement designs in the codebase/gsp-project-review QA validate implementation against designs/gsp-add-reference add reference material to a project─── Expertise ───────────────────────/gsp-color color systems — palettes, contrast, semantic mapping, dark mode/gsp-typography type systems — scale, pairing, fluid type, vertical rhythm/gsp-visuals visual direction — imagery, 3D, video, textures/gsp-icons icon systems — library, sizing, containers, custom SVG/gsp-logo logo directions — concepts, variations, usage rules/gsp-accessibility contrast, tokens, design/code audit, statement/gsp-style apply a design style preset─── Utilities ────────────────────────/gsp-design-system scan and document existing design system state/gsp-scaffold deterministic stack setup — deps, configs, verify build/gsp-doctor check project health/gsp-update update GSP to latest version─── Easter Eggs ────────────────────/gsp-art ASCII art studio/gsp-pretty surprise terminal art─── Flow ─────────────────────────────brand first, then build.— or —quick mode: pick a style → jump straight to project.branding brief → research → strategy → identity → guidelinesproject brief → research → design → critique → build → review↑ ↑critique loop QA loopquick style → brief → research → design → critique → build → reviewrun any skill directly — routing is optional.─── Directory Structure ──────────────.design/├── branding/│ └── {brand}/│ ├── config.json brand config│ ├── STATE.md progress tracking│ ├── discover/ research chunks│ ├── strategy/ strategy + voice and messaging│ ├── identity/ visual identity│ └── system/ tokens + components└── projects/└── {project}/├── config.json project config├── STATE.md progress tracking├── brand.ref brand reference├── brief/ scope + adaptations├── research/ UX + tech research├── design/ screen specs + preview├── critique/ design critique├── build/ BUILD-LOG.md├── review/ QA acceptance├── references/ custom reference material└── exports/INDEX.md chunk indexget-shit-pretty v{VERSION}github.com/jubscodes/get-shit-pretty
Replace {VERSION} with the value read from the VERSION file.
Do NOT add any text, commentary, or suggestions after this output. </process>