atframework

Use when: generating deployment configs, rendering per-instance scripts, editing Helm values, analyzing install/**/*.tpl Go templates, yaml.tpl/sh.tpl/bat.tpl files, or using atdtool deployment workflows.

Use when: auditing or optimizing AI agent prompts, bridge files, skills, SKILL.md metadata, and cross-tool compatibility.

Use when: writing or reviewing C++/CMake/Markdown code, applying project engineering conventions, checking cpplint, clang-format, cmake-format, cmake-lint, markdownlint, clang-tidy, protobuf, RPC, generated-code, service/component CMake rules.

Use when: working on atgateway v2 protocol code, ECDH handshakes, encryption, compression, reconnection, FlatBuffers schema, or gateway unit tests.

Use when: configuring or building atsf4g-co with CMake, resolving build errors, or adjusting Windows/MSVC/vcpkg and Unix/Linux/macOS build options.

Use when: editing enable_expression config fields, environment-variable expansion syntax, YAML deployment values, or atapp config templates.

Use when: running or writing unit tests, discovering/filtering private test-framework cases, or fixing Windows DLL/PATH test startup issues.

Use when: building the Robot binary, running the connection test case, checking where robot logs are written, asking to run task all from the repository root, or asking how to start the built robot from build/install/bin.

Use when: deploying AICR to a remote server, repairing managed issue state after deployment, updating deployed config.yaml, syncing source files, or troubleshooting podman build/run issues; do not use for local development or CI pipeline changes.

Use when: changing or auditing output channel configuration, no-problems behavior, output templates, target links, author mentions, or dispatch contracts; do not use for agent runtime or VCS fetch internals.

Use when: comparing roadmap/docs with implementation, auditing or retiring completed task plans/specs, identifying gaps, fixing issues, or adding missing tests; do not use for unrelated feature work.

Use when: validating repository-wide build, lint, test, markdown, Docker, docs, CI, root tooling, or workspace topology changes; do not use for isolated package-only feature edits.

Use when: auditing, creating, or optimizing AI agent prompts, bridge files, skills, SKILL.md metadata, and cross-tool compatibility; do not use for ordinary feature edits that leave AI-facing assets unchanged.

Use when: implementing or auditing agent CLI runtime materialization, LLM config translation, MCP tool mapping, prompt/instruction layering, and skills merging; do not use for ordinary review logic or output rendering changes.

Use when: planning, coding, refactoring, reviewing, or editing prompts for non-trivial tasks where assumptions, scope control, simplicity, or verification matter; do not use for obvious one-line fixes.

Use when: adding, removing, or reshaping pnpm workspace packages, package manifests, project references, or shared build wiring; do not use for package-local feature edits that leave the scaffold unchanged.

Review or implement user-visible CLI command changes in this repository. Use when changing subcommands, flags, help text, defaults, output paths, or command behavior.

Synchronize documentation after code changes in this repository. Use when implementation changes affect commands, values precedence, template runtime behavior, project structure docs, or examples.

Review or change Helm/chart values precedence in this repository. Use when working on global.yaml, chart-name yaml, modules, runtime values, template overrides, or --set merge behavior.

Implement or refactor production code in this Go repository. Use when adding features, fixing bugs, changing CLI behavior, or modifying files under cmd/, cli/, internal/, pkg/, or logarchive/.

Write, repair, or stabilize tests in this Go repository. Use when adding unit tests, reproducing bugs with tests, fixing failing or flaky tests, updating testdata, or improving coverage for changed behavior.

libatbus-go module structure, concurrency model, C++ parity patterns, and design decisions. Use when: understanding module organization, debugging concurrency issues, making design decisions, reviewing C++/Go differences, adding new features.

Build libatbus-go, generate protobuf code, and manage dependencies. Use when: building the module, running code generation, resolving import errors, updating proto definitions, checking prerequisites.

ECDH key exchange, encryption/compression algorithms, message framing, and access token authentication in libatbus-go. Use when: working with ConnectionContext, handshake flow, cipher negotiation, pack/unpack, cross-language crypto vectors, access_data signatures.

Run and write unit tests for libatbus-go. Use when: running tests, writing new test cases, debugging test failures, working with cross-language test vectors, testing concurrency safety, verifying C++ parity.

Use when drafting, reviewing, or extending DSA, DSC, DSM pseudocode in this repo. Triggers: 伪代码, pseudocode, DS lifecycle, scheduler, session routing, protocol, SDK, atframework component, x-server style, design-to-implementation. Read the design guide, implementation plan, pseudocode roadmap, and atframework/x-server baseline before editing.

etcd_module Actor/CSP 并发模型迁移。用于：继续实现 Phase 1-5 中任一阶段；评审迁移方案；排查 SetLease I/O 阻塞、kaCtx 生命周期、TopologyActor 快照等并发问题；验证 Actor 设计决策（mailbox 容量、背压策略、atomic.Pointer 用法）。关键词：Actor, CSP, mailbox, RegistrationScheduler, LeaseActor, TopologyActor, 单写者, 并发重构, 服务发现, etcd_module。