pi-ensemble

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.

CI/CD pipelines, Docker, Kubernetes, and infrastructure as code. Use when configuring deployment pipelines, containerization, or cloud infrastructure. Do NOT use for fixing application code - delegate code issues to appropriate specialists.

Evaluate the maturity, completeness, and quality of a software project's technical documentation. Use whenever the user wants to assess, audit, review, score, or grade project docs — analyzing a repo, reviewing uploaded documents, or identifying gaps. Trigger on "evaluate our docs", "documentation audit", "how good is our documentation", "doc maturity", "documentation review", "what's missing from our docs", "documentation assessment", "rate our documentation", "doc quality check", "documentation completeness", or any request to systematically judge how well a project is documented. Also trigger when a user asks what documentation they should have, what's missing, or how to improve their docs — these are gap analyses this skill handles. Works for any project size. Accepts repos, file trees, uploaded docs, or verbal descriptions.

Go development following Go proverbs, stdlib-first philosophy, and idiomatic patterns. Use when working on Go projects requiring simplicity, clarity, and performance. Emphasizes table-driven tests and small interfaces. Do NOT use for other programming languages.

PostgreSQL database architecture, optimization, and AWS Aurora expertise. Use when working on schema design, query optimization, migrations, or database operations. Do NOT use for application code or other databases.

Python development with TDD using pytest, type checking with mypy, and linting with ruff/black. Use when working on Python projects requiring test-driven development, quality gates, or Python code review. Do NOT use for other programming languages.

Ruby on Rails development following Rails Way conventions, RSpec testing, and security best practices. Use when working on Rails projects requiring MVC architecture, Active Record, or API development. Do NOT use for other programming languages or frameworks.

Expo and React Native mobile development for iOS and Android. Use when building cross-platform mobile apps, native modules, or mobile-specific UI. Covers React Navigation, platform-specific code, and mobile performance. Do NOT use for React web development.

React/TypeScript web development with modern patterns, component architecture, and testing discipline. Use when building React web applications, hooks, state management, or frontend components. Do NOT use for React Native mobile development or other frameworks.

Rust systems programming with zero-cost abstractions, memory safety, and TDD. Use when working on Rust projects requiring performance, safety, or systems-level code. Emphasizes std-first philosophy and minimal dependencies. Do NOT use for other programming languages.

POSIX-compliant shell scripting and automation with focus on portability, robustness, and Unix philosophy. Use when writing bash scripts, automation, or CLI tools. Includes BATS testing patterns. Do NOT use for other programming languages.

Conduct a structured, adaptive technical interview to extract system continuity information from an engineer or architect — covering architecture, infrastructure, deployments, monitoring, backups, restore processes, security, and team responsibilities. Use this skill whenever the user wants to document their system for continuity, handover, or disaster recovery purposes, or asks to be "interviewed" about their system, stack, or infrastructure. Also trigger when someone says "document our system", "runbook interview", "continuity doc", "capture how our system works", "help me document our architecture", "interview me about our setup", or anything about producing continuity/handover/DR documentation from a conversation. The skill should always be used when the goal is to *extract* technical knowledge from the human through dialogue rather than have Claude produce content unprompted.

Write, improve, and maintain technical documentation for software projects — from READMEs and API references to architecture docs, runbooks, ADRs, and security policies. Use this skill whenever the user wants to create or improve any form of technical documentation. Trigger on "write a README", "document this", "create docs for", "write documentation", "technical writing", "help me document", "write a runbook", "create an ADR", "architecture doc", "API documentation", "deployment guide", "onboarding guide", "CONTRIBUTING.md", "SECURITY.md", "CHANGELOG", "configuration reference", or any request to produce, edit, or restructure documentation for a software project. Also trigger when the user describes a system, codebase, or workflow and wants it turned into clear documentation, or when they paste rough notes and want them shaped into proper docs. Even if the user doesn't say "documentation" explicitly — if they want to explain something technical in written form for an audience, this skill applies.