minimal or work. Each has its own configuration and dark/light published SVG pair on the gitascii branch:
Use the generated
<picture> embed for each slug. For example, the dark source for work is https://raw.githubusercontent.com/USERNAME/USERNAME/gitascii/profiles/work/dark.svg; the light source has the same path ending in light.svg. The publishing Action discovers configuration files and refreshes the corresponding SVGs.
In /pro/profiles, you can create, duplicate, rename, delete, and restore profile versions. Promoting a named profile to default publishes the new canonical default and a backup in one Git commit. The default profile itself cannot be deleted.
The Pro badge uses a slug query parameter, so badge request totals can be grouped by profile. Those totals are proxy fetch observations, not unique visitors. Dynamic rules affect only the optional default HTTP API embed with ?dynamic=1; direct published-file URLs always display the named slug.
Creating, duplicating and restoring profiles invokes the V2 publisher after saving app state. These management operations require an App installation and assume the repository workflow already exists; they do not install the workflow or add a README embed. Copy the desired slug embed into your README yourself. Renaming display metadata is separate from changing the rendered design. Deletion removes the named configuration/SVG files and its marked README block through separate GitHub operations. A partial error can leave app and repository state out of sync; inspect both before retrying.