aevatarAI

Govern canon changes: require explicit reason/impact/retroactive policy, and produce an actionable propagation plan.

Turn "AI draft -> author edits" diffs into structured deviation items, an author-intent prompt, and a concrete propagation plan.

Help the author write narrative unit tests (rules/constraints) and interpret failures with a concrete fix roadmap.

Simulate multiple reader personas to score a chapter (爽点/困惑/信息负荷) and propose actionable alternatives.

Manage rewrite branches: when to branch, how to compare, and how to merge back with minimal chaos.

Maintain a structured Setup/Payoff ledger (promises, debts, payoffs) and generate a payoff roadmap.

Define what the Story Control Panel shows, how to compute signals, and how the author should act on alerts.

Aggregate a writing session into a readable log + a reusable author-intent prompt.

Pull and inspect Aevatar mainnet/prod Kubernetes logs with the scoped kubeconfig at ~/Code/aelf-shared-k8s-prod.yaml. Use when debugging Aevatar online logs, Lark bot replies, NyxID relay callbacks, AgentRun/ConversationGAgent turns, Ornn skill publish behavior, approval hallucinations, webhook delivery, or console-backend stdout in prod.

Use when product meaning is unclear or drifting across UI, copy, API contracts, data models, tests, docs, or user expectations. Trigger for questions like "why is this here?", "this feels unlike n8n/Linear/GitHub", "this field name is misleading", "optional control is too prominent", "backend concept leaked into UI", "should this be a trigger/input/prompt/setting?", "make the product semantics self-evolve", or any task that should update implementation plus tests/docs so the corrected product semantics persist across future changes.

Unattended three-phase refactor loop (analyze → implement → verify) driven by codex CLI in isolated git worktrees. Use when user wants fully autonomous parallel refactoring against CLAUDE.md violations, with /loop dynamic wakeups and per-cluster worktree merges.

Orchestrate a fully automated multi-agent frontend refactoring workflow to audit frontend code, detect backend contract impact, fix, review, browser-QA, and PR frontend architecture and design issues against CLAUDE.md and docs/canon frontend rules.

Inject NyxID auth session into the test browser's localStorage via refresh token. Solves automated browser testing login for apps using OAuth2/PKCE with localStorage-based session storage.

Write and edit Aevatar workflow YAML definitions. Covers canonical schema, closed_world_mode, formal roles config (provider/model/limits/event modules/routes/connectors), all 26 primitives, branching, retry/error policies, and validation constraints.

Unattended sequential implementation loop driven by codex CLI + Claude subagent reviewer. Walks every issue under a GitHub milestone in order; each issue gets implement (codex) → stacked PR → review (subagent) → fix (codex if needed) until reviewer passes; then advances to the next issue. Use when user wants the full milestone landed as a stacked PR train with /loop dynamic wakeups.

Use when auditing architecture compliance against CLAUDE.md, checking for drift before milestones, validating architecture drift after large merges, or running periodic architecture checks. Triggers on "架构审计", "architecture audit", "architecture drift".