Foggydev

update on the game (pictures and combat at night) - first city basics build - combat starts to feel smooth @spawn takes a little learning curve for more complex game and build mechanics so here are some tips I found useful: concept art: savi works splendidly if you either have her create pictures or give her visual input, simply copy/paste into the chat she can take alot of file formats repeatability: if you found one good way to create something; turn it into a skill, script or schema - make it replicatable once you have success sources: spawn has phenomenal basics but it isnt exceptional in all minute details, so if you find opensource repositories with assets, tips, mechanics or skills - give it to savi to read trough it and tell her to adapt it and distill learnings, anything that is already proven good can be smoothly translated into your game tab + F: it lets you take a note with the screen you see, so it takes a snapshot of it and you can leave a note, this becomes a little waypoint for savi to see exactly what you want to have changed with a description you can input for it - super useful for corrections she can work off one by one (i usually have a good 10+ of these waypoints after a big build to correct details) overall: compared to claude code or codex, where it is about code and audits, i found that creating todo lists work very good, leveraging her wisps (her own agents) for gruntwork like generating blender assets in the background while you discuss what comes next, keeping documentations and skills, best practices and goals in the game repo for her makes compaction easy and eases the headache of telling her what *exactly* needs to be done between sessions @spawn really created a proper gamedev agent that fully understands what is being build, keeping everything orderly and helping her build it out still needs you - but you can legit just prompt with examples and go a long way very very pleasent user experience on my part ngl