daily-briefing
Provides a high-signal briefing on events in a specific location and timeframe, backed by primary video sources and transcripts.
Provides a high-signal briefing on events in a specific location and timeframe, backed by primary video sources and transcripts.
Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.
This skill should be used when writing or reviewing tests for Android code in Bitwarden. Triggered by "BaseViewModelTest", "BitwardenComposeTest", "BaseServiceTest", "stateEventFlow", "bufferedMutableSharedFlow", "FakeDispatcherManager", "expectNoEvents", "assertCoroutineThrows", "createMockCipher", "createMockSend", "asSuccess", "Why is my Bitwarden test failing?", or testing questions about ViewModels, repositories, Compose screens, or data sources in Bitwarden.
Use this skill when a task needs browser automation through PinchTab: open a website, inspect interactive elements, click through flows, fill out forms, scrape page text, log into sites with a persistent profile, export screenshots or PDFs, manage multiple browser instances, or fall back to the HTTP API when the CLI is unavailable. Prefer this skill for token-efficient browser work driven by stable accessibility refs such as `e5` and `e12`.
Add a new AI provider integration to the Sentry JavaScript SDK. Use when contributing a new AI instrumentation (OpenAI, Anthropic, Vercel AI, LangChain, etc.) or modifying an existing one.
Scan agent skills for security issues. Use when asked to "scan a skill", "audit a skill", "review skill security", "check skill for injection", "validate SKILL.md", or assess whether an agent skill is safe to install. Checks for prompt injection, malicious scripts, excessive permissions, secret exposure, and supply chain risks.
Bump size limits in .size-limit.js when the size-limit CI check is failing. Use when the user mentions size limit failures, bundle size checks failing, CI size check errors, or needs to update size-limit thresholds. Also use when the user says "bumpSizeLimit", "fix size limit", "size check failing", or "update bundle size limits".
Validate extracted Claude Code prompt data by reading files and checking rules directly — no external scripts or API calls needed. Checks JSON structure (30+ rules), generated markdown files, README consistency, and semantic variable name correctness. Use whenever asked to validate prompt JSON files, check generated output, run pre-release checks, debug validation errors, or analyze variable naming. Trigger phrases: "validate", "check prompts", "run validation", "verify prompts", "structural checks", "semantic check", "release prep". Also use when investigating a specific validation rule (A1–A21, B1–B6, C1–C7, A23) or when encountering errors in prompt data.
Verify changelog entries against actual prompt diffs by reading both JSON files and evaluating accuracy directly. Compares two prompt JSON versions (old → new), identifies added/removed/changed prompts, and checks that a human-written changelog accurately describes the changes. Use whenever writing, reviewing, or verifying a changelog entry for a new Claude Code version, when comparing prompt versions, when preparing a release, or when asked to "verify changelog", "check changelog", "changelog accuracy", or "diff vs changelog". Also use when asked whether a changelog is correct, complete, or well-worded, or when asked to help write a changelog for a version.
Verify Claude-generated prompt names, IDs, descriptions, and variable names in extracted prompt JSON files. Catches wrong category prefixes, duplicate IDs, fabricated categories, inconsistent variable names, and inaccurate descriptions by cross-referencing against actual repo conventions. Use after running `tools/nameWithClaude.js` to name or rename prompts, when reviewing newly named prompts before committing, or when validation errors mention A1–A3, A5, A15, A16, A20, or A23 rules. Trigger phrases: "verify names", "check names", "review naming", "verify prompt names", "are these names right", "validate naming".
Audit GDD-specified content counts against implemented content. Identifies what's planned vs built.
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'.
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.
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.
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 after art bible and GDD/level design are approved, before production begins.
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.
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.
After 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).
Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.