Complex examples - Githubissues

Friction log for working on prompt-name

Boy is it annoying to write in JSON, even with schema completion!
It's really confusing when to use var vs retrieve, and how to do the naming scheme.
It feels weird to have a prefix for var but not for store (and also store really should

things to do to improve it:

[x] Allow let to take a map of properties and values to set at once (so you can set store iwthin sub-expressions)
[ ] Allow template to directly fetch things from env and store (e.g. @store(_default_store:komoroske.com:value) (it gets funky because variable names might have weird characters in them and it needs to be another delimiter))
[x] name vs key in let and store is weird, they feel like they should be the same
[x] store.key --> store.name
[x] var and retrieve should have else clauses. If the value is not set (is undefined) then the else clause is evaluated and returned instead. This allows a pattern where you can request-or-calculate-and-store the value. (use it in complex examples)
[ ] Update examples-complex.json to use the retrieve/else behavior
[x] Should var have an optional default that is retrurned if the var is not bound?
[ ] Prompt should be able to take an optional model argument, just like other ones can now be passed a model or get it from environment
[x] Should there be a entrypoints in seed packet that describe the usage of different named entrypoints (and which ones are SUPPOSED to be used, vs internals?). Then the CLI could show entrypoints mainly
[x] Add a comment field. description is used for external facing behavior, comment is used for internal notes to self or people reading the code, and never shows anywhere
[ ] verbose log should have an amount of indents tied to how nested it is.
[x] addition, substraction, deletion, multiplication seed types
[ ] slice, shuffle array operations
[x] does array.length operation work using property seed_type already?
[x] Tooling to detect invalid refs to local seeds after unrolling
[x] It would be less annoying to type if sub-seeds didn't ened a "type", but could be determined from the precense of which keys they had (taking care to design it so each seed as at least one distinctive property). But then that would make the detection of if a value is a sub-seed or not way harder (currently it's just hte precense of 'type').
[ ] should let.name ==> let.var?
[x] typing komoroske.com prefix a million times gets repetitive, maybe have a prefix property in seed packet that will be auto-expanded when seeds unrolled? Add a var_prefix environment variable that adds it if it's not a known key and doesn't have a prefix already.
[x] Add a vars at top level of seed packet that basically adds a let-multi seed in front of every top one
[ ] should recall take an optional create: boolean and only create the store if it's passed? That way you can do a probe check for memories without erroring, but in the common case where you just had a typo you don't have to wory about it
[x] write-favorire-things-limerick and favorite-things-limerick have to do a lot of duplication of setting memory and the recalled memories, because each might be run as an entrypoint. Are there ways to de-duplicate them? For example, what if the seed packet was allowed to set an evironment overlay for all seeds in the packet?
[x] Could we get rid of type:object and just have it search through keys and find any that were seed-reference-like?
[x] is id distinctive enough in a seed reference? should it be seed?
[ ] There should be a way to delete a memory as a command (needs approval)
[x] array should be able to return its last item (then use it for the block where we store

jkomoros / prompt-garden

Complex examples #36