All authors
Claude Skills by IdoCohen560
github.com/IdoCohen560343 skills0 installs422 views
- Asset AuditAudits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.Votes: 0GitHub stars: 17
- Asset SpecGenerate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.Votes: 0GitHub stars: 17
- Balance CheckAnalyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.Votes: 0GitHub stars: 17
- BrainstormGuided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.Votes: 0GitHub stars: 17
- Bug ReportCreates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.Votes: 0GitHub stars: 17
- Bug TriageRead all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.Votes: 0GitHub stars: 17
- ChangelogAuto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.Votes: 0GitHub stars: 17
- Code ReviewPerforms an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.Votes: 0GitHub stars: 17
- Consistency CheckScan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variables. Grep-first approach — reads registry then targets only conflicting GDD sections rather than full document reads.Votes: 0GitHub stars: 17
- Content AuditAudit GDD-specified content counts against implemented content. Identifies what's planned vs built.Votes: 0GitHub stars: 17
- Create ArchitectureGuided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a complete architecture blueprint before any code is written. Engine-version-aware: flags knowledge gaps and validates decisions against the pinned engine version.Votes: 0GitHub stars: 17
- Create Control ManifestAfter architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).Votes: 0GitHub stars: 17
- Create EpicsTranslate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.Votes: 0GitHub stars: 17
- Create StoriesBreak a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.Votes: 0GitHub stars: 17
- Day One PatchPrepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately after public launch. Treats the patch as a mini-sprint with its own QA gate and rollback plan.Votes: 0GitHub stars: 17
- Design ReviewReviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.Votes: 0GitHub stars: 17
- Design SystemGuided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.Votes: 0GitHub stars: 17
- Dev StoryRead a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.Votes: 0GitHub stars: 17
- Eng Unity Mobile OptimizationMobile-specific Unity optimization patterns for memory, battery, thermal, and performance.Votes: 0GitHub stars: 17
- EstimateEstimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.Votes: 0GitHub stars: 17
- Gate CheckValidate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.Votes: 0GitHub stars: 17
- HelpAnalyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now or I'm stuck or I don't know what to doVotes: 0GitHub stars: 17
- HotfixEmergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.Votes: 0GitHub stars: 17
- Launch ChecklistComplete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.Votes: 0GitHub stars: 17
- LocalizeFull localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO localization, test RTL/platform requirements, enforce string freeze, and report coverage.Votes: 0GitHub stars: 17
- Map SystemsDecompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.Votes: 0GitHub stars: 17
- Milestone ReviewGenerates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.Votes: 0GitHub stars: 17
- OnboardGenerates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the specified role or area.Votes: 0GitHub stars: 17
- Patch NotesGenerate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.Votes: 0GitHub stars: 17
- Perf ProfileStructured performance profiling workflow. Identifies bottlenecks, measures against budgets, and generates optimization recommendations with priority rankings.Votes: 0GitHub stars: 17
- Playtest ReportGenerates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.Votes: 0GitHub stars: 17
- Project Stage DetectAutomatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are we in development', 'what stage are we in', 'full project audit'.Votes: 0GitHub stars: 17
- Propagate Design ChangeWhen a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.Votes: 0GitHub stars: 17
- PrototypeRapid prototyping workflow. Skips normal standards to quickly validate a game concept or mechanic. Produces throwaway code and a structured prototype report.Votes: 0GitHub stars: 17
- Qa PlanGenerate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when starting a major feature.Votes: 0GitHub stars: 17
- Quick DesignLightweight design spec for small changes — tuning adjustments, minor mechanics, balance tweaks. Skips full GDD authoring when a system GDD already exists or the change is too small to warrant one. Produces a Quick Design Spec that embeds directly into story files.Votes: 0GitHub stars: 17
- Regression SuiteMap test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.Votes: 0GitHub stars: 17
- Release ChecklistGenerates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.Votes: 0GitHub stars: 17
- RetrospectiveGenerates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.Votes: 0GitHub stars: 17
- Reverse DocumentGenerate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.Votes: 0GitHub stars: 17
- Review All GddsHolistic 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.Votes: 0GitHub stars: 17
- Scope CheckAnalyze 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'.Votes: 0GitHub stars: 17
- Security AuditAudit 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: 17
- 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: 17
- Skill ImproveImprove 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.Votes: 0GitHub stars: 17
- Skill TestValidate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report).Votes: 0GitHub stars: 17
- 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: 17
- 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: 17
- 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: 17
- 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: 17