Custom slash commands: apne shortcuts
Hamari pehli pro feature sab se simple aur foran kaam aane wali hai: apne slash commands banana. Agar aap ek hi hidayat baar baar type karte hain to usay command mein lapet dein aur Git ke zariye poori team ke saath share karein.
Aap ne poore course mein built-in slash commands use kiye hain — /context, /init, /agents. Ab apne commands banayein. Hamesha ki tarah intehai simple hai: baat phir .claude folder par aa jati hai.
01Slash command kya hota hai
Slash command asal mein naam ke saath save kiya hua prompt hai. / type karein, list se select karein aur Claude Code andar wali hidayat chala dega — aap command ke baad jo chahein woh bhi de sakte hain. Isay banane ke do tareeqe hain, dono dekhenge.
02Ek banayein: commands folder
.claude ke andar (project mein, ya har jagah apply karne ke liye home directory mein) commands naam ka folder banayein. Is mein rakhi har markdown file slash command ban jati hai — filename hi command ka naam hota hai. Riwayat: lowercase aur hyphens.
Folder banayeinek baar
.claude/commands/ — poora setup itna hi hai.
Markdown file add kareinhar command ke liye
doc-review.md /doc-review command ban jayegi. Is ka content prompt hai.
Save karein — ho gayaforan
File save karte hi command maujood hai. Restart ya config ki zaroorat nahi.
03$ARGUMENTS ka tareeqa
Command ko flexible banane ke liye prompt mein $ARGUMENTS (block caps mein) daal dein. User command name ke baad jo type karega woh yahan aa jayega.
Review the documentation file in the planning folder called
$ARGUMENTS and add questions, clarifications, or feedback to a
new section at the end — along with any opportunities to simplify.Ghaur karein ke command hamesha simplification ke mauqe poochti hai. Achhi aadat ko command mein encode karne ka matlab hai ke woh har dafa muft milti hai. Isi tarah ki chhoti baatein custom commands ko faidemand banati hain.
04Aazmayein: /doc-review plan.md
Claude launch karein, / type karein aur command saamne hai. Argument dein aur isay chalte dekhein:
> /doc-review plan.md # Claude reads plan.md, finds it’s empty scaffolding, # and appends a “Document review” section with: • Questions & clarifications (orphan headings, naming mismatches…) • Simplification opportunities (drop the massive API? snapshot every 30s?)
Command ne achhe sawalat aur kuch aisi simplifications saamne rakheen jin se instructor muttfiq nahi tha (market-data API aur per-user IDs hata dena). Achhi baat qabool karein, baqi reject karein. Tool sawal karta hai; faisla aap karte hain — aap ki value yahin hai.
05Doosra tareeqa: skills muft command dete hain
Yahan mazedaar baat hai. Har skill khud-ba-khud slash command ke taur par bhi nazar aati hai. Aap ke paas cerebras-inference skill hai, is liye /cerebras-inference pehle se list mein hai — commands folder ki zaroorat nahi.
Agar aap ka .claude folder Git mein committed hai to repo clone karne wale har shakhs ko aap ke commands aur skills khud mil jate hain. Isi tarah team shared shortcuts par standardise hoti hai.
06Command aur sub-agent — aham farq
Jab aap command chalate hain to us ka har kaam main conversation history ka hissa ban jata hai — Claude poori guftagu yaad rakhta hai. Sub-agent (agla section) mukhtalif hai: yeh task ko alag context mein chalata hai aur sirf result wapas deta hai, is liye main chat saaf rehti hai.
Command / skill → kaam aap ke context mein hota hai. Sub-agent → kaam aap ke context se bahar hota hai aur aap ko sirf jawab milta hai. Yahi ek farq Class 12.4 ka poora nuqta hai.
✓ Ahm baatein
- Slash command saved prompt hota hai;
.claude/commands/mein markdown file daalein aur yeh tayyar hai. $ARGUMENTSuser ke command name ke baad type ki hui cheez ko jagah deta hai.- Achhi aadatein (jaise “simplifications suggest karein”) commands mein shamil karein — lekin output qabool ya reject aap karte hain.
- Har skill muft slash command bhi hai — aaj nayi command banane ka aam tareeqa.
- Commands aap ke context mein chalti hain; sub-agents is se bahar — agla mauzu yahi hai.