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
Claude Code skill: investigate an unfamiliar server and produce a single-file HTML recon report
Forge portable coding-agent skills with linting, activation tests, render adapters, and local-first packaging.
MCP server & CLI for iOS/macOS .xcstrings localization — 26 MCP tools + 11 CLI commands for the full lifecycle: create → extract → translate → validate → export
张鑫旭真人倒膜 - 让AI写出老工程师博客味道的中文技术文章 (Claude Code Skill)
Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades.
🛰️ Agent Teams reinvented for collaborative coding supporting Claude Code and Codex, with full code transparency