System Understanding
Developmentsystem-understandingSystem Understanding is an Agent Skill for development published in the rapidaai/voice-ai repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Build a code-grounded implementation plan before coding. Use to trace packet flow, factory boundaries, provider config loading, and exact file-level change scope for a requested integration.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/rapidaai/voice-ai/blob/HEAD/.claude/skills/system-understanding/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/system-understanding, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
System Understanding Skill
Mission
Produce an executable, minimal-risk implementation plan from real code paths before changing feature logic.
Scope
Planning and analysis only. Do not implement production changes in this skill run.
Mandatory discovery sequence
- Identify feature lane and factory switch:
- telephony:
api/assistant-api/internal/channel/telephony/telephony.go - stt/tts:
api/assistant-api/internal/transformer/transformer.go - vad:
api/assistant-api/internal/vad/vad.go - eos:
api/assistant-api/internal/end_of_speech/end_of_speech.go - llm:
api/integration-api/internal/caller/caller.go
- Trace runtime packet flow in dispatcher:
api/assistant-api/internal/adapters/internal/dispatch.go
- Verify UI/provider config load behavior:
ui/src/providers/provider.development.jsonui/src/providers/provider.production.jsonui/src/providers/config-loader.ts
- Produce exact edit scope:
- provider folder
- factory file
- optional shared contract files
- tests to update
Output requirements
- Requested integration type and inferred defaults.
- Transport/signal mode chosen and why.
- Exact file list to edit (and explicit out-of-scope file list).
- Test and validation command plan.
- Risks and rollback path.
Validation commands
rg -n "GetTelephony|GetSpeechToTextTransformer|GetTextToSpeechTransformer|GetEndOfSpeech|GetVAD" apirg -n "GetLargeLanguageCaller|GetEmbeddingCaller|GetRerankingCaller|GetVerifier" api/integration-apirg -n "OnPacket\(|dispatch\(" api/assistant-api/internal/adapters/internal/dispatch.go