Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Removing shared state before locking it v1.0.0

Use this resource to eliminate concurrent writes to shared state

New

  • 470 downloads
  • 198 likes
  • 229 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install remove-shared-state-before-locking

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent checks whether the actors truly need the same mutable object. If they do, it enforces serialization through a structure (lock, sequential phases, exclusive owner), since instructions alone do not coordinate writes.

Mostly picked by

Updated November 2, 2026

Card for the “Removing shared state before locking it” skill

Details

Generates with
Your agent's model
Licence
MIT

Similar resources

View all

What you get

  • SKILL.md: steps to find shared mutable state
  • SKILL.md: structural serialization mechanisms to choose from

Good fit for

  • Two agents write to the same configuration file
  • Parallel jobs update the same cache key

Not for

    Tags

    • concurrency
    • shared-state
    • lock
    • design

    About

    You say

    “Two agents write to the same tracking file: split the files before adding a lock.”

    Card for the “Removing shared state before locking it” skill

    Skill published by backnotprop under the MIT license, delivered in its original version.

    Show more

    How to use it

    1. Install the skill in your agent's skills folder
    2. Ask your agent to eliminate concurrent writes to shared state
    3. Review and adjust the result

    Content preview

    Files

    • LICENSE1.1 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • SKILL.md1.5 KB

    Origin and licence

    Listed unmodified

    Author
    backnotprop
    Source
    github.com/backnotprop/pstack/tree/23707a30f9cd2f12edef61f2506e2222e30b35aa/skills/principle-separate-before-serializing-shared-state
    Licence
    MIT

    Notice

    « principle-separate-before-serializing-shared-state » (backnotprop, MIT) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.