api-design
CommandREST API design best practices. Use when designing APIs, choosing status codes, or creating endpoints.
Sync managed GSD skills across runtime roots so multi-runtime users stay aligned after an update
$ npx -y skills add Tibsfox/gsd-skill-creator --agent claude-code
name: gsd:sync-skills description: Sync managed GSD skills across runtime roots so multi-runtime users stay aligned after an update allowed-tools: - Bash - AskUserQuestion gsd-build-source: 1.38.3 gsd-build-source-url: https://github.com/gsd-build/get-shit-done/blob/v1.38.3/commands/gsd/sync-skills.md local-modified: false gsd-skill-creator-vendored-at: 2026-04-25
<objective> Sync managed `gsd-*` skill directories from one canonical runtime's skills root to one or more destination runtime skills roots.
Routes to the sync-skills workflow which handles:
</objective>
An adaptive learning and coprocessor architecture for Claude Code, built as an extension to GSD (open-gsd)
REST API design best practices. Use when designing APIs, choosing status codes, or creating endpoints.
Reviews code for bugs, style, and best practices. Use when reviewing PRs or checking code quality.
Creates context handoff documents for session continuity. Use when ending sessions, switching tasks, or handing off work.
Thinking frameworks for decisions and problem analysis. Use when evaluating options, root causes, or prioritizing.
Environment configuration and secrets management. Use when setting up .env files, managing secrets, or configuring environments.
Safe file operation patterns. Use when performing bulk file operations or writing deployment scripts.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.