horribleCodes

> Should we adhere to a specific format for text in general, so for example Markdown? Markdown seems good, I was using it so far. I think simple bullet points...

Should I also ask assistant replies to include Markdown-style formatting? I assume it will be enabled for the actual model, so we probably should take advantage of that. Likewise, I've...

I majorly reworked the document - first, since the guidelines weren't just limited to writing prompts, I renamed it to `Guidelines`. I also moved the examples to another document since...

> A suggestion: we should maybe tell users not to demand insane amounts of work as the prompter. This only encourages poor-quality answers, most likely ChatGPT spam. Example: > >...

Not really sure why the pre-commit check is failing. I also tried running the site on a codespace, but I keep getting a 502 error. If anyone has any advice,...

Got it to work locally, had some issues setting up yarn. The changes look good, the links are working. I also didn't realize pre-commit was its own thing, I assumed...

> Suggestion: provide numerical values both as metric and imperial units when appropriate. I like that idea, though personally I think allowing prompt engineering to declare a preferred system would...

Now that the guidelines have been updated, could we add a direct link to them on each respective task? Ideally, I'd like to have a collapsible container so users don't...

Do we have at least one clearly visible instruction to read the guidelines from registering to sending your first submission? It might be overkill, but since any form of comment...

The rewriting system is a whole other can of worms because it'd get used to correct factual errors, replies without necessary warnings and other things. But this is a dimension...