Guides FeatBit users through initial setup, boolean and multi-variant flag creation, Dino Game demo interaction, and basic SDK integration. For getting started tutorials and first flags.
npx claudepluginhub joshuarweaver/cascade-code-devops-misc-1 --plugin featbit-featbit-skillsThis skill uses the workspace's default tool permissions.
Complete hands-on guide to getting started with FeatBit, covering environment initialization, creating boolean and multi-variant feature flags, interacting with the Dino Game demo, and integrating FeatBit SDKs into your applications.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Complete hands-on guide to getting started with FeatBit, covering environment initialization, creating boolean and multi-variant feature flags, interacting with the Dino Game demo, and integrating FeatBit SDKs into your applications.
This skill provides practical, step-by-step guidance for new FeatBit users to quickly understand core concepts through the interactive "Getting Started" experience in the FeatBit portal. You'll learn to create feature flags, see them in action with the Dino Game demo, and integrate FeatBit into your applications using SDKs.
First-Time Login Setup:
Prerequisites:
Basic Feature Flag Creation:
The simplest feature flag type is boolean (true/false). The "game runner" flag demonstrates this:
Steps:
false (disables feature)true (enables feature)Understanding Boolean Flags:
Accessing the Demo:
Initial State:
Making the Game Appear:
Key Concept: This demonstrates real-time feature control - changing flag state in the portal immediately affects the application behavior without code deployment or restart.
Beyond Boolean - Multiple Variations:
Multi-variant flags allow more than two states, perfect for A/B/C testing, configuration values, or progressive rollouts.
Example: Difficulty Mode Flag
Steps:
easynormalhardeasynormalDemo Interaction:
Multi-Variant Use Cases:
Portal-Guided Integration:
FeatBit provides automatically generated starter code for quick SDK integration.
Integration Steps:
Step 1 - Select Feature Flag:
Step 2 - Choose SDK and Copy Code:
Step 3 - Verify Connection:
Supported SDKs:
See SDK Overview for complete list.
Start with Boolean Flags: When learning FeatBit, begin with simple boolean flags before moving to multi-variant flags. This helps you understand the core concepts without complexity.
Use the Interactive Demo: The Dino Game demo is designed to provide immediate visual feedback. Use it to experiment with flag changes and understand the impact in real-time before implementing in your application.
Follow the Portal Guidance: The Getting Started wizard in the portal provides automatically generated, environment-specific code. This eliminates configuration errors and ensures correct setup.
Test Flag Changes: Before implementing flags in production applications, verify behavior in the demo environment or development environment to understand how flag evaluation works.
Understand Flag States: Remember that boolean flags have two states (ON/OFF) but multi-variant flags can serve different values in each state. Plan your flag variations based on your use case requirements.
SDK Connection Verification: Always verify SDK connection in the portal's Step 3 before proceeding to production integration. This confirms proper configuration and network connectivity.
User Context Matters: When evaluating flags, provide meaningful user context (user ID, attributes). This enables advanced targeting and segmentation later.
Real-Time Updates: FeatBit SDKs support real-time flag updates via WebSocket. Leverage this for instant feature control without application restarts.
Use Case: Show/hide a feature based on flag state
// After SDK initialization
const isGameEnabled = await client.boolVariation('game-runner', false);
if (isGameEnabled) {
// Render game component
renderDinoGame();
} else {
// Show placeholder or nothing
showPlaceholder('Feature not available');
}
Use Case: Adjust application behavior based on flag variation
// Get difficulty mode
const difficulty = await client.variation('difficulty-mode', 'easy');
// Configure game based on difficulty
switch(difficulty) {
case 'easy':
setGameSpeed(1.0);
break;
case 'normal':
setGameSpeed(1.5);
break;
case 'hard':
setGameSpeed(2.0);
break;
}
Use Case: React to flag changes without page reload
// Listen for flag changes
client.on('update', (changes) => {
if (changes.includes('difficulty-mode')) {
const newDifficulty = client.variation('difficulty-mode', 'easy');
updateGameDifficulty(newDifficulty);
}
});
After completing the Getting Started guide, explore these topics:
Immediate Next Steps:
Advanced Topics: 5. Experimentation & A/B Testing - Measure feature impact with metrics 6. Entitlement Management - Control feature access based on subscription tiers 7. Remote Configuration - Use feature flags for dynamic configuration 8. Feature Workflow - Implement scheduled flag changes and triggers
Issue: Demo doesn't show flag changes
Issue: SDK connection fails in Step 3
Issue: Flag evaluation returns default value
Official Getting Started Documentation:
Additional Resources: