655 skills · sorted by relevance
Plan, review, and retire feature flags, switches that control feature availability. Includes tools to identify aging flags, generate phased release schedules, and check that documentation records ownership and emergency shutdown procedures.
Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.
The English summary is being prepared. Showing the original description.
Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.
The English summary is being prepared. Showing the original description.
Locate CBasePlayerController::FakeClientFlags in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CBasePlayerController::FakeClientFlags" (symbol CBasePlayerController_FakeClientFlags). This is a VIRTUAL function - resolve the CBasePlayerController::FakeClientFlags vtable via RTTI and identify the slot, then emit the slot. Verify by xrefs from expected call sites. vtable slots commonly differ between platforms - never assume identical indices. Trigger: CBasePlayerController_FakeClientFlags, CBasePlayerController::FakeClientFlags
The English summary is being prepared. Showing the original description.
Add, read, or remove feature flags, switches that control feature availability, in a web app and Rust backend. The skill covers PostHog rollout controls, environment settings, loading behavior, and cleanup after a feature is fully released.
Inventory feature flags, switches that control feature availability, and remove eligible flags with their unused code branches. Leave ongoing rollouts and experiments untouched, run verification checks, and prepare a pull request for human review.
Focused Signals scout for PostHog projects using feature flags. Watches the flag roster and the `$feature_flag_called` evaluation stream for contradictions between a flag's configured state and its real traffic: evaluation cliffs on healthy flags, ghost flags (code calling keys that no longer exist), response-distribution shifts with no corresponding flag edit, and flag debt (stale, fully-rolled-out, or dead flags still burning evaluations). Emits findings only when they clear the confidence bar; otherwise writes durable memory and closes out empty. Self-contained peer in the signals-scout-* fleet — no dependencies on other skills.
The English summary is being prepared. Showing the original description.
Find feature flags that were soft-deleted in the active project within a recent time window. Use when the user asks "what flags were deleted in the last N days", "show me recently deleted feature flags", "who deleted flag X", "audit recent flag deletions", or anything similar. Handles the non-obvious gotcha that system.feature_flags exposes the deleted boolean but does not expose a deletion timestamp — the actual deleted-at time lives in the per-flag activity log and must be cross-referenced.
The English summary is being prepared. Showing the original description.
Builds command-line tools in Go with Cobra, the library behind kubectl, Hugo and the GitHub CLI: subcommands, flags, argument validation, generated help and shell completions. Use when a user asks to create a Go CLI, add subcommands or flags, validate arguments, bind flags to config files and environment variables with Viper, or generate bash, zsh, fish or PowerShell completions.
The English summary is being prepared. Showing the original description.
Measure Storybook startup from launching the process to displaying the first story. Separate server readiness from browser rendering, summarize repeated runs, and compare versions or feature flags to investigate slower startup.
Write Python code to manage settings in Azure App Configuration. Covers reading, updating, filtering, and locking settings, managing feature flags that switch features on or off, and creating snapshots of configuration values.
Helps implement centralized settings management in Java with Azure App Configuration. Covers environment-specific settings, feature flags that control feature availability, and snapshots that preserve settings at a particular point in time.
Configure a Claude Code hook that checks shell commands before execution and blocks flags that skip Git checks or commit signing. It helps preserve existing commit quality checks while documenting the guard's limits.
Manage OpenWork feature releases with feature flags, switches that control access to new behavior. Register features before coding, release them by organization and deployment, prepare a global shutdown option, and remove temporary flags after rollout.
Scan recent merges to main for unfinished tasks, deprecated APIs, broken documentation links, and obsolete feature flags. Get a concise report with file locations, risk, effort, and suggested follow-up actions for each merge.
Analyze product usage in PostHog and manage experiments, dashboards, surveys, and feature flags, which control feature availability. Use connected tools to investigate user behavior and errors, run queries, and summarize findings with numbers and links.
Interpret AI-writing flags without treating them as proof of authorship. Separate tool results from editorial observations, consider plausible human explanations, and identify drafts, revision histories, or other process evidence needed for consequential academic, hiring, or publication decisions.
[omh] Wants Jev risk flags on a diff under review: Jev review flags for a diff: auth, tests, migration risk, severity; flags only, never approves a merge. Use when the user says: jev-review-gate, jev review gate, ask jev to review this diff.
The English summary is being prepared. Showing the original description.
Feature flag strategy, lifecycle, and operations. Use when designing a flag taxonomy, planning a gradual rollout, building kill switches, auditing flag debt, defining governance, running progressive delivery, or rolling back via flags.
The English summary is being prepared. Showing the original description.
PostHog feature flags, rollouts, A/B testing. Use when implementing gradual rollouts, A/B tests, kill switches, remote configuration, beta features, or user targeting with PostHog.
The English summary is being prepared. Showing the original description.
Environment configuration manager for 12-factor config, feature flags, and multi-environment management. Activate on: environment variables, ConfigMap, feature flags, 12-factor config, dotenv management, config per environment, runtime config. NOT for: secret storage (use secret-management-expert), IaC provisioning (use terraform-module-builder), CI/CD variables (use github-actions-pipeline-builder).
The English summary is being prepared. Showing the original description.
Flags where a P&ID draft raises a process safety question and points to the candidate evidence an engineer would review (HAZOP register, relief study, SIL assessment, isolation philosophy), as questions and quoted passages with UNKNOWN for missing documents, plus safety functions, relief devices and isolation requirements carried over as stated. Never rates, sizes, classifies, resolves or declares protection adequate. Use when the user asks to "write the process safety flags", "produce the process safety section of the P&ID enrichment", "list which protection questions this P&ID raises" or "map the HAZOP and relief study evidence to the draft" after gate G2, once the piping and instrumentation sections exist. Do not use for proposing loops, alarms or trips from the control philosophy, use instrumentation-and-control-enrichment instead; do not use for checking identifiers, use tagging-and-numbering. Drafts for human review; never approves, authorises or signs off.
The English summary is being prepared. Showing the original description.
Identify and clean up stale feature flags in a PostHog project. Use when the user wants to find unused, fully rolled out, or abandoned feature flags, review them for safety, and then disable or delete them. Covers staleness detection, dependency checking, and safe removal workflows.
The English summary is being prepared. Showing the original description.
Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.
The English summary is being prepared. Showing the original description.