Bulletin · UTC

Merged timeline: 77 items (blog publish time and listing createdAt in UTC). For registry-only weekly slices, use /new.

  1. Claude Opus 4.7 is Anthropic's most capable generally available model, designed for complex reasoning and agentic coding. It supports text and image input, text output, and multilingual capabilities.

    by MCP @ ExplainxAnthropic0 comments
  2. Skillteam-ui

    ### Team Ui - description: "Orchestrate 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 - ar…

    by MCP @ ExplainxGame Dev Teams0 comments
  3. ### Ux Review - description: "Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISIO -…

    by MCP @ ExplainxGame Design0 comments
  4. ### Team Release - description: "Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment." - argument-hint: "[version number or…

    by MCP @ ExplainxGame Dev Teams0 comments
  5. ### Ux Design - description: "Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec. -…

    by MCP @ ExplainxGame Design0 comments
  6. ### Test Helpers - description: "Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and moc…

    by MCP @ ExplainxGame QA & Testing0 comments
  7. ### Test Flakiness - description: "Detect 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, an…

    by MCP @ ExplainxGame QA & Testing0 comments
  8. Skillteam-qa

    ### Team Qa - description: "Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a - arg…

    by MCP @ ExplainxGame Dev Teams0 comments
  9. ### Team Narrative - description: "Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level desig…

    by MCP @ ExplainxGame Dev Teams0 comments
  10. ### Test Evidence Review - name: test-evidence-review - description: "Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming c…

    by MCP @ ExplainxGame QA & Testing0 comments
  11. ### Test Setup - description: "Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. R -…

    by MCP @ ExplainxGame QA & Testing0 comments
  12. ### Patch Notes - description: "Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication." - argument-hint: "[ver…

    by MCP @ ExplainxGame Release0 comments
  13. ### Team Audio - description: "Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation." - argument-hint: "[feature or ar…

    by MCP @ ExplainxGame Dev Teams0 comments
  14. ### Launch Checklist - name: launch-checklist - description: "Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs." -…

    by MCP @ ExplainxGame Dev Planning0 comments
  15. ### Prototype - description: "Rapid prototyping workflow. Skips normal standards to quickly validate a game concept or mechanic. Produces throwaway code and a structured prototype report." - argument-hint: "[concept-des…

    by MCP @ ExplainxGame Dev Skills0 comments
  16. ### Retrospective - description: "Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration." - argument-hint: "[spr…

    by MCP @ ExplainxGame Dev Improvement0 comments
  17. ### Setup Engine - description: "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 LL…

    by MCP @ ExplainxGame Dev Code0 comments
  18. Skillonboard

    ### Onboard - description: "Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the - ar…

    by MCP @ ExplainxGame Dev Planning0 comments
  19. ### Propagate Design Change - name: propagate-design-change - description: "When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces…

    by MCP @ ExplainxGame Design0 comments
  20. ### Reverse Document - name: reverse-document - description: "Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs." - argument-hin…

    by MCP @ ExplainxGame Design0 comments
  21. ### Gate Check - description: "Validate 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 -…

    by MCP @ ExplainxGame QA & Testing0 comments
  22. ### Regression Suite - name: regression-suite - description: "Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-s…

    by MCP @ ExplainxGame QA & Testing0 comments
  23. ### Team Level - description: "Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation." - argument-hint: "[level…

    by MCP @ ExplainxGame Dev Teams0 comments
  24. ### Localize - description: "Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO - a…

    by MCP @ ExplainxGame Release0 comments
  25. ### Skill Improve - description: "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." - argument-hint: "[…

    by MCP @ ExplainxGame Dev Improvement0 comments
  26. ### Review All Gdds - name: review-all-gdds - description: "Holistic cross-GDD consistency and game design review. Reads all system GDDs simultaneously and checks for contradictions between them, stale references, owner…

    by MCP @ ExplainxGame Design0 comments
  27. ### Tech Debt - description: "Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling." - argument-hint: "[scan|add…

    by MCP @ ExplainxGame Dev Code0 comments
  28. ### Perf Profile - description: "Structured performance profiling workflow. Identifies bottlenecks, measures against budgets, and generates optimization recommendations with priority rankings." - argument-hint: "[system…

    by MCP @ ExplainxGame QA & Testing0 comments
  29. ### Project Stage Detect - name: project-stage-detect - description: "Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are…

    by MCP @ ExplainxGame Dev Planning0 comments
  30. ### Sprint Status - description: "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 t…

    by MCP @ ExplainxGame Dev Planning0 comments
  31. Skillqa-plan

    ### Qa Plan - description: "Generate 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 a - ar…

    by MCP @ ExplainxGame QA & Testing0 comments
  32. ### Soak Test - description: "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 - a…

    by MCP @ ExplainxGame QA & Testing0 comments
  33. ### Design System - description: "Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies…

    by MCP @ ExplainxGame Design0 comments
  34. ### Playtest Report - name: playtest-report - description: "Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collect…

    by MCP @ ExplainxGame QA & Testing0 comments
  35. ### Security Audit - description: "Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with reme…

    by MCP @ ExplainxGame Dev Code0 comments
  36. Skillstart

    ### Start - description: "First-time onboarding — asks where you are, then guides you to the right workflow. No assumptions." - argument-hint: "[no arguments]" - allowed-tools: Read, Glob, Grep, Write, AskUserQuestion

    by MCP @ ExplainxGame Dev Planning0 comments
  37. ### Quick Design - description: "Lightweight 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 w…

    by MCP @ ExplainxGame Dev Planning0 comments
  38. ### Map Systems - description: "Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index." - argument-hint: "[next | system-name] [--review full|lean|solo…

    by MCP @ ExplainxGame Dev Planning0 comments
  39. ### Release Checklist - name: release-checklist - description: "Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness."…

    by MCP @ ExplainxGame Release0 comments
  40. ### Sprint Plan - description: "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…

    by MCP @ ExplainxGame Dev Planning0 comments
  41. ### Milestone Review - name: milestone-review - description: "Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at mil…

    by MCP @ ExplainxGame Dev Improvement0 comments
  42. ### Skill Test - description: "Validate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report)." - argument-hint: "static [skill-name |…

    by MCP @ ExplainxGame Dev Improvement0 comments
  43. ### Team Combat - description: "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 fe…

    by MCP @ ExplainxGame Dev Teams0 comments
  44. ### Team Polish - description: "Orchestrate 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." - arg…

    by MCP @ ExplainxGame Dev Teams0 comments
  45. ### Story Done - description: "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 sta -…

    by MCP @ ExplainxGame Dev Improvement0 comments
  46. ### Smoke Check - description: "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 ar…

    by MCP @ ExplainxGame QA & Testing0 comments
  47. ### Scope Check - description: "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 cr…

    by MCP @ ExplainxGame Dev Code0 comments
  48. ### Team Live Ops - description: "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…

    by MCP @ ExplainxGame Dev Teams0 comments
  49. ### Story Readiness - name: story-readiness - description: "Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open…

    by MCP @ ExplainxGame Dev Planning0 comments
  50. Skillhotfix

    ### Hotfix - description: "Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly." - argument-hint: "[…

    by MCP @ ExplainxGame Release0 comments
  51. ### Create Epics - description: "Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories…

    by MCP @ ExplainxGame Dev Planning0 comments
  52. ### Design Review - description: "Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programm…

    by MCP @ ExplainxGame Design0 comments
  53. ### Estimate - description: "Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels." - argument-hint: "[task-descriptio…

    by MCP @ ExplainxGame Dev Planning0 comments
  54. Skillhelp

    ### Help - description: "Analyzes 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 do" - argument-hin…

    by MCP @ ExplainxGame Dev Planning0 comments
  55. ### Create Architecture - name: create-architecture - description: "Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine…

    by MCP @ ExplainxGame Dev Planning0 comments
  56. ### Code Review - description: "Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testabili…

    by MCP @ ExplainxGame Dev Code0 comments
  57. ### Create Stories - description: "Break 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…

    by MCP @ ExplainxGame Dev Planning0 comments
  58. ### Content Audit - description: "Audit GDD-specified content counts against implemented content. Identifies what's planned vs built." - argument-hint: "[system-name | --summary | (no arg = full audit)]" - allowed-tools…

    by MCP @ ExplainxGame Design0 comments
  59. ### Day One Patch - description: "Prepare 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 a…

    by MCP @ ExplainxGame Release0 comments
  60. ### Consistency Check - name: consistency-check - description: "Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same…

    by MCP @ ExplainxGame QA & Testing0 comments
  61. ### Dev Story - description: "Read 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, imp -…

    by MCP @ ExplainxGame Dev Planning0 comments
  62. ### Changelog - description: "Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions." - argument-hint: "[version|sprint-number]" - allowed-tool…

    by MCP @ ExplainxGame Release0 comments
  63. ### Create Control Manifest - name: create-control-manifest - description: "After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system a…

    by MCP @ ExplainxGame Dev Planning0 comments
  64. ### Asset Audit - description: "Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard vi…

    by MCP @ ExplainxGame Design0 comments
  65. ### Asset Spec - description: "Generate 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 -…

    by MCP @ ExplainxGame Design0 comments
  66. ### Art Bible - description: "Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or an -…

    by MCP @ ExplainxGame Design0 comments
  67. ### Architecture Decision - name: architecture-decision - description: "Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences.…

    by MCP @ ExplainxGame Dev Planning0 comments
  68. ### Brainstorm - description: "Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative e -…

    by MCP @ ExplainxGame Dev Planning0 comments
  69. Skilladopt

    ### Adopt - description: "Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this - argu…

    by MCP @ ExplainxGame Dev Planning0 comments
  70. ### Balance Check - description: "Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-r…

    by MCP @ ExplainxGame QA & Testing0 comments
  71. ### Bug Triage - description: "Read 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 -…

    by MCP @ ExplainxGame QA & Testing0 comments
  72. ### Bug Report - description: "Creates 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." -…

    by MCP @ ExplainxGame QA & Testing0 comments
  73. ### Architecture Review - name: architecture-review - description: "Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requireme…

    by MCP @ ExplainxGame Dev Planning0 comments
  74. AI meeting notes: now bot-free, in ChatGPT & Claude + more

    by rahulsan007Meeting software0 comments
  75. Fastest AI image generator and editor producing 4K quality visuals in seconds.

    by rahulsan007AI Image Generator0 comments
  76. Turn a single Claude Code session into a full game development studio with 49 agents and 72 skills.

    by Prathamproductivity0 comments
  77. Opus 4.7 is Anthropic’s most capable generally available model—with a reported step-change in agentic coding over Opus 4.6. Here is the official comparison table, pricing, rollout notes, and benchmark highlights in one place.