4 ms·
I like to keep a personal recipe book of prompt modifiers. For bash scripting I often write my prompt and then copy-paste the following to prompt: ``` When mak
by DevDesmond 1y ago
I like to keep a personal recipe book of prompt modifiers. For bash scripting I often write my prompt and then copy-paste the following to prompt:
```
When making edits to the script, ensure the script remains
- Idempotent
- Functional after a fresh install of a virtual machine
Additionally, keep things stupid simple and avoid:
- Unnecessary error checks
- Defining colors and custom logging functions
- Bells and wistles
- Backups
- Branching Paths
- Script Arguments
```
I find it helps cull back the LLM 's overenthusiasm for abstractions.
- SOLAR_FIELDS 1y agoIn general I usually toss “follow KISS principles” into nearly every plan prompt. If you tell it that, it helps cut out a lot of the noise and only focuses on the core functionality
- dotancohen 1y agoI'd love to see some more of that recipe book. If you don't want to share here, my Gmail username is the same as my HN username. Thank you!
- mattmanser 1y agoTry this one, it works 100% of the time: X. Don't write stupid code. Replace X with your prompt.