Prepare for me, a one-liner headline and link that is only 8 words long, on the topic of “Los Angeles Mayor’s Race”, sourced from the most popular news websites. The headline should summarize and provoke a click. Make the headline short. The link should go to the story. For every headline, use the md format: Topic: Headline: link

---

Repeat for the following topics: “Gaza War”, “Iran War”, “Gas Prices”, “Recession”, “Inflation”

Repeat for the following topics: Gaza War, Iran War, US China Relations, California Governors, Voting Rights Act, Inflation Crisis, Economic Pain, Rise in Racism, Rise in Misogyny, Arcadia Mayor Resigns, Anti-Chinese Sentiment, Asian Americans and Gentrification, Los Angeles Mayor’s Race, Housing Affordability, Climate Change, Pollution, AI and Jobs, AI and War, Trade Conflicts, Healthcare, Health Insurance, Supply Chain, Interest Rates, Energy and Power

(Note that the longer the list is, the more the LLM will hallucinate headlines and links. It also helps if the news source has an RSS feed. It seems to know how to use those, sometimes. Otherwise, I don’t know how it’s getting the news. I realize this makes the LLM sound like a shit version of an RSS feed aggregator.)

---

for the wordpress contact form 7 plugin, create a form with the fields first name, email, phone, zip, and a list of checkboxes for the following categories of stuff to give away: vintage, electronics, computer parts, scrap metal, office supplies, art supplies, boxes, clothes, housewares, books.

---

consider index_builder.py to be obsolete legacy within this new system. implementing new commands is acceptable.

(This helps to release Work from holding on to it’s goal of retaining backward compatibility.)

---

update then clean up the docs

(Telling Work to work on the docs seems to help. It also externalizes some of the internal state into a file, so it can be re-read in the future, or in the event of a crash.)

---

continue

(Work keeps a to do list and plans. It doesn’t always complete them. So “continue” will tell it to keep working on it.)

---

Warm up the context:

How does Thaura find dependencies between tasks in a task list?

Then, copy-paste a bunch of your recent chat messages about a project:

Extract all the listed tasks or to-dos in this chat:

Then, tell it to try its best ordering the tasks, and also ask for additional info as needed:

Please put these tasks in order. Ask if clarification is necessary. Keep refining the order until the list is in the correct order.

---

Tell it to examine a prior project, and specifically note the features I feel are useful to copy. These features took a long time to create.

Look at ../Reading Material Archive.thaura/ and study the documents in there (but ignore the numbered folders because they are the actual document archives). study about how the PDF files were classified as books, journal articles, pdf prints of web pages, etc.

---

After some time generating code, I ask it to consolidate repetitive code into libraries. (It saved several hundred lines of code.) I’m trying to use the DRY style of programming – bottom-up, where you first produce code, then consolidate.

are there opportunities to DRY out the code and put some functions into a library?