github
01MCP server Claude CodeCodexCursor +2
One of 2 in .mcp.json
GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.
MCP server Claude CodeCodexCursor +2
One of 2 in .mcp.json
GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.
MCP server Claude CodeCodexCursor +2
One of 2 in .mcp.json
MCP server "figma" as configured in jubscodes/get-shit-pretty. Runs locally from the @anthropic/mcp-figma npm package. Needs 1 environment variable to run.
Skill Claude Code needs its repo
Verify GSP pipeline integrity — agent/skill contracts, installer correctness, runtime compatibility, version sync, and template coherence. Internal development tool for GSP maintainers.
Skill Claude Code
Benchmark GSP token budget — capture snapshots, compare between versions/PRs, track improvements over time.
Skill Claude Code
Maintain CHANGELOG.md from git history — update Unreleased section, promote to versioned release, or rebuild from scratch. Follows Keep a Changelog format.
Skill Claude Code
Read milestones, issues, and branch state to propose the next task for GSP development.
Skill Claude Code
Quality eval for any non-trivial change to skill/agent/methodology files — spawns parallel evaluator agents that score against a fixed 8-dimension rubric (change intent + skill intent coherence + 6 preservation dimensions). Covers additions, modifications, refactors, trims, and rewrites under gsp/skills/ or…
Skill Claude Code
Quick drift-catching pass — find and fix version mismatches, stale references, count drift, and terminology rot after moderate changes. Run often.
Skill Claude Code needs its repo
AI-driven semantic analysis of GSP skills and agents — finds dead weight, contradictions, vagueness, and over-prompting that automated checks can't catch.
Skill Claude Code needs its repo
Publish a new GSP version — bump versions, changelog, audit, tag, release, prompt npm publish.
Skill Claude Code
Research live documentation for Claude Code, OpenCode, Gemini CLI, and Codex CLI — check discovery paths, tool names, frontmatter fields, and flag drift against the GSP installer. Internal GSP development tool.
Agent Claude Code
Audits designs and code for WCAG 2.2 AA/AAA compliance. Spawned by /gsp-accessibility or /gsp-project-critique.
Agent Claude Code
Audits existing brand identities for evolution. Spawned by /gsp-brand-audit.
Agent Claude Code
Brand coherence auditor — scores intensity dials against archetype and surfaces tensions between declared values and expressed output.
Agent Claude Code
Creative director — makes visual identity decisions (logo, color, typography, imagery). Domain skills enrich with technical precision. Spawned by /gsp-brand-identity.
Agent Claude Code
Operationalizes brand identity for projects — assembles .yml, STYLE.md, token mapping, component specs, guidelines. Spawned by /gsp-brand-guidelines.
Agent Claude Code
Researches market landscape and competitive positioning. Spawned by /gsp-brand-research.
Agent Claude Code
Develops brand strategy, voice, and messaging. Spawned by /gsp-brand-strategy.
Agent Claude Code
Detects and fixes AI-slop craft failures in React/Tailwind codebases. Spawned by /gsp-polish.
Agent Claude Code
Implements designs in the codebase as production-ready frontend code. Spawned by /gsp-project-build.
Agent Claude Code
Structured design critique — strategy, brand contract, usability (Nielsen-scored), accessibility, content, implementation, and taste. Spawned by /gsp-project-critique.
Agent Claude Code
Designs UI/UX screens and interaction flows following Apple HIG. Spawned by /gsp-project-design.
Agent Claude Code
Deep project research — UX patterns, competitor UX, technical approaches, reference specs. Spawned by /gsp-project-research.
Agent Claude Code
QA validates actual codebase implementation against design intent. Spawned by /gsp-project-review.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: