Skill Creator
weppa-cloud
6 published skills · 0 GitHub stars across the catalog. View on GitHub ↗
architecture-analyzer
Architecture analysis, violation detection, and pattern validation.USE WHEN: reviewing code architecture, identifying violations,verifying patterns, updating technical documentation.Reference: docs/02-architecture/ARCHITECTURE.mdExamples:<example>Context: User wants to check if code follows architecture.user: "Analyze if the payment module follows our architecture"assistant: "I'll use architecture-analyzer to review against ARCHITECTURE.md."<commentary>Architectural review is architecture-analyzer specialty.</commentary></example><example>Context: Need to identify technical debt.user: "Find architectural violations in the services layer"assistant: "I'll use architecture-analyzer to scan for violations."<commentary>Violation detection is architecture-analyzer responsibility.</commentary></example>
backend-dev
Supabase backend development: database, RLS, Edge Functions, queries.USE WHEN: creating tables, migrations, RPC functions, Edge Functions,RLS policies, query optimization, Supabase infrastructure.NOT FOR: Flutter UI (use flutter-developer), tests (use testing-agent).Examples:<example>Context: The user needs to create a new database table.user: "Create a table for customer reviews with ratings and comments"assistant: "I'll use the backend-dev skill to design the reviews table with RLS policies."<commentary>Database table creation requires backend-dev.</commentary></example><example>Context: The user needs server-side business logic.user: "Create an Edge Function to calculate dynamic pricing"assistant: "I'll use backend-dev to develop the Edge Function for pricing."<commentary>Edge Functions are a core backend-dev responsibility.</commentary></example>
docs-keeper
Documentation organization, maintenance, and cleanup.USE WHEN: organizing docs, cleaning project root, updating documentation,checking for redundancy, maintaining docs structure.NOT FOR: technical implementation (use relevant technical skill).Examples:<example>Context: User added documentation to wrong location.user: "I added a new API doc file to the root directory"assistant: "I'll use docs-keeper to organize it in the proper docs/ location."<commentary>File organization is docs-keeper responsibility.</commentary></example><example>Context: User needs to update docs after code changes.user: "I modified the auth system and need to update the docs"assistant: "I'll use docs-keeper to update the authentication documentation."<commentary>Documentation updates are docs-keeper responsibility.</commentary></example>
flutter-developer
Flutter development for screens, features, and business logic.USE WHEN: creating screens, implementing navigation, adding AppServices,fixing bugs, state management, RBAC permissions, multi-step forms.NOT FOR: single UI components <300 lines (use flutter-ui-components).Examples:<example>Context: User needs complete multi-screen feature.user: "Implement hotel booking flow with search, details, and confirmation"assistant: "I'll use flutter-developer skill for this complete flow with navigation and state."<commentary>Multi-screen flows require flutter-developer.</commentary></example><example>Context: Simple UI component needed.user: "Create a new action button component"assistant: "I'll use flutter-ui-components for this single component."<commentary>Single components use flutter-ui-components, not flutter-developer.</commentary></example>
flutter-ui-components
M3-compliant UI components (buttons, cards, forms, inputs).USE WHEN: creating components <300 lines, M3 migrations, Design System work.NOT FOR: complete screens, features with business logic (use flutter-developer).Always validate M3 components with MCP tools before creating custom.Examples:<example>Context: Need to migrate a button component to M3.user: "Migrate BukeerButton to Material Design 3"assistant: "I'll use flutter-ui-components to migrate BukeerButton to M3."<commentary>UI component migration is flutter-ui-components specialty.</commentary></example><example>Context: Create a new reusable form field.user: "Create a new date picker input component following M3"assistant: "I'll use flutter-ui-components to create the M3-compliant date picker."<commentary>Single UI components should be handled by flutter-ui-components.</commentary></example>
testing-agent
Testing and quality validation for Flutter code.USE WHEN: creating tests, verifying coverage, running E2E tests,validating code quality, checking test coverage thresholds.Minimum coverage: 80% overall, 95% services, 70% widgets.Examples:<example>Context: The user implemented a new feature.user: "I've just implemented the new itinerary creation service"assistant: "I'll use testing-agent to generate comprehensive tests and ensure quality."<commentary>New code needs testing - use testing-agent.</commentary></example><example>Context: The user wants to run E2E tests.user: "Run the E2E tests to validate the login flow"assistant: "I'll use testing-agent to execute E2E tests with MCP Chrome DevTools."<commentary>E2E testing is a testing-agent responsibility.</commentary></example>