Menu
Wire a new pipecat FrameProcessor into the ORBIS pipeline — class authoring through pipeline insertion
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Full clean rebuild of ORBIS — wipes web/dist, dist-sdist, src-tauri bundle, staged sidecar binary, pyapp env cache, WKWebView state, sidecar.log, and stale unix sockets, then rebuilds frontend → sdist → pyapp sidecar → tauri bundle in the correct order, and launches with stderr captured. Use when voice doesn't work, the orb shows weird state, "Load failed" appears anywhere in the UI, or anything feels off after a code change.
Step-by-step workflow for adding a new processing component to the ORBIS agent pipeline
Step-by-step workflow for integrating a new stage into the ORBIS audio/processing pipeline
Integrate a new ML component (classifier, reranker, etc.) into an existing agent pipeline by reading the codebase, identifying hook points, implementing the module, and wiring it in.
Commit pending changes, bump the patch version tag, and publish a beta release
Scaffold and plan a new marketing site — branding audit, stack selection, hero design, and deployment config
| name | wire-frame-processor |
| description | Wire a new pipecat FrameProcessor into the ORBIS pipeline — class authoring through pipeline insertion |
Use this when adding a new processing stage to the ORBIS pipecat pipeline: writing the FrameProcessor subclass, wiring it into app.py, and positioning it correctly between existing pipeline components.
FrameProcessor subclass to the appropriate module under agent/ (e.g. agent/intent.py). Include __init__, process_frame, and any supporting methods.FrameProcessor, uses await self.push_frame(frame) for pass-through, and handles only the Frame types it cares about.app.py imports — Add the new class to the import block at the top of app.py.run_bot — Instantiate the processor and any associated handlers/callbacks inside the run_bot function, near the other component constructions.Pipeline([...]) list at the correct position relative to existing components (e.g. between audio_tags and user_agg for pre-LLM interception).IntentRouterProcessor between audio_tags and user_agg to intercept TranscriptionFrame before the LLM aggregator sees it.FrameProcessor between user_agg and llm to filter or transform LLMMessagesFrame before generation.