When should I use explicit identity patterns?

You should use these patterns whenever you are spawning child processes, using IDs as database query keys, or passing state through a long-running pipeline.

Why avoid 'latest' session queries?

Querying for the 'most recent' session is a race condition. If two processes start nearly simultaneously, the wrong context could be retrieved by the second process.

How does this skill help with observability?

It enforces strict separation between session IDs, root span IDs, and turn span IDs, allowing tools like Braintrust to accurately map every action to the correct trace.

What are async boundaries?

Async boundaries occur when code waits for a task (await) or spawns a new process. In these moments, the 'current' state might change before execution finishes, leading to errors.

Explicit Identity Management

Name: Explicit Identity Management
Author: scooter-lacroix

byscooter-lacroix

분석 및 모니터링

Enforces unique identifier usage across process and asynchronous boundaries to eliminate race conditions and ensure data integrity.

소개

The Explicit Identity skill provides Claude with specialized architectural guidance to prevent common state-related bugs in complex software systems. By mandating the use of explicit UUIDs and session identifiers instead of relying on fragile 'latest' or 'current' references, it ensures that logs, traces, and state transitions are accurately attributed across execution contexts. This pattern is essential for developers working with distributed systems, multi-process architectures, or advanced observability tools where precise correlation between disparate tasks is critical for reliability.

주요 기능

Eliminates race conditions by banning 'latest' state references
Distinguishes between session, root span, and turn span identifiers
Enforces the use of full UUIDs for precise data correlation
0 GitHub stars
Mandates explicit session ID passing across process boundaries
Standardizes state file storage for reliable later correlation

사용 사례

Managing concurrent developer sessions without data leakage or overlap
Debugging complex asynchronous pipelines with reliable audit trails
Implementing distributed tracing in microservices or multi-process applications

소개

주요 기능

Eliminates race conditions by banning 'latest' state references
Distinguishes between session, root span, and turn span identifiers
Enforces the use of full UUIDs for precise data correlation
0 GitHub stars
Mandates explicit session ID passing across process boundaries
Standardizes state file storage for reliable later correlation

사용 사례

Managing concurrent developer sessions without data leakage or overlap
Debugging complex asynchronous pipelines with reliable audit trails
Implementing distributed tracing in microservices or multi-process applications