Feature flags visualization pattern
Skill kjuhwa/skills-hub/skills/design/feature-flags-visualization-pattern
Self-correcting knowledge corpus for Claude Code — 9 stable shape clusters, bias-correction pipeline baked into contribution flow. 47 papers, 45 techniques, 1.1k skills.
npx -y skills add kjuhwa/skills-hub --skill feature-flags-visualization-patternAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Visualization pattern for feature-flag rollout, dependency, and A/B experiment dashboards
SKILL.md
1.9 KB, 344 tokens by cl100k_base, as published. Nobody here has run it
feature-flags-visualization-pattern
Feature-flag UIs cluster around three canonical views that share a common visual grammar: a rollout progress strip (percentage bar segmented by cohort/variant with color-coded states — off/canary/partial/full), a dependency graph (directed nodes where parent flags gate children, with edge labels showing the boolean condition like requires=ON or variant=B), and an A/B experiment panel (side-by-side variant cards showing exposure count, conversion rate, and a confidence-interval bar). Use a consistent flag-state palette across all three: gray=OFF, amber=PARTIAL/ROLLING, green=ON, blue=EXPERIMENT, red=KILL-SWITCH — so a user jumping between screens can read state at a glance.
Layout rule: put the flag identifier (key + environment badge) as a sticky header on every flag-scoped view, because flag keys are the only stable join across rollout/dependency/experiment screens. For the dependency graph specifically, render cycles as red dashed edges and highlight orphan flags (no parents, no children) in a side list — these are the two structural problems ops actually need to find. For rollout, overlay the target percentage as a ghost bar behind the actual-exposure bar so drift is visible without a second chart.
Interactive affordances that recur: click-a-flag-node-to-pin-context (all other panels filter to that flag), hover-variant-to-see-sample-size (avoids misreading a 2-user "100% conversion"), and a time scrubber that replays the rollout history — flags change frequently, so a static snapshot hides the most useful signal (who turned what on, when).