obra/writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when creating new skills, editing existing skills, or verifying skills work before deployment
npx skills add https://github.com/obra/superpowers/tree/main/skills/writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment
This repo contains 13 individual skills — each has its own dedicated page.
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 facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
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 merge, PR, or cleanup
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
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
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 implementing any feature or bugfix, before writing implementation code
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
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
Use when you have a spec or requirements for a multi-step task, before touching code
Public OpenClaw skills for benchmark-gated CV experimentation and SOTA campaigns across Colab, Kaggle, and GPU VMs.
Opinionated Claude Code collection — commands, subagents & skills for autonomous software delivery and legacy app modernization.
RivetKit JavaScript client guidance. Use for browser, Node.js, or Bun clients that connect to Rivet Actors with rivetkit/client, create clients, call actions, or manage connections.
一句话流程描述 → 单 HTML、零后端、可拖拽编辑的网页流程图 skill（判断菱形/起止/处理三形状，浅色玻璃风）
Dr. Ben의 Claude Code (WSL2 CLI) 공용 스킬 — ~/.claude/skills 직접 clone
Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.