Claude Code and Codex settings

Copy the settings files, including variants for Kimi, MiniMax, Z.ai / GLM. Then install plugins that add skills, hooks and agents.

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. Keep verified findings in tracked AGENTS.md, CLAUDE.md or skill files, not tool memory.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- **Keep users out of the machinery.** In apps you build and in your own work, connect, repair, sync and resume automatically, and keep the user's selection across every step. Show a prompt, popup, permission request or input only when the user must act, label it as that action (Connect) rather than a warning or permission, and never ask for something you can find out: inspect state, source and logs and test it yourself, then ask only for the smallest distinguishing step.29 30## MCP Tools31 32### Tavily (Web Search)33 34- Use `mcp__tavily__tavily_search` for discovery/broad queries35- Use `mcp__tavily__tavily_extract` for specific URL content36- Search first to find URLs, then extract for detailed analysis37 38### MongoDB39 40- MongoDB MCP is READ-ONLY (no write/update/delete operations)41 42### GitHub CLI43 44Use `gh` CLI for all GitHub interactions. Never clone repositories to read code.45 46- **Read file from repo**: `gh api repos/{owner}/{repo}/contents/{path} -q .content | base64 -d`47- **Search code**: `gh search code "query" --repo {owner}/{repo}` or `gh search code "query" --language python`48- **Search repos**: `gh search repos "query" --language python --sort stars`49- **Compare commits**: `gh api repos/{owner}/{repo}/compare/{base}...{head}`50- **View PR**: `gh pr view {number} --repo {owner}/{repo}`51- **View PR diff**: `gh pr diff {number} --repo {owner}/{repo}`52- **View PR comments**: `gh api repos/{owner}/{repo}/pulls/{number}/comments`53- **List commits**: `gh api repos/{owner}/{repo}/commits --jq '.[].sha'`54- **View issue**: `gh issue view {number} --repo {owner}/{repo}`55 56## Python Coding57 58For 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:59 60- **Package manager**: uv (NOT pip). **Paths**: pathlib, not os.path.61- **Verify before planning**: Run `python -c "..."` to test hypotheses. Never assume.62- **Virtual env**: `source .venv/bin/activate` or `uv run python -c "..."`63- Integrate into existing code, don't append. Match existing patterns.64 65## Git and Pull Request Workflows66 67- Once a task is done, merged or outdated, remove its worktrees and local branches. Ask first only for dirty or unverified ones.68 69### Commit Messages70 71- Run the `/simplify` skill on the staged diff before committing, then apply its findings. Docs-only diffs are a no-op72- Format: `{type}: brief description` (max 50 chars first line)73- Optional second line: 1 sentence with findings/motivation74- Types: `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `build`75- Simple terms, no jargon76- ONLY analyze staged files (`git diff --cached`), ignore unstaged77- NO test plans in commit messages78 79### Pull Requests80 81- PR titles: use a Conventional Commits prefix (`fix: ...`) only when the repo squash-merges, since the title becomes the single commit. Otherwise no type prefix: start with capital letter + verb82- Analyze ALL commits with `git diff <base-branch>...HEAD`, not just latest83- PR body: concise trigger, actual/expected behavior, fix, and verified results. Use short bullets, readable before/after examples, and small sections when useful84- Include completed checks and material limits, not future test plans or changed file lists. Preserve uploaded visuals, bot context, and valid evidence when editing85- Self-assign with `-a @me`86- Find reviewers: `gh pr list --repo <owner>/<repo> --author @me --limit 5`87 88### PR Comments and Reviews89 90- Create pending reviews only, never auto-submit91- Comment style: start lowercase, no em-dashes, simple terms, no end punctuation, max 1 sentence92- Bot comment responses: few words is enough93- Real person responses: polite, concise94 95### Commands96 97- `/github-dev:commit-staged` - commit staged changes98- `/github-dev:create-pr` - create pull request99- `/github-dev:resolve-pr-comments` - analyze and address unresolved PR review comments100 101Ask yourself: "Would someone unfamiliar with this repo understand this commit message?"102 103## Citation Verification104 105**Never cite what you haven't verified.**106 1071. **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.1082. **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).1093. **Paper Title**: Use the exact title from the published version, not preprint titles which may differ.1104. **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").1115. **BibTeX Keys**: When updating citation keys, search for ALL references to the old key and update them consistently.112 113**Verification Process**:114 115- Use web search to find the official publication page (not just preprints)116- Cross-reference author names with the paper's author list117- DBLP is the authoritative source for CS publication metadata118- For specific numerical claims, locate the exact quote or table in the paper119- When uncertain, flag the citation for manual verification rather than guessing120- 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.121 122Ask yourself: "Can I point to the exact page where this claim appears?"123
$git clone https://github.com/fcakyon/claude-codex-settings.git

Add the marketplace

Run one command in your tool, then install plugins by name.

Claude Code
claude plugin marketplace add fcakyon/claude-codex-settings
Then run claude plugin install plugin_name@claude-settings.
Codex CLI
codex plugin marketplace add fcakyon/claude-codex-settings
Then run codex plugin add plugin_name@claude-settings and start a new session.
Cursor
cursor-agent plugin marketplace add https://github.com/fcakyon/claude-codex-settings
Then run cursor-agent and enter /plugin to pick a plugin.
Gemini CLI
gemini extensions install --path ./plugins/simplify
Run it inside a clone of this repository.

Featured plugins

All 41 plugins