Write down the rules
people will actually follow.

Usually for one of three reasons. The guide shows what the brand looks like without stating the rules, so a reader admires it and then guesses when they hit a case it did not cover. Or the rules have no reasons attached, which means they cannot be extended by judgment and get abandoned the first time reality does not match the examples. Or, most mundanely, the guide is a large PDF that lives in a shared drive, gets opened once, and is thereafter approximated from memory. The fix for the first two is writing reasons and counter-examples. The fix for the third is making it a link that is always current.

Not during early access. Storyflow is paid-only right now, with plans starting at $9.99 a month, and a Free plan launches before the end of 2026. Anyone a paid member invites to a board joins free today, so freelancers and partners can read and work from the guide without paying. If you want something free this minute, a well-structured document with real examples and counter-examples does most of this, and it is far better than a beautiful guide nobody opens.

A style guide documents the visual language: type, colour, spacing, imagery, and voice, expressed as rules a human reads and applies. A design system is a working library of components implemented in both design and code, where the rules are enforced by the components rather than by the reader's discipline. They serve different audiences and different levels of maturity. A style guide is what you need when work is produced by people making individual decisions, which covers most marketing, brand, and agency work. A design system is what you need when you are building a product interface at scale, and it usually assumes a style guide already exists underneath it.

If your guide is primarily for a product team and needs to link to live components, then yes, Figma is the better home, because the components in the guide can be the actual components people use. Where Figma is weaker is distribution: reading a Figma file well usually implies having Figma, and the people who most need a style guide are often freelancers, marketers, and partners who do not have it open. Storyflow's advantage here is a link anyone can open plus the ability to see a whole section at once. Plenty of teams keep component documentation in Figma and the broader brand guide somewhere more shareable.

It can build the structure and help with wording, and it should not be making the decisions. Describe the brand and the AI lays out the standard sections ready to fill, which removes the setup work. Once you have decided a rule, it is genuinely good at drafting a clear statement of it and articulating the reason behind it, which is often the part people find hardest. What it cannot do is decide what your brand should look or sound like. A useful prompt in the other direction is asking what a new freelancer would still not know after reading the guide, which reliably surfaces unstated assumptions.

Show sentences, not adjectives. Every brand describes its voice as some combination of friendly, professional, and human, and none of those words let a writer reproduce anything. What works is taking a real sentence, showing the version that is wrong for your brand, then the version that is right, and writing one line about what changed. Do that a dozen times across different contexts such as an error message, a marketing headline, a support reply, and a release note, and a writer can extrapolate. This is the section most often skipped and the one that most improves consistency in practice.

Keep it in one place that is edited in place rather than versioned as files, so the link people already have always points at the current guide. Versioned PDFs are the classic failure, because within a year there are five of them circulating and nobody knows which is current. It also helps to record the date and reason when a rule changes, since a rule that changed for a reason is more likely to stick than one that appears to have changed arbitrarily.

Yes. Share a view-only link and anyone opens the full guide in a browser with no account and nothing to install. This matters more than it might sound, because the audience for a style guide is disproportionately people outside your team: contractors, agency partners, printers, and new hires who have not been granted tool access yet. If you want someone to contribute, invite them to the board and they join free when invited by a paid member.

Yes, and the adjacency is useful. The style guide can sit beside the brand strategy, the positioning work, the moodboards that informed the visual direction, and the customer personas the brand is speaking to. When someone asks why the palette is what it is, the answer is one scroll away rather than in a deck from eighteen months ago that nobody can find.