← All creators

nhhthong

User

A project-memory kit for .claude/: layout, ledgers, and the loop that keeps them true.

8 indexed · 0 Featured · 2 stars · avg score 78
Prolific

Categories

Indexed Skills (8)

Web & Frontend Listed

setup

Set up Clio in the current project — scaffold .claude/ (CLAUDE.md, CONTEXT.md, requirements.md, the two ledgers, stack rules), then fill them by asking the user, never guessing. Run once per repository, before any other clio:* skill.

2 Updated yesterday
nhhthong
Data & Documents Listed

update

After a spec file changes, work out what the change means for code already written — which task/decision docs it invalidates, whether it is safe to implement yet — record each delta in .claude/clio/debt.jsonl, and move the requirements.md row marker when the decision itself changed. Run when a requirement, contract or ticket changes.

2 Updated yesterday
nhhthong
Web & Frontend Listed

context

Load the spec, prior task docs and open debt for an area before working in it. Use before any non-trivial task, and when the user asks "where are we", "what's next", "why is X like this" or "any history on this".

2 Updated yesterday
nhhthong
Web & Frontend Listed

ingest

Turn a long requirement document (contract, PRD, spec.md, ticket export) into the distilled spec layer — one .claude/docs/specs/memory/*.md per domain area plus the requirements.md row table — marking every undecided point ⚠️ instead of inventing an answer. Run once after /clio:setup when the project has a requirement source, and again whenever a new source arrives.

2 Updated yesterday
nhhthong
Data & Documents Listed

ask

Explain Clio — what each clio:* command does, when to run it, which files it reads and writes, and how the three ledgers work. Use when the user asks "what does /clio:memo do", "how does Clio work", "which clio command should I run", or anything about the Clio plugin.

2 Updated yesterday
nhhthong
Testing & QA Listed

plan

Break a spec area into the smallest independently testable tasks — one observable behaviour each, with the exact test that proves it — written to .claude/docs/plans/<area>.md in dependency order. Run after /clio:ingest, whenever the user asks Clio to read a spec and plan the work, and again after /clio:update moves a row.

2 Updated yesterday
nhhthong
Data & Documents Listed

debt

Show what is still owed — open records in .claude/clio/debt.jsonl split into actionable-now vs blocked, optionally filtered by domain, requirement row number or keyword. Read-only.

2 Updated yesterday
nhhthong
Code & Development Listed

memo

Record a finished piece of work — update (or create) its task doc in .claude/docs/tasks/, append the run to .claude/clio/index.jsonl, log what is still owed to .claude/clio/debt.jsonl, and propose a CONTEXT.md diff or an ADR when warranted. Run after finishing a feature, fix or refactor.

2 Updated yesterday
nhhthong

Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.