AI Tools Cheatsheets

AI Tools Cheatsheets

The open-source AI coding handbook for developers: practical cheat sheets, comparisons, prompts, MCP guidance, repo instructions, and engineering workflows for Claude Code, Codex, Cursor, Copilot, Gemini, and modern coding agents.

Claude Code · OpenAI Codex · Cursor · GitHub Copilot · Gemini CLI · MCP · AGENTS.md · CLAUDE.md · Prompts · Workflows

Start With the Most Useful Pages

What you want to do Best starting page
Pick the right AI coding toolAI Coding Tools Comparison Matrix
Get productive quicklyQuick Start
Learn Claude CodeClaude Code Cheat Sheet
Learn OpenAI CodexOpenAI Codex Cheat Sheet
Configure repo instructionsAGENTS.md · CLAUDE.md
Connect tools through MCPMCP Overview · Useful MCP Servers
Copy reusable promptsPrompt Library · Master Prompts
Run a real engineering taskWorkflow Library
Make a small open-source contributionCommunity Hub · Contribute in 10 Minutes
01

Tool Cheat Sheets

Jump to Claude Code, Codex, Cursor, Copilot, or the full tool index.

02

Prompts and Workflows

Copy structured prompts and pair them with repeatable review, debugging, testing, and migration workflows.

03

MCP and Agent Setup

Standardize AGENTS.md, CLAUDE.md, and MCP with least-privilege guidance before enabling broad access.

Choose Your Path

AudienceStart hereWhy
DevelopersFor DevelopersTools, repo instructions, workflows, prompts, and safer next steps.
TeamsFor TeamsStandardize tools, prompts, MCP usage, and rollout practices.
Engineering LeadersFor Engineering LeadersEvaluate adoption, governance, value, and internal handbook strategy.
Platform and SecurityFor Platform and SecurityReview permissions, MCP risk, least privilege, and approval controls.

Safety note: Treat coding agents, MCP servers, shell execution, and repo write access as privileged. Start with Security and Permissions.

Built for Fast-Moving AI Tooling

This handbook uses explicit verification labels because AI coding tools change quickly. Verified, Locally tested, Documentation verified, Needs verification, Experimental, account/plan constraints, and similar labels communicate how much confidence to place in a page before standardizing on it.

When a page includes a Sources section, treat those links as the evidence boundary for its claims.

Fork It for Your Team

Use the public handbook as a neutral baseline, then customize approved tools, repo instructions, MCP servers, prompts, workflows, and policies for your organization.

Contribute

A first contribution can be one corrected command, official source, validation step, prompt improvement, accessibility fix, or clearer example.

The public issue queue is intentionally curated: starter issues should name the file, acceptance criteria, source expectations, and validation command. If the handbook saves you time, star the repository so you can find it again and more developers can discover it.