disqualifier
5e787edbb0
New docs/workflow.md covering how we actually work day to day: - why git / why WSL2 (our reasons, links out for generic install) - signing up on our Gitea (self-serve register, SSH + deploy-key model) - our git vs public git: per-repo identity, signed commits, develop->main - our-flavored git basics (everyday loop, commit small/often, gl graph) - the dev workflow: plan-in-chat / build-in-Claude-Code, tmux split, claudedo voice control, the .claude/ project convention, AI-assist habits (git diff | clip.exe) - recommended setup (WSL + VS Code + Claude Code, pyenv, flake8) - handy .zshrc/.bashrc snippets with prose on the high-value ones Claude-first but soft: any AI works, we recommend Claude, and the .claude/ structure is built on that preference. Sanitized with placeholders throughout. Nav: Home / Libraries / Standards / Workflow / Deploy; landing card grid updated. Verified: mkdocs build --strict clean. Signed-off-by: disqualifier <dev@disqualifier.me>
1.2 KiB
Rethink Studios Handbook
The public reference for building and shipping with Rethink Studios: our shared libraries, our coding standards, and how to deploy a project on our network.
This is a public site — it documents generic patterns and conventions. Real
infrastructure specifics (hostnames, internal IPs, exact topology, secrets) stay
out of it; examples use placeholders like <dev>, <project>, and /srv/....
Sections
-
:material-package-variant: Libraries
The live list of the
rethink-publiclibrary suite, pulled straight from Gitea — each entry links to the repo, where the README and tags live. -
:material-ruler-square: Standards
House coding standards — file hygiene, docstrings, type hints, linting, and how we handle errors.
-
:material-sitemap: Workflow
How we actually work day to day — our Gitea, git habits, and the plan-in-chat / build-in-Claude-Code flow, plus shell setup.
-
:material-rocket-launch: Deploy
How to get a project running on rethink-net — containers, paths and mounts, permissions, and secrets.