[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"readme:squid":3},"\u003Ch1>Squid: An Opinionated Software Factory for Claude Code\u003C\u002Fh1>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fiusztinpaul\u002Fsquid\u002Fblob\u002FHEAD\u002FLICENSE\" rel=\"nofollow ugc noopener\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLicense-Apache_2.0-blue.svg\" alt=\"License: Apache 2.0\" \u002F>\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fclaude.com\u002Fclaude-code\" rel=\"nofollow ugc noopener\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FClaude%20Code-2.1%2B-blue\" alt=\"Claude Code\" \u002F>\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fiusztinpaul\u002Fsquid\u002Ftags\" rel=\"nofollow ugc noopener\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fv\u002Ftag\u002Fiusztinpaul\u002Fsquid?label=version\" alt=\"Plugin version\" \u002F>\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Claude Code writes code fast. It's worse at writing the code \u003Cem>your team\u003C\u002Fem> would actually ship — code that follows your conventions, has tests you trust, and survives review.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Squid is a \u003Ca href=\"https:\u002F\u002Fclaude.com\u002Fclaude-code\" rel=\"nofollow ugc noopener\">Claude Code\u003C\u002Fa> plugin that turns a feature spec into a reviewed PR through a 5-agent pipeline — PA → SWE → Tester → PR Reviewer → On-Call — with exactly two human gates: plan approval and final merge.\u003C\u002Fstrong> No file templates, no render step: just markdown specs and agent contracts, and every file in your project gets written by an agent that reads them.\u003C\u002Fp>\n\u003Ch2>How it works\u003C\u002Fh2>\n\u003Cp>Run \u003Ccode>\u002Fsquid-plan <feature-spec>\u003C\u002Fcode> then \u003Ccode>\u002Fsquid-implement-night\u003C\u002Fcode>, and Squid drives this end-to-end:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>  feature spec\n       │\n       ▼   \u002Fsquid-plan\n  ┌──────────────────────────────────────────────────────────────┐\n  │ grill → PA grooms Tasks Plan (+ADR) → HUMAN approves (1\u002F2)     │\n  │ → branch + worktree                                            │\n  └──────────────────────────────────────────────────────────────┘\n       │   \u002Fsquid-implement-night  (runs end-to-end in the worktree)\n       ▼\n  ┌──────────────────────┐    ┌───────────────────┐    ┌─────────────────┐\n  │ \u002Fsquid-implement-task│──▶ │ \u002Fsquid-review     │──▶ │ \u002Fsquid-review-ci│\n  │ SWE ↔ Tester         │    │ push → PA accept →│    │ On-Call drives  │\n  │ commit each task     │    │ PR-Reviewer       │    │ CI to green     │\n  └──────────────────────┘    └───────────────────┘    └─────────────────┘\n                                                                │\n                                                                ▼\n                                                    HUMAN squash-merges (2\u002F2)\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Branch + worktree, grooming, the per-task implement\u002Fverify loop, push, diff review, and CI are all automated — you only show up for the two gates. For a quick single change, run \u003Ccode>\u002Fsquid-implement-task <task>\u003C\u002Fcode> (the same SWE ↔ Tester loop, no planning or review pipeline). Starting from an empty repo? Run \u003Ccode>\u002Fsquid-scaffold\u003C\u002Fcode> first — it interviews you about the stack and writes a tailored \u003Ccode>AGENTS.md\u003C\u002Fcode> plus a folder skeleton (no application source).\u003C\u002Fp>\n\u003Ch2>Who this is for\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Yes:\u003C\u002Fstrong> solo devs and small teams shipping Python backends, TypeScript frontends, or Go TUIs who want Claude Code to \u003Cem>consistently\u003C\u002Fem> hit your team's bar without re-explaining conventions every session.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Maybe not:\u003C\u002Fstrong> teams with an established in-house agent pipeline they don't want to displace, or stacks Squid doesn't cover yet (Rust, Java, mobile — \u003Ca href=\"#contributing\" rel=\"nofollow ugc noopener\">PRs welcome\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>\u003Ca href=\"https:\u002F\u002Fdecodingai.com\" rel=\"nofollow ugc noopener\">Learn How to Build Agentic Coding Frameworks From Scratch\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>  ▎ Join 40k+ engineers subscribed to \u003Ca href=\"https:\u002F\u002Fdecodingai.com\" rel=\"nofollow ugc noopener\">the Decoding AI Magazine\u003C\u002Fa> — and learn to build agentic coding frameworks like Squid from scratch.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002Fiusztinpaul\u002Fsquid\u002FHEAD\u002Fassets\u002Fdecodingai.jpg\" alt=\"Decoding AI Magazine\" \u002F>\u003C\u002Fp>\n\u003Ch2>Install\u003C\u002Fh2>\n\u003Cpre>\u003Ccode>\u002Fplugin marketplace add iusztinpaul\u002Fsquid\n\u002Fplugin install squid@iusztinpaul\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>That's it. Open any repo in Claude Code; the agents and skills appear in \u003Ccode>\u002Fagents\u003C\u002Fcode> and \u003Ccode>\u002Fhelp\u003C\u002Fcode>. Run \u003Ccode>\u002Fplugin marketplace update iusztinpaul\u003C\u002Fcode> later to pull fresh changes.\u003C\u002Fp>\n\u003Cp>Installing Squid also pulls in three plugins the agent team relies on, all from Anthropic's official \u003Ccode>claude-plugins-official\u003C\u002Fcode> marketplace — \u003Ccode>context7\u003C\u002Fcode> (live library docs via MCP), \u003Ccode>code-review\u003C\u002Fcode>, and \u003Ccode>commit-commands\u003C\u002Fcode>. That marketplace ships with Claude Code, so these resolve and enable on their own. (Requires Claude Code v2.1.143+ for auto-enable; v2.1.110+ for the dependency mechanism. If a dependency fails to resolve, run \u003Ccode>\u002Fplugin marketplace update claude-plugins-official\u003C\u002Fcode>.)\u003C\u002Fp>\n\u003Ch3>Optional companion: ca\u003C\u002Fh3>\n",1784240408159]