Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

garry tan just open-sourced a 128k-star repo that basically turns claude code into your entire engineering org it’s called gstack: 23 tools that break a single claude workflow into product, engineering, qa, review, and release lanes > /office-hours turns a rough idea into a real product spec > /plan-ceo-review... + /plan-eng-review try to tear the plan apart before any code ships > /review hunts for bugs and patches them > /qa spins up an actual browser and tests the app end to end > /ship runs the final checks and pushes the pr think → plan → build → review → test → ship → reflect garry says this setup let him ship 3 production services and 40+ features in 60 days while still running yc full-time one developer sets the compass. the repo runs the loop.show more

CyrilXBT

196,917 subscribers

20,997 views • 1 month ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

13 Comments

matteo1 month ago

@garrytan 🐐

KP bhoomika1 month ago

Scaling agents is easy. Proving their work is correct while you sleep is the real engineering challenge.

Ziwen1 month ago

garry tan is goat

deezzex1 month ago

"tear the plan apart before any code ships" is the part worth keeping regardless of the tool. most teams skip that step even without ai in the loop, it's just more visible now that the code shows up faster

TARAS PD1 month ago

This is a fascinating development. Shifting from individual tool usage to a unified system like gstack changes the dynamic. It's about orchestrating focus, turning raw ideas into structured execution. This capability mirrors how investors see potential in organized capital.

ハル｜雑記1 month ago

分業を増やすほど、全体を見ている人間がいなくなる——それで転んだことがあるから、23ツールは面白いけど素直に喜べない

Lea Thompson1 month ago

dev team on rails is a good way to put it. damn this is ambitious for one person. still i care more about the price action than the workflow

Mark Ruff 💎1 month ago

I'm really amazed with all the projects powered by Claude Code. They're all brilliant but sadly I can't even try with my free plan, it runs out of tokens too quickly :((( and my local card can't get the premium subscription

Milo1 month ago

engineering org is a strong word for 23 slash commands lol

AI Mastery Guide1 month ago

23 tools running a whole org, wild

The AI Therapist1 month ago

Gstack replaces 128k lines of glue code with 23 tools. classic saas dies. service-as-software takes the seat.

Avid1 month ago

this is cool stuff

Lucide1 month ago

the review lanes are the interesting part but plan-eng-review is the same model reading its own plan. if the spec has a wrong assumption baked in, review inherits it and signs off clean. the bugs that survive that loop are the ones where every stage agreedthe review lanes are the interesting part but plan-eng-review is the same model reading its own plan. if the spec has a wrong assumption baked in, review inherits it and signs off clean. the bugs that survive that loop are the ones every stage agreed on.

Related Videos

GStack is an open-source toolkit built by YC President & CEO Garry Tan that turns Claude Code into an AI engineering team — with skills for office hours, design, code review, QA, and browser testing. In this video, Garry walks through how GStack works, starting with Office Hours, a skill modeled after real YC partner sessions that pressure-tests your idea before you write a line of code. He demos it live, going from idea through adversarial review, design mockups, and automated QA in a single session.

GStack is an open-source toolkit built by YC President & CEO Garry Tan that turns Claude Code into an AI engineering team — with skills for office hours, design, code review, QA, and browser testing. In this video, Garry walks through how GStack works, starting with Office Hours, a skill modeled after real YC partner sessions that pressure-tests your idea before you write a line of code. He demos it live, going from idea through adversarial review, design mockups, and automated QA in a single session.

Y Combinator

925,584 views • 5 months ago

Cline v3.2 has a new Plan/Act toggle 🚀 Plan mode turns Cline into an architect that gathers information, asks clarifying questions, and designs a solution for you to review. Switch back to Act mode to let him execute the plan! This gives you a chance to flush out task details before wasting time and tokens going down the wrong direction.

Cline v3.2 has a new Plan/Act toggle 🚀 Plan mode turns Cline into an architect that gathers information, asks clarifying questions, and designs a solution for you to review. Switch back to Act mode to let him execute the plan! This gives you a chance to flush out task details before wasting time and tokens going down the wrong direction.

Saoud Rizwan

75,455 views • 1 year ago

ANTHROPIC LEAKED A 6-AGENT SETUP THAT TURNS ONE PROMPT INTO A FINISHED PR your name shows up in this process exactly once - at the very end, for 5 minutes. spec → planner → 3 builders → critic → scribe → PR → back into the spec the planner runs once and the whole line inherits its decisions - a bad plan executed by five perfect agents is still a bad result. 3 lanes build in parallel - and they only work because the planner cut the steps so none of them reads another's output. tests loop until green and red goes back to the coder - the critic never sees a broken build. the critic rejects to the plan, not the code - tests ask does it run, the critic asks should it exist. the scribe writes the PR from the trace, not from memory - cut this seat and you get 8 PRs nobody can tell apart. the back edge into the spec is the whole trick - today's failures become tomorrow's constraints without you typing them. one human step in the whole thing: approve or send back - 5 minutes instead of 5 hours. save this and read the full graph engineering course below ↓

ANTHROPIC LEAKED A 6-AGENT SETUP THAT TURNS ONE PROMPT INTO A FINISHED PR your name shows up in this process exactly once - at the very end, for 5 minutes. spec → planner → 3 builders → critic → scribe → PR → back into the spec the planner runs once and the whole line inherits its decisions - a bad plan executed by five perfect agents is still a bad result. 3 lanes build in parallel - and they only work because the planner cut the steps so none of them reads another's output. tests loop until green and red goes back to the coder - the critic never sees a broken build. the critic rejects to the plan, not the code - tests ask does it run, the critic asks should it exist. the scribe writes the PR from the trace, not from memory - cut this seat and you get 8 PRs nobody can tell apart. the back edge into the spec is the whole trick - today's failures become tomorrow's constraints without you typing them. one human step in the whole thing: approve or send back - 5 minutes instead of 5 hours. save this and read the full graph engineering course below ↓

Hanako

164,286 views • 1 month ago

ANTHROPIC LEAKED 6 RULES THAT RUN 8 LOOPS AT ONCE - AND ONE ENGINEER DOES THE WORK OF A TEAM one engineer with this system replaces an entire team - and costs the company 8 times less You → Opus 5 plan → Fable 5 ×8 execute → Fable 5 review → you: 5 min Opus 5 takes your intent and breaks it into subtasks - a bad plan multiplied across every loop gives the same number of disasters - the plan is the only thing you read carefully one repo - isolated worktrees for each loop - nobody stands on anyone's file - parallel PRs ship while you do nothing the agent runs the tests and fixes until green PR - a red build never reaches your eyes one CLAUDE.md for the whole fleet - without it you get different opinions from every loop and one merge hell the average engineer closes 3-4 tasks a day - this system closes a full sprint overnight with zero working hours Fable 5 pre-reviews every PR before it reaches you - you spend 5 minutes - your throughput is now measured in diffs read per hour bookmark and paste into Claude Code - your first fleet can start tonight

ANTHROPIC LEAKED 6 RULES THAT RUN 8 LOOPS AT ONCE - AND ONE ENGINEER DOES THE WORK OF A TEAM one engineer with this system replaces an entire team - and costs the company 8 times less You → Opus 5 plan → Fable 5 ×8 execute → Fable 5 review → you: 5 min Opus 5 takes your intent and breaks it into subtasks - a bad plan multiplied across every loop gives the same number of disasters - the plan is the only thing you read carefully one repo - isolated worktrees for each loop - nobody stands on anyone's file - parallel PRs ship while you do nothing the agent runs the tests and fixes until green PR - a red build never reaches your eyes one CLAUDE.md for the whole fleet - without it you get different opinions from every loop and one merge hell the average engineer closes 3-4 tasks a day - this system closes a full sprint overnight with zero working hours Fable 5 pre-reviews every PR before it reaches you - you spend 5 minutes - your throughput is now measured in diffs read per hour bookmark and paste into Claude Code - your first fleet can start tonight

Sprytix

37,904 views • 2 months ago

Announcing the latest release from Qodo: Modern engineering runs across hundreds of repos, dozens of teams, and AI that writes code faster than anyone can review it. Today, Qodo releases features built for these teams. - Cross Repo Review: Qodo now maps dependencies across your repos and catches breaking changes before they merge. A change to a shared SDK, API contract, or database schema no longer ships before anyone knows it broke something downstream. - Rules Miner: Qodo analyzes your PR review history, recurring comments, accepted vs. rejected suggestions, and reviewer patterns, and turns them into enforceable rules. The standards that lived in senior engineers' heads are now in the system. - Skill Review Standards: Skills are now a managed entity in Qodo, with visibility, governance controls, and per-skill analytics. The instructions encoding how your team builds software are visible to the people responsible for enforcing them. All of these features are now available in BETA. Sign up for a 14-day free trial.

Announcing the latest release from Qodo: Modern engineering runs across hundreds of repos, dozens of teams, and AI that writes code faster than anyone can review it. Today, Qodo releases features built for these teams. - Cross Repo Review: Qodo now maps dependencies across your repos and catches breaking changes before they merge. A change to a shared SDK, API contract, or database schema no longer ships before anyone knows it broke something downstream. - Rules Miner: Qodo analyzes your PR review history, recurring comments, accepted vs. rejected suggestions, and reviewer patterns, and turns them into enforceable rules. The standards that lived in senior engineers' heads are now in the system. - Skill Review Standards: Skills are now a managed entity in Qodo, with visibility, governance controls, and per-skill analytics. The instructions encoding how your team builds software are visible to the people responsible for enforcing them. All of these features are now available in BETA. Sign up for a 14-day free trial.

Qodo

633,155 views • 3 months ago

ANTHROPIC'S LEAD ENGINEER LEAKED A $1.2M SYSTEM THAT TURNS ONE ENGINEER INTO A FLEET OF 10 LOOPS your hands were the bottleneck all along - here are 8 steps that change that stop writing, start delegating - loop: feature, loop: bugfix, loop: tests - each runs independently and ships in parallel CLAUDE.md is law - every agent reads one file before acting - ten agents, one voice, zero chaos Opus 5 breaks the task into 3 independent subtasks - a bad plan multiplied by 10 workers equals 10 disasters each agent gets an isolated git worktree - three features land in the repo while you review one crash at hour 3 means resume at hour 3 not zero - without this you lose hours every day every loop writes its findings to the shared graph - worker 3 never repeats worker 1's dead end at night CLAUDE.md patches itself based on failures - tomorrow the fleet wakes up smarter save this and paste into Claude Code - and your first fleet of 10 loops is already running

ANTHROPIC'S LEAD ENGINEER LEAKED A $1.2M SYSTEM THAT TURNS ONE ENGINEER INTO A FLEET OF 10 LOOPS your hands were the bottleneck all along - here are 8 steps that change that stop writing, start delegating - loop: feature, loop: bugfix, loop: tests - each runs independently and ships in parallel CLAUDE.md is law - every agent reads one file before acting - ten agents, one voice, zero chaos Opus 5 breaks the task into 3 independent subtasks - a bad plan multiplied by 10 workers equals 10 disasters each agent gets an isolated git worktree - three features land in the repo while you review one crash at hour 3 means resume at hour 3 not zero - without this you lose hours every day every loop writes its findings to the shared graph - worker 3 never repeats worker 1's dead end at night CLAUDE.md patches itself based on failures - tomorrow the fleet wakes up smarter save this and paste into Claude Code - and your first fleet of 10 loops is already running

Sprytix

61,481 views • 2 months ago

The era of needing a 10-man dev team to ship a product is officially over. Claude Code isn't just an assistant it’s a terminal based engineer that actually builds while you think. If you’re a solo builder still stuck in "tutorial purgatory," this is your exit ramp. The "Company of One" Stack: The Architect: Claude Code (running directly in your terminal) The Brain: Obsidian for knowledge mapping The Goal: From zero to a deployed SaaS in 30 days Bookmark it and take action

The era of needing a 10-man dev team to ship a product is officially over. Claude Code isn't just an assistant it’s a terminal based engineer that actually builds while you think. If you’re a solo builder still stuck in "tutorial purgatory," this is your exit ramp. The "Company of One" Stack: The Architect: Claude Code (running directly in your terminal) The Brain: Obsidian for knowledge mapping The Goal: From zero to a deployed SaaS in 30 days Bookmark it and take action

CyrilXBT

15,459 views • 5 months ago

My AI app looked ready to ship. Replay QA proved otherwise. Before launching, I connected the GitHub repo to Replay QA, let it run through the app like a real user, and within a few minutes it surfaced issues I would've never noticed by manually clicking around. What I liked most wasn't just finding bugs. It showed exactly what happened in the browser, explained the likely root cause, and gave enough context to fix the issue without guessing. Instead of running a one-time check, I connected the repo so Replay QA can keep testing every time I push changes or open a PR. No Playwright setup. No complicated pipeline configuration. Just a practical QA gate before users ever find the problems. If you're building with Cursor, Claude Code, Codex, Lovable, Bolt, Replit, or any AI coding workflow, this is worth adding before your next launch. Replay

My AI app looked ready to ship. Replay QA proved otherwise. Before launching, I connected the GitHub repo to Replay QA, let it run through the app like a real user, and within a few minutes it surfaced issues I would've never noticed by manually clicking around. What I liked most wasn't just finding bugs. It showed exactly what happened in the browser, explained the likely root cause, and gave enough context to fix the issue without guessing. Instead of running a one-time check, I connected the repo so Replay QA can keep testing every time I push changes or open a PR. No Playwright setup. No complicated pipeline configuration. Just a practical QA gate before users ever find the problems. If you're building with Cursor, Claude Code, Codex, Lovable, Bolt, Replit, or any AI coding workflow, this is worth adding before your next launch. Replay

Kaitee

64,294 views • 2 months ago

Grok Build CLI just dropped. Not for dabbling. This is dev mode. Runs in your terminal and actually gets work done. Activate your personal dev mode. SuperGrok Heavy users only. Try it: * Confirm access - this is SuperGrok Heavy only, not your regular plan * Upgrade if needed - or * Install it - run the one-liner in your terminal * Jump into your project - cd into your repo * Launch Grok - type “grok” and log in once * Start prompting - audits, features, fixes, whatever you need * Use plan mode - review tasks and diffs before anything runs * Spin up sub-agents - let it handle big workloads * Go headless - automate scripts when you don’t want to babysit * Keep iterating - refine, rerun, improve You’re up and running in minutes. No excuses. Tip: Start with a small task in an existing repo to get comfortable with the plan and review workflow. xAI engineers are actively gathering feedback. Share your experience on 𝕏. xAI

Grok Build CLI just dropped. Not for dabbling. This is dev mode. Runs in your terminal and actually gets work done. Activate your personal dev mode. SuperGrok Heavy users only. Try it: * Confirm access - this is SuperGrok Heavy only, not your regular plan * Upgrade if needed - or * Install it - run the one-liner in your terminal * Jump into your project - cd into your repo * Launch Grok - type “grok” and log in once * Start prompting - audits, features, fixes, whatever you need * Use plan mode - review tasks and diffs before anything runs * Spin up sub-agents - let it handle big workloads * Go headless - automate scripts when you don’t want to babysit * Keep iterating - refine, rerun, improve You’re up and running in minutes. No excuses. Tip: Start with a small task in an existing repo to get comfortable with the plan and review workflow. xAI engineers are actively gathering feedback. Share your experience on 𝕏. xAI

Mario Nawfal

75,474 views • 4 months ago

Sherlock AI is the security homebase for Web3 engineering teams. Pick a repo, branch, and commit, start a run, and get visibility into vulnerabilities and attack paths tied to the code you’re about to ship. The payoff is simple: it gives engineers time back. Less time doing manual review. Less time getting a repo “audit-ready.” Less time stuck in remediation loops and follow-up reviews after every fix. Sherlock AI catches issues earlier and lets teams verify patches on the next commit, so devs can focus on building. AI auditing is the new baseline. Protocols that adopt it ship faster. Protocols that don’t will keep paying the same tax in time, churn, and rework.

Sherlock AI is the security homebase for Web3 engineering teams. Pick a repo, branch, and commit, start a run, and get visibility into vulnerabilities and attack paths tied to the code you’re about to ship. The payoff is simple: it gives engineers time back. Less time doing manual review. Less time getting a repo “audit-ready.” Less time stuck in remediation loops and follow-up reviews after every fix. Sherlock AI catches issues earlier and lets teams verify patches on the next commit, so devs can focus on building. AI auditing is the new baseline. Protocols that adopt it ship faster. Protocols that don’t will keep paying the same tax in time, churn, and rework.

SHERLOCK

1,391,475 views • 8 months ago

PROMPTS ARE DEAD. LOOPS JUST REPLACED YOUR $200K ENGINEER. Claire Vo showed how to turn one prompt into a self-running loop. It reviews your aging pull requests every morning and hunts for new skills every week. And it spins up its own subagents to check its own work. Runs on Claude Code + Codex. One afternoon. One prompt. The numbers are insane: - Senior doing code review: $200K/year - Automation engineer: $150K/year - This setup: about $200/month - Time to build: one afternoon - Skill required: describe the job like you are onboarding a hire The opportunity is even wilder: Teams pay people to babysit pull requests and chase stale reviews. The loop does it itself at 10:15 a.m., alerts the team, and validates itself with subagents. An agency would charge thousands to wire this up. One person + Claude Code + Codex + one prompt = an engineering team that reviews code and finds new skills while you sleep. Save and watch the clip.

PROMPTS ARE DEAD. LOOPS JUST REPLACED YOUR $200K ENGINEER. Claire Vo showed how to turn one prompt into a self-running loop. It reviews your aging pull requests every morning and hunts for new skills every week. And it spins up its own subagents to check its own work. Runs on Claude Code + Codex. One afternoon. One prompt. The numbers are insane: - Senior doing code review: $200K/year - Automation engineer: $150K/year - This setup: about $200/month - Time to build: one afternoon - Skill required: describe the job like you are onboarding a hire The opportunity is even wilder: Teams pay people to babysit pull requests and chase stale reviews. The loop does it itself at 10:15 a.m., alerts the team, and validates itself with subagents. An agency would charge thousands to wire this up. One person + Claude Code + Codex + one prompt = an engineering team that reviews code and finds new skills while you sleep. Save and watch the clip.

shmidt

51,155 views • 3 months ago

“Our biggest bottleneck is becoming the review of code, rather than the actual writing and generation of code.” Cisco CPO Jeetu Patel says code review is still super important though, because without human taste and judgment, code quickly turns into slop: “Every engineer on that team is now just a spec developer.” “They just build specs. They create markdown files. They give context to the model. They give context to the agent. And then the agent’s writing the code.” “I think, presumably, the review is going to get easier, too.” “You’ll have really crappy software that gets written if people aren’t paying attention to it. It doesn’t obviate the need for having taste, and having judgment, and having instinct, and making sure that you’re thinking about what you’re building."

“Our biggest bottleneck is becoming the review of code, rather than the actual writing and generation of code.” Cisco CPO Jeetu Patel says code review is still super important though, because without human taste and judgment, code quickly turns into slop: “Every engineer on that team is now just a spec developer.” “They just build specs. They create markdown files. They give context to the model. They give context to the agent. And then the agent’s writing the code.” “I think, presumably, the review is going to get easier, too.” “You’ll have really crappy software that gets written if people aren’t paying attention to it. It doesn’t obviate the need for having taste, and having judgment, and having instinct, and making sure that you’re thinking about what you’re building."

TBPN

11,289 views • 8 months ago

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

Yarchi

818,868 views • 4 months ago

Your Plan SUCKS! 👀 Inspired by the legend Andrej Karpathy himself, I created a new skill: LLM Council. Create better plans, by committee. Supports: > Codex CLI > Gemini CLI > Claude Code > OpenCode Call the skill with your feature that you'd like to build. It will ask you some clarifying question, and then launch up to four parallel planning agents to create a detailed plan. Once the plans are in, all plans are anonymized and the "The Judge" will critique and choose the best plan *OR* the best parts from all of them. Finally, it will output a final-plan, which you can review and refine. I even created a nice UI for you to review and refine your plans. This Skill has been tested on Linux only, but should work on other platforms. Please report any bugs! Links in the comments.

Your Plan SUCKS! 👀 Inspired by the legend Andrej Karpathy himself, I created a new skill: LLM Council. Create better plans, by committee. Supports: > Codex CLI > Gemini CLI > Claude Code > OpenCode Call the skill with your feature that you'd like to build. It will ask you some clarifying question, and then launch up to four parallel planning agents to create a detailed plan. Once the plans are in, all plans are anonymized and the "The Judge" will critique and choose the best plan OR the best parts from all of them. Finally, it will output a final-plan, which you can review and refine. I even created a nice UI for you to review and refine your plans. This Skill has been tested on Linux only, but should work on other platforms. Please report any bugs! Links in the comments.

am.will

69,134 views • 8 months ago

The winner of an Anthropic hackathon open sourced his entire Claude Code setup and this is absolute f*cking gold. 68 subagents, 286 skills, 94 commands, MIT license. ECC turns one Claude Code assistant into a staffed engineering org. The plan lands before the build, the failing test lands before the fix, and every change gets read again by a context that never watched it get written. • Who does what > Planning -> give it one sentence, get a plan you approve before any code exists. > Review -> reads your diff cold, with a separate reviewer per language. > Build repair -> one fixer per toolchain, PyTorch and CUDA included. > Security -> an OWASP sweep, plus a scanner looking for injection holes in your agent config. > Architecture -> kills design mistakes while they're still cheap, long before migrations. > Domain work -> database queries, ML pipelines, e2e tests, docs. That security pair is what almost nobody bothers to set up. An outside OWASP audit runs four figures and a week of waiting this one finishes on your branch by lunch. • What the skills cover > Testing -> tdd-workflow walks red to green, eval-harness sits on top. > Language packs -> Python, Go, Rust, C++, Django, Laravel, Spring Boot, Next.js. > Context -> search-first reads the docs before writing, iterative-retrieval keeps your repo from flooding the window. > Shipping -> Docker, CI/CD, health checks, rollbacks, migrations. > Beyond code -> writing in your voice, market research, pitch decks. Fork it, cut it down, run your own version tomorrow. Start with one plan and one rules pack switching on all 286 skills at once is the fastest route to a worse setup. Whoever wires this in over a weekend spends next quarter reviewing work instead of typing it.

The winner of an Anthropic hackathon open sourced his entire Claude Code setup and this is absolute f*cking gold. 68 subagents, 286 skills, 94 commands, MIT license. ECC turns one Claude Code assistant into a staffed engineering org. The plan lands before the build, the failing test lands before the fix, and every change gets read again by a context that never watched it get written. • Who does what > Planning -> give it one sentence, get a plan you approve before any code exists. > Review -> reads your diff cold, with a separate reviewer per language. > Build repair -> one fixer per toolchain, PyTorch and CUDA included. > Security -> an OWASP sweep, plus a scanner looking for injection holes in your agent config. > Architecture -> kills design mistakes while they're still cheap, long before migrations. > Domain work -> database queries, ML pipelines, e2e tests, docs. That security pair is what almost nobody bothers to set up. An outside OWASP audit runs four figures and a week of waiting this one finishes on your branch by lunch. • What the skills cover > Testing -> tdd-workflow walks red to green, eval-harness sits on top. > Language packs -> Python, Go, Rust, C++, Django, Laravel, Spring Boot, Next.js. > Context -> search-first reads the docs before writing, iterative-retrieval keeps your repo from flooding the window. > Shipping -> Docker, CI/CD, health checks, rollbacks, migrations. > Beyond code -> writing in your voice, market research, pitch decks. Fork it, cut it down, run your own version tomorrow. Start with one plan and one rules pack switching on all 286 skills at once is the fastest route to a worse setup. Whoever wires this in over a weekend spends next quarter reviewing work instead of typing it.

slash1s

50,640 views • 20 days ago

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

Ado

71,910 views • 7 months ago

how is this even allowed i dropped my $200/mo claude plan for deepseek harness, it’s basically free the whole thing runs on one simple rule: everything is a plugin [setup takes 3 minutes, here’s the playbook] 1. clone/install the repo called deepseek-harness 2. skim the architecture docs 3. that’s it, you’re live bookmark this and hand it to your agent right now.

how is this even allowed i dropped my $200/mo claude plan for deepseek harness, it’s basically free the whole thing runs on one simple rule: everything is a plugin [setup takes 3 minutes, here’s the playbook] 1. clone/install the repo called deepseek-harness 2. skim the architecture docs 3. that’s it, you’re live bookmark this and hand it to your agent right now.

CyrilXBT

42,892 views • 1 month ago

this GPT-6 Astra setup is getting f...cking dangerous 8 GitHub repos for turning one coding agent into an entire engineering team 01 OpenHands ▸ → autonomous software development 02 SWE-agent ▸ → issue → inspect repo → patch → test BUILD THE WORKERS 03 Aider ▸ → pair programming directly inside your repo 04 Cline ▸ → plan → edit → terminal → browser 05 Roo Code ▸ → specialized coding agent modes GIVE THEM A WORKSPACE 06 E2B ▸ → isolated sandboxes for parallel execution 07 Daytona ▸ → reproducible environments for agent workloads CHECK THE WORK 08 SWE-bench ▸ → test agents against real GitHub issues the swarm: issue → planner → split tasks → parallel agents → patches → tests → critic → merge one agent fixes the backend another handles the frontend another runs tests while a critic checks the diff that's where GPT-6 Astra gets interesting not one AI writing more code an entire software team running inside the repo ⭣

this GPT-6 Astra setup is getting f...cking dangerous 8 GitHub repos for turning one coding agent into an entire engineering team 01 OpenHands ▸ → autonomous software development 02 SWE-agent ▸ → issue → inspect repo → patch → test BUILD THE WORKERS 03 Aider ▸ → pair programming directly inside your repo 04 Cline ▸ → plan → edit → terminal → browser 05 Roo Code ▸ → specialized coding agent modes GIVE THEM A WORKSPACE 06 E2B ▸ → isolated sandboxes for parallel execution 07 Daytona ▸ → reproducible environments for agent workloads CHECK THE WORK 08 SWE-bench ▸ → test agents against real GitHub issues the swarm: issue → planner → split tasks → parallel agents → patches → tests → critic → merge one agent fixes the backend another handles the frontend another runs tests while a critic checks the diff that's where GPT-6 Astra gets interesting not one AI writing more code an entire software team running inside the repo ⭣

Lummox

35,870 views • 9 days ago

Want to create beautiful, high-converting landing pages like this without spending days in Figma or Webflow? Here's my AI-first workflow: Start with Claude Have Claude interview you about the product, audience, positioning, features, concerns and tradeoffs using this prompt: "Create me a plan file for [Product Idea] and interview me in detail using the AskUserQuestionTool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc." Turn the plan into a prototype Use the plan file to generate a working prototype and pull inspiration, layouts and motion ideas from Generate the landing page in code Skip static mockups and build directly in the browser. Run a design review Use the Design Review skill to identify hierarchy, spacing, branding, usability and accessibility issues. Iterate relentlessly Keep refining until it feels designed and polished, not generated. The future isn't designers vs AI. It's builders with great taste using AI as leverage. Anyone can generate. Taste is the moat. Follow for more AI design and vibe coding workflows. And if you want more practical systems like this, my book 'Think. Prompt. Create.' is available now on Amazon

Want to create beautiful, high-converting landing pages like this without spending days in Figma or Webflow? Here's my AI-first workflow: Start with Claude Have Claude interview you about the product, audience, positioning, features, concerns and tradeoffs using this prompt: "Create me a plan file for [Product Idea] and interview me in detail using the AskUserQuestionTool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc." Turn the plan into a prototype Use the plan file to generate a working prototype and pull inspiration, layouts and motion ideas from Generate the landing page in code Skip static mockups and build directly in the browser. Run a design review Use the Design Review skill to identify hierarchy, spacing, branding, usability and accessibility issues. Iterate relentlessly Keep refining until it feels designed and polished, not generated. The future isn't designers vs AI. It's builders with great taste using AI as leverage. Anyone can generate. Taste is the moat. Follow for more AI design and vibe coding workflows. And if you want more practical systems like this, my book 'Think. Prompt. Create.' is available now on Amazon

Joey Primiani

471,049 views • 4 months ago