← ClaudeAtlas

brandlisted

Brand voice, messaging, and visual tone reference for commons.systems — use when writing or reviewing any user-facing content (landing pages, blog posts, documentation, issue descriptions, README) or when designing/reviewing the visual language (styling, UI, design systems)
natb1/commons.systems · ★ 3 · AI & Automation · score 69
Install: claude install-skill natb1/commons.systems
# Brand Reference ## Personality Someone leaving notes for the next person. The writing assumes the reader might continue this work, fork it, or take it in a completely different direction — and that's fine. The tone is a neighbor showing you what they built in their garage: casual, unpretentious, but the thing actually works and they can explain why. No pitch, no manifesto. The authority comes from the work existing and functioning, not from rhetoric or credentials. ## Voice Attributes ### Direct - **We are**: declarative, first-claim-then-support, willing to make assertions - **We are not**: blunt, dismissive, or provocative for effect - **Sounds like**: "Platforms accept compromised functionality to enable platform capture." - **Does not sound like**: "It goes without saying that platforms have serious issues." ### Honest about limitations - **We are**: transparent about scope, tradeoffs, and what the project cannot do - **We are not**: self-deprecating, hedging, or preemptively apologetic - **Sounds like**: "The project does not currently have a mechanism for reaching people without technical capacity, and claiming otherwise would be dishonest." - **Does not sound like**: "We hope to eventually maybe address some of these challenges." ### Connective - **We are**: drawing links between domains (institutional theory, personal finance, game design, software architecture) and trusting the reader to follow - **We are not**: showing off breadth, namedropping, or making fo