Jamie Taylor

There's a markdown file that links to a shell script or a PowerShell script.

And those PowerShell scripts have helper functions, like maybe every so often it needs to clear the context, or maybe it needs to read something

from the user.

So it sets up a whole bunch of stuff about how it should behave, as well as telling the LLM, OK, so the user is about to give you a specification for a thing.

Be ready, and be ready to create a git branch if there isn't one.

get ready to make sure we're on main and we've pulled recently so that then when you create the branch, you're not creating it from an old version of main, right?

So there's a whole bunch of setup for it.

And if I'm brownfield, I, I, what I'm going to do is I'm going to give a spec kit.

I'm going to install in inverted commas, spec kit and init it.

And then I'm going to say, Hey, spec kit.

First thing I want to do is I want to say, Hey, go create a constitution, right?

So the constitution is this markdown file that sets up the,

all of the different coding standards for the particular project we're looking at.

So it might set up things like, oh, we use a linter, use this particular editor config or test-driven development.

So I'm from a .NET C sharp land, so it might say, make sure that you do .NET format, which is kind of like linting, but not 100% every time.

Yeah, exactly right.

Setting up the rules of how the code should be written and then setting up things like if you are doing test-driven development, this much code coverage is a bare minimum.

Or maybe, you know, first-party packages first, then widely supported third-party packages, and then maybe experimental ones if there isn't something that supports what we want to do.

So the first thing it does is it sets that up.

And then that way, regardless of what you ask your LLM to write, it will always look at that first and say, am I about to write something that's insecure, that violates the Constitution?