Skip to content
Request access

The approved brand source for teams and AI

Your brand.In every build.

Stop re-explaining the same decisions. Keep your brand's foundations, assets, and rules in one approved source, and hand the current revision to every designer, developer, marketer, and AI tool that builds with it.

Request your workspaceTry a sample brand

Early access · Workspaces open by request · The sample needs no account

Five copies of the sample brand Tallwater, made from different sources, line up behind one approved revision.
Sample brand

The cost of reinterpretation

Every new build starts by re-explaining the brand.

  • Designer, briefing a contractorWhich orange is the real one?--color-ember: #EF6A3C
  • Marketer, building a campaignIs this the current logo, or the one from the old deck?logo-primary.svg · revision 12
  • Developer, starting a featureWhat does the app use for headings?--font-heading: "Helvetica Neue"
  • AI agent, generating a screenWhat are the rules for this page?brand-context.md · 5 rules
  • Brand lead, reviewing a launchWhich version did this come from?Exported from revision 12

A PDF can't answer in the moment. A shared folder can't say which version is approved. A new AI session starts with no brand at all unless someone pastes the rules in again.

Each new person, brand, vendor, and AI tool multiplies the questions, and the near-misses. iStyleGuide answers them from one approved source, with the revision attached.

How it works

Define it once. Approve it on purpose. Deliver it everywhere.

  1. 01 / Define

    Put every decision in one place.

    Colors, type, rules, and files live together as structured data. Bring an existing brand in by pasting CSS variables or token JSON.

    Colors
    Named tokens, roles, and semantic mapping
    Type
    Heading and body families
    Rules
    Written guidance people and agents can read
    Assets
    Logo, wordmark, fonts, and original files
  2. 02 / Approve

    Draft freely. Release deliberately.

    Save & approve creates the next numbered revision. Exports only ever come from an approved revision, and a save based on an older revision is stopped before it can overwrite newer work.

    2 unsaved changes
    • Ember #EF6A3C → #E85D2F
    • Rule 2 reworded
    Exports still serve revision 12
  3. 03 / Deliver

    Hand everyone the same revision.

    Each role gets the format it works in, and every file is stamped with the brand and revision it came from.

    Designers and marketers
    Originals, bound logo and wordmark, written rules
    Developers
    tokens.css · app-theme.css · tokens.json
    AI tools
    brand-context.md · AGENTS.md · agent package

Put the brand to work

Change one decision. Watch every output follow.

Runs the real export engine

Edit a sample brand and inspect exactly what a developer or an AI tool would receive. It runs in your browser and isn't saved. Your own brand lives in a workspace.

Start from
Colors
Primary text and dark surface
Light canvas
Action accent
Muted text
Secondary surface

Tallwater · revision 12 · sample

  • Fjord#10213APrimary text and dark surface
  • Mist#EEF1F4Light canvas
  • Ember#EF6A3CAction accent
  • Slate#5B6B7FMuted text
  • Lichen#C9D3C0Secondary surface

Headings in Helvetica Neue. Body in Helvetica Neue.

  1. Set headlines in Helvetica Neue Bold, uppercase, with tight tracking.
  2. Use Ember for primary actions and one highlight per layout.
  3. Place text on Mist or Fjord. Set button labels in Fjord on Ember.
  4. Keep corners square: 2px radius on controls and cards.
  5. Write like a guide: short sentences and concrete distances.

Want this for your brand? Request your workspace

Keep the work aligned

Catch the color that almost matches.

Paste CSS from a contractor, a template, or an AI tool. Brand checks list every hex color, flag the ones outside the approved palette, name the nearest approved token, and label WCAG contrast.

Checks cover hex colors and contrast today. They point out specific, explainable differences; they don't certify that a design follows every rule.

2 of 4 colors are outside the Tallwater palette.

  • #EEF1F4Approved · MistBackground
  • #10213AApproved · Fjord14.24:1 on Mist · AA pass
  • #E85D2FOutside · nearest Ember #EF6A3C (ΔE 5.2)3.07:1 on Mist · AA fail
  • #7A8797Outside · nearest Slate #5B6B7F (ΔE 11.5)3.23:1 on Mist · AA fail

Where the brand goes next

Bring the approved brand to the tools where work happens.

Let AI tools ask for the brand.

Today, the agent package gives you brand-context.md, AGENTS.md, and token files to drop into a repository for Cursor, Claude Code, Codex, or any tool that reads project files. With an MCP connection, an authorized tool asks iStyleGuide for the context a task needs and gets the current approved revision every time.

MCP, the Model Context Protocol, is an open standard AI tools use to connect to data sources. Context gives a model the approved decisions; review still decides what ships.

Request MCP accessHow agent context works
Preview · MCP in early access
  1. 1 · The agent asks
    {
  "tool": "get_brand_context",
  "brand": "tallwater",
  "task": "pricing page",
  "include": [
    "colors",
    "type",
    "rules"
  ]
}
  2. 2 · iStyleGuide answers with revision 12
    {
  "brand": "Tallwater",
  "revision": 12,
  "status": "approved",
  "colors": {
    "action": "Ember #EF6A3C",
    "text": "Fjord #10213A",
    "canvas": "Mist #EEF1F4"
  },
  "type": {
    "heading": "Helvetica Neue, bold, uppercase"
  },
  "rules": [
    "Set headlines in Helvetica Neue Bold, uppercase, with tight tracking.",
    "Use Ember for primary actions and one highlight per layout.",
    "Keep corners square: 2px radius on controls and cards."
  ]
}
  3. 3 · The build uses it
    Pricing · Guide plan

    $12 / month

    Offline maps, route planning, and weather on every trail.

    Start planning

Ship brand changes as pull requests.

An approved revision should reach your code the way every other change does: as a readable diff your team reviews and merges. Export the files by hand today; pull requests opened from approved revisions are in early access.

Explore the GitHub previewRequest GitHub access
Preview · early access
Update Tallwater brand tokens to revision 13your-org/web · istyleguide/tallwater-r13 → main · 2 files changed
styles/tokens.css/* Tallwater · approved snapshot v13 */Removed: --color-ember: #EF6A3C;Added: --color-ember: #E85D2F; --color-fjord: #10213A;Removed: --font-heading: "Helvetica Neue", Arial, sans-serif;Added: --font-heading: "Arial Black", Arial, sans-serif;

Opened for review from approved revision 13. Nothing reaches main until your team merges it.

Who it's for

Built for product and brand teams that ship with many hands.

As a company adds designers, developers, marketers, contractors, and AI tools, the brand gets reinterpreted more often. iStyleGuide gives all of them the same approved revision.

  • Onboard a designer, developer, or contractor with the approved source instead of a walkthrough.
  • Give developers tokens and an app theme that match the approved revision.
  • Start every AI session with the brand's colors, type, and rules.
  • Know which revision a campaign, screen, or file came from.
See the Team plan

Agencies and studios

Keep several client brands in one workspace today, each with its own approved revision, assets, and exports. Hand a client team a source, not a PDF. Separate client workspaces are planned.

See the Agency plan

Teams building with AI

Give Cursor, Claude Code, or Codex the approved brand before the first prompt, not after the third correction. The agent package works today; the MCP connection is in early access.

How agent context works

What you can use today

Clear about what's ready.

Available now

  • Brand foundationsNamed color tokens with roles, semantic roles, heading and body type, and written rules in one approved source.
  • Approved revisionsSave & approve creates the next numbered revision. A save based on an older revision is stopped instead of overwriting newer work.
  • Asset libraryPrivate uploads of logos, fonts, images, and PDFs, with a bound logo and wordmark for each brand.
  • Developer and agent exportsCSS variables, an app theme, token JSON, brand-context.md, and an agent package with AGENTS.md, each stamped with its revision.
  • Bring an existing brand inPaste existing CSS variables or token JSON, review the differences, and apply them to a draft.
  • Brand checksFind every hex color in a code fragment, flag colors outside the palette, name the nearest approved token, and label WCAG contrast.
  • Multiple brands and membersSeveral brands in one workspace, with owner, editor, and viewer roles.

Early access

  • Workspaces for new teamsNew workspaces open by request while iStyleGuide is in early access.
  • MCP connection for AI toolsAuthorized AI tools request the approved context a task needs, instead of relying on a file someone attached.
  • GitHub pull requestsAn approved revision becomes a reviewable pull request that updates token and theme files in the repositories you choose.

Planned

  • Revision history and comparisonBrowse earlier revisions and compare what changed between two of them.
  • Separate client workspacesIsolated workspaces with their own members for each client brand an agency manages.
  • Ongoing repository syncKeep connected repositories on the latest approved revision automatically.

Questions

Before you bring your brand in.

How is this different from a brand PDF or a shared folder?

A PDF describes the brand; iStyleGuide makes it usable. Colors, type, and rules are structured data with an approved revision number, so a developer can take tokens, an AI tool can read context, and anyone can tell which version a deliverable came from. Files live next to the rules for using them.

Can we bring in our existing brand?

Yes. Paste existing CSS variables or token JSON, review the differences, and apply them to a draft. Then upload logos, fonts, and other originals, bind your logo and wordmark, and approve the first revision.

Who is it for?

Product and brand teams at growing companies, where designers, developers, marketers, contractors, and AI tools all build with the same brand. Agencies use it to manage several client brands, and AI-heavy teams use it to give their agents real brand context.

What can our developers export?

CSS custom properties, an app theme that maps your semantic roles to shadcn-style variables, design-token JSON, and a Markdown context file. Every file carries the brand name and revision it came from.

How does it help AI-assisted work?

Today you can download an agent package, with brand-context.md, AGENTS.md, and token files, for Cursor, Claude Code, Codex, or any tool that reads project files. An MCP connection that lets authorized tools request context directly is in early access. Context gives a model the approved decisions; it does not guarantee every output follows them, so review and brand checks still matter.

What is available today?

Brand foundations, approved revisions, the asset library, all exports and the agent package, import from CSS or token JSON, color and contrast checks, multiple brands, and member roles. The sample brand on this site runs the same export code in your browser.

Which connections require early access?

New workspaces, the MCP connection for AI tools, and GitHub pull requests. Revision comparison, separate client workspaces, and ongoing repository sync are planned.

How do teams and agencies work with multiple brands?

A workspace holds several brands, each with its own approved revision, assets, and exports, and you switch between them in the sidebar. Members have owner, editor, or viewer roles across the workspace. Separate client workspaces, each with its own members, are planned.

Is the sample brand saved anywhere?

No. The sample runs in your browser and resets when you leave. Your own brand is saved and approved in a workspace.

Give your next build the approved brand.

Tell us about your brand and team, and we'll follow up about opening your workspace. Bring your existing CSS variables or token JSON, and approve your first revision on day one.

Request your workspace Sign in to your workspace