One design language
Components carry the design decisions so apps do not each re-invent them. Tokens are the contract; raw color and spacing values are not.
One set of components, defaults and design language across every LiveReader app.
Early days
Habitus is being set up. The styling approach and token structure are settled, but the component set is deliberately thin and the palette values are still placeholders — see TO DISCUSS in the repository README for what remains open before building anything substantial on top of it.