ai-wikilisted

# ai-wiki — file content into the knowledge base (lightweight, default) Turns "write this up" into a correctly named, correctly linked note inside the AI-managed folder. **This command does not create topics.** It produces one note and requires at least one `[[wikilink]]` to an **existing** note. To place a note under a topic hub with reciprocal links, use `/ai-wiki-full`. > Why topics are off by default: when every paper gets its own hub, the hub organises nothing — it only gives the paper a longer name. A topic is a research direction, not a paper's subject. The test is in `references/note-specs.md` under "What qualifies as a topic". ## Where output goes **Everything this skill files lands in the AI-managed folder.** | Zone | How to treat it | |---|---| | AI-managed folder (`<AI_WIKI>/**`) | create / edit / move / rename / delete — free hand | | The user's own note folders | read and search freely; additive edits fine; **ask before** deleting, renaming, moving, or overwriting | | `.claude/rules/`, `CLAUDE.md` | static config — edit only when the user asks to change Claude's behaviour; bump `updated:`. The sole dynamic exception is `.claude/rules/active.md` | | `.obsidian/`, `.trash/` | reachable but hands-off — editing Obsidian's config can break the vault | Nothing is blocked at the permission layer, so the restraint above is judgement. A vault is usually not a git repo; a bad overwrite of a hand-written note is recoverable only from file-sync version history. Read