owent

Use when: changing libatapp etcd client, lease, watch, service-discovery, topology, etcd_module lifecycle, node-selection behavior, or etcd-specific tests. Do not use when: only running generic unit tests or editing non-etcd connectors.

Use when: writing libatapp modules, connectors, endpoint management, connection handles, message routing, suspend_stop logic, or multi-node tests.

Use when: designing, writing, reviewing, or running libatapp unit tests, filtering private-framework cases, testing multi-app/synthetic-time behavior, selecting etcd integration tests, or diagnosing Windows test startup/PATH.

Use when: initializing, auditing, or optimizing repository AI guidance, including AGENTS.md/CLAUDE.md bridges, Agent Skills, trigger descriptions, progressive disclosure, source tracking, or cross-tool compatibility. Do not use when: only implementing code…

Use when: writing or reviewing C++, public headers, template function visibility, exported API ABI, ATFW_UTIL_SYMBOL_VISIBLE, or ATFW_UTIL_FORCEINLINE.

Use when: configuring or building libatapp with CMake, editing or reviewing CMake generation/dependency rules, changing shared/static builds, or adjusting build type options.

Use when: editing libatapp enable_expression config fields, environment-variable expansion syntax, YAML/INI/env loading, or atapp_conf.proto config metadata.

Use when: working on libatbus protocol transport, ECDH handshakes, cipher/compression negotiation, message framing, access token auth, connection_context, or crypto-related tests.

Use when: designing, writing, reviewing, or running libatbus unit tests, filtering private-framework cases, testing topology/channel behavior, or diagnosing Windows test startup/PATH.

Use when: initializing, auditing, or optimizing repository AI guidance, including AGENTS.md/CLAUDE.md bridges, Agent Skills, trigger descriptions, progressive disclosure, source tracking, or cross-tool compatibility. Do not use when: only implementing code…

Use when: writing or reviewing C++, public headers, template function visibility, exported API ABI, ATFW_UTIL_SYMBOL_VISIBLE, or ATFW_UTIL_FORCEINLINE.

Use when: configuring or building libatbus with CMake, editing or reviewing CMake generation/dependency rules, changing shared/static builds, or adjusting bus ID/build type options.

Use when: designing, writing, reviewing, or running atframe_utils private-framework unit tests, filtering cases, or diagnosing Windows test startup/PATH.

Use when: initializing, auditing, or optimizing repository AI guidance, including AGENTS.md/CLAUDE.md bridges, Agent Skills, trigger descriptions, progressive disclosure, source tracking, or cross-tool compatibility. Do not use when: only implementing code…

Use when: diagnosing or fixing a defect, test/build/runtime failure, or planning and implementing a nontrivial feature, behavior change, cross-module refactor, public API/ABI, data model/migration, security, or deployment change. Do not use when: only making…

Use when: writing or reviewing C++, public headers, template function visibility, exported API ABI, ATFW_UTIL_SYMBOL_VISIBLE, or ATFW_UTIL_FORCEINLINE.

Use when: configuring or building atframe_utils with CMake, editing or reviewing CMake generation/dependency rules, enabling samples/tests/tools, or selecting crypto/unwind backends.

Use when: running hiredis-happ tests, adding regression coverage, debugging CTest failures, or planning Redis/raw/cluster integration tests.

Use when: updating AGENTS.md, CLAUDE.md, compatibility shims, Agent Skills, source indexes, or cross-tool AI configuration for hiredis-happ.

Use when: configuring, building, packaging, installing, or debugging CMake/CI/dependency/runtime-path issues in hiredis-happ.

Use when: reviewing or modifying hiredis-happ C++ code, Redis/hiredis async lifecycle, cluster routing, command ownership, tests, or CI risk.

Use when: designing, reviewing, registering, or running cmake-toolset CTest cases, configure/module regressions, generated-tool checks, or dependency link/startup smoke tests. For port upgrades use port-upgrade; for CI failure diagnosis use ci-fix-port.

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

Use when: diagnosing or fixing cmake-toolset CI failures after port upgrades, patch-apply errors, changed upstream build options, or GitHub Actions job failures.

Use when: upgrading cmake-toolset ports, checking upstream releases, resolving dependency pins, validating patches, handling cross-compiling host tools, or reviewing CI impact.

Use this skill when reviewing or changing an existing Hugo technical post, including requests to 润色、完善、扩写、改写、校对、事实核查 or prepare it for publication by fixing structure, examples, front matter, links, or visuals. Do not use when the intended result is a new…

Use this skill when drafting a new technical blog post in this Hugo repository, including requests to 写文章、起草博客、把笔记或调研整理成新稿, or create a new post's title, summary, front matter, structure, examples, and visuals. Do not use for localized edits, polishing, or…

Use when: maintaining this repo's self-hosted Excalidraw GitHub Pages deployment, weekly upstream build workflow, gh-pages snapshot branch, excalidraw.x-ha.com domain docs, or custom font patching. Do not use when: the task is a generic code edit unrelated to…