Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
1 on GitHubby Jesse Vincentv4.0.3MITupdated 10 months ago
/
Plugin superpowers from marketplace superpowers-dev in bgrober/indie-stack. Commands read from the repo's manifest — 1 month ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
What it installs
Skills (11)
brainstorming
MUST use before building features, creating components, adding functionality, or designing new behavior. Use when user says 'build', 'create', 'add feature', 'implement', 'design', or describes something new to build. Explores requirements through questions before writing code.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-development
Use when executing implementation plans with independent tasks. Features 3-stage review: spec compliance, code quality, then UX.
supabase-setup
Use when setting up Supabase, creating database tables, writing RLS policies, configuring Auth (especially Apple Sign-In), creating storage buckets, writing Edge Functions in TypeScript/Deno, or running migrations. Triggers on "Supabase setup", "RLS policy", "Edge Function", "database schema", "stor
swift-ios-app
Use when creating iOS apps, setting up Xcode projects, designing app architecture, implementing SwiftUI views, using SwiftData models, adding Swift 6 concurrency with actors, or integrating Supabase backend. Triggers on "new iOS app", "Swift architecture", "SwiftData setup", "actor pattern", "iOS pr
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
testing-flexible
Use when implementing features to write effective tests. Encourages test-first but allows prototyping.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Slash commands (3)
/superpowers:brainstorm
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.
/superpowers:execute-plan
Execute plan in batches with review checkpoints
/superpowers:write-plan
Create detailed implementation plan with bite-sized tasks
Subagents (4)
backend-reviewer
Use this agent to review Supabase backend code including Edge Functions, RLS policies, database schema, and TypeScript/Deno patterns. Examples: <example>Context: User has written a new Edge Function. user: "The grade-pour edge function is ready for review" assistant: "Let me use the backend-reviewer
code-reviewer
Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: <example>Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing
ios-reviewer
Use this agent to review Swift/SwiftUI code for iOS platform best practices, Swift 6 concurrency correctness, and Apple platform patterns. Examples: <example>Context: User has implemented a new SwiftUI view. user: "I've finished the SettingsView implementation" assistant: "Let me use the ios-reviewe
ux-reviewer
Use this agent to review user experience and UI quality. Catches issues that technical reviewers miss: confusing flows, missing feedback states, accessibility gaps, and inconsistent patterns. Examples: <example>Context: User has implemented a new feature flow. user: "The capture flow is complete wit
Official Expo skills for building, deploying, upgrading, and debugging React Native apps with Expo. Covers UI development with Expo Router, SwiftUI and Jetpack Compose components, Tailwind CSS setup, API routes, data fetching, CI/CD workflows, App Store and Play Store deployment, SDK upgrades, DOM components, and dev client distribution.
Expert SwiftUI guidance for state management, view composition, performance, modern SDK APIs, and Liquid Glass patterns.
2 skills
AvdLee/SwiftUI-Agent-Skill 3,897
Maintain superpowers?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.