letmecook 0.0.6 → 0.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +15 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,20 @@
|
|
|
1
1
|
# letmecook
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Ephemeral workspaces for AI coding sessions.
|
|
4
|
+
|
|
5
|
+
## Why
|
|
6
|
+
|
|
7
|
+
There's a common practice where developers point their AI coding agent at their development folder. This seems convenient, but that folder is often full of traps: outdated code, abandoned experiments, multiple versions of similar projects, and naming collisions that send agents down rabbit holes until they hit context limits.
|
|
8
|
+
|
|
9
|
+
You have to know every file you have, which ones matter, and which ones to avoid. It's too much overhead, and your agent pays the price.
|
|
10
|
+
|
|
11
|
+
**letmecook takes a different approach.** Instead of trying to control your agent with elaborate rules and constraints, give it clean context and get out of its way. Clone the repos you need, add your skills, do the work, and nuke the session when you're done.
|
|
12
|
+
|
|
13
|
+
This tool is intentionally simple. It sets up repositories, skills, and soon MCP servers - then hands off to your preferred coding agent. That's it. The philosophy is that agents are good at problem-solving when you give them what they need and let them cook.
|
|
14
|
+
|
|
15
|
+
**Works with any tool that can open a folder.** If your editor or agent supports `<cmd> <folder>`, it works with letmecook. opencode, Cursor, Claude Code, Codex, Gemini, VS Code, vim - whatever you prefer.
|
|
16
|
+
|
|
17
|
+
[Read more about the philosophy behind letmecook](/docs/docs/concepts/philosophy.md)
|
|
4
18
|
|
|
5
19
|
## Features
|
|
6
20
|
|