|
|
|
|
|
by zackify
4 hours ago
|
|
I just approach everything as a one off task. Fresh context. "Use this CLI tool and figure it out. Look up this sentry issue using it" "Add a service that watches for an error in the log. Look at the home assistant MCP data and find my phone, send a notification to it and make it send when there's an error" Now after it manually does it and makes the code. "Make this into a skill for anytime I paste a URL with sentry inside the message" But also important: "make that procedure a prompt file so when I invoke it I just pass X after it and it works fully" Having too many skills for things that are very specific where you can directly invoke it via slash command, wastes context space with the skill headers I find. So I make those prompts instead |
|