Kami Reader

by kkenny0
Screenshot of the Kami Reader Obsidian theme
5
4
3
2
1
New Theme

Description

This theme supports Dark Mode
This theme supports Light Mode

README file from

Github

Kami Reader — Obsidian Theme

English | 简体中文

Last updated: 2026-06-20

Inspired by tw93/kami. Not affiliated with or endorsed by tw93. All visual design tokens trace to the original kami project (MIT); this repo is an Obsidian-side adaptation.

An Obsidian theme inspired by tw93/kami. Translates kami's print-grade typographic system — warm parchment surface, ink-blue accent, serif-led hierarchy, warm-gray neutrals — onto the Obsidian editor.

Status: Published on the Obsidian Theme Gallery. Public repo: https://github.com/KKenny0/obsidian-kami · Latest release: 0.1.2


Visual Language

Aligned to kami v1.1.0.

Token Light Dark Role
Parchment / Deep Dark #f5f4ed #141413 Primary note background
Ivory / Dark Ivory #faf9f5 #1a1917 Sidebars, surfaces
Warm Sand #e8e6dc #353330 Borders, dividers
Dark Surface / Warm Ivory #30302e #e8e3d2 Body text
Ink Blue / Ink Light #1B365D #2D5A8A Accent: headings, links, selection, CTA
Olive #504e49 #b4b09e Quote / caption text
Warm Highlight #f3e3a8 #5a4a1f ==mark== highlight
Tag Tint #E4ECF5 #E4ECF5 Tag background (solid, never rgba)

All neutrals carry a yellow-brown warm undertone (no cold blue-grays) in both light and dark variants. Ink blue is used sparingly — the print-design ≤5% rule is relaxed for the editor context but the intent holds: accent only, never chrome.


Screenshots

Reading View (Light) Editing View (Light)
Light Reading Light Editing
Reading View (Dark) Callout Severity Ladder
Dark Reading Callouts
Featured Card Embed Command Palette Settings Panel
Embed Command Palette Settings

Screenshots not captured yet — see screenshots/SCREENSHOTS.md for the shot list. Once captured with the exact filenames, this section renders automatically.


Style Settings

This theme ships a Style Settings schema exposing the highest-leverage variables for user tuning — no CSS editing required.

Dual schema mode (both kept in sync):

  • Snippet mode (current install path on macOS Sequoia): schema embedded as /* @settings ... */ YAML comment at the top of theme.css. Style Settings does not scan .obsidian/snippets/ for standalone JSON files, so the schema must live inside the CSS.
  • Theme mode (after Phase 2c Gallery install): schema in root data-theme.json. Used when Obsidian loads the theme from .obsidian/themes/kami-reader/.

After installing the Style Settings community plugin, go to Settings → Style Settings → Kami Reader to adjust:

  • Body font family — swap LXGW WenKai Screen (kaiti) for Source Han Serif (songti) if kaiti fatigues
  • Body line-height — 1.55 default, range 1.3–1.9 (Live Preview needs Cmd+E toggle after change; Reading View updates instantly)
  • Note max width — 700px default
  • Accent color (light + dark) — single accent swap, instantly re-themes
  • Primary background (light + dark) — tune parchment warmth

The schema intentionally exposes only 5 variables. Everything else stays fixed in theme.css to honor kami's restraint principle — over-configurability would dilute the design system.


Typography

--font-text-theme: "Charter", "Georgia",
                   "LXGW WenKai Screen", "LXGW WenKai",
                   "Source Han Serif SC", "Noto Serif CJK SC",
                   "Songti SC", "STSong", "SimSun", serif;
  • Charter — English serif. macOS-native (/System/Library/Fonts/Charter.ttc), no install needed. Falls back to Georgia on other platforms. This is the font kami itself uses for English.
  • LXGW WenKai Screen — CJK 楷书, OFL 1.1. Screen variant optimized for low-DPI displays. Closes the gap with kami's original 仓耳今楷02 (which is commercial-restricted).
  • JetBrains Mono — Code, OFL 1.1.
  • Inter — UI / interface, OFL 1.1.

Optional font install

Only LXGW WenKai Screen needs manual install. Without it, CJK falls back to Songti SC (macOS) / SimSun (Windows) — readable but loses the kaiti warmth.


Installation

  1. Obsidian → Settings → Appearance → click Manage next to Themes
  2. Browse → search "Kami Reader" → InstallUse
  3. (Optional) Install the Style Settings community plugin for the 5 tunable variables (font, line-height, width, accent, background)

Phase 2b verified Obsidian's own Gallery downloader writes files with Obsidian provenance — App Store users install cleanly with no macOS Sequoia sandbox issue.

Manual install / developer iteration (macOS Sequoia sandbox workaround)

⚠️ Why this section exists. Mac App Store Obsidian runs in a sandbox. macOS Sequoia 15+ tags every file created by cp from Terminal with com.apple.provenance. The sandbox then refuses to load those files as theme resources — Obsidian silently skips the theme folder. This matters for developers iterating on theme.css who copy files into their own vault's .obsidian/themes/ directory. End users installing via Gallery (the path above) are not affected.

The workaround for local iteration: ship kami as a CSS snippet instead of a theme, and inject it via Obsidian's own Vault API from the DevTools console. Files written by app.vault carry Obsidian provenance and load normally.

One-time setup
  1. Confirm Appearance → Themes is set to Default (no other theme should be active; another theme's body.<name>-theme class will out-spec kami's body.theme-light selector).
  2. From this directory, generate the inject script:
    ./sync.sh
    
  3. Open the generated inject-kami-snippet.js, Cmd+A select all, Cmd+C copy.
  4. In Obsidian: Cmd+Option+I → Console tab → Cmd+V paste → Enter. You should see ✓ kami.css created (... chars).
  5. Settings → Appearance → scroll to CSS Snippets → enable kami.
Iterating on the CSS
# Edit theme.css, then:
./sync.sh
# Re-copy inject-kami-snippet.js contents → paste into Obsidian Console.
# Then toggle the kami snippet off → on to force reload.

Hot-reload of modified snippets is not automatic — Obsidian reads snippet files at startup. After re-injecting via app.vault.modify, toggle the snippet off and on in Settings → Appearance → CSS Snippets to pull the new content.


Coverage

Phase 1 targets full visual coverage:

  • ✅ Base color tokens (60+ variables, both light and dark palettes)
  • Dark variant — Deep Dark #141413 + Ink Light #2D5A8A, preserving the same yellow-brown undertone and single-accent restraint as light mode.
  • ✅ Reading View: headings, body, lists (em-dash markers), tables, blockquote (2pt ink-blue rail + olive text, no bg), code, frontmatter, embeds
  • ✅ Editing View (CodeMirror 6): syntax tokens, cursor, selection, active line, formatting marks
  • ✅ UI chrome: titlebar, tabs, ribbon, file explorer, status bar, command palette, settings panel, modals, menus, toggles, checkboxes, scrollbars
  • ✅ Reduced-motion preference respected

Not covered (deferred):

  • PDF Export stylesheet (kami is print-native; this is a Phase 1.5 candidate)
  • Style Settings plugin schema (Phase 2 — lets users tune color temperature, font, contrast)
  • Plugin-specific overrides (Dataview, Templater, Excalidraw) — verify as encountered

Phase 1 dogfooding confirmed the visual transfer holds. Phase 2 is complete; the theme is live at https://community.obsidian.md/themes/kami-reader.

Phase 2a — Polish & docs (✅ done in this commit)

  • Style Settings schema (data-theme.json) — 5 high-leverage variables exposed (font stack, line-height, note width, accent color, primary bg).
  • Screenshot checklist (screenshots/SCREENSHOTS.md) — 7-shot list embedded in both READMEs. Filenames reserved; capture to render.
  • LXGW WenKai Screen woff2 bundling — deferred. Needs fonttools / cn-font-split toolchain + OFL license-file handling; not worth the risk in a single Phase 2a session. README documents manual font install path instead.

The single load-bearing assumption of Phase 2: does Obsidian's own Theme Gallery downloader write files with Obsidian provenance, bypassing the macOS Sequoia sandbox wall?

Verified 2026-06-20: installed Shade Sanctuary from Browse Themes in a fresh vault, ran xattr -l on the downloaded theme.css — output was empty (no com.apple.provenance). Obsidian's own downloader writes Obsidian-provenance files; App Store users install cleanly from Gallery. Plan A is safe.

Live at https://community.obsidian.md/themes/kami-reader. Auto-synced to obsidianmd/obsidian-releases/community-css-themes.json via the hourly mirror workflow.

Plan A (preferred, in progress): submit via community.obsidian.md developer form.

The official "Submit your theme" doc on docs.obsidian.md is stale — it still says PR to obsidian-releases, but that repo closed PRs and switched to an hourly mirror workflow. The actual source of truth is community.obsidian.md, a Next.js app that mirrors to obsidianmd/obsidian-releases hourly via the mirror-community-json.yml workflow. Recent obsidian-releases commits are all "chore: Mirror community plugins and themes" by Obsidian Bot — no human PRs.

Submission steps:

  1. Sign in to community.obsidian.md with an obsidian.md account.
  2. Open the developer submission form (in account menu).
  3. Submit:
    name: Kami Reader
    repo: KKenny0/obsidian-kami
    screenshot: screenshots/light-reading.png
    modes: light, dark
    
  4. Ensure a GitHub release tagged exactly with manifest.json version (no v prefix). Obsidian pulls theme files from that release's tag.
  5. Obsidian team reviews (1-2 weeks typical), then auto-syncs to obsidian-releases.

Phase 2b confirmed Obsidian's Gallery downloader writes files without com.apple.provenance — App Store users install cleanly with no sandbox issue.

Plan B (fallback if Plan A rejects): ship as a community plugin. onload() injects CSS via app.customCss. Plugin loading mechanism is separate from theme loading and likely unaffected by the sandbox wall. Higher upfront engineering cost but unblocks App Store users if Plan A fails.

Phase 2c submission lint history

community.obsidian.md runs automated lint on submission. Each warning required its own fix and a new release tag:

Release Lint warning Fix
0.1.0 No release matches manifest version Created GitHub release tagged 0.1.0 (no v prefix)
0.1.1 Repository has no recognized license Restored pure MIT LICENSE (GitHub licensee strictly matches MIT template; attribution appended after standard text broke the match)
0.1.1 css-scrollbar partially supported by Obsidian 1.4.5 Dropped CSS Scrollbars spec properties (scrollbar-width, scrollbar-color); kept webkit ::-webkit-scrollbar vendor extension
0.1.2 Avoid !important at theme.css:788, 1105, 1106 CodeMirror selection uses 0,3,0 specificity compound selector; reduced-motion uses explicit selector list instead of * !important

Design Decisions

  1. Forked from Obsidian Default, not Minimal. Minimal carries its own design language; mixing parchment into it produces visual dissonance. Minimal also uses body.minimal-theme class selectors (specificity 0,1,1) that beat kami's old :root (0,0,1). Default has no such class.
  2. Variables on body.theme-light / body.theme-dark, not :root. Obsidian's built-in app.css defines base vars under .theme-light / .theme-dark (specificity 0,1,0). :root (0,0,1) loses the cascade; body.theme-light (0,1,1) wins.
  3. Charter, not Newsreader. kami v1.1.0 specifies Charter for English; it's also macOS-native, removing a font-install step.
  4. Tag backgrounds use solid #E4ECF5, never rgba. kami explicitly bans rgba tag backgrounds (WeasyPrint double-rect bug in PDF export).
  5. Ring + whisper shadows, never hard drop shadows. kami spec; hard drop shadows look heavy in print and on screen.
  6. Em-dash list markers, not bullets. kami Dash List — "短横线代替圆点, 更书卷气".
  7. Blockquote: 2pt ink-blue rail + olive text, no background, no italic. Restraint over decoration.
  8. LXGW WenKai Screen over Source Han Serif. Kami's original (仓耳今楷02) is a kaiti; Source Han Serif is a print songti. The kaiti keeps the calligraphic warmth that defines kami's character.
  9. No synthetic bold weights. Kami forbids fake bold; headings use 500/600 actual weights only.
  10. Shipped as snippet, not theme, in Phase 1. Workaround for macOS Sequoia sandbox; see Installation section.

Fragile Assumptions to Verify in Phase 1

  1. Parchment background is comfortable for long editing sessions on screen. If after a week you instinctively switch back to a cooler light or a dark theme, the transfer fails. Pivot option: "Kami-Lite" — keep ink-blue accent, swap parchment for ivory #faf9f5 or near-white.
  2. Kaiti is legible at body size on screen during active writing. Screen variant of LXGW WenKai specifically addresses this, but real verification requires a week of dogfooding. If kaiti fatigues, fall back to Source Han Serif via the CSS variable.

File Layout

kami-obsidian/
├── manifest.json              # Theme metadata (name, version, minAppVersion)
├── theme.css                  # Source of truth for all kami styles + inline @settings YAML
├── data-theme.json            # Style Settings schema for theme-folder mode (Phase 2c)
├── sync.sh                    # Regenerates inject-kami-snippet.js from theme.css
├── inject-kami-snippet.js     # Generated by sync.sh — paste into Obsidian Console
├── screenshots/               # 7-shot set (see SCREENSHOTS.md)
├── LICENSE                    # MIT (pure text so GitHub licensee detects SPDX:MIT)
├── README.md                  # English docs (this file)
└── README.zh-CN.md            # 简体中文文档

inject-kami-snippet.js is a build artifact, not source. Regenerate via ./sync.sh after any theme.css change.


Releases

Tag Notes
0.1.0 Phase 1: visual system + dark variant + atomic components + Style Settings
0.1.1 Compat: drop CSS Scrollbars spec for Obsidian 1.4.5; restore pure MIT LICENSE
0.1.2 Lint compliance: remove !important from CodeMirror selection + reduced-motion

Release tags match manifest.json version exactly (no v prefix) — Obsidian pulls theme files from the GitHub release tagged with the manifest version.


License

MIT — see LICENSE.

Visual design system source: tw93/kami (MIT). This theme is a derivative adaptation; all design token values trace to the original kami project.

Fonts referenced but not bundled:


Credits

  • Visual system & design tokens: tw93/kami — MIT
  • Fonts: Charter (OFL, macOS-native), LXGW WenKai (OFL), JetBrains Mono (OFL), Inter (OFL)