productivity▌

Detect code smells, security vulnerabilities, anomalies, and trends across codebases using regex, AST analysis, and statistical methods. \n \n Identifies problematic patterns including long functions, duplicate code, magic numbers, empty catch blocks, and TODO/FIXME markers \n Scans for security risks such as SQL injection, hard-coded secrets, dangerous function usage (eval, innerHTML), and credential exposure patterns \n Performs statistical anomaly detection using Z-score and IQR methods to fl

Structured daily standup facilitation with three formats: 3-question updates, board-walking, and async remote standups. \n \n Provides three standup formats (3 Questions, Walking the Board, and Slack-based async) adaptable to in-person, hybrid, and fully remote teams \n Includes time-boxed 15-minute structure with built-in templates for tracking yesterday's work, today's plans, and blockers \n Enforces core constraints: consistent daily timing, full team participation, and separation of problem-

Persistent memory and context management for AI agents across sessions, repositories, and dates. \n \n Load project background before work, search prior conclusions during tasks, and store decisions afterward using slash commands ( /opencontext-context , /opencontext-search , /opencontext-iterate ) \n Supports keyword, vector, and hybrid search modes with optional semantic indexing via embeddings API \n Integrates with multi-agent workflows (Claude, Gemini, Codex) through MCP tools for knowledge

Imperative and declarative routing patterns for Flutter screen transitions and deep linking. \n \n Covers both Navigator (imperative, stack-based) and Router (declarative, URL-synchronized) approaches with guidance on when to use each \n Supports deep linking on iOS, Android, and Web; includes data passing via constructors, route arguments, and return values \n Implements nested navigation for multi-step flows (e.g., setup wizards) with independent sub-navigators and back-button interception \n

Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns. \n \n Provides three file ownership models (by directory, module, or layer) and enforces the cardinal rule: one owner per file to prevent merge conflicts \n Defines interface contracts as read-only coordination points between implementers, allowing shared boundaries without direct file conflicts \n Covers two integration patterns (vertical slice for independent features, ho

Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with structured task descriptions. \n \n Provides four decomposition strategies: by architectural layer, functional component, cross-cutting concern, or file ownership to parallelize work effectively \n Includes dependency graph patterns (independent, sequential, diamond) with principles for minimizing chain depth and identifying critical paths \n Offers task description template covering objective, owned files, r

Structured messaging protocols for coordinating agent teams through direct messages, broadcasts, plan approvals, and graceful shutdown. \n \n Three message types: message for direct teammate coordination, broadcast for critical shared-resource updates, and shutdown_request for graceful termination with approval workflows \n Plan approval workflow where teammates in plan mode submit proposals to a lead for review and feedback before execution \n Shutdown protocol with rejection handling: lead sen

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Command-line interface for deploying, managing, and developing Vercel projects locally and in CI/CD pipelines. \n \n Requires explicit project linking via vercel link (single project) or vercel link --repo (monorepos); commands must run from the directory containing .vercel/ folder \n Core workflows: vercel dev for local development, vercel deploy for preview deployments, vercel --prod for production \n Supports environment variables, domains, DNS, blob storage, integrations, Node.js backends, m

Prep meetings by pulling Notion context, tailoring agendas/pre-reads, and enriching with Codex research.