`skbk` CLI tool

[flatpickles]

This is a BIG one – perhaps a fundamental reconceptualization of how Sketchbook works, and is used. A project unto itself. Maybe a major version increment if we do this after hitting 1.0.

Currently, Sketchbook is a web app repo that you clone in whole, and add to. This works well, and makes deployment easy, but it's a little bit clunky. Your sketchbook repo has to have a bunch of code in it that you didn't write, which doesn't feel great.

It'd be nicer to create just a src/art directory equivalent, and run commands like:

skbk init
skbk dev
skbk -v
skbk update

This would still be using all the existing code, but in a less direct way. Probably app code would still be present and gitignored within /.skbk. You would still be able to npm i and use other packages. We'd have figure out types and intellisense and other things.

Nice things:

• Version checking when you run skbk commands; prompt to update when changes are pushed centrally
• Custom Vercel build templates? Allow you to deploy a Sketchbook repo directly from GitHub/Vercel
• Set a custom Sketchbook app upstream, so you can use your own fork (or maybe a local fork?)

Ultimately the skbk CLI tool would be doing a lot of file management, and indirectly running SvelteKit/Vite scripts.

First steps:

• get a prototype SvelteKit project up and running within a hidden directory (/.skbk)
• leverage top-level files
• leverage packages that have been npm install-ed at the top level
• get IntelliSense working at the top level for types declared within the hidden directory
• experiment with scripts for setup, running, updating, etc

[flatpickles]

Helpful references, perhaps:

• https://dylandupasquier.medium.com/creating-an-npm-package-using-sveltekit-c08349b8d69b
• https://scottspence.com/posts/making-npm-packages-with-sveltekit

These are optimized for packaging components only, and I want to package the whole dang thing, so we'll see how relevant this actually is.

[flatpickles]

• Shader Art & P5 & other stuff as “plugins” - add ons that you opt into, but that aren’t downloaded as a part of the project in its basic form
  • Also could be good to have “templates”, e.g. a webaudio starter project
• A skbk new command would be huge - create the boilerplate
• Template for Three.JS