![]() |
VOOZH | about |
dotnet add package BlazingStory.ToolKit --version 1.0.0-preview.87
NuGet\Install-Package BlazingStory.ToolKit -Version 1.0.0-preview.87
<PackageReference Include="BlazingStory.ToolKit" Version="1.0.0-preview.87" />
<PackageVersion Include="BlazingStory.ToolKit" Version="1.0.0-preview.87" />Directory.Packages.props
<PackageReference Include="BlazingStory.ToolKit" />Project file
paket add BlazingStory.ToolKit --version 1.0.0-preview.87
#r "nuget: BlazingStory.ToolKit, 1.0.0-preview.87"
#:package BlazingStory.ToolKit@1.0.0-preview.87
#addin nuget:?package=BlazingStory.ToolKit&version=1.0.0-preview.87&prereleaseInstall as a Cake Addin
#tool nuget:?package=BlazingStory.ToolKit&version=1.0.0-preview.87&prereleaseInstall as a Cake Tool
👁 tests
👁 NuGet Package
👁 Discord
The clone of "Storybook" for Blazor — a frontend workshop for building UI components and pages in isolation.
👁 alternate text is missing from this package README image
Built almost 100% on Blazor native (only a few JavaScript helpers), so you can create a UI catalog application the Blazor way — no npm, package.json, webpack, or JS/TS code required.
Blazing Story also provides an MCP server feature that exposes component and story information to AI agents for highly accurate code generation.
👉 Try the live demo: https://jsakamoto.github.io/BlazingStory/
This walkthrough assumes you already have a Blazor app project (e.g. MyBlazorApp1) with components you want to catalog.
dotnet new install BlazingStory.ProjectTemplates
Add a Blazing Story app project alongside your existing app:
# For Blazor WebAssembly:
dotnet new blazingstorywasm -n MyBlazorApp1.Stories
# For Blazor Server (add -mcp to enable the MCP server feature):
dotnet new blazingstoryserver -n MyBlazorApp1.Stories
dotnet sln add ./MyBlazorApp1.Stories/
The MCP server feature is only available with the Blazor Server variant.
Visual Studio users can do the equivalent through Add → New Project and pick the "Blazing Story (WebAssembly App)" or "Blazing Story (Server App)" template.
dotnet add ./MyBlazorApp1.Stories reference ./MyBlazorApp1
Place a *.stories.razor file (typically under a Stories/ folder) in the Blazing Story app project:
@* MyBlazorApp1.Stories/Stories/Button.stories.razor *@
@using MyBlazorApp1.Components
@attribute [Stories("Components/Button")]
<Stories TComponent="Button">
<Story Name="Primary">
<Template>
<Button Label="Button" Primary="true" @attributes="context.Args" />
</Template>
</Story>
</Stories>
The file name must end with .stories.razor — this is required by the "Show code" feature on the "Docs" pages.
dotnet run --project ./MyBlazorApp1.Stories
🎉 You'll see the Storybook clone built on Blazor!
👁 alternate text is missing from this package README image
For advanced topics — story structure, args, controls, decorators, addons, and more — see the Blazing Story Documentation Site.
Agent skills are published to help AI coding assistants implement stories and custom addons for Blazing Story:
blazing-story-story — generate .stories.razor files for your componentsblazing-story-addon — scaffold and register custom addons (toolbar, panel, preview decorator)Install with GitHub CLI (v2.90.0+):
gh skill install BlazingStory/agent-skills blazing-story-story
gh skill install BlazingStory/agent-skills blazing-story-addon
For details and the latest information, see the upstream repository: https://github.com/BlazingStory/agent-skills
.NET SDK 8 or later
Assembly files of a Blazing Story app embed the project file path as metadata.
👁 alternate text is missing from this package README image
If the project path must remain confidential, avoid using Blazing Story.
Blazing Story is a personal hobby project and a technical exhibition — it is not an officially derived product of Storybook. I plan to keep improving it, but it may be abandoned if I cannot spend enough time on it. Forks and community maintenance are welcome.
Because Blazing Story is a Blazor-native re-implementation that mimics Storybook's look, behavior, and functionality, none of the Storybook community's contributions, addons, or related services are available here. The trade-off is that Blazor developers get a Storybook-like component catalog within the familiar .NET ecosystem, free from the JavaScript front-end toolchain.
See RELEASE-NOTES.txt.
Mozilla Public License Version 2.0
The third party notice is here.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 net8.0 is compatible. net8.0-android net8.0-android was computed. net8.0-browser net8.0-browser was computed. net8.0-ios net8.0-ios was computed. net8.0-maccatalyst net8.0-maccatalyst was computed. net8.0-macos net8.0-macos was computed. net8.0-tvos net8.0-tvos was computed. net8.0-windows net8.0-windows was computed. net9.0 net9.0 is compatible. net9.0-android net9.0-android was computed. net9.0-browser net9.0-browser was computed. net9.0-ios net9.0-ios was computed. net9.0-maccatalyst net9.0-maccatalyst was computed. net9.0-macos net9.0-macos was computed. net9.0-tvos net9.0-tvos was computed. net9.0-windows net9.0-windows was computed. net10.0 net10.0 is compatible. net10.0-android net10.0-android was computed. net10.0-browser net10.0-browser was computed. net10.0-ios net10.0-ios was computed. net10.0-maccatalyst net10.0-maccatalyst was computed. net10.0-macos net10.0-macos was computed. net10.0-tvos net10.0-tvos was computed. net10.0-windows net10.0-windows was computed. |
Showing the top 2 NuGet packages that depend on BlazingStory.ToolKit:
| Package | Downloads |
|---|---|
|
BlazingStory
The clone of "Storybook" for Blazor, a frontend workshop for building UI components and pages in isolation. |
|
|
BlazingStory.Addons.BuiltIns
The clone of "Storybook" for Blazor, a frontend workshop for building UI components and pages in isolation. |
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.0.0-preview.87 | 121 | 6/16/2026 |
| 1.0.0-preview.86 | 161 | 6/14/2026 |
| 1.0.0-preview.85 | 101 | 6/11/2026 |
| 1.0.0-preview.84 | 205 | 6/9/2026 |
| 1.0.0-preview.83 | 917 | 5/31/2026 |
| 1.0.0-preview.82 | 1,813 | 5/26/2026 |
| 1.0.0-preview.81 | 195 | 5/24/2026 |
| 1.0.0-preview.80 | 133 | 5/21/2026 |
| 1.0.0-preview.79 | 282 | 5/16/2026 |
| 1.0.0-preview.78 | 2,316 | 4/27/2026 |
| 1.0.0-preview.77 | 1,793 | 4/22/2026 |
| 1.0.0-preview.76 | 3,110 | 4/12/2026 |
| 1.0.0-preview.75 | 2,353 | 4/4/2026 |
| 1.0.0-preview.74 | 278 | 4/2/2026 |
| 1.0.0-preview.73 | 172 | 3/31/2026 |
| 1.0.0-preview.72 | 312 | 3/28/2026 |
| 1.0.0-preview.71 | 70 | 3/28/2026 |
| 1.0.0-preview.70 | 1,239 | 3/26/2026 |
| 1.0.0-preview.69 | 106 | 3/24/2026 |
| 1.0.0-preview.68 | 130 | 3/24/2026 |
v.1.0.0-preview.87
- Feature: Added support for user-defined custom parameter controllers, enabling story authors to build tailored parameter editing UIs beyond the built-in controls. (PR #123 contributed by @Hecatron)
To see all the change logs, please visit the following URL.
- https://github.com/jsakamoto/BlazingStory/blob/main/RELEASE-NOTES.txt