Prompting

A new idea I wanna test out for vibe coding: a classification of ‘essential’ and ‘non-essential’ artefacts.

Keeping a status for this might help us clean stuff up later. This could extend to skills, md files etc.

For example: a todo.md would be an essential artefact, howeever, if we complete some of the items, those could be marked as ‘non-essential’.

Or while doing various versions, its easy to incur old bloat, and maybe those could slowly go into ‘non-essential’ thus asking the LLM to use them less. Maybe a “count” could be used for all vibe coded files, on how many times they’re getting used… this could be done for functions, classes, skill files, etc. and over time, they help us move things from ‘essential’ –> ‘non-essential’ —> ‘delete’