中文

claude-code-best-practice

The repository is reference material first, to be read as a course, not as a workflow or skill.

Verified

Core facts

Read by a script from the official API, not rewritten by a model.

License
MIT
Languages
HTML
Maintainer
shanraisshan
Verified

What it is

This repository is reference material first; things are run later. The repository is to be read as a course, not as a workflow or skill.

Main features

  1. Claude Code can be used together with other models, namely Codex, Gemini, GPT, Kimi, DeepSeek and local models, via three mechanisms.

  2. In one of these mechanisms, another model's CLI runs inside Claude Code.

  3. In another, Claude Code calls another model as a tool through Model Context Protocol.

  4. In the third, Claude Code's API endpoint is swapped to a different provider.

  5. The tips and tricks section is headed with a count of 83.

  6. The repository says each tip is sourced from the Claude team or the community.

Getting started

  1. The how-to-use steps say that running weather-orchestrator shows a complete command → agent → skill flow.

  2. These steps also say to learn the primitives — agents, commands, skills, hooks — and assemble them into your own workflow.

  3. These steps also say not to use Claude as a chatbot.

  4. These steps also say to listen for the custom hook sounds while you work.

From the README · bash
claude
/weather-orchestrator

Who it is for

The repository lists the workflow of Boris Cherny, Creator of Claude Code. The repository lists the workflow of Thariq (Anthropic). The repository lists the workflow of Andrej Karpathy (Founding Member, OpenAI).

The repository lists the workflow of Peter Steinberger (Creator of OpenClaw). The agent collections section lists repos primarily known as curated libraries of subagent definitions. Spinner Verbs & Tips is extracted from CLI binary v2.1.121.

One tip says to use ASCII diagrams a lot to understand your architecture. Focus mode hides intermediate work and shows only the final result. One tip says to keep PRs small and focused.

One tip says to include scripts and libraries in skills so Claude composes rather than reconstructs boilerplate. One tip says to write detailed specs and reduce ambiguity before handing work off. One tip reads: new task = new session.

One tip says to spin up a second Claude to review your plan as a staff engineer. One tip says to make a phase-wise gated plan, with each phase having multiple tests (unit, automation, integration). One tip says to build 20-30 versions instead of writing specs.

One tip says to use subagents for context management. One tip says to build a Gotchas section in every skill.

Sources

This page is written from the official sources below. Open them to check the original text.

Verified ·

This page is written by AI from the official sources above and checked automatically. This site has not tested it. Found a mistake? Tell us.