Tested kits and draft kits

A tested kit comes from a recipe that a fresh coding agent built from start to finish, from the kit files alone, before the recipe was listed. A draft kit is assembled for your own idea in the kit builder; nobody has built it yet, so you check more yourself.

Tested kits #

There are 8 tested recipes today, listed on Project kits.

• How they are tested. The agent got only the kit files in a clean sandbox, had to build the project and wrote down everything in the brief that was wrong, missing or unclear. Those findings went back into the recipe.
• What the record shows. Each recipe page has a section What happened when an agent built from it: every build, how many lines of the definition of done were met, what was reported, and what nobody has checked yet.
• Checked every week. AgentGid checks every recipe each week, without a model: the pinned packages still exist, the Python install lines resolve together, and the links in the brief open. The recipe page says when it was last checked.
• Your choices. If you change a part or an answer, the kit is no longer exactly the tested one. The brief says which parts differ, so your agent knows where to be careful.

Matching your goal to a recipe is a lookup, not a model call, so the same request always gives the same kit.

Draft kits #

Press ✦ Create my own kit in the kit builder and describe any project.

• A model splits your goal into jobs, in about 20 seconds. The parts for those jobs still come only from AgentGid's catalogs, never from the model's memory.
• A job with no fitting part in the catalogs is shown as Not in AgentGid's catalog yet.
• Read Check these yourself at the bottom of a draft before you start, and expect to fix a step or two.
• Creating a kit needs a free account: up to 5 a day. Each kit you create goes to My kits in your account.

Which to use #

When a tested recipe is close to your idea, start from it and change the parts you need.