Code library.
Every developer builds a private junk drawer of code: that one regex, the Docker snippet that finally worked, the SQL you'll need again in three months. Most of us stash it in a notes app that mangles the indentation, kills the syntax highlighting, and has no idea what a tag is. Then you burn ten minutes hunting for a snippet you know you saved. This blueprint builds you a proper snippet library instead, one that speaks code and one you own outright in your own repository.
A snippet manager built for actual code: syntax highlighting that adapts to the language of each snippet, tags so you can group things by project or topic, and a search box that finds a snippet by its content or its tags in a keystroke. Your snippets stay legible, indentation intact and colors correct, instead of collapsing into gray notes-app text.
You watch it happen in the task workspace: the agent scaffolds the project, wires up the highlighting, the tag filter, and the search, starts the dev server, and confirms you can save and find a snippet before handing you a live preview. The code lands on a branch in your repository with a pull request ready.
The first version is a base you steer with plain follow-up messages:
Each follow-up wakes the same repository and the agent continues on its own code.
Do I need to know how to code? You clearly write some, but you don't build the app itself. You describe the library you want; the agent writes it, verifies saving and search work, and ships the code to your repository.
Where does my snippet library live? In your app, in your repository, under your account. Your code stays yours, not sitting in someone else's cloud notes product.
Does it highlight my language? Common languages work out of the box. If one you use is missing, ask for it and the agent will add support.