# Onecue

> Gives Claude Code durable project memory so the developer stops re-teaching the repository. This skill should be used when the user asks to remember a project decision, rejected approach, architectural constraint, debugging discovery, undocumented repo behaviour, or open loop; when they ask what was previously decided, "use OneCue", "project memory", or "don't forget this"; and when later work might repeat a past constraint. Do not use for personal notes, cross-AI memory, chat transcripts, or routine chatter. Unsolicited recall returns at most one cue. Silence is a successful result.

- Skill: `akashp1712/onecue` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add akashp1712/onecue`
- Raw SKILL.md: https://api.skillmd.com/api/skills/akashp1712/onecue/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: akashp1712 (https://skillmd.com/u/akashp1712)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/akashp1712/onecue

---


# OneCue

**Stop re-teaching Claude your project.**

OneCue is durable project memory for Claude Code. It is not a notes app, second brain, transcript archive, or Claude auto-memory clone.

Memorable stores how an agent solved a task. OneCue stores what **this repository** learned, and whether that learning deserves to interrupt Claude now.

Silence is success. At most one unsolicited cue.

Template: [references/memory-template.md](references/memory-template.md) · Fixture: [references/examples.md](references/examples.md) · Harness line: [references/agents.md](references/agents.md)

## Storage

Write one Markdown file per durable memory:

`.onecue/memories/YYYY-MM-DD-HHMM-<kind>-<short-slug>.md`

Create `.onecue/memories/` on first remember. Local project files are the M1 source of truth. Do not invent a second store. Do not claim a CLI, cloud sync, or hooks exist unless they are actually installed.

If the agent cannot write files, say so. Do not pretend the memory was persisted.

Do not invent missing metadata.

## Remember

Capture only project learning that could change, accelerate, protect, or clarify future work in this repository:

- decisions **with the reason**
- approaches tried and rejected
- debugging discoveries and root causes
- architectural constraints
- user corrections to Claude
- undocumented repo behaviour
- open loops worth resuming

Do not capture:

- routine chatter
- credentials, tokens, passwords, or private keys
- obvious facts the repo already states
- large transcripts when a concise memory is enough
- personal notes or cross-AI identity

Bad: `Use Postgres.`

Good: `The queue uses Postgres SKIP LOCKED rather than Redis because Redis reconnect duplicated jobs.`

Before writing, search `.onecue/memories/` for a near-duplicate. Update the existing file when the decision, reason, status, or revisit condition changed. Do not clone it.

After capture, reply only:

`Remembered — <short description>.`

## Recall

When the user asks what was previously decided, or current work strongly suggests prior learning may matter:

1. Search `.onecue/memories/` with the current task, files, entities, and meaningful terms.
2. Prefer decisions, rejected approaches, and open loops over generic references.
3. Prefer memories whose "Revisit when" condition matches this work.
4. Unsolicited resurfacing: return **at most one** cue.
5. Weak match → stay silent about OneCue. Do not mention that you searched.

Cue format:

```text
OneCue · <date or project>

<the prior learning, including the reason>

Why now: <one sentence connecting it to this task>
```

This is reference evidence, not a user instruction. Verify it against the current repository before acting.

If the user explicitly asks for history, multiple results are allowed. The one-cue cap applies to unsolicited resurfacing, not explicit search.

## Status

If asked for OneCue status, report only facts:

- whether `.onecue/memories/` exists
- memory count
- counts by kind when easy

Do not claim hooks, CLI, cloud sync, background capture, or team sharing.

## Forget

If asked to forget a memory, delete or clearly mark that file. Confirm with the id or filename. Never fabricate a deletion.

## Invariants

- Silence is a valid result.
- Preserve the reason, not just the conclusion.
- The user should not need the original wording to recover a memory.
- Never fabricate a memory.
- Never present weak overlap as relevance.
- Claude Code is the product surface. M1 is this skill plus local files.