Explore skills

Define the reader/customer avatar, painful current state, desired outcome, transformation bridge, objections, and proof needed before writing profile copy, posts, articles, landing pages, or visual concepts.

Set up common Claude Code hooks - auto-formatting after edits, blocking dangerous commands, and notifications. Interactive setup for your project.

Find, install, and configure an MCP server for a specific service. Handles discovery, installation, and verification.

Set up a build/test/lint validation loop for the current project. Detects the tech stack and configures CLAUDE.md with verification commands.

Investigate a codebase question using an isolated subagent. Use when you need to read many files without bloating the main context.

Convert a YouTube video transcript into Claude Code skills. Extracts tips, evaluates against selection criteria, and generates SKILL.md files with full transparency.

Full-spectrum web application VAPT skill for Claude Code, OpenCode, Codex CLI & Gemini CLI — from reconnaissance to exploitation to remediation reporting

Full-spectrum web application VAPT skill for Claude Code, OpenCode, Codex CLI & Gemini CLI — from reconnaissance to exploitation to remediation reporting

Post AI Thinking — unbiased solution space explorer. Strips inherited human heuristics, enumerates ALL possible approaches, then lets the user choose. No paradigm gets priority. Auto-calibrates depth: simple problems get a quick scan (3 paradigms), architectural decisions get the full space (7 paradigms, all phases). Existing solutions are fully included — if they fit best, use them. Invoke as: /p

Product pressure test before you build. Two modes: Startup (6 YC-style forcing questions that expose demand reality, status quo, target user, narrowest wedge, observation, and future-fit) and Builder (generative brainstorming for side projects, hackathons, and open source). Produces a design doc. Invoke when the user describes a new idea, asks whether something is worth building, or wants to press

Scan the current codebase or a specified file/diff for production bugs, logic errors, and risky code before it ships. Use when the user says "review", "check my code", "is this safe to ship", or "any bugs in this?". Produces a prioritised bug list with exact file:line references and optional auto-fixes.

Audit code for security vulnerabilities. Use when the user says "security-audit", "security check", "is this secure", "audit for vulnerabilities", or before any public deployment. Covers OWASP Top 10 and common API/backend attack surfaces.