Skip to main content

system-understanding

Build a code-grounded implementation plan before coding. Use to trace packet flow, factory boundaries, provider config loading, and exact file-level scope for requested integrations.

Ir para a instalação

Informações da origem

Repositório
rapidaai/voice-ai
Última atividade na origem
23 de agosto de 2026 às 07:23
Idioma detectado do SKILL.md
inglês
Estrelas
729
Forks
120

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
6 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
name
system-understanding
description
Build a code-grounded implementation plan before coding. Use to trace packet flow, factory boundaries, provider config loading, and exact file-level scope for requested integrations.
# System Understanding Skill ## Mission Produce an implementation plan from real factory/packet/config paths before writing feature code. ## Scope Planning and analysis only. Do not implement production changes in this skill. ## Discovery sequence 1. Identify factory lane: - 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` 2. Trace packet flow: - `api/assistant-api/internal/adapters/internal/dispatch.go` 3. Verify UI config loading: - `ui/src/providers/provider.development.json` - `ui/src/providers/provider.production.json` - `ui/src/providers/config-loader.ts` 4. Produce exact edit boundaries: - provider folder - factory file - optional contract files - tests to update ## Output requirements - inferred integration type and defaults - chosen transport/signal strategy - exact in-scope file list and explicit out-of-scope files - test + validation command plan - risk + rollback path ## Governed lifecycle - This planning skill owns only the `understand` and `plan` phases from `DEVELOPMENT_PROCESS.md`. - The plan must declare acceptance criteria, non-goals, allowed paths, explicit owners, principles, required tests and commands, risks, and rollback. - A separate `plan-challenger` must review the output; this skill may not approve its own plan or perform implementation. - The coordinator attests the approved plan before any implementation worker starts. ## Validation commands - `rg -n "GetTelephony|GetSpeechToTextTransformer|GetTextToSpeechTransformer|GetEndOfSpeech|GetVAD" api` - `rg -n "GetLargeLanguageCaller|GetEmbeddingCaller|GetRerankingCaller|GetVerifier" api/integration-api` - `rg -n "OnPacket\(|dispatch\(" api/assistant-api/internal/adapters/internal/dispatch.go` ## References - `references/checklist.md` - `references/system-map.md` - `examples/sample.md`
Ver no GitHub