Claude Code Mastery

Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.

Look up how Claude Code itself works — hooks, skills, subagents, MCP, plugins, settings — from the official docs, so answers come from the c...

Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.

Close out a session — summarise what changed, capture what was learned, and prepare the commit.

Hand over a spec and walk away — plans, builds, tests and audits on its own, stopping only at a real blocker.

Run the project's own tests, linter, type checker and build, and report what actually failed.

The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.

Audit the code for vulnerabilities, leaked secrets and risky dependencies before it ships.

Save a project fact, decision or gotcha so your next session already knows it.

Hand off an unfinished session to the next one — what's done, what's next, what's blocked.

Navigate your projects. Get context, paths, status. Use when needing project overview or finding specific work.

Write the spec before the code, then check the built thing against it — so agents build what was agreed, not what they invented.

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make...

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI be...

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-design...

Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model...

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS,...

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor...