The warp terminal is an AI enhanced terminal that understand human-written prompts, like any other LLM. It’s a fantastic way to get the boilerplate of interacting with a regular terminal out of the way, and focus on the actual problem you’re trying to solve.Their free plan is quite generous, and you can use it to get started with the Katana primitives and Katana’s starter kit.
A cool feature of Warp is the “rules” directory which allows you to explain to the AI how to “do things” - think of it as macros on steroids.Here is a rule we can test for booting up a Katana project. Once you install Warp, open your Rules and add the following:
Copy
Ask AI
When asked to start a new katana project:1. Clone http://github.com/katana-network/specialk/ (ask the user into which folder, if the folder is not specified in the prompt)2. Make sure the user has bun (bun.sh) and foundry installed. If not `curl -L https://foundry.paradigm.xyz | bash` and `foundryup` should take care of it.3. After cloning, cd into the folder and run `bun install` and `cp .env.example .env`, then `bun run build:all`.4. Then tell the user that they can run `bun run start:anvil katana` to run a local clone of katana, and that they can run `bun run dev` to host their built app. They can rebuild the app using only `bun run build` going forward.
Edit this as you see fit, this is just an example.Now, if you ask Warp to “start a new katana project in a folder called myproject”, it will follow the rules you’ve set.Other rules you can set include:
Running this will add it to your Warp “Shared with me” directory, and you’ll be able to summon it at will. Let’s try running it on the specialk repo we just initialized!
Lastly, let’s integrate MCP into Warp.We have 2 MCPs at our disposal:
the MCP of these docs
the MCP of SpecialK, Katana’s starter kit
Let’s add both and enhance Warp’s knowledge scope of our work.Click the MCP option in Warp, then “Add MCP”. For remote MCPs, we can call them like this:
Now the terminal has the ability to search the Superdocs:For local MCPs, you follow the official MCP instructions. In our case, we add the following JSON: