RepoPilot

moeru-ai / airi

Search moeru-ai/airi

GitHub

Code

How moeru-ai/airi is laid out, and where to start for common changes.

There is no import map for this report yet.

Where to start reading

  1. Repository root
  2. Repository root
  3. Likely public API
  4. Likely public API
  5. Likely start-up file
  6. Likely start-up file
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add a new game plugin

  • Create plugin package in packages/plugin-sdk-{gamename}/src with gamelet and kits directories
  • Define plugin APIs extending the base plugin protocol by creating activation plan and channel definitions
  • Integrate game logic as agents using tool cards to expose character actions
  • Register game renderer in stage scenarios and wire WebSocket communication via plugin channels

Add a new character skill/tool

  • Define tool capability in packages/agents/src/tool-card/index.ts with input/output schema
  • Implement tool handler in core-agent runtime and register with agent hooks
  • Add tool invocation logic to LLM prompt generation to surface tool to agent decision-making
  • Test tool with chat-completions protocol including multi-turn tool calling

Add a new voice/TTS provider

  • Create provider configuration in packages/provider-inference/src/providers/cloud with validation schema
  • Implement TTS processing in audio pipeline by extending tts-chunker processor
  • Wire provider into audio output rendering with format encoding support
  • Add provider UI settings in stage-pages experimental features and test server configuration

Add a new localization language

  • Register speech transformers for language-specific notation in packages/speech-transformer-{type}/src/locales/{lang}.test.ts
  • Add language fallback chain in i18n fallback.ts and test locale resolution

Change the public API

Trace runtime behavior

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

  • Files marked “likely” are guessed from their names.

Code quality and hotspots

Largest source files

  • Branch points55 per file on average
  • Code issues1 error, 12 warnings
  • Largest file1,580 lines
  • Hotspot load1 high-risk file

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions36 workflows
  • Tests881 test filesJest/Vitest · 0.36 test files per source file (file count, not coverage)
  • Dependency updatesNo config detected

Test folders: apps/stage-tamagotchi-kirie/src-web/src/renderer/host-context · apps/stage-tamagotchi-kirie/src-web/src/renderer/components/stage-islands/controls-island · apps/stage-tamagotchi-kirie/src-web/src/renderer/composables

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.