一键导入
wire-component-into-pipeline
Step-by-step workflow for integrating a new component (classifier, reranker, etc.) into an existing app pipeline with metrics and hooks
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Step-by-step workflow for integrating a new component (classifier, reranker, etc.) into an existing app pipeline with metrics and hooks
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 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-component-into-pipeline |
| description | Step-by-step workflow for integrating a new component (classifier, reranker, etc.) into an existing app pipeline with metrics and hooks |
Use this when adding a new processing component (e.g. intent classifier, reranker, embedder) to an existing pipeline — requiring code edits across multiple files, metrics registration, and hook-in at the right execution stage.
memory/reranker.py, classifiers/intent.py)memory/facts.py search()) to call the componentapp.py, instantiate it, and insert it into the pre-LLM / pipeline path_METRICS dict (or equivalent) and add counters/histograms for the new componenton_user_turn_handler) to find exactly where to invoke the component relative to the LLM callapp.py → add intent_classified_total to _METRICSfacts.py search() after vector retrieval → add rerank_latency_seconds histogram to metrics