From supervibe
Use BEFORE starting any non-trivial task to search project memory for prior decisions, patterns, incidents, learnings, solutions matching current context. Triggers: 'поищи в памяти', 'past decisions', 'как мы делали раньше', 'project memory'.
npx claudepluginhub vtrka/supervibe --plugin supervibeThis skill is limited to using the following tools:
Retrieval policy: memory is mandatory for non-trivial planning, architecture,
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Retrieval policy: memory is mandatory for non-trivial planning, architecture,
recurring bugs, policy decisions and project-history questions. If skipped,
state the supervibe-retrieval-decision-policy reason explicitly.
Design intelligence writes only accepted, rejected, or learned decisions into existing memory categories. Use tags such as design, brand, ux, a11y, tokens, prototype, slides, collateral, and rejected. Do not create a separate design memory root.
BEFORE starting any non-trivial task — feature, bug fix, refactor, design decision. Especially BEFORE invoking supervibe:brainstorming or supervibe:writing-plans.
This skill is the library card catalog for the project's accumulated wisdom. Without consulting it, every task starts from zero — that's wasted effort across the lifetime of the project.
Follow docs/references/skill-expert-operating-standard.md: start from source of truth, preserve retrieval evidence, apply scope safety, use real producers with runtime receipts for durable delegated outputs, verify before completion claims, and keep confidence below gate when evidence is partial.
.supervibe/memory/ exists; if not, propose supervibe:add-memory is needed first.supervibe/memory/index.json (auto-generated by scripts/build-memory-index.mjs).supervibe/memory/ contains 5 categories of markdown files:
.supervibe/memory/
├── index.json # auto-generated tag→entries index
├── decisions/ # PRD decision sections lived shorter than full PRD decision section; tactical choices
│ └── <date>-<slug>.md
├── patterns/ # reusable patterns observed/established
│ └── <slug>.md
├── incidents/ # postmortem learnings (compressed)
│ └── <date>-<slug>.md
├── learnings/ # general project insights from any agent
│ └── <slug>.md
└── solutions/ # how-we-solved-X catalog
└── <slug>.md
Each entry has frontmatter:
---
id: <slug>
type: decision | pattern | incident | learning | solution
date: YYYY-MM-DD
tags: [billing, stripe, idempotency, redis-cache]
related: [other-entry-ids]
agent: <which agent created — for traceability>
confidence: <0-10 — quality of this memory entry>
---
Search strategy:
1. Tag-overlap search — match task topic tags against memory entry tags
├─ ≥3 matching entries → read top 3 by tag-overlap score
├─ 1-2 matching entries → read all matching
└─ 0 matches → fallback to grep:
2. Grep fallback — search markdown content for task keywords
├─ Found → read top 5 by relevance
└─ Not found → return "no prior memory; consider this novel territory"
3. Type filter (when applicable):
- "Have we made this decision before?" → search decisions/
- "Is there a pattern for this?" → search patterns/
- "Did we have an incident like this?" → search incidents/
- "Have we solved similar before?" → search solutions/
confidence: field — only treat as authoritative if ≥9freshness, stale, supersededBy and contradictionIds from scripts/search-memory.mjsdate: — flag if >180 days (may be stale; verify still applicable)📚 Project memory matches:
1. [decision] 2026-03-15 — billing-idempotency-via-redis-lock
Tags: billing, idempotency, redis-cache
Summary: We chose Redis SETNX for idempotency keys (5-min TTL) over DB-row-lock because billing DB write throughput was bottleneck.
Confidence: 10
Read full: .supervibe/memory/decisions/2026-03-15-billing-idempotency-via-redis-lock.md
2. [solution] 2026-04-01 — stripe-webhook-replay-protection
...
3. [pattern] reusable: queue-job-with-idempotency
...
Recommendation: <how findings apply to current task>
Returns:
supervibe:add-memory — writes new memory entries (this skill READS only)agents/_meta/memory-curator — maintains memory hygienesupervibe:brainstorming — primary consumer (reads memory before exploring)supervibe:writing-plans — secondary consumer (reads patterns before planning)