sp-ecc

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Extract learned patterns from session - invoked automatically by finishing-a-development-branch or manually anytime

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for review, delivery, or cleanup

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when verifying implementation correctness - provides a systematic loop for checking tests, lint, build, and runtime behavior

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Logging best practices focused on wide events (canonical log lines) for structured, context-rich application logging.

Use before starting any task. Forces the agent to ask the user for clarification whenever it is confused, missing required information, or about to make assumptions. Prevents silent guessing and ensures requirements are fully understood before executing.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Framework-agnostic UI development patterns for component composition, state management, data fetching, forms, accessibility, performance, and animation. Applies to React, Vue, Svelte, Rails views, Flutter, and any UI framework.

Detailed model routing framework. Provides task classification, bug complexity scoring, escalation triggers, and cost optimization patterns for Opus/Sonnet/Haiku tiers.

Scan Claude Code configuration for security vulnerabilities using AgentShield. Use before committing config changes or during periodic security checks.

Audit all installed skills, commands, agents, and hooks for quality, freshness, and duplication. Use periodically to maintain a clean plugin.

Use when implementing any feature or bugfix, before writing implementation code

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

Use when writing Dart code - provides idiomatic patterns for null safety, async programming, collections, and error handling

Use when verifying Flutter applications - covers widget tests, integration tests, golden tests, performance testing, and build validation

Use when working with Ruby on Rails projects - provides patterns for models, controllers, services, and Rails Engines architecture

Use when reviewing or implementing security in Rails applications - covers OWASP guidelines and Rails-specific security patterns

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when writing Ruby code - provides idiomatic patterns, best practices, and community standards for maintainable Ruby

Dart testing patterns with dart test package, including mocking with mockito, async testing, test coverage, TDD workflow, and integration testing strategies

Flutter development patterns covering widget composition, state management (Bloc/Cubit, Riverpod, Provider), navigation, theming, responsive design, performance optimization, and platform-specific code

Test-driven development for Ruby on Rails with RSpec, model/controller/request/system tests, Capybara, FactoryBot, test database management, and TDD workflow with 80%+ coverage

Verification loop for Rails projects: migrations, routes, security, performance, tests with coverage, asset pipeline, and deployment readiness checks before release or PR.

Ruby testing patterns with RSpec and Minitest, including mocking, test data, TDD workflow, and async testing strategies