mirror of
https://github.com/cursor/plugins.git
synced 2026-09-14 20:00:00 +08:00
lauren
24bd6eb895
lauren tan's working style as a Cursor plugin. Bundles the poteto-mode routing skill plus the workflow skills it routes through (how, why, architect, arena, unslop, interrogate, automate-me, reflect, tdd) and the full seventeen-skill set of first principles. Ships the poteto-agent subagent that runs the same workflow end-to-end. The why skill discovers available MCPs at run time and maps each to an evidence category (source control, issue tracker, long-form docs, real-time chat, infra observability, error tracking, analytics warehouse). No third-party service integrations required. cursor-team-kit's control-cli, control-ui, and deslop are referenced as sibling-plugin dependencies for surfaces and commit cleanup; the kit works standalone otherwise. Marketplace entry registered at the root .cursor-plugin/marketplace.json.
1.6 KiB
1.6 KiB
name, description, disable-model-invocation
| name | description | disable-model-invocation |
|---|---|---|
| principle-separate-before-serializing-shared-state | Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant. | true |
Separate Before Serializing Shared State
When concurrent actors might share mutable state, first ask whether they truly need the same mutable object. If not, eliminate the sharing. When sharing is real, enforce serialization structurally: lockfiles, sequential phases, exclusive ownership. Instructions and conventions are not concurrency control.
Why: Concurrent writes to shared state create race conditions that are intermittent, hard to reproduce, and expensive to debug. Telling agents or goroutines to "take turns" does not work.
Pattern:
- Identify shared mutable state (files both read and write, branches both push to, APIs both define and consume).
- Default: eliminate the shared write target. Ask: do these actors need one canonical object, or are they publishing independent facts? Give each actor its own owned file, key, branch, or state directory, and merge only at the read/reporting boundary. Two workers writing their own
lastXfield into onestate.jsonis still shared mutation;indexer-state.json+metrics-state.jsonis not. - Only when one shared write target is a real invariant, serialize access structurally (lockfiles, sequential phases, single-writer actor, or atomic compare-and-swap). Treat "we need a lock" as a design smell to check, not as the default answer.