kaecer68
@kaecer68
Public Skills
atlas-doc-governance
by kaecer68
文件治理守門員 — 在 AI agent 準備建立或移動 docs/ 內檔案時強制檢查歸屬規則。防止 transient content 污染永久文件目錄。觸發條件：任何涉及 docs/ 目錄的檔案建立、移動、或大量編輯，或使用者提到「文件管理」「歸檔」「spec」「manifest」。
atlas-audit-manifest-protocol
by kaecer68
"MUST use when debugging, auditing, investigating bugs, or doing code/design review follow-ups that lead to implementation. Triggers: 'why is X failing', 'trace this error', 'audit this code', 'review this and fix'. Connects root-cause investigation → invariant manifest → implementation plan → commit → PR. Prevents agents from guessing fixes, losing track of issues, and leaving unverified code in the working tree."
atlas-imac-prod-guard
by kaecer68
"[已退役 / RETIRED 2026-09-22 — iMac 已出售，本流程一律不可照做；改用 a2a-dev docs/operations/MACMINI-RECOVER.md + a2a-dev scripts/prod-guard.sh] 歷史記錄：iMac (KiMac) 上的 docker compose / docker rm / make rebuild 前置護欄（比對 container_name / image / port / password 與 docs/operations/docker-compose.prod.yml）。Triggers: iMac rebuild, docker rm atlas-*, make rebuild-all, make rebuild-atlas, docker compose up -d, PR #1695 follow-up"
atlas-monitoring-observability
by kaecer68
"Use when modifying or troubleshooting the Wave 9 observability system (5 detectors), Prometheus metric emission (PR-926 naming convention), /api/llm/health probe path, or wave9 alert rules. Triggers: Wave9Observability, wave9_runtime, atlas_db_init_failures_total, atlas_channel_health_errors_total, /api/llm/health 401, wave9_channel_individual_health, IsAuthFreePath, isPublicPath, MetricDBInitFailures, MetricChannelHealthErrors"
gitnexus-impact-analysis
by kaecer68
"Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\""
gitnexus-exploring
by kaecer68
"Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\""
gitnexus-cli
by kaecer68
"Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\""
gitnexus-debugging
by kaecer68
"Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\""
gitnexus-refactoring
by kaecer68
"Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\""
atlas-llm-provider-capability
by kaecer68
"SOP for adding a new LLM provider client or capability handler in atlas-go. Covers BaseClient embedding, ProviderImpl interface, capability constant registration, routing table updates, handler wiring, and required tests. Trigger: user asks to add a new LLM provider, capability, or routing chain entry."
atlas-experimental-feature-launch-gate
by kaecer68
Use when adding a new experimental feature that needs a launch gate, designing rollout safety, or promoting L2.x observation patterns. Reference for the canonical "5-condition hard gate" pattern established by L2.4 preflight + auto-cron.
atlas-mcp-tool-tour
by kaecer68
"Navigable guide to atlas-go's MCP tools — grouped by task domain, with entry-point tools, companion relationships, and common task combinations."
atlas-mcp-integration
by kaecer68
"Teach external AI agents how to connect to atlas-go via MCP protocol — configuration, authentication, first call, and common task patterns."
atlas-pre-change-protocol
by kaecer68
"MUST use before ANY code modification in atlas-go. Mandates overlap detection (Step 0), GitNexus blast radius for changes, GitNexus architecture check, data source tracing, and design intent verification. Triggers: any edit, refactor, fix, add, delete, or code change request. Prevents shallow patch fixes, dead code misidentification, and parallel duplicate implementations. (Read-only investigations are exempt — this skill only triggers on write-intent tasks.)"
codebase-memory — 深度圖分析與語意搜尋
by kaecer68
完整工具路由決策樹請見 docs/tools.md。
atlas-macro-narrative
by kaecer68
"Use when analyzing macro narrative events, deriving foreign capital flow probabilities, or working with the six macro dimensions. Triggers: macro analysis, narrative event detection, Taiwan stress index, causal chain analysis."
CodeGraph — 輕量快速源碼探索
by kaecer68
注意：codebase-memory 與 codegraph 在「單次源碼＋呼叫路徑查詢」有功能重疊 — 此時優先使用 codebase-memory（Hybrid LSP 型別解析更強，支援 158 語言）。
atlas-guest-mode
by kaecer68
"Canonical pattern for atlas-go's user authentication bypass in pre-commercialisation deploys. Use when touching /api/auth/, /api/user/, internal/subscription/*, frontend auth.js, or any task involving login, SSO, OAuth, tier gate, user signup, JWT, session, cookie, commercialize auth, or 'add login wall'. Prevents agents from re-implementing parallel user-auth middleware."
atlas-fubon-supervisor-invariants
by kaecer68
"Mandatory invariants (F1-F9) for modifying the fubon-proxy ProcessManager supervisor, Start pre-flight, Stop cancellation, backoff, and zombie auto-kill logic in atlas-go. Prevents orphan processes, goroutine leaks, Stop deadlocks, and EADDRINUSE backoff loops."
atlas-taiwan-leading-indicators
by kaecer68
"Use when working with the 4 core leading indicators for short-term Taiwan stock direction (1-3 day). Triggers: ForeignInvestorNet, TSMADR, NVDA, DXY, data source tracing for short-term judgment, MacroDataSnapshot field usage."
atlas-strategy-techniques
by kaecer68
"Use when working with the 5-layer investment techniques library (L1-L5), StrategyFrame design, or 12 production seeds. Triggers: new strategy techniques, layer classification, hit rate tracking, attribution, LLM annotation."
atlas-data-visibility
by kaecer68
"Use when fixing zero-value display bugs, silent channel failures, or implementing data visibility safeguards. Triggers: zero-card bug, silent fetch failure, status.data_status, ChannelErrors, FetchResult.Fallback, MacroDataSnapshot all-zero"
atlas-strategy-evolution
by kaecer68
"Use when working with the strategy evolution loop, model performance feedback, or dynamic agent adjustment. Triggers: evolution cycle, agent performance evaluation, mutation brief, weakest agent selection."
atlas-factor-change-protocol
by kaecer68
"Mandatory 8-step protocol for adding, removing, or renaming FactorType values in atlas-go. Ensures optimizer constants, weight engine maps, domain structs, pipeline score structs, and event adjustments stay synchronized."