tauri-config-ipc
Skill1.2k starsChanged 5 months agoMITView on GitHub
Extend MarkerOn settings, persisted config, or Tauri IPC commands. Use when adding config fields, new invoke commands, settings UI toggles, or changing config.json shape.
Trending
Quiet since July.thin dataabout the whole repository
Who's talking about ifer47/markeron
- ScoopInstaller/Scoop“[Bug] checkver github mode not working for url ending with #/dl.7z”GitHub · Jul 14, 2026
- ScoopInstaller/Extras“[Request]: MarkerOn”GitHub · Jul 14, 2026
The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/commit-conventions.mdcCursor rule
- .cursor/rules/cross-platform-ui-styles.mdcCursor rule
- .cursor/rules/i18n.mdcCursor rule
- .cursor/rules/node-toolchain.mdcCursor rule
- .cursor/rules/release-workflow.mdcCursor rule
- cross-platform-tauri-uiSkill
- grill-meSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Always add #[serde(default)] (or default = "fn") on new fields so old config.json files deserialize.
- Very specific: line 75
If the overlay must react live, ensure save_general emits config-changed (already does).
- Very specific: line 86
Call from Vue: invoke('your_fn', { arg: value }) — args use camelCase in JS, match command param names
- Distinctive: line 116
Never break backward compatibility: new fields need serde defaults.
- Very specific: line 117
Keep TS AppConfig in sync with Rust AppConfig / nested structs.
- Very specific: line 118
Do not add invoke commands without registering in generate_handler!
- Very specific: line 119
Prefer extending save_general over one-command-per-toggle unless logic is distinct (like save_locale).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tauri Config & IPC (MarkerOn)
Architecture
config.json (disk, camelCase JSON)
↔ config.rs (Rust structs, serde rename)
↔ commands.rs (#[tauri::command])
↔ lib.rs (generate_handler! registration)
↔ src/types/app.d.ts (TypeScript types)
↔ Vue (invoke get_config / save_*)Config path: app config dir → config.json (config::config_path), or {exe_dir}/data/config.json when a markeron.portable marker file is next to the executable.
Naming convention
| Layer | Convention | Example |
| JSON / TS / Vue | camelCase | enableDragging, toggleDrawing |
| Rust field | snake_case + #[serde(rename = "...")] | enable_dragging ↔ enableDragging |
Always add #[serde(default)] (or default = "fn") on new fields so old config.json files deserialize.
Checklist: add a general setting
Example: new boolean fooBar in settings.
1. Rust — src-tauri/src/config.rs
// In GeneralConfig:
#[serde(default, rename = "fooBar")]
pub foo_bar: bool,
// In Default for GeneralConfig:
foo_bar: false,
// In normalized() if value needs clamping/validation2. TypeScript — src/types/app.d.ts
general: {
// ...
fooBar: boolean
}3. Command — usually no change
General settings use existing save_general (commands.rs). It saves GeneralConfig, emits config-changed, persists to disk.
New top-level config section → new struct + new save_* command.
4. Frontend UI
- Settings window:
GeneralTab.vueorSettingsView.vue - Pattern: optimistic
emit('update:…')→get_config→ mutatecfg.general→invoke('save_general', { general: cfg.general }) - Overlay runtime:
DrawingOverlay.vueloads config on mount and listens:
await listen<AppConfig>('config-changed', (event) => { /* apply */ })If the overlay must react live, ensure save_general emits config-changed (already does).
5. Tests
- Rust: add/update tests in
config.rs#[cfg(test)]module (defaults, normalization, serde round-trip). - Frontend: only if new behavior in composables.
Checklist: add a new IPC command
- Implement in
src-tauri/src/commands.rs(orclipboard.rsetc.) with#[tauri::command] - Register in
lib.rs→generate_handler![..., commands::your_fn] - Call from Vue:
invoke('your_fn', { arg: value })— args use camelCase in JS, match command param names - Return
AppResult<T>for errors surfaced to UI
Existing commands:
| Command | Purpose |
get_config | Read full AppConfig |
save_shortcuts | Global hotkeys; rolls back on invalid/register failure |
save_general | General settings + config-changed event |
save_locale | Persist locale + Rust i18n + tray + window title |
exit_drawing | Leave annotation mode |
open_url | Allowed URLs only (GitHub, Microsoft Store) |
copy_screen / copy_whiteboard | Clipboard |
Checklist: add / change shortcuts
Shortcuts are not in GeneralConfig — they live in Shortcuts struct.
Touch:
config.rs—Shortcuts,default_shortcuts()(macOS usesCommand+, othersCtrl+)commands.rs—save_shortcutsvalidationshortcuts.rs— register handlers + unit testsSettingsView.vue— capture UIsrc/types/app.d.ts—shortcutskeysREADME.md+README_zh.md— shortcut tables
Agent rules
- Never break backward compatibility: new fields need serde defaults.
- Keep TS
AppConfigin sync with RustAppConfig/ nested structs. - Do not add invoke commands without registering in
generate_handler!. - Prefer extending
save_generalover one-command-per-toggle unless logic is distinct (likesave_locale).
Related
- Locale strings:
.cursor/rules/i18n.mdc - Platform window behavior:
src-tauri/src/lib.rs,macos.rs,win32.rs
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

