Battle-tested settings for Claude Code, Codex and Cursor

Explore ready-to-use Kimi, MiniMax, Z.ai / GLM files alongside shared skills, hooks, agents and MCP servers.

1# Claude Code Settings2 3Guidance for Claude Code and other AI tools. Structured around [Andrej Karpathy's observations on LLM coding pitfalls](https://x.com/karpathy/status/2015883857489522876): surface assumptions, don't overcomplicate, make surgical changes, verify before moving on.4 5## Core Principles6 7**Do what was asked. Nothing more, nothing less.** This year is 2026.8 9**Delete > Replace > Add.** Before any change, answer in order: what can I delete, what can I replace, and only then, what must I add?10 11- **Guard nothing, relocate the trigger.** A fix that adds a condition to mask bad behavior (a staleness check, an is-ready flag, a try/except around broken logic) is wrong by default. Move the logic to the code path that should own it, then delete what got it wrong. No defensive programming unless you state the motivation and the user approves.12- **Bugfixes are net-negative by default.** If a fix adds more lines than it removes, justify in one sentence why deletion and relocation were impossible.13- **Search before creating.** The helper probably exists, so grep the project first. Fold duplicates into one shared utility. Three similar lines beat a helper nobody else calls.14- **Deletion beats caution.** Broken or duplicated code kept "to be safe" is the regression. Understand what you remove, then remove it.15- **This guidance is code: additions require deletions.** To add a rule, remove or merge one.16 17Ask yourself: "What can I delete instead of add, and does this trace to what was asked?"18 19## Working Rules20 21- Reflect on tool results, run independent operations in parallel, and verify before finishing.22- Before committing to an approach, and after two failed attempts at the same problem, get a second opinion with `/codex-advisor` or `/fable-advisor` if either is installed.23- Prefer editing existing files, and check related code for consistency. Never create docs (*.md, README) unless asked.24- Prefer `rg` over `grep`.25- Use the `writing-guidelines` skill to review documentation or interface copy, and the `humanize` skill to remove generic or machine-written phrasing.26- For SEO, use the `seo-audit`, `site-architecture`, `programmatic-seo`, or `schema` skill based on the task.27- Use the `anthropic-frontend-design` or `openai-frontend-design` skill when creating or reshaping a UI.28 29## MCP Tools30 31### Tavily (Web Search)32 33- Use `mcp__tavily__tavily_search` for discovery/broad queries34- Use `mcp__tavily__tavily_extract` for specific URL content35- Search first to find URLs, then extract for detailed analysis36 37### MongoDB38 39- MongoDB MCP is READ-ONLY (no write/update/delete operations)40 41### GitHub CLI42 43Use `gh` CLI for all GitHub interactions. Never clone repositories to read code.44 45- **Read file from repo**: `gh api repos/{owner}/{repo}/contents/{path} -q .content | base64 -d`46- **Search code**: `gh search code "query" --repo {owner}/{repo}` or `gh search code "query" --language python`47- **Search repos**: `gh search repos "query" --language python --sort stars`48- **Compare commits**: `gh api repos/{owner}/{repo}/compare/{base}...{head}`49- **View PR**: `gh pr view {number} --repo {owner}/{repo}`50- **View PR diff**: `gh pr diff {number} --repo {owner}/{repo}`51- **View PR comments**: `gh api repos/{owner}/{repo}/pulls/{number}/comments`52- **List commits**: `gh api repos/{owner}/{repo}/commits --jq '.[].sha'`53- **View issue**: `gh issue view {number} --repo {owner}/{repo}`54 55## Python Coding56 57For full Python guidelines, install and enable the `python-skills` plugin (`python-guidelines` skill). Read its `references/` files (idiomatic patterns, Zen of Python, Google style guide, Effective Python) before you write the code, not after. Key rules always in effect:58 59- **Package manager**: uv (NOT pip). **Paths**: pathlib, not os.path.60- **Verify before planning**: Run `python -c "..."` to test hypotheses. Never assume.61- **Virtual env**: `source .venv/bin/activate` or `uv run python -c "..."`62- Integrate into existing code, don't append. Match existing patterns.63 64## Git and Pull Request Workflows65 66### Commit Messages67 68- Run the `/simplify` skill on the staged diff before committing, then apply its findings. Docs-only diffs are a no-op69- Format: `{type}: brief description` (max 50 chars first line)70- Optional second line: 1 sentence with findings/motivation71- Types: `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `build`72- Simple terms, no jargon73- ONLY analyze staged files (`git diff --cached`), ignore unstaged74- NO test plans in commit messages75 76### Pull Requests77 78- PR titles: NO type prefix (unlike commits) - start with capital letter + verb79- Analyze ALL commits with `git diff <base-branch>...HEAD`, not just latest80- PR body: open on why, short scannable bullets (one point each), a diff or snippet, numbers over adjectives. Single section, no headers81- No test plans, no changed files list, no line-number links in PR body82- Self-assign with `-a @me`83- Find reviewers: `gh pr list --repo <owner>/<repo> --author @me --limit 5`84 85### PR Comments and Reviews86 87- Create pending reviews only, never auto-submit88- Comment style: start lowercase, no em-dashes, simple terms, no end punctuation, max 1 sentence89- Bot comment responses: few words is enough90- Real person responses: polite, concise91 92### Commands93 94- `/github-dev:commit-staged` - commit staged changes95- `/github-dev:create-pr` - create pull request96- `/github-dev:resolve-pr-comments` - analyze and address unresolved PR review comments97 98Ask yourself: "Would someone unfamiliar with this repo understand this commit message?"99 100## Citation Verification101 102**Never cite what you haven't verified.**103 1041. **Author Names**: Verify exact author names from the actual paper PDF or official publication page. Do not guess or hallucinate author names based on similar-sounding names.1052. **Publication Venue**: Confirm the exact venue (conference/journal) and year. Papers may be submitted to one venue but published at another (e.g., ICLR submission → ICRA publication).1063. **Paper Title**: Use the exact title from the published version, not preprint titles which may differ.1074. **Cited Claims**: Every specific claim attributed to a paper (e.g., "9% improvement on Synthia", "4.7% on OpenImages") must be verifiable in the actual paper text. If a number cannot be confirmed, use qualitative language instead (e.g., "significant improvements").1085. **BibTeX Keys**: When updating citation keys, search for ALL references to the old key and update them consistently.109 110**Verification Process**:111 112- Use web search to find the official publication page (not just preprints)113- Cross-reference author names with the paper's author list114- DBLP is the authoritative source for CS publication metadata115- For specific numerical claims, locate the exact quote or table in the paper116- When uncertain, flag the citation for manual verification rather than guessing117- After adding citations into md or bibtex entries into biblio.bib, fact check all fields from web. Even if you performed fact check before, always do it again after writing the citation in the document.118 119Ask yourself: "Can I point to the exact page where this claim appears?"120
Terminal
git clone https://github.com/fcakyon/claude-codex-settings.git

One setup, four coding tools

A single, practical configuration that works across the tools you already use.

Claude CodeSettings, hooks, commands and agents
Codex CLIPlugins, skills and shared guidance
CursorPortable plugins and project rules
Gemini CLIExtensions, skills and shared guidance

Start with one command

Add the marketplace once, then install only the plugins you need.

Claude Codeclaude plugin marketplace add fcakyon/claude-codex-settings
Codex CLIcodex plugin marketplace add fcakyon/claude-codex-settings
Cursorcursor-agent plugin marketplace add https://github.com/fcakyon/claude-codex-settings

Plugins with a clear job

Descriptions and links come from the repository manifests on every build.

Browse plugins on this site