Add Harry writing style skill

2026-06-03 21:28:18 +01:00
parent 6ee5596160
commit 5d71aa1308
27 changed files with 1567 additions and 0 deletions
@@ -0,0 +1,33 @@
+# Bad Examples: debugging-help
+
+1. > Could you provide some more details about what you mean by flushing Redpanda data?
+
+   Fails because the user asked for a command. Give the command or ask only for the missing target/scope.
+
+2. > It sounds like the issue is still persisting. Let's work through it step by step.
+
+   Fails because it translates "still fucked" into support-agent filler.
+
+3. > The server registration flow may not be correctly associating resources with the active organisation.
+
+   Fails because it restates the question instead of investigating why the server is not registered.
+
+4. > Laravel Boost appears to be installed, but there may be an issue with command discovery.
+
+   Fails if it drops the exact command and namespace error.
+
+5. > There are browser console issues that should be reviewed and addressed.
+
+   Fails because it sounds like a Jira ticket and loses urgency.
+
+6. > The hardcoded Tailwind values may warrant further investigation.
+
+   Fails because the real question is direct: why are `[]` Tailwind values being used here?
+
+7. > UUIDs may not be the correct keying strategy in this area.
+
+   Fails because the source has severity: "we SHOULD NOT BE USING UUIDS AS KEYS."
+
+8. > Codex process initialization is working, but authentication is experiencing issues.
+
+   Fails because "codex now spawns, but auth is broken" is clearer.
@@ -0,0 +1,41 @@
+# Good Examples: debugging-help
+
+1. > I need a command to flush all the data out of redpanda.
+
+   Works because it asks for the exact operational output, not a lecture.
+
+2. > still fucked
+
+   Works when paired with logs/errors. Do not sanitise this to "still failing" unless asked.
+
+3. > Why is the server not being registered to the organisation?
+
+   Works because it asks for root cause, not generic debugging steps.
+
+4. > laravel boost is installed but `a boost:install` says there are no commands defined in the boost namespace.
+
+   Works because it gives current state and exact failure.
+
+5. > Got some errors in the browser logs that need fixing.
+
+   Works because it is a terse handoff when the logs are available in context.
+
+6. > Okay. There are some hardcoded values being used here with the [] tailwind syntax. Why is that?
+
+   Works because it spots a suspicious implementation detail and asks for justification.
+
+7. > we SHOULD NOT BE USING UUIDS AS KEYS.
+
+   Works because the capitalisation is part of the severity.
+
+8. > codex now spawns, but auth is broken.
+
+   Works because it reports the new state after one fix and the next blocker.
+
+9. > still immediately closes when opening with debug logging. Do a simplification and bug hunting sweep.
+
+   Works because it combines repro state with the requested diagnostic style.
+
+10. > Both sources, separate commands is fine yeah
+
+   Works because it answers an implementation choice without over-explaining.