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.
Instructions for randomm/pi-ensemble, covering agent guidelines for pi-ensemble, 1. 🚨 pre-push quality gates (blocking), 2. type-check, lint, and smoke-test (extension/), live smoke tests are not in the pre-push set and 2. two change paths (read first before editing).
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.
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…
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…
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"…
Vipune is a CLI semantic memory store with project scoping, hybrid search, and typed memories — the authoritative persistent memory layer for every pi-ensemble session.