What shipped, newest first. Identity Forge is built in the open and moves most weeks.
Last update 14 Aug. Machine-readable feed.
14 Aug
Domain research now treats a new registration and an aftermarket purchase as separate paths. State which one you are considering and Identity Forge returns registrar evidence or a public sale-page observation without treating one as proof of the other. Repeat the same successful check within ten minutes and it costs no additional units.
Take a look14 Aug
The CLI can configure the Identity Forge MCP server for Claude Code, Cursor, Codex, Gemini CLI, VS Code, Copilot, opencode, or Pi, then verify the connection with `doctor`. It checks npm for new releases in the background, and `update-check` gives you an immediate version report.
Take a look11 Aug
You can now search, filter, and inspect upcoming .com, .net, and .uk domain drops from public source feeds. The workbench shows the source, scheduled drop time, and observation freshness, with saved views and collections available after sign-in.
Take a look4 Aug
Coding agents can now search the full Google Fonts catalog, ask for curated heading and body pairings, and find fonts similar to one they already like, straight from the MCP server, the CLI, or the public API. Font swaps on a kit can finally be grounded in the catalog instead of guessed.
Take a look4 Aug
The inspiration gallery now shows real sites side by side with the design system extracted from each one. Hover or flip a card to see a page an agent built from the extracted kit alone, copy any palette color with a click, and search by site, style, or font.
Take a look4 Aug
New palette pages collect kits by their lead color: green, red, blue, orange, and yellow. Every palette shows its full roled system (background, text, primary, accent, muted, border) in light and dark with click-to-copy hex codes, and links the complete kit behind it.
Take a look4 Aug
The new shadcn page gives every free kit a copy-ready `npx shadcn add` command. Running it writes the kit's full theme into your project's CSS: all semantic tokens in light and dark, fonts, radii, shadows, and gradients, as a native registry item.
Take a look3 Aug
Every design kit is now available as one paste-ready prompt per app builder: the full system with color tokens in light and dark, fonts, type scale, motifs, and rules, with instructions the builder follows. Pick a kit on the new per-builder pages and copy its prompt straight into your project chat or knowledge settings.
Take a look30 Jul
Every kit and brand now has a version timeline: what changed, when, and by whom, with colour changes measured rather than eyeballed so a diff says how far a colour actually moved. Existing kits and brands received a baseline version, so a history you consult today has a starting point instead of an empty list.
Take a look30 Jul
Every kit now reports how well its chart colours actually work: how far apart the series are, including under colour-blind vision, how many distinct hue families they cover, and whether any of them is close enough to your red, amber and green to be mistaken for a status. Kits also hand over two extra colour scales built for data, one for ranked values and one for up to twelve independent categories, both kept clear of those status colours.
Take a look27 Jul
Add .md to a kit or collection URL and you get the same page as clean markdown. Useful if you are pasting a kit into a conversation, or pointing a coding agent at one without asking it to parse a web page.
Take a look26 Jul
An agent with a key can now revise a saved kit in place, remove one, and change what a brand is composed of, rather than forking a new copy for every change. Kits also carry a permanent id that survives renaming, so anything built against a kit keeps pointing at it.
Take a look25 Jul
Eighteen interface styles with comparable specimens, so you can choose the grammar of a product surface separately from its palette and type. Filterable, and readable by an agent through the same API as everything else.
Take a look25 Jul
Twenty-four image directions and thirty-two page recipes, each with a stated judgment about when it fits. These compose on top of a kit, so a brand can specify how its pictures look and how its pages are built without changing its tokens.
Take a look21 Jul
The landing page, kits, articles, pricing and the agent documentation are now available in four more languages.
21 Jul
An agent can read a project brief, split naming research across approaches, and return candidates with their reasoning, through the web app, the API, the CLI or the MCP server. Naming language is now separate from the markets a name has to work in.
Take a look17 Jul
Kit browsing was rebuilt around lenses and use-case lanes with ranked, synonym-aware search, so looking for something for a dashboard or a storefront puts the plausible kits first. Kit pages state where a kit fits.
Take a look17 Jul
Install the CLI with npx and your coding agent can browse kits, pull a design brief and apply a kit without leaving the terminal. The same package runs as a local MCP server for agents that speak it.
Take a look15 Jul
A single place that explains what an agent can pull, in what formats, and with which key. Point your agent at it and it can work out the rest on its own.
Take a look14 Jul
The first articles on design systems, themes and agent handoffs, covering the question most people arrive with: whether they need a theme, a system, or something an agent can implement.
Take a look12 Jul
A brand can now be rendered onto real-world surfaces, so you can look at a signage board, a packaging front or an app screen wearing it instead of judging the system from swatches. Renders are kept with the brand and can be shared.
12 Jul
A brand can hold several variations and go out as one link, with an optional password. Whoever opens it sees each variation on real surfaces and can leave comments per variation, so feedback arrives attached to the thing it is about.
12 Jul
With a key that carries write access, an agent can create a kit, assemble a brand from it and hand back a link, through the API or the local server it speaks to. Repeated calls are safe to retry without creating duplicates.
Take a look12 Jul
A brand now comes with a wordmark and a monogram drawn from its own type and colour roles, plus the icon sizes a site needs, exported alongside the rest of the brand.
2 Jul
The home page now carries a filterable wall of complete example builds, each one a real page produced from a single kit, which you can scroll in place before opening it. Storefronts, dashboards, marketing pages and service sites are all represented.
30 Jun
Kits are classified along two axes, how ornamented they are and what era they read as, and the gallery can be filtered by either. Each kit also previews in light and dark rather than one fixed mode.
Take a look29 Jun
Every kit now describes its structure and its vibe in comparable terms, so a kit page can list its near neighbours and you can move sideways through the catalogue instead of starting over. Agents get the same comparison through the API.
Take a look28 Jun
Refine a kit on one screen: colours by role, type, shape, elevation and motion, with the result drawn live on real surfaces. Save it and it is yours to apply and export.
25 Jun
Point at an image or a live page and it comes back as a complete kit, with colour roles, type and the rules that go with them, rather than a list of extracted colours. Extracted kits are collected in a gallery you can browse for a starting point.
Take a look24 Jun
Identity Forge started as a name and domain generator. From here it is a branding pipeline: names and domains are one stage, and the thing you leave with is a complete design kit, colour roles in light and dark, type, spacing, shape, elevation, motifs and the rules that keep an implementation on brand, in a form a coding agent can build from directly.
Entries start at the point Identity Forge became a design kit pipeline. Before that it was a name and domain generator, and that part of its history is not itemised here.