Agent skill

Ipc Contract Design

by muratgur in muratgur/ordinus

Design and maintain Ordinus typed IPC contracts. An agent skill from muratgur/ordinus.

MITAuto-check passedFrontend & Design

Install Ipc Contract Design

skills CLI
$ npx skills add muratgur/ordinus --skill ipc-contract-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install muratgur/ordinus ipc-contract-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/muratgur/ordinus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/ipc-contract-design .claude/skills/ipc-contract-design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ipc-contract-design
GitHub stars
112
Token cost
~509 tokens
SKILL.md length
230 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Design and maintain Ordinus typed IPC contracts. An agent skill from muratgur/ordinus.

  • Works in 7 steps: Name the user-facing capability before… → Add or update shared types and Zod… → Add the IPC channel constant. → …
  • Changing window.ordinus APIs
  • SKILL.md covers Objective, Contract Shape, Workflow and Guidelines, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ipc Contract Design is an agent skill from muratgur/ordinus. Design and maintain Ordinus typed IPC contracts. Use when adding or changing window.ordinus APIs, ipcMain handlers, ipc channel names, shared request/response types, Zod schemas, preload bridge methods, or renderer calls into main process.

Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Frontend & Design, covering Forms and validation. It works with Zod. The repository describes itself as: Your local-first command center for working with AI agents like a real team. The licence is MIT.

When your agent uses it

  • Changing window.ordinus APIs
  • IpcMain handlers
  • Ipc channel names
  • Shared request/response types

Example prompts

  • “/ipc-contract-design”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Name the user-facing capability before creating an IPC method.
  2. Add or update shared types and Zod schemas.
  3. Add the IPC channel constant.
  4. Implement the main handler and validate untrusted input.
  5. Add the narrow preload method that invokes that channel.
  6. Consume the method in renderer through window.ordinus.
  7. Run typecheck, lint, and build.

What it can do on your machine

Read from SKILL.md and the folder at commit c27f289. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ipc Contract Design loads about 509 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 230 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~509

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from muratgur/ordinus at commit c27f289, republished under its MIT licence (© muratgur). 230 words, ~509 tokens.

Download SKILL.mdSave it as .claude/skills/ipc-contract-design/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ipc-contract-design
description
Design and maintain Ordinus typed IPC contracts. Use when adding or changing window.ordinus APIs, ipcMain handlers, ipc channel names, shared request/response types, Zod schemas, preload bridge methods, or renderer calls into main process.

IPC Contract Design

Objective

Keep Ordinus IPC small, typed, explicit, and stable enough for the renderer to act as a safe UI over main-process capabilities.

Contract Shape

  • Define channel names in src/shared/ipc.ts.
  • Define shared request/response schemas and types in src/shared/contracts.ts.
  • Register handlers in main process modules, not renderer.
  • Expose renderer-facing methods through window.ordinus in preload.
  • Use feature-shaped methods such as workspace.selectFolder() instead of generic transport methods.

Workflow

  1. Name the user-facing capability before creating an IPC method.
  2. Add or update shared types and Zod schemas.
  3. Add the IPC channel constant.
  4. Implement the main handler and validate untrusted input.
  5. Add the narrow preload method that invokes that channel.
  6. Consume the method in renderer through window.ordinus.
  7. Run typecheck, lint, and build.

Guidelines

  • Keep method names domain-oriented: app.getInfo, db.getStatus, workspace.selectFolder.
  • Prefer one explicit method over a generic catch-all channel.
  • Keep renderer errors user-readable and main errors diagnostic enough to debug.
  • When IPC responses drive renderer status, empty states, or error copy, align user-visible naming with DESIGN.md.
  • Do not add IPC for future features until there is an immediate caller.
  • Do not return secrets, raw environment details, or unrestricted local paths unless the UI truly needs them.

Anti-Patterns

  • window.ordinus.invoke(channel, payload).
  • Passing raw command strings from renderer to main.
  • Duplicating response shapes separately in main and renderer.
  • Letting renderer decide privileged policy such as workspace boundaries or executable paths.

© muratgur, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .codex/skills/ipc-contract-design of muratgur/ordinus.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit c27f289

Compare with similar skills

Ipc Contract Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ipc Contract Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ipc Contract Design this skillmuratgur/ordinus112—~509Automated safety check: PassMIT
World Book Skillecho-xianyu/worldbook-skill211—~1.8kAutomated safety check: PassCustom licence
Reglevictorgarciaesgi/regle506—~840Automated safety check: PassMIT
Buzzformbuildnbuzz/buzzform101—~1.5kAutomated safety check: PassMIT
Regle Migrate Vuelidatevictorgarciaesgi/regle506—~752Automated safety check: PassMIT
Shared SchemasInsForge/InsForge13k—~628Automated safety check: PassApache-2.0

Similar skills

  • World Book Skill

    echo-xianyu/worldbook-skill

    Create and manage SillyTavern Character Cards (角色卡) and World Books (世界书).

    211 GitHub stars~1.8k tokensUpdated 4 mo ago
    Frontend & DesignAuto-check passed
  • Regle

    victorgarciaesgi/regle

    Core Regle form validation in Vue 3 — setup with useRegle, the reactive r$ object, validation properties, displaying errors, and modifiers.

    506 GitHub stars~840 tokensUpdated 10 days ago
    Frontend & DesignAuto-check passed
  • Buzzform

    buildnbuzz/buzzform

    A skill your agent uses when working with BuzzForm schema-driven forms, @buildnbuzz/form-core, @buildnbuzz/form-react, or any related APIs like defineSchema, InferType, FormProvider, useDataField…

    101 GitHub stars~1.5k tokensUpdated 4 mo ago
    Frontend & DesignAuto-check passed
  • Regle Migrate Vuelidate

    victorgarciaesgi/regle

    Migrate Vuelidate form validation to Regle. An agent skill from victorgarciaesgi/regle.

    506 GitHub stars~752 tokensUpdated 10 days ago
    Frontend & DesignAuto-check passed
  • Shared Schemas

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's shared schema package.

    13k GitHub stars~628 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • Sets the conventions for the Opik React frontend: TanStack Query for data, Zustand for shared state, one-way layer imports and a fix for Google Translate crashes.

    22k GitHub stars~1.1k tokensUpdated today
    Frontend & DesignAuto-check passed

More from muratgur/ordinus

  • Shadcn Project Workflow

    muratgur/ordinus

    Work with shadcn/ui in Ordinus. An agent skill from muratgur/ordinus.

    112 GitHub stars~859 tokensUpdated 1 mo ago
    Auto-check passed
  • Electron Secure Boundary

    muratgur/ordinus

    Maintain Ordinus Electron security boundaries. An agent skill from muratgur/ordinus.

    112 GitHub stars~523 tokensUpdated 1 mo ago
    Auto-check passed
  • Ordinus UI System

    muratgur/ordinus

    Build Ordinus renderer UI in the intended product style. An agent skill from muratgur/ordinus.

    112 GitHub stars~881 tokensUpdated 1 mo ago
    Auto-check passed
  • Provider Runtime Adapter

    muratgur/ordinus

    Design Ordinus provider runtime adapters for local AI CLIs. An agent skill from muratgur/ordinus.

    112 GitHub stars~587 tokensUpdated 1 mo ago
    Auto-check passed
  • Extend Ordinus SQLite persistence conservatively. An agent skill from muratgur/ordinus.

    112 GitHub stars~480 tokensUpdated 1 mo ago
    Auto-check passed
  • Idea Discovery

    muratgur/ordinus

    Explore a new feature, product idea, technical design, workflow change, or ADR candidate before committing to an implementation plan.

    112 GitHub stars~851 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Ipc Contract Design

What does Ipc Contract Design do?

Design and maintain Ordinus typed IPC contracts. An agent skill from muratgur/ordinus. Ipc Contract Design is an agent skill from muratgur/ordinus. Design and maintain Ordinus typed IPC contracts.

When should I use Ipc Contract Design?

Ipc Contract Design fits situations like: changing window.ordinus APIs; ipcMain handlers; ipc channel names; shared request/response types.

How do I install Ipc Contract Design in Claude Code?

Run `npx skills add muratgur/ordinus --skill ipc-contract-design -a claude-code`. Or copy the skill folder (.codex/skills/ipc-contract-design in muratgur/ordinus) into .claude/skills/ipc-contract-design in your project. Claude Code loads it when a task matches its description.

How do I install Ipc Contract Design in Codex?

Run `npx skills add muratgur/ordinus --skill ipc-contract-design -a codex`. Or copy the skill folder (.codex/skills/ipc-contract-design in muratgur/ordinus) into .agents/skills/ipc-contract-design in your project. Codex loads it when a task matches its description.

Can I use Ipc Contract Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add muratgur/ordinus --skill ipc-contract-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ipc-contract-design, .gemini/skills/ipc-contract-design, .github/skills/ipc-contract-design and .opencode/skills/ipc-contract-design in your project.

What does Ipc Contract Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Ipc Contract Design is instructions for the agent only.

Does Ipc Contract Design access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ipc Contract Design safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ipc Contract Design use?

Ipc Contract Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ipc Contract Design use?

About 509 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ipc Contract Design?

Skills that share tags, products or a category with Ipc Contract Design: World Book Skill (echo-xianyu/worldbook-skill, 211 stars), Regle (victorgarciaesgi/regle, 506 stars), Buzzform (buildnbuzz/buzzform, 101 stars) and Regle Migrate Vuelidate (victorgarciaesgi/regle, 506 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ipc Contract Design?

muratgur (a GitHub user) maintains it in muratgur/ordinus, which has 112 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 3, 2026.

Source: muratgur/ordinus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.