メニュー
Protect Amy's Echo account-versus-profile identity boundaries. Use when working on auth, settings, profile switching, uploads, training sync, or API flows where session/token and profileId can diverge.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Apply Amy's Echo Amy-first delivery workflow for implementation and review tasks. Use when changing code, tests, or docs in this repository. Enforce discovery, planning, Amy-impact validation, and mandatory verification before merge.
Execute Amy's Echo model training workflows end-to-end with reproducible evidence. Use when changing trainer code, training metadata contracts, model artifact handling, few-shot evaluation, or release-readiness checks for training outputs.
Build and harden Amy's Echo backend APIs using Express 5 and Zod contracts. Use when adding or modifying server routes, middleware, request validation, auth/profile checks, error handling, and response-shape guarantees.
Implement and debug MediaPipe Tasks Vision gesture recognition in Amy's Echo webapp. Use when changing webcam capture, landmark extraction, gesture recognizer setup, model loading, runtime confidence logic, or detection diagnostics tied to MediaPipe behavior.
Diagnose and improve Amy's Echo web sign-language ML detection quality. Use when working on MediaPipe landmarks, MLP inference thresholds, confidence/margin behavior, detector telemetry, fixture diagnostics, or profile-aware recognition regressions.
Run Amy's Echo testing and quality gates with clear evidence reporting. Use when preparing a change for commit/PR, diagnosing regressions, or deciding the minimum safe check set for touched webapp, server, or integration areas.
| name | identity-boundary-guard |
| description | Protect Amy's Echo account-versus-profile identity boundaries. Use when working on auth, settings, profile switching, uploads, training sync, or API flows where session/token and profileId can diverge. |
Prevent auth/profile mixups that cause silent data corruption or false success states.
For every touched module, classify it as:
profileId), personalization, training scope.If a flow needs both, validate both explicitly.
profileId is missing/stale.401, 4xx, network failure).Use the referenced architecture map before adding new auth/profile logic.
Cover at least these cases when relevant:
references/identity-map.md — High-level identity architecture and component relationships; consult for design and integration decisions.references/identity-test-checklist.md — Step-by-step regression checklist; use during testing and release validation.