#Improve Anything (SudoLang)

18 messages · Page 1 of 1 (latest)

calm plaza
#

Improve Anything

Let's roleplay. You are a world-class editor and subject matter expert. Your job is to help me improve anything I give you as input by following these instructions:

// Works best in GPT-4+
improve(target, criteria = {
accurate
error free
readable
concise
}) {
log each step:

target |>
critique |> critique |>
applyCritique(target)
}

mighty echo
#

this is amazing! thank you

short swift
#

Sorry, how to use it, just as prompt? ChatGPT understand this?

thin vapor
#

Also want to know how to use this prompt? It seems GPT-4 will treat it as code snippet rather than a working prompt.

median roost
#

looks like 🙂

calm plaza
#

This is a SudoLang function. You can usually get it to work by preceding it with "Let's roleplay. You are a SudoLang interpreter, capable of emulating the function of and code and accurately predicting its output."

Paste something to improve and then type "improve <thing to improve>"

#

If that doesn't work, pasting the SudoLang spec should do the trick. It's available on GitHub.

#

Usually, SudoLang just works in GPT-4 without any additional prompting, but I'm considering the addition of a standard preamble to the spec that you can include ahead of SudoLang program invocations to get it to work a majority of the time in both GPT-4 and GPT-3.5

reef crater
#

following

honest swallow
#

If I put “let’s role play…” then put the sudolang function, you mentioned that I then paste the thing to improve. Do I need to put it parentheses? Or just paste it? To confirm, is the format?

Let's roleplay. You are a SudoLang interpreter, capable of emulating the function of and code and accurately predicting its output.

improve(target, criteria = {
accurate
error free
readable
concise
}) {
log each step:

target |>
critique |> critique |>
applyCritique(target)
}

Actual thing I want to improve

Improve <description of thing I want to improve>

plucky elm
#

I don't understand what you mean by the SudoLang spec...is it copy / paste from whole github readme?

calm plaza
# plucky elm I don't understand what you mean by the SudoLang spec...is it copy / paste from ...

You generally don't need the spec. For this prompt, it might help to use it in the context of the thing you want to improve, e.g., if it's creative fiction:

Novel Maker Pro

Let's roleplay. You are a world class fiction author, drawing inspiration from Stephen King, William Gibson, and Douglas Adams. Your role is to help me edit my manuscripts, following these instructions:

// Works best in GPT-4+
improve(target, criteria = {
accurate
error free
readable
concise,
creative,
expressive,
impactful
}) {
log each step:

target |>
critique |> critique |>
applyCritique(target)
}

Please help me improve the following:

<your chapter here>

improve Chapter

summer cipher
#

I'm realizing the potential of sudolang the more I look at it. I don't have GPT-4 though.
Could you provide examples of sudolang's flexibility?

Specifically in the function
improve(target, criteria = { refinements, ... })
what is something analogous? let's say the user wants to do something other than improve, or perhaps the user specifically wants "dumb" outputs

critique |> critique |>
  applyCritique(target)

How else might this be used as well? As opposed to critiquing, what potential functionality can be used here?

I think sudolang is really neat, I'm just trying to wrap my head around it

calm plaza
summer cipher
#

I tried to think of a good programming example that leverages lexical differences to demonstrate functional usage.
Let's say the user wants to generate LISP code and also have the assistant rudimentarily simulate a LISP REPL / Interpeter
Does this look correct?
(at least for comprehending sudoLang in this example, I'm not interested in LISP generation specifically)

sudoLISPy v0.0.1a


target |>
generations |> generations |>
LISPGenerations(LISP)
}
Hello World, Please Dear Assistant:

Create LISP code, 
Simulate REPL evaluation per generations. ```
calm plaza
#

Try:

SudoLISPy

Please roleplay as an expert LISP programmer and interactive LISP REPL to help generate LISP code.

LISPY {
  REPLhistory
  constraints {
     generated code must be: concise, correct, modular, expressive, readable
    name each generated LISP function
  }
  generate() {
    log each step:
    generateLisp |> critique |> critique |> applyCritique(code)
  }
  /eval [functionName] {
    emulate the evaluation of the LISP function
  }
  /repl {
    enter REPL mode. /exit to return to chat mode
  }
}
summer cipher
#

Thank you!! Not only does SudoLang make way more sense with your vastly more descriptive example (versus mine lol) it also truly demonstrates to me how modular and powerful SudoLang is.
As a programmer who thinks better in pseudocode, thank you for helping me understand sudolang way better.

#

🔥 🔥 📌 ❤️‍🔥