agentleFS
muratgurmuratgur/ordinus/.claude/skills/electron-secure-boundary/SKILL.md

electron-secure-boundary

Skill111 starsChanged 5 months agoMITView on GitHub

Maintain Ordinus Electron security boundaries. Use when changing BrowserWindow options, main/preload/renderer responsibilities, privileged OS access, filesystem/database/process usage, or anything that could expose Electron or Node capabilities to renderer code.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep Ordinus secure by preserving the separation between privileged desktop code and UI code.

    line 10
  2. Distinctive:

    Keep privileged work in Electron main process: filesystem, SQLite, child processes, provider runtimes, secrets, native dialogs, and OS …

    line 14
  3. Distinctive:

    Keep renderer as UI-only React code.

    line 15
  4. Very specific:

    Keep preload small and typed.

    line 16
  5. Very specific:

    Never expose raw ipcRenderer, electron, filesystem, process, database, or generic command execution APIs to renderer.

    line 17
  6. Very specific:

    Avoid third-party runtime imports in preload.

    line 19
  7. Distinctive:

    Add the narrowest preload method needed for renderer.

    line 25
  8. Distinctive:

    Keep validation and trust decisions in main/shared, not renderer.

    line 26
  9. Very specific:

    Run npm run typecheck, npm run lint, and npm run build.

    line 27

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Electron Secure Boundary

Objective

Keep Ordinus secure by preserving the separation between privileged desktop code and UI code.

Rules

  • Keep privileged work in Electron main process: filesystem, SQLite, child processes, provider runtimes, secrets, native dialogs, and OS integration.
  • Keep renderer as UI-only React code. Do not import or use Node APIs, Electron APIs, SQLite clients, filesystem modules, or child process modules in renderer.
  • Keep preload small and typed. Expose only purpose-built window.ordinus.* methods.
  • Never expose raw ipcRenderer, electron, filesystem, process, database, or generic command execution APIs to renderer.
  • Preserve nodeIntegration: false, contextIsolation: true, and sandbox: true unless the user explicitly asks for a security model redesign.
  • Avoid third-party runtime imports in preload. In sandboxed preload, prefer type-only imports plus ipcRenderer.invoke.

Workflow

  1. Identify which side of the boundary the change touches: main, preload, renderer, or shared contracts.
  2. Move privileged behavior to main process services or IPC handlers.
  3. Add the narrowest preload method needed for renderer.
  4. Keep validation and trust decisions in main/shared, not renderer.
  5. Run npm run typecheck, npm run lint, and npm run build.
  6. For boundary changes, smoke test npm run dev or the packaged app.

Red Flags

  • Renderer imports from electron, node:*, fs, path, child_process, better-sqlite3, or main-process modules.
  • Preload exposes general-purpose methods such as invoke(channel, payload) or runCommand(command).
  • IPC handlers trust renderer payloads without validation.
  • A UI feature requires relaxing sandbox settings before simpler IPC design has been tried.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.