.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/lawzava/megapowers
home/skills/lawzava/megapowers
lawzava avatar

lawzava/megapowers

31 skills

View on GitHub
$npx skills add lawzava/megapowers
SkillInstalls
autonomous-runUse when a long task must continue unattended across many steps or sessions, preserve durable progress, resume later, or keep going until done.—best-of-nUse when a hard implementation or design task needs independent candidates and one winner chosen by tests or blind comparison.—brainstormingUse to design a feature, capability, or unclear behavior change. Triggers on "add a feature" or "figure out the approach".—council-adjudicationUse when a hard architecture, design, strategy, or tradeoff decision lacks an executable oracle and needs independent model judgments.—cross-model-verificationUse when risky billing, auth, concurrency, security, or other high-stakes work needs another vendor to independently refute or adversarially verify it.—designing-frontendsUse to build or redesign a rendered UI when visual direction, palette, typography, layout, motion, or UX copy matters, especially if output looks templated or…—effect-brokerUse before a deploy, send, charge, database migration, destructive query, DNS change, external API write, or other costly real-world side effect.—executing-plansUse to execute a written implementation plan inline with one writer, especially coupled tasks.—finishing-a-development-branchUse when verified work needs branch integration or cleanup. Triggers on "work is done", "ship this", "merge or PR", or "wrap up the branch".—golang-patternsUse for Go in an existing project when choosing interfaces, dependency injection, goroutines, channels, context, errors, functional options, or package layout.—greenfield-go-stackUse to start or scaffold a Go project, service, SaaS, backend, or server rendered app, or choose its framework, database, auth, payments, hosting, and…—greenfield-python-stackUse to start or scaffold a Python project or service, or choose its package manager, tooling, web framework, validation, async, database, middleware, and…—greenfield-ts-stackUse to start or scaffold a TypeScript or Node service, or choose its package manager, tsconfig, tests, linting, validation, web framework, database, and layout.—humanizing-proseUse to draft or edit user-facing docs, release notes, PRs, announcements, or errors. Triggers on "humanize", "sounds like AI", "slop", or "read naturally".—multi-agent-delegationUse when a scoped build, plan or code review, or visual or browser task should go to a different model or runtime rather than same-model subagents.—orchestratingUse before a non-trivial, multi-part, or high-stakes task to decide how to approach, split, delegate, compare candidates, or run autonomously.—project-memoryUse to save or recall durable project knowledge across sessions: decisions, hidden constraints, gotchas, or references.—python-patternsUse for Python in an existing project when choosing idiomatic typing, Pydantic models, error handling, asyncio, concurrency, or async design.—receiving-code-reviewUse to evaluate review feedback before changing code, especially unclear or suspect suggestions. Triggers on reviewer comments or requested changes.—requesting-code-reviewUse when finished work needs review before merge. Triggers on "review this", "ready to merge", or "check my work". Verify behavior first.—subagent-driven-developmentUse when a plan has independent tasks for subagents or requests recursive multi-writer execution.—systematic-debuggingUse to diagnose or fix bugs, failing or flaky tests, or unexpected behavior.—test-driven-developmentUse for any feature or bug fix. Triggers on "TDD", "test-first", "write the test first", "red-green-refactor", "implement and test", or requests to add code…—typescript-patternsUse for TypeScript in an existing project when choosing idiomatic types, discriminated unions, typed errors, promises, concurrency, or async design.—upgrading-megapowersUse when asked to update, upgrade, refresh, or migrate Megapowers, check for a newer release, or discover new Megapowers plugins.—using-git-worktreesUse when starting feature work or an implementation plan that should verify or establish an isolated workspace. Reuse an existing worktree when suitable.—using-megapowersUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before any response including clarifying questions—verification-before-completionUse before claiming work is complete, fixed, passing, ready to merge or publish, and before commits or pull requests. Triggers on any success or status claim.—wayfindingUse when long-horizon work has unknown ownership, unresolved decisions, or unclear sequencing that prevents an honest specification or implementation plan.—writing-plansUse when requirements need a multi-step plan before coding. Triggers on "write a plan", "break into steps", "save the plan", or "do not implement yet".—writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment—