Crescendo shuru hota hai — aur aik zero-shot demo
Crescendo ke aaghaz mein khushamdeed. Aaj hum bare worry — bare codebases — se nipat te hain aur phir kuch “spice” add karte hain. Lekin pehle, aik treat: kal wala remote Sprite chalta raha, aur usne aik aisi cheez produce ki jo pehli hi koshish par bilkul perfect chali.
Yeh hafta 3, din 3 hai — aik bunyadi learning day. Originally yeh poora din large-team work par hone wala tha, lekin hum pehle hi foundations cover kar chuke hain, is liye hum jaldi se zaroori baatein summarize karke mazeedar practical demo par aa sakte hain. Chaliye shuru karte hain ab tak seekhi hui cheezon ke quick recap se.
01Aik quick recap (ab tak ka silsila)
Pro toolkit, aik baar phir, taake terms second nature ban jayein:
| Tool | Aik line mein |
|---|---|
| Slash commands | Configurable, lekin aaj kal zyada tar skills se replace ho chuki hain. |
| Skills | Agents ko functionality dene ka universal tarika — Claude Code, Codex, OpenCode sab mein ek jaisa. MCP ki jagah le raha hai. |
| Multi-agents | Ek sath kai Claudes — locally, ya cloud mein (GitHub @claude, ya Sprites). |
| Sub-agents | Ek task ko isolated context mein delegate karna (e.g. built-in Explore agent) aur sirf result wapas lena. |
| Hooks | Jab kuch ho to command / prompt / sub-agent trigger karna. Occasional; kabhi kabhi plugins mein aate hain. |
| Plugins & marketplaces | Skills / sub-agents / commands ko package karna aur doosron ke add karne ke liye publish karna. |
Aur kal ki sandboxing: native /sandbox, managed Claude Code on the Web (ampersand, --remote, browser, mobile, aur pyara @claude issue), aur third-party Sprites.dev — fast, stateful, aur full-YOLO ke liye safe kyun ke yeh isolated hai.
02Sprite jo kaam karta raha
13.4 se remote box itna mazedar tha ke use band nahi kiya gaya. Class ke aakhir mein instructor ne use do aur kaam karne ko kahe — aur usne bas... unhe cloud mein bina kisi supervision ke mukammal kar diya:
Docs ko consolidate kiya
Tamam planning documentation ko aik saaf summary document mein merge karein.
Demo build kiya
Isko prove karne ke liye terminal market-data demo banayein ke simulator waqai data generate karta hai — phir use push karein.
Locally pull karein
Laptop par wapas: naye code ko neeche lane ke liye git pull karein, try karne ke liye tayyar.
03Live market-data demo
Ise locally chalana — cd backend phir uv run market-data-demo — ne terminal mein hi aik live, moving dashboard produce kiya: tickers, red aur green flash hote prices, aur har stock ki movement ko chart karti text “sparklines”.
04“Zero-shot” ka kya matlab hai
Yeh pehli koshish par hi chala — koi “yeh kharab hai, ise fix karo” feedback loop nahi tha. Demo aik baar manga gaya aur bas chala. Yehi woh bar hai jo coding agents ab well-scoped, from-scratch kaam par cross kar rahe hain.
Is feeling ko pakad kar rakhein, kyun ke agla section counter-weight hai: agents is tarah ke chote, saaf projects par chamakte hain — asli skill is jaadoo ko aik massive team codebase ke andar zinda rakhna hai. Yehi agla topic hai.
✓ Aham baatein
- Pro toolkit aik sentence mein: skills, multi-agents, sub-agents, hooks, plugins.
- Sandboxing recap: native
/sandbox, managed cloud (web/mobile/@claude), aur Sprites.dev. - Remote Sprite ne docs consolidate kiye aur live demo banaya — locally pull hokar, yeh zero-shot chala.
- Agents chote clean builds par excel karte hain; challenge (agla) bare codebases par achha kaam karna hai.