mrleo1nid/swarm-assistent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add FTS lookup for seeded Civitai Krea2 prompt examples.

Browse Source 
Index Assistent/civitai-examples.jsonl without embeddings and expose AssistentLookupExamples plus ask:examples hop for remix references.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Leonid Pershin
2026-08-23 08:15:40 +03:00
co-authored by Cursor
parent 7aadb40a11
commit e2d48b4bf9
8 changed files with 454 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Config/_base/skills/memory.md
+5 -2
View File
@@ -1,21 +1,23 @@
# Skill: memory
You have four memory tools:
You have five memory tools:
1. **Exact memory** (`## Exact memory` + live `exact` / `session_exact`) — canonical KV defaults. Always prefer Exact over RAG for numbers.
2. **About the user** (`## About the user`) — durable human preferences (global across personas + personal for this agent). Tunable weight in settings. Prefer this for taste (“no blondes”, preferred aspect, NSFW ok for this persona).
3. **Vector craft memory** (`memory_hits`) — hybrid FTS+cosine notes (LoRA tips, pitfalls, paths, cards). Shared + this persona; personal overwrites shared on the same `kind`+`key`.
4. **Tag catalog** (`lookup_tags`) — Danbooru csv (canonical name, aliases, post_count). **Not** RAG. Krea prompts stay natural prose; use this to check spelling/aliases only.
5. **Civitai examples** (`ask: examples` / `lookup_examples`) — popular Krea 2 prompts indexed with FTS (no embeddings). Use when you want a **reference** for how others phrased a scene — remix, do not copy 1:1.
## Priority
User (this turn) > About the user > `session_exact` > Exact KV > filled live fields > craft `memory_hits` > guesses. Never let a vector hit override Exact steps/CFG/aspect, About the user, or an explicit user param request.
User (this turn) > About the user > `session_exact` > Exact KV > filled live fields > craft `memory_hits` > Civitai examples > guesses. Never let a vector hit or example override Exact steps/CFG/aspect, About the user, or an explicit user param request.
## Read tools (hop, like Civitai)
- `memory_get` + `memories: [{kind,key}]` — exact craft row (personal overlay if any).
- `memory_search` + `memory_query` (optional `memory_kind`) — hybrid search when `memory_hits` are not enough.
- `lookup_tags` + `tag_query` — csv lookup. Do **not** paste tag soup into the prompt.
- `"ask": ["examples"]` + `example_query` (optional `example_rating`: pg|pg13|r|x) — FTS over seeded Civitai examples. Treat hits as style references only.
Omit the tool action on the follow-up turn once you have results.
@@ -39,4 +41,5 @@ Omit the tool action on the follow-up turn once you have results.
- Do not store the user's taste in craft `memories` — use `user_prefs` instead.
- Do not upsert trivia already in `memory_hits` or already listed under About the user.
- Do not upsert Danbooru tags — the csv catalog already has them.
- Do not upsert Civitai example rows — they live in the FTS index from `civitai-examples.jsonl`.
- `memory_forget` without `scope` only removes the personal overlay.