Orchestrate production-ready LiveStacks solutions from PRDs, working PRDs, or minimal business-first inputs such as industry, pain point, category, Oracle feature mapping, deployment target, and implementation notes. Use when Codex needs to turn a business or industry pain point, PRD, workbook-style brief, or solution concept into a secure, portable, Oracle Database-first LiveStacks application bundle with architecture, data design, ORDS-mediated APIs, container artifacts, implementation guidance, documentation, and customer rebuild instructions.
Create clean distributable ZIP archives from files or project directories while excluding macOS metadata, Python caches, VCS metadata, editor temporary files, and other generated artifacts. Use when packaging a project, source tree, handoff bundle, deployment archive, or any ZIP that must not contain .DS_Store, __MACOSX, __pycache__, resource forks, or similar clutter.
Disable Polly retrieval and memory writes for the current local Git clone while preserving its canonical repository and quiet-mode settings. Use when a repository should no longer participate in Polly or was enabled unintentionally.
Enable Polly for the current clone or fork and configure its canonical upstream GitHub repository using local git config. Use when opting a repository into Polly or correcting fork-to-upstream memory resolution.
Diagnose Polly enrollment, repository enablement, secure token availability, canonical repository resolution, and server health. Use when Polly context is missing or setup needs verification.
Save a durable developer-only project memory in Polly without tying it to the current Codex session or sharing it with collaborators. Use when the user wants a personal decision, hypothesis, reminder, preference, or continuity note available in future sessions for the same canonical repository.
Pause, resume, or inspect Polly memory writes for the current git repository while keeping context retrieval active. Use before test prompts, experiments, sensitive exploratory work, or any session whose checkpoints and manual memories must not be stored.
Share a coding decision, constraint, assumption, blocker, or progress note with collaborators through Polly. Use when the user explicitly wants collaborators to receive a durable piece of project context.