- C# 85%
- HTML 12.5%
- CSS 2.3%
- Dockerfile 0.1%
|
|
||
|---|---|---|
| .config | ||
| .github | ||
| deploy | ||
| docs | ||
| external | ||
| src | ||
| tests | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| Directory.Build.props | ||
| Directory.Packages.props | ||
| Kagura.slnx | ||
| README.md | ||
Kagura
An AI-powered visual novel creation suite — a self-hosted content-management and creation system for multiple VN projects, built around a deeply connected knowledge base (characters, lore, locations, chapters, timelines) that grounds user–AI collaboration: from AI-assisted sprite and background generation, through scene-by-scene writing, to previewing the result — all in one Blazor app.
At a glance
- Self-hosted, single user on a home server, behind a shared-secret access gate.
- ASP.NET Core + Blazor Server on .NET 10, structured as a modular monolith in clean ports-and-adapters.
- One SQLite knowledge graph (records are nodes, relationships are links) plus on-disk assets; every change is auto-applied, journaled, and reversible (undo + Wikipedia-style per-document history).
- Image generation via NovelAI (Diffusion 5, with 4.5 for reference-driven generations); LLM collaboration via OpenRouter; a bundled booru tag database for spelling-safe tag authoring.
- A built-in C#-native player for previewing; shipped as a Docker image.
- An AI collaborator that reads and edits the same project data you do, through the same validated use cases — every change reversible.
Architecture in brief
- Ports & adapters —
Server/BlazorAdapter/UI/UseCases/Domain/Infrastructure/Kernel(ADR 0003), organized as bounded-context modules over one graph DB (ADR 0017). - Knowledge graph —
Entrynodes + genericLinkedges + backlink navigation (ADR 0019). - Reversible by design — a persistent change journal, soft delete, and per-document revision history (ADR 0020, 0022).
- Fluxor UI state with per-circuit event bridges + cross-session sync (ADR 0016); Material Symbols icons + CSS-variable design tokens (ADR 0023).
- DB-native scenes (ordered steps) and a C#-native player engine (ADR 0007, 0008).
Built on / informed by
Reused as dependencies:
- NovelAI.ImageGen — NovelAI Diffusion 4.5 / 5 client
- OpenRouter.Net — LLM client + agent loop
- booru_tag_db_dart — the danbooru tag database (bundled, read-only reference data)
Designed fresh, informed by (references, not dependencies): VNovelPlayer (scene format + player design), NovelAI.VisualNovelCreator (generation pipeline), novel-crafter / NovelArtist (knowledge base + agent tooling), story-forge (timeline / routes / biography).
Documentation
Planning is complete and captured here — a good reading order:
- Requirements (SRS) — actors, epics, and a checkable requirement list; detailed per-feature stories under docs/stories/
- Project plan — goal, MVP scope, the phased roadmap, risks
- Architecture overview — system shape and runtime flows
- Architecture Decision Records — the accepted decisions (0001–0024; 0012 withdrawn)
- Design system — tokens, theming, icons, component inventory
Status
Planning complete — 23 accepted ADRs, a full SRS with ~20 feature stories, an architecture overview, a design system, and a phased plan. The repository is documentation only; implementation begins with Phase 0 (scaffold) in the project plan.