Loading...
Loading...
Found 3,081 Skills
Guide to effective Claude Code skill authoring using TDD methodology and persuasion principles. Use when creating new skills, improving compliance, or validating quality before deployment. Do not use for evaluating existing skills (use skills-eval) or analyzing architecture (use modular-skills). Follow the Iron Law: write a failing test before writing any skill.
Draft, rewrite, and validate Odoo-style commit messages using [TAG] module: summary format, 50/72 length limits, imperative English, WHY-first body, and correct tag selection. Includes optional migration tagging ([MIG]) when the project workflow (like OCA) uses it.
Validate Business Requirements Documents (BRD) against Layer 1 MVP schema standards
Generates business/company names across 10 categories (Descriptive, Metaphoric, Invented, Founder-based, Acronym, Compound, Foreign, Playful, Geographic, Legacy) with USPTO trademark screening, domain availability checking, and 0-100 scoring. Use when users need company/product/brand naming for new business launches, rebranding, trademark strategy, IP protection naming, evaluating current name strength, or any naming/branding tasks requiring systematic analysis with legal clearance.
Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns.
Review code for bugs, security vulnerabilities, performance issues, and maintainability. Trigger with "review this code", "check this PR", "look at this diff", "is this code safe?", or when the user shares code and asks for feedback.
Review and refactor code in your project according to defined instructions
Audits a local plugin directory to ensure it perfectly matches the Agent Skills and Claude Plugin Open Standards.
Design a rigorous A/B test or experiment when the user asks to create an experiment, design an A/B test, or validate a hypothesis
Defense-in-depth verification before declaring any task complete. Run tests, check build, validate changed files, verify no regressions. Applies 4-level adversarial artifact verification (EXISTS > SUBSTANTIVE > WIRED > DATA FLOWS) with goal-backward framing. Use before saying "done", "fixed", or "complete" on any code change. Use for "verify", "make sure it works", "check before committing", or "validate changes". Do NOT use for debugging (use systematic-debugging) or code review (use systematic-code-review).
ALWAYS use when working with Angular Signal Forms, reactive forms with signals, FormControl with signals, or new forms API in Angular.
Design a conversion loop for a one-person company from reach to lead capture to purchase. Use when Codex needs to explain conversion concepts when needed, verify MVP prerequisites, ask one question at a time, present multiple conversion-path options, and write user-confirmed outputs into `opc-doc/`.