DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to carry your personal agent rules into every project with Operator Memory

Store your own standards and knowledge in a user partition that applies across all your repos.

Who it is forA developer who works on several projects and wants the same working rules and preferences applied by the agent in each one.

The problemCorrections and standards you teach an agent in one project are lost when you start work in another.

The outcomeYour personal rules sit in ~/.operator/user/ and load in each project, so you teach the agent once.

What you need first

  • Node.js with npm, or Bun, to install the Operator Helper
  • A supported harness installed, such as Claude Code or Codex
  • A local project repository you want the agent to document

Steps

  1. Install the Helper with npm install --global @aerovato/operator-helper.
  2. Run /operator:user-init once in a new conversation to create your global user partition.
  3. Ask the agent to record a standard you want applied everywhere, such as a coding convention you correct often.
  4. Open a project, run /operator:project-init, and start a new conversation to confirm the rule is consulted.
  5. Check the Markdown file in ~/.operator/user/ and edit or delete it if the rule changes.

Prompt for your agent

Using the Operator Memory repo (https://github.com/aerovato/operator-memory), set up the user partition and record this standard: <standard-text>. Expected output: a Markdown file under ~/.operator/user/ containing that standard. Verify by opening a different project and checking that the agent applies it.

Caveat. The README describes user rules as a separate partition, but it does not say how strictly the agent follows them, so check behavior in a second project.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page