featurectrl
Official@featurectrl
Feature flags designed for engineers by engineers
Agent Skills by featurectrl
Showing 12 vetted skills indexed across 1 GitHub repositories.
web-design-guidelines
Compare frontend files against Web Interface Guidelines and report violations in file:line format.
convex-migration-helper
Plan and execute Convex schema and data migrations with the widen-migrate-narrow workflow.
shadcn
Centralizes shadcn/ui component and preset management across multi-project environments via CLI commands.
vercel-react-view-transitions
Apply View Transition API transitions to React and Next.js apps.
convex
Route Convex user requests to the most specific Convex skill.
next-best-practices
Codify Next.js best practices covering file conventions, RSC boundaries, and data patterns.
convex-create-component
Create Convex components with isolated tables and app-facing APIs.
convex-quickstart
Scaffold a new Convex project or integrate it into an existing frontend.
next-upgrade
Upgrade Next.js projects by applying official codemods and updating dependencies.
vercel-react-best-practices
Apply React and Next.js performance best practices during code reviews and refactors.
convex-performance-audit
Diagnose Convex performance bottlenecks from deployment signals and code paths.
vercel-composition-patterns
Refactor React component libraries with composition patterns and context providers.
Frequently Asked Questions About featurectrl
FAQPage SchemaWhat specific engineering tasks does featurectrl enable?▼
Featurectrl enables systematic database schema migrations, automated enforcement of Next.js file conventions, and performance auditing for Convex backends. It provides structured modules for managing React component libraries, applying official codemods for framework upgrades, and diagnosing bottlenecks within distributed frontend and database architectures.
Which technical personas benefit most from these modules?▼
These modules are designed for frontend engineers, full-stack developers, and technical leads managing complex React and Next.js ecosystems. They are particularly useful for teams maintaining multi-project environments who require consistent component presets, standardized data patterns, and reliable database migration paths.
What are the prerequisites for implementing these modules?▼
Implementation requires an existing React or Next.js project structure and a Convex backend environment. Users should have familiarity with RSC boundaries, component composition patterns, and standard dependency management to effectively integrate these modules into their existing development lifecycle.