Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/release-checklist/SKILL.md
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
Often used withplaytest-reportteam-polishsetup-engine
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/retrospective/SKILL.md
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.
Often used withproject-stage-detectteam-levelteam-narrative
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/reverse-document/SKILL.md
Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/review-all-gdds/SKILL.md
Holistic cross-GDD consistency and game design review. Reads all system GDDs simultaneously and checks for contradictions between them, stale references, ownership conflicts, formula incompatibilities, and game design theory violations (dominant strategies, economic imbalance, cognitive overload, pillar drift). Run after all MVP GDDs are written, before architecture begins.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/scope-check/SKILL.md
Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts. Use when user says 'any scope creep', 'scope review', 'are we staying in scope'.
Often used withteam-polishteam-audioplaytest-report
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/security-audit/SKILL.md
Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with remediation guidance. Run before any public release or multiplayer launch.
Often used withcommunity-led-growthph-community-outreach
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/setup-engine/SKILL.md
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Often used withart-bible
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/skill-improve/SKILL.md
Improve a skill using a test-fix-retest loop. Runs static checks, proposes targeted fixes, rewrites the skill, re-tests, and keeps or reverts based on score change.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/skill-test/SKILL.md
Validate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report).
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/smoke-check/SKILL.md
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/soak-test/SKILL.md
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/sprint-plan/SKILL.md
Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs.
Often used withbalance-checkestimateteam-combat
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/sprint-status/SKILL.md
Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/start/SKILL.md
First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions.
Often used withteam-audiosetup-engineproject-stage-detect
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/story-done/SKILL.md
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/story-readiness/SKILL.md
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is story X ready to implement'.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/team-audio/SKILL.md
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/team-combat/SKILL.md
Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat feature end-to-end.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/team-level/SKILL.md
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
lilangMaxSkilllilangMax/ClaudeCodeGameStudios/.claude/skills/team-live-ops/SKILL.md
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.
