Class 7 · 7.1

Commands, shortcuts & configuration ki tafseeli jankari

Claude Code ke andar doosra din. Everyday commands, aap ke context window ko manage karne wale teen C's, shortcut keys, aur .claude folder aur @ trick kaise kaam karte hain, is par maharat hasil karein.

🎯 Goal: fluent command-line control⏱ Read: 12 min🧭 Type: deep dive

01Hum kahan hain: coding-agent landscape

Week 2, day 2 mein khushamdeed — Claude Code ke andar reh kar mazeed gahraiyyon mein jane ka doosra din. Ek bhi command touch karne se pehle, poora naksha apne zehen mein rakhein. Har tool jo hum se mila hai teen camps mein se ek mein aata hai, aur unhein ek baar phir pehlu-ba-pehlu dekhna munasib hai.

Coding agents ki teen families. Aaj hum Claude Code mein mazeed mazeed mehfooz tareeqay se rahein ge — woh tool jis ne poore CLI camp ke liye raftaar set ki.

Kisi doosre tool mein follow kar rahe hain?

Agar aap kal OpenCode ya AMP ke aadi ho gaye the, to poora week unhein use karein — jo niche bataya gaya hai us ka zyadatar hissa wahan bhi apply hota hai. Commands tool ke andar hone par taqriban hamesha slash ke baad ek name hota hai; sirf exact names alag hote hain. Resources par nazar rakhein, kyun ke yeh category har week badalti hai.

02Commands discover karna — do-second ki trick

Claude ke andar, / (slash) type karne par ek command chalti hai jo tool khud handle karta hai — yeh model ko nahi bheji jaati. Aap ko kabhi bhi list zabaani yaad karne ki zaroorat nahi hai. On-demand sab kuch samne lane ke do tarike hain:

`/` type karein phir `↓` press karein

Commands ka poora menu scroll karein, har ek ke sath ek line ki description di gayi hai. Sirf yeh aap ko taqriban har zaroori cheez bata deta hai.

`/help` run karein

Ahem commands aur shortcut keys ka ek compact summary — jab tak muscle memory banti hai yeh ek behtareen cheat-sheet hai.

In overlay screens mein se kisi ko bhi chhorne aur prompt par wapas aane ke liye Esc press karein.

03Woh commands jo aap rozana use karein ge

Kuch commands baar baar saamne aati hain. Yahan working set di gayi hai, unke maqsad ke mutabiq group ki gayi hai.

Command	Yeh kya karti hai	Kab use karein
`/init`	Project ko explore karti hai aur fresh `CLAUDE.md` likhti hai.	Naye project mein pehli baar (waise haath se likhna aksar behtar hota hai).
`/model`	Current model dikhati hai aur aap ko switch karne deti hai.	Opus se cheaper model par aana, ya mushkil kaam ke liye wapas upar jana.
`/status`	Tamam halaat: version, settings, session & weekly usage.	Ek quick health check.
`/context`	Memory printout — is waqt window mein kya bhar raha hai.	Har waqt. Aap ki sab se zyada use hone wali single command.
`/compact`	Conversation ko compress karti hai taake aap jaari rakh sakein.	Proactively, is se pehle ke window mid-task mein force kare.
`/clear`	Conversation history ko saaf karti hai — naye saray se start karne ki tarah.	`CLAUDE.md` ko re-read karne ke liye deliberately reset karna.
`/config`, `/usage`, `/stats`	Settings, usage detail, aur ek dilchasp daily token chart.	Track karna ke aap platform ko kitna use kar rahe hain.

Teen C's: context, compact, clear

Yeh ek sath aate hain kyun ke yeh sab same keemti resource ko manage karte hain — context window. In ke aapas ke relation ko samajhna smooth sessions aur out-of-control sessions ke beech ka farq hai.

Apni sharton par compact karein, is ki sharton par nahi

Claude ko task ke beech mein auto-compact hone dena coherence loss ka bais ban sakta hai aur kaam ko kharab kar sakta hai. Ek natural break par khud /compact run karein. Aap instructions bhi add kar sakte hain — /compact keep the API design decisions — agarche bohot se log aisi durable information ko CLAUDE.md mein rakhna aur is par control rakhna pasand karte hain.

Ek clean-slate workflow jo kaam karta hai

Ek reliable rhythm: apni CLAUDE.md aur plan.md ko up to date rakhein (Claude ko unhein maintain karne ka kahein), phir /clear — ya Ctrl+C do baar press karke quit karein aur relaunch karein — aur fresh, tidy start ki tasdeeq ke liye /context run karein. Yeh lambi conversation ko chalaye rakhne se ziada fast aur predictable hai. Compacting bhi achha kaam karti hai; yeh sirf pasand ki baat hai.

04Jaanna zaroori shortcut keys

Aap waqt ke sath mazeed sekhein ge, lekin chaar shuru mein hi apni jagah bana leti hain.

Keys	Effect
`Shift`+`Tab`	Cycle modes: accept-edits on → plan mode → normal. Accept-edits file edits ko auto-approve karta hai (full YOLO jaisa nahi hai).
`Ctrl`+`O`	Detailed transcript ko toggle karein — agent ki soch ka mukammal trace.
`Ctrl`+`E`	Thinking trace ko expand/collapse karein taake aap poora padh sakein.
`Ctrl`+`B`	Current job ko background mein chalane ke liye bhejien jabke aap commands type karte rahein.
Ctrl+Shift+`	(VS Code) Ek bilkul fresh terminal kholein — stale environment variables se chutkara paane ke liye useful.

Plan mode ki ab kam zaroorat hai

Plan mode Claude ko amal karne se pehle planning karne par majboor karta hai. Opus jaise strong models ke sath yeh pehle jaisa ziada use nahi hota — model khud decide kar leta hai ke planning kab zaroori hai. Yeh jaanna achha hai ke yeh mojood hai; har baar majboor karne ki zaroorat nahi.

05Under the hood: `.claude` folder

Jaise aap ne kaam kiya hai, aap ke project ke top par ek .claude directory khamoshi se numayan ho gayi hai. Is ke andar ek settings JSON file hai — aur har baar jab aap ne 2 press kiya ("yes, and don't ask again") Claude ne is mein ek line likhi jo record karti hai ke ab ise kya karne ki ijazat hai.

.claude/settings.local.json

{
  "permissions": {
    "allow": [
      "Bash(git add:*)",
      "Bash(docker build:*)",
      "Edit(src/**)"
    ],
    "deny": []
  }
}

Aap is file ko direct edit kar sakte hain — instant control ke liye abilities add karein, ya permission line delete karke ise hata dein. Claude ke andar se rules dekhne, add aur remove karne ke liye ek /permissions command bhi hai, lekin JSON ko haath se edit karna aksar teez hota hai.

06`@` trick: files ko context mein lana

Claude Code ke andar, @ file path ke contents ko zahir karta hai. Yeh prompt mein aur memory files ke andar dono jagah kaam karta hai, aur chote tukron se aap ki instructions compose karne ki key hai.

CLAUDE.md

# Detailed plan
@docs/plan.md            # yahan poori plan file ko inline kar deta hai

# One-file trick: make CLAUDE.md == AGENTS.md
@AGENTS.md               # Claude Code AUR Copilot dono ke liye single file maintain karein

Handy

Folder ko @ karein

Kisi folder ko reference karne se is ki files ki listing aati hai — unke contents nahi — Claude ko map dene ka sasta tarika.

Ehtiyaat

Bari file ko @ karein

Lambi file ko inline karna context window ko tezi se bhar deta hai. Powerful, lekin maqsad ke sath use karein — baad mein /context dekhein.

Single-source trick

Claude Code aur GitHub Copilot ke liye same guidance chahte hain? Poori CLAUDE.md mat likhein. Is ke bajaye is ke tamam contents ko ek line banayein: @AGENTS.md. Ab CLAUDE.md siri se AGENTS.md hi hai, aur aap do ke bajaye ek file maintain karte hain.

✓ Aham baatein

Slash tool commands chalata hai, model prompts nahi — unhein / + ↓ ya /help se discover karein.
Teen C's window manage karte hain: /context dekhta hai, /compact compress karta hai, /clear saaf karta hai. Gentlest command choose karein.
Natural break par khud compact karein — ise task ke beech mein auto-compact na hone dein.
Shift+Tab, Ctrl+O, Ctrl+B jaldi seekh lein.
Permissions .claude/settings mein rehti hain — haath se ya /permissions ke zariye edit ki ja sakti hain.
Prompts aur memory mein @path file ko inline karta hai (ya folder list karta hai) — composable instructions ki bunyaad.