randomm

pi-ensemble's bundled vipune memory doctrine — full reference for using the vipune CLI as a project-scoped semantic memory store. Encodes the 5-type memory taxonomy (fact, preference, procedure, guard, observation), the active/candidate status split as the long-term/short-term mechanism, freshness verification before acting on recalled memories, conflict handling via --supersedes, periodic consolidation reflexes, the hard prohibition on storing secrets, and pi-ensemble-specific framing (multi-agent shared DB, session autosave). Use this skill whenever starting a project task; before delegating work; before making architectural decisions; after task completion; when the user mentions "remember"/"recall"/"vipune"; when surprised by codebase reality vs recalled memory; or when encountering a known-feeling pitfall. Project-scoped, semantic-search-driven; designed to make every session smarter than the last without context bloat or memory rot.

REST and GraphQL API design with versioning, authentication, and OpenAPI documentation. Use when designing API endpoints, request/response formats, or API architecture. Do NOT use for implementation in specific languages.

Architecture code review lens for assessing design quality, coupling, cohesion, and structural integrity.

Error-handling and resilience code review lens for catching silent failures, unbounded I/O, swallowed exceptions, and partial-failure pitfalls.

Performance code review lens for identifying bottlenecks, inefficient algorithms, and resource waste.

Security-focused code review lens for identifying vulnerabilities, injection risks, auth flaws, and unsafe patterns.

Simplicity code review lens for identifying unnecessary complexity, dead code, and maintainability issues.

Type-safety code review lens for catching type errors, schema mismatches, and unsafe type coercions.

Bootstrap project-specific oo output patterns for a repository. Scans the repo to detect its toolchain and creates .oo/patterns/*.toml files that compress verbose command output for AI agents. Use when you want to set up oo patterns for a project, teach oo about a repo's commands, or create .oo/patterns.

Mandates the use of the vipune memory CLI as the primary persistent memory store for software development agents. Search vipune at the start of any task to discover prior decisions, conventions, pitfalls, and validated patterns. Save new findings as typed memories—code conventions, architectural decisions, failed approaches, quality-gate gotchas, and ADR-lite rationale—at task boundaries. Covers issue/PR linkage, experiment tracking, pre-flight gotcha checks, dev-loop phase mapping, lightweight ADR capture, the 5-type memory taxonomy (fact/preference/procedure/guard/observation), active/candidate split, mandatory freshness verification, contradiction handling via --supersedes, and the hard prohibition on storing secrets.