Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the `partialPrefetching` flag, opt routes in with `export const prefetch = 'partial'`, audit `Link prefetch={true}` behavior, preserve existing prefetched UI with `instant()` tests, or resolve the instant-link-prefetch-partial and instant-shell-url-data insights.

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Debug UI changes with a repeatable evidence-first workflow. Use when validating visual regressions, reproducing frontend bugs, comparing baseline vs changed behavior, collecting screenshots/DOM/logs, or producing stakeholder-ready UI debug reports. Keywords: ui bug, visual regression, browser devtools, playwright, screenshot evidence, dom snapshot, frontend debugging.

Fetches and analyzes GitLab merge request (MR) comments, metadata, and review feedback using authenticated API calls. Capabilities include fetching comment threads, retrieving reviewer feedback, filtering unresolved discussions, and generating MR activity reports. Use when the user asks about GitLab MR comments, code review discussions, review feedback, approval status, troubleshooting review delays, or needs to fetch merge request metadata via the GitLab API.

Stress-test an unwritten idea or decision by spawning independent subagents in genuinely OPPOSING roles (advocate, skeptic, migration/risk) rather than complementary review lenses — grounded in real repo investigation, not assumption, and concluding in a synthesized verdict rather than a list of opinions. Use for "should we do X", "what are the pros and cons", "I need pushback", "collegial review", "second opinion on this decision" — BEFORE a plan exists. NOT for reviewing an already-written plan file (use plan-review) and NOT for refining a vague question through dialogue with the user (use socratic-method).

Groups plan phases and tasks into dependency-ordered waves for parallel subagent execution via git worktrees. Builds a task dependency DAG, assigns wave numbers via topological sort, emits a living wave document that tracks status as work lands, and updates wave progress when tasks complete. Use when asked to: group tasks into waves, plan parallel execution, schedule worktrees, create a wave breakdown, wave planning, dependency grouping, update wave statuses, parallel subagents, which tasks can run in parallel.

Converts a PRD or requirements document into a structured, phased implementation plan with individual phase files and granular per-task files written to .context/plans/. Also restructures existing monolithic planning documents into digestible, hierarchical directory structures. Creates a root plan index summarising all phases, a numbered phase file per phase, and a numbered task file per task inside each phase directory. Use when the user asks to create an implementation plan, break down a PRD, convert requirements to tasks, structure project phases, generate a roadmap, plan a project in sprints, organise task breakdown, split a monolithic planning doc, or decompose a spec into phases and tasks.

Generate label matchers, line filters, log aggregations, and metric queries in LogQL (Loki Query Language) following current standards and conventions. Use this skill when creating new LogQL queries, implementing log analysis dashboards, alerting rules, or troubleshooting with Loki.

Comprehensive toolkit for generating best-practice Terragrunt configurations (HCL files) following current standards and conventions. Generates terragrunt.hcl files, root configurations, child modules, stacks, and environment setups; configures remote state backends, dependency blocks, include blocks, feature flags, exclude blocks, and errors blocks; supports DRY Terraform patterns, multi-environment layouts (dev/staging/prod), and OpenTofu engine integration. Use when creating new Terragrunt projects or resources, scaffolding multi-environment infrastructure, implementing DRY Terraform wrapper configurations, setting up terragrunt.hcl files with remote state or provider config, managing module dependencies, or building infrastructure modules with Terragrunt stacks.

Create and apply custom themes to an Astro Starlight documentation site. Use when customizing colors, typography, or spacing via CSS custom properties, using the Tailwind CSS integration, applying light/dark mode variants, or loading custom fonts.

Comprehensive toolkit for validating, linting, and optimizing Makefiles. Use when working with Makefiles (Makefile, makefile, *.mk files), validating build configurations, checking for best practices, identifying security issues, or debugging Makefile problems. Concrete capabilities include detecting missing .PHONY declarations, validating tab indentation in recipes, checking variable expansion safety, identifying hardcoded credentials, and flagging missing prerequisites or syntax errors.

Ports the visual identity of any live website into a React plus Tailwind CSS project. Extracts colours, typography, spacing, component styles via browser automation, source inspection, curl, wget, DevTools. Writes structured documentation, applies findings as Tailwind v4 CSS tokens, then verifies by visually diffing the original site against the local build. Use when cloning a brand, replicating a design system, matching a reference site, migrating visual identity, copying a style guide, porting a theme from any live URL into a React codebase, matching a client reference design.

Complete Biome toolchain guidance for real repository workflows. Use when users ask to configure biome.json, run lint or format commands, migrate from ESLint or Prettier, tune rule severity, fix formatter drift, or replace mixed ESLint+Prettier pipelines with Biome-only workflows.

Generate an original, high-energy observational stand-up bit — a routine built on one bold contrastive claim ("there's a difference between X and Y") about society, relationships, race, gender, class, money, respectability politics, media hypocrisy — escalating through rhythmic repetition, rising volume, a voiced-then-defeated imagined objector, a sharpened recurring refrain, toward a tight, quotable, unhedged aphoristic closing line, in the tradition of Chris-Rock-style observational stand-up. Trigger on requests to write a stand-up bit, comedy routine, observational monologue with escalating examples building to a punchline. This skill is not for scripted sketch comedy, character-based sketches, mockumentary bits, confessional storytelling comedy, flat one-liner lists lacking escalation, or requests to reproduce a real comedian's actual material verbatim.

Generate a new, reusable comedy-writing SKILL.md for a requested comedic tradition — real, generic, or invented — by extracting its transferable comic mechanics (premise construction, escalation pattern, rhythm, rhetorical devices) into concrete, actionable writing rules instead of vague adjectives, and by converting any living performer's persona into technique rather than voice-imitation. Use this when a user asks to create a comedy skill for a style, or a skill "like" a comedian or show, and wants a complete SKILL.md file back. Do NOT use this to write comedic material directly (that is the generated skill's job, not this one's), for non-comedy skill generation, or to produce a skill whose body just says "be funny" or "make it absurd" without concrete mechanics.

Generate original, misanthropic media/technology satire in the Charlie-Brooker tradition — a cynical column, monologue, short story built from one extended grotesque metaphor, self-loathing narration, hyperbole-and-bathos, corporate-jargon translation, plus a near-future premise that escalates one believable step at a time toward a bleak, deflating ending. Use for a satirical takedown of a TV show, app, gadget, news format, or social-media trend, plus dystopian near-future short stories about a plausible technology/social mechanic. Do NOT use for mockumentary/character-voice sketches, deadpan two-hander political interviews, observational stand-up; also not for reproducing a real writer's actual column, script, episode — this skill only generates new material inspired by the technique, never a copy.

Validates .gitlab-ci.yml syntax, detects security misconfigurations in job definitions, checks for deprecated keywords, ensures proper stage ordering, and audits pipeline configurations for best practices. Use when working with .gitlab-ci.yml files, validating GitLab CI/CD pipeline syntax, debugging configuration errors, checking for hardcoded secrets or credentials in pipeline jobs, optimizing pipeline performance with DAG or cache, or performing security audits on GitLab CI/CD configurations.

Create the baseline session context from the in-folder of raw project documents, classifying each file by priority, writing a manifest, summarising oversized files and producing a token-budgeted baseline. Use when bootstrapping project context or setting up the ctx snapshot once per project. Triggers include "create context", "bootstrap context", "setup context", "init context".

Audit a project's Claude Code tool stack (MCP servers, plugins, hooks) against the curated recommendations at Context Radar (thoroc.github.io/context-radar): a 90-plus-tool, 20-layer comparison of context-reduction, memory, and code-nav tools for coding agents. Use when asked to review the Claude Code / MCP tool stack, check for redundant or conflicting tools, decide what to install next, or evaluate a new context/memory/code-nav tool against what's already running. DO NOT use for reviewing application dependencies (npm/cargo packages) or general code review - scope is Claude Code tooling only. Triggers: 'context radar', 'what tools should we use', 'audit our tool stack', 'is X redundant with Y', 'should I install this MCP server', 'tool stack review', 'context reduction tools'.

OpenTelemetry semantic convention lookup and naming guidance. Use when selecting released semantic convention groups, attributes, or span naming rules, when checking semantic convention compliance, or checking which semantic-conventions version a language SDK's semconv package exposes.