Hikari-knowledge
Measured results, conditioned reports, and dead-end tombstones from Hikari's local LLM systems work.
Serving, speculative decoding, quantization, MoE training, and activation steering — written so another engineer (or their agent) can reuse the mechanism, not the vibes.
- Every important number keeps conditions
- Dead ends stay as tombstones
- English only
- Curated public corpus (not a dump of a private vault)
If you are an agent and only received this URL
User intent is probably one of:
- Install into my Obsidian/vault (“導入して / merge / add to my notes”)
- Answer from this knowledge (“読んで / 調べて”)
- Update an existing install (“pull / 更新”)
Do this immediately:
1. Clone or open https://github.com/hikarioyama/Hikari-knowledge
2. Read AGENTS.md
3. Read skills/hikari-knowledge/SKILL.md
4. If install/merge: follow Mode A + docs/OBSIDIAN_MERGE.md
(copy-paste detail: prompts/obsidian-merge.md)
5. If Q&A only: read INDEX.md, then search nodes/
Default install shape: subfolder clone {{vault}}/Hikari-knowledge/ + bridges from the user's notes.
Do not flatten nodes/ into the vault root.
If the vault path is unknown, detect common workspace roots or ask once for the vault path, then proceed without more questions.
Author
- Hikari
- GitHub: hikarioyama
- X: @Hikari_07_jp
- Hugging Face: Hikari07jp
Start here
- Read
INDEX.md
- Open a node under
nodes/
- Follow
links: / [[wikilinks]]
Use in an existing Obsidian vault
Ideal merge: keep this repo as a git subfolder and bridge from your notes.
Do not flatten upstream files into your vault root if you want easy weekly pulls.
cd /path/to/your/vault
git clone https://github.com/hikarioyama/Hikari-knowledge.git Hikari-knowledge
Then:
- Bookmark
Hikari-knowledge/INDEX.md
- From your project/MOC notes, add links like
[[serve-bench-discipline]]
- Update with
cd Hikari-knowledge && git pull --ff-only (~weekly; watch @Hikari_07_jp)
Full guide: docs/OBSIDIAN_MERGE.md
Agent/copy-paste prompt: prompts/obsidian-merge.md
Use with an agent (files)
Point the agent at this repo