菜单
Use when adding or updating emulator-backed tests, APDU trace fixtures, fake reader contexts, or command tests that should avoid real hardware. Helps align new tests with the repository's existing emulator and trace patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when changing adapters, adapter runtime resolution, vendor-specific token behavior, capability reporting, initialization/reset flows, or built-in adapter registration. Helps keep vendor logic in the right package and aligned with emulator-backed tests.
Use when working on cmd/piv or internal/cli/app, especially for commands, flags, formatting, JSON output, trace routing, config handling, or destructive-operation safety. Helps keep stdout/stderr contracts stable and preserves dry-run and confirmation behavior.
Use when the task involves preparing, reviewing, staging, or committing repository changes. Helps keep commits focused, avoids bundling unrelated diffs, and keeps commit messages consistent with the repository's expected style.
| name | emulator-test-authoring |
| description | Use when adding or updating emulator-backed tests, APDU trace fixtures, fake reader contexts, or command tests that should avoid real hardware. Helps align new tests with the repository's existing emulator and trace patterns. |
Use this skill when a change needs tests but should not rely on a physical reader or token.
iso7816/ or piv/ for protocol behavioremulator/.internal/testtrace/.cmd/piv/cli_test.go.adapters/safenet/initialization_test.go.