Review of first version #1
Description
Thanks for putting this together. :) As always, some notes. 🫣
Summary
I feel like that a prerequisites section might be benificial to note that certain actions require PWT MCP or additional files. Many prompts don't feel actionable because they refer to files that I don't have when I'm browsing around. 👇
Examples of uptime monitors are in:
- prompts/src/checks/uptime/url.check.ts - URL monitor
- prompts/src/checks/uptime/tcp.check.ts - TCP monitor
- prompts/src/checks/uptime/heartbeat.check.ts - Heartbeat monitor
Ideally things would just work via C&P but if they don't a prerequisites sections might be helpful.
Note
Here I am again, but I still don't think that pointing to existing project files should be the recommendation or way to go. 🫣 The checkly rules file should be enough context because it include so much code and examples. As shown in the webinar, they go a long way with providing enough context. :) Especially, for folks starting out we can not expect that there are any existing files...
Feedback to the prompts I checked
"API Network Interception"
TIL that PWT MCP provides a call for network calls. Nice! The prompt also worked quite well. Good stuff.
Nit: The prompt isn't about any interception. It "only" analyzes. :)
"Monitor Your API"
This prompt states
Examples of monitors are in:
- prompts/src/checks/synthetics/01-api.check.ts
This isn't really actionable because I won't have this file.
"Monitor Critical User Flows"
I think this prompt has a similar issue. It states:
- Follow the rules in .claude/checkly.rules.md
- Look for example tests in /prompts/src/checks/synthetics/
Which, I assume, makes it impossible to use without additional context.
I stopped checking more prompts because they seem to have similar issues. :)