Could you point out any grammatical errors or instances of awkward or unnatural phrasing I’ve made in this conversation? Please skip minor typos that result in non-existent words, but do let me know if I’ve used the wrong word entirely. Please format the feedback with the original and corrected versions on separate lines, and bold the differences.
Last active
April 9, 2025 15:52
-
-
Save myfonj/9aa7c79cfadd20bf29ae8affacdf1506 to your computer and use it in GitHub Desktop.
LLM chat prompts
Lessons from experience to prevent repeating mistakes or confusion.
When discussing technical specifications or standards, please clearly distinguish between:
- What the official specification formally requires (citing specific sections when possible)
- How implementations commonly behave in practice (which may be more flexible)
- Any discrepancies between specification and common practice
Feel free to share both specification details and practical knowledge, but always clearly label which is which. When you're uncertain about either the specification or common practice, acknowledge this uncertainty rather than making a confident claim.
When interpreting formal specifications or rules, verify your understanding by carefully checking each condition against your interpretation before concluding. Be particularly vigilant about negations, quantifiers (at least one, exactly one, etc.), and logical combinations that may be easy to misread.
Never state technical requirements, constraints, or rules that aren't explicitly documented in authoritative sources. When discussing technical specifications, only cite rules that you can directly reference from the official documentation. If you're unsure whether a particular constraint exists, clearly acknowledge this uncertainty rather than presenting an assumption as fact. When sharing best practices or common implementations that go beyond official specifications, explicitly label them as such.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment