All authors
Claude Skills by furkantokkan
github.com/furkantokkan189 skills0 installs14 views
- ReferencesAudit 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.Votes: 0GitHub stars: 10
- Setup EngineConfigure 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.Votes: 0GitHub stars: 10
- ReferencesConfigure or audit this template as a real Unity project. Pins the repository's existing Unity version, canonical paths/stack, automation order, ownership, and risk gates; it does not offer other engines.Votes: 0GitHub stars: 10
- Skill ImproveImprove one skill with a predictable scoped test-fix-retest loop. Diagnose completion, routing, invocation, duplication, and instruction hygiene as well as structural checks; apply only when explicitly requested.Votes: 0GitHub stars: 10
- ReferencesImprove one skill with a scoped test-fix-retest loop. Analysis is read-only unless --apply is supplied; the target skill is the only writable source file.Votes: 0GitHub stars: 10
- Skill TestValidate skill files for structural compliance, checkable completion, single-source routing, invocation policy, and instruction hygiene; keep instruction conformance distinct from executed Unity evidence.Votes: 0GitHub stars: 10
- ReferencesValidate skill files with structural checks, instruction-level specs, category rubrics, and externally orchestrated Unity fixture evaluations. Static/spec results never substitute for compile and test evidence.Votes: 0GitHub stars: 10
- Smoke CheckRun 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.Votes: 0GitHub stars: 10
- ReferencesRun critical Unity compilation, EditMode, PlayMode, console, and task-evidence checks for tracked tasks, a feature, sprint, or release candidate.Votes: 0GitHub stars: 10
- Soak TestGenerate 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.Votes: 0GitHub stars: 10
- ReferencesGenerate 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.Votes: 0GitHub stars: 10
- Sprint PlanGenerates 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.Votes: 0GitHub stars: 10
- ReferencesGenerates 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.Votes: 0GitHub stars: 10
- Sprint StatusFast 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'.Votes: 0GitHub stars: 10
- ReferencesFast 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'.Votes: 0GitHub stars: 10
- StartFirst-time onboarding — asks where you are, then guides you to the right workflow. No assumptions.Votes: 0GitHub stars: 10
- ReferencesFirst-time onboarding for the Unity studio template. Detects project maturity, selects review intensity, records minimal workflow state, and routes to the next skill without choosing an engine.Votes: 0GitHub stars: 10
- Steam Store LaunchUse when planning, drafting, auditing, or launching a Steam Coming Soon or store page for an indie game, including Steamworks requirements, capsules, screenshots, trailer, copy, tags, wishlist strategy, competitor research, press and creator CRM, festivals, Steam Next Fest, Reddit/social announce posts, UTM tracking, and launch readiness.Votes: 0GitHub stars: 10
- Story DoneBackward-compatible alias for task-done when given a task ID or task contract path, plus the legacy completion review for an explicit story file. Use only for compatibility; canonical tracked-task closure is $task-done.Votes: 0GitHub stars: 10
- ReferencesBackward-compatible alias for task-done when given a task ID/contract path, plus legacy completion review for an explicit story file. Canonical tracked-task closure is /task-done.Votes: 0GitHub stars: 10
- Story ReadinessValidate 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'.Votes: 0GitHub stars: 10
- ReferencesValidate 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'.Votes: 0GitHub stars: 10
- Task BugAutomatically intake explicit commands or raw post-implementation bug feedback, resolve the one tracked task that owns the failed behavior, and dispatch it to task-cycle without pre-classifying a defect; when natural-language feedback has no task match, route it once to create-task.Votes: 0GitHub stars: 10
- Task CycleExecute the canonical defect lifecycle for one already-resolved tracked task by confirming candidate matches, maintaining the sole defect ledger and linked evidence, running bounded repair and verification, closing automatically when every gate passes and the caller's policy authorizes it, and reopening safely. Use $task-bug first for new user bug feedback.Votes: 0GitHub stars: 10
- Task DoneClose one or more exact tracked tasks. Invoke automatically for an explicit user close order in a tool command or ordinary language; use --strict to require satisfied acceptance criteria.Votes: 0GitHub stars: 10
- Task StatusShow a fast read-only snapshot for one or more tracked tasks from each contract's managed lifecycle block, including phase, changed paths, evidence, blockers, decisions, and next command. Use for progress checks without running tests, writing status files, changing task state, or starting a cycle.Votes: 0GitHub stars: 10
- Team AudioOrchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.Votes: 0GitHub stars: 10
- ReferencesOrchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.Votes: 0GitHub stars: 10
- Team CombatOrchestrate 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.Votes: 0GitHub stars: 10
- ReferencesOrchestrate 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.Votes: 0GitHub stars: 10
- Team LevelOrchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.Votes: 0GitHub stars: 10
- ReferencesOrchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.Votes: 0GitHub stars: 10
- Team Live OpsOrchestrate 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.Votes: 0GitHub stars: 10
- ReferencesOrchestrate 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.Votes: 0GitHub stars: 10
- Team NarrativeOrchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.Votes: 0GitHub stars: 10
- ReferencesOrchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.Votes: 0GitHub stars: 10
- Team PolishOrchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.Votes: 0GitHub stars: 10
- ReferencesOrchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.Votes: 0GitHub stars: 10
- Team QaOrchestrate an evidence-backed QA cycle for tracked tasks, a sprint, or a feature. Route failures to task-bug, bug-report, or create-task without duplicating defect ownership.Votes: 0GitHub stars: 10
- ReferencesOrchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + evidence routing) to produce a complete QA package for tracked tasks, a sprint, or a feature.Votes: 0GitHub stars: 10
- Team ReleaseOrchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.Votes: 0GitHub stars: 10
- ReferencesOrchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.Votes: 0GitHub stars: 10
- Team UiOrchestrate the UI team through the full UX pipeline: from UX spec authoring through visual design, implementation, review, and polish. Integrates with /ux-design, /ux-review, and studio UX templates.Votes: 0GitHub stars: 10
- ReferencesOrchestrate the UI team through the full UX pipeline: from UX spec authoring through visual design, implementation, review, and polish. Integrates with /ux-design, /ux-review, and studio UX templates.Votes: 0GitHub stars: 10
- Tech DebtTrack, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.Votes: 0GitHub stars: 10
- ReferencesTrack, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.Votes: 0GitHub stars: 10
- Test Evidence ReviewQuality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness. Produces ADEQUATE/INCOMPLETE/MISSING verdict per story. Run before QA sign-off or on demand.Votes: 0GitHub stars: 10
- ReferencesReview Unity acceptance-criterion evidence using actual EditMode/PlayMode results, manual artifacts, and assembly boundaries.Votes: 0GitHub stars: 10
- Test FlakinessDetect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and maintains a flaky test registry. Best run during Polish phase or after multiple CI runs.Votes: 0GitHub stars: 10
- ReferencesDetect nondeterministic Unity EditMode/PlayMode tests from comparable NUnit XML history, classify likely causes, and maintain an evidence-backed quarantine registry.Votes: 0GitHub stars: 10