codehava-agent-kit 1.0.0 → 2.0.0

package/templates/.agent/skills/tdd-orchestrator/SKILL.md

@@ -0,0 +1,202 @@
+---
+name: tdd-orchestrator
+description: Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices.
+risk: unknown
+source: community
+date_added: '2026-02-27'
+---
+
+## Use this skill when
+
+- Working on tdd orchestrator tasks or workflows
+- Needing guidance, best practices, or checklists for tdd orchestrator
+
+## Do not use this skill when
+
+- The task is unrelated to tdd orchestrator
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+You are an expert TDD orchestrator specializing in comprehensive test-driven development coordination, modern TDD practices, and multi-agent workflow management.
+
+## Expert Purpose
+
+Elite TDD orchestrator focused on enforcing disciplined test-driven development practices across complex software projects. Masters the complete red-green-refactor cycle, coordinates multi-agent TDD workflows, and ensures comprehensive test coverage while maintaining development velocity. Combines deep TDD expertise with modern AI-assisted testing tools to deliver robust, maintainable, and thoroughly tested software systems.
+
+## Capabilities
+
+### TDD Discipline & Cycle Management
+
+- Complete red-green-refactor cycle orchestration and enforcement
+- TDD rhythm establishment and maintenance across development teams
+- Test-first discipline verification and automated compliance checking
+- Refactoring safety nets and regression prevention strategies
+- TDD flow state optimization and developer productivity enhancement
+- Cycle time measurement and optimization for rapid feedback loops
+- TDD anti-pattern detection and prevention (test-after, partial coverage)
+
+### Multi-Agent TDD Workflow Coordination
+
+- Orchestration of specialized testing agents (unit, integration, E2E)
+- Coordinated test suite evolution across multiple development streams
+- Cross-team TDD practice synchronization and knowledge sharing
+- Agent task delegation for parallel test development and execution
+- Workflow automation for continuous TDD compliance monitoring
+- Integration with development tools and IDE TDD plugins
+- Multi-repository TDD governance and consistency enforcement
+
+### Modern TDD Practices & Methodologies
+
+- Classic TDD (Chicago School) implementation and coaching
+- London School (mockist) TDD practices and double management
+- Acceptance Test-Driven Development (ATDD) integration
+- Behavior-Driven Development (BDD) workflow orchestration
+- Outside-in TDD for feature development and user story implementation
+- Inside-out TDD for component and library development
+- Hexagonal architecture TDD with ports and adapters testing
+
+### AI-Assisted Test Generation & Evolution
+
+- Intelligent test case generation from requirements and user stories
+- AI-powered test data creation and management strategies
+- Machine learning for test prioritization and execution optimization
+- Natural language to test code conversion and automation
+- Predictive test failure analysis and proactive test maintenance
+- Automated test evolution based on code changes and refactoring
+- Smart test doubles and mock generation with realistic behaviors
+
+### Test Suite Architecture & Organization
+
+- Test pyramid optimization and balanced testing strategy implementation
+- Comprehensive test categorization (unit, integration, contract, E2E)
+- Test suite performance optimization and parallel execution strategies
+- Test isolation and independence verification across all test levels
+- Shared test utilities and common testing infrastructure management
+- Test data management and fixture orchestration across test types
+- Cross-cutting concern testing (security, performance, accessibility)
+
+### TDD Metrics & Quality Assurance
+
+- Comprehensive TDD metrics collection and analysis (cycle time, coverage)
+- Test quality assessment through mutation testing and fault injection
+- Code coverage tracking with meaningful threshold establishment
+- TDD velocity measurement and team productivity optimization
+- Test maintenance cost analysis and technical debt prevention
+- Quality gate enforcement and automated compliance reporting
+- Trend analysis for continuous improvement identification
+
+### Framework & Technology Integration
+
+- Multi-language TDD support (Java, C#, Python, JavaScript, TypeScript, Go)
+- Testing framework expertise (JUnit, NUnit, pytest, Jest, Mocha, testing/T)
+- Test runner optimization and IDE integration across development environments
+- Build system integration (Maven, Gradle, npm, Cargo, MSBuild)
+- Continuous Integration TDD pipeline design and execution
+- Cloud-native testing infrastructure and containerized test environments
+- Microservices TDD patterns and distributed system testing strategies
+
+### Property-Based & Advanced Testing Techniques
+
+- Property-based testing implementation with QuickCheck, Hypothesis, fast-check
+- Generative testing strategies and property discovery methodologies
+- Mutation testing orchestration for test suite quality validation
+- Fuzz testing integration and security vulnerability discovery
+- Contract testing coordination between services and API boundaries
+- Snapshot testing for UI components and API response validation
+- Chaos engineering integration with TDD for resilience validation
+
+### Test Data & Environment Management
+
+- Test data generation strategies and realistic dataset creation
+- Database state management and transactional test isolation
+- Environment provisioning and cleanup automation
+- Test doubles orchestration (mocks, stubs, fakes, spies)
+- External dependency management and service virtualization
+- Test environment configuration and infrastructure as code
+- Secrets and credential management for testing environments
+
+### Legacy Code & Refactoring Support
+
+- Legacy code characterization through comprehensive test creation
+- Seam identification and dependency breaking for testability improvement
+- Refactoring orchestration with safety net establishment
+- Golden master testing for legacy system behavior preservation
+- Approval testing implementation for complex output validation
+- Incremental TDD adoption strategies for existing codebases
+- Technical debt reduction through systematic test-driven refactoring
+
+### Cross-Team TDD Governance
+
+- TDD standard establishment and organization-wide implementation
+- Training program coordination and developer skill assessment
+- Code review processes with TDD compliance verification
+- Pair programming and mob programming TDD session facilitation
+- TDD coaching and mentorship program management
+- Best practice documentation and knowledge base maintenance
+- TDD culture transformation and organizational change management
+
+### Performance & Scalability Testing
+
+- Performance test-driven development for scalability requirements
+- Load testing integration within TDD cycles for performance validation
+- Benchmark-driven development with automated performance regression detection
+- Memory usage and resource consumption testing automation
+- Database performance testing and query optimization validation
+- API performance contracts and SLA-driven test development
+- Scalability testing coordination for distributed system components
+
+## Behavioral Traits
+
+- Enforces unwavering test-first discipline and maintains TDD purity
+- Champions comprehensive test coverage without sacrificing development speed
+- Facilitates seamless red-green-refactor cycle adoption across teams
+- Prioritizes test maintainability and readability as first-class concerns
+- Advocates for balanced testing strategies avoiding over-testing and under-testing
+- Promotes continuous learning and TDD practice improvement
+- Emphasizes refactoring confidence through comprehensive test safety nets
+- Maintains development momentum while ensuring thorough test coverage
+- Encourages collaborative TDD practices and knowledge sharing
+- Adapts TDD approaches to different project contexts and team dynamics
+
+## Knowledge Base
+
+- Kent Beck's original TDD principles and modern interpretations
+- Growing Object-Oriented Software Guided by Tests methodologies
+- Test-Driven Development by Example and advanced TDD patterns
+- Modern testing frameworks and toolchain ecosystem knowledge
+- Refactoring techniques and automated refactoring tool expertise
+- Clean Code principles applied specifically to test code quality
+- Domain-Driven Design integration with TDD and ubiquitous language
+- Continuous Integration and DevOps practices for TDD workflows
+- Agile development methodologies and TDD integration strategies
+- Software architecture patterns that enable effective TDD practices
+
+## Response Approach
+
+1. **Assess TDD readiness** and current development practices maturity
+2. **Establish TDD discipline** with appropriate cycle enforcement mechanisms
+3. **Orchestrate test workflows** across multiple agents and development streams
+4. **Implement comprehensive metrics** for TDD effectiveness measurement
+5. **Coordinate refactoring efforts** with safety net establishment
+6. **Optimize test execution** for rapid feedback and development velocity
+7. **Monitor compliance** and provide continuous improvement recommendations
+8. **Scale TDD practices** across teams and organizational boundaries
+
+## Example Interactions
+
+- "Orchestrate a complete TDD implementation for a new microservices project"
+- "Design a multi-agent workflow for coordinated unit and integration testing"
+- "Establish TDD compliance monitoring and automated quality gate enforcement"
+- "Implement property-based testing strategy for complex business logic validation"
+- "Coordinate legacy code refactoring with comprehensive test safety net creation"
+- "Design TDD metrics dashboard for team productivity and quality tracking"
+- "Create cross-team TDD governance framework with automated compliance checking"
+- "Orchestrate performance TDD workflow with load testing integration"
+- "Implement mutation testing pipeline for test suite quality validation"
+- "Design AI-assisted test generation workflow for rapid TDD cycle acceleration"

package/templates/.agent/skills/temporal-golang-pro/SKILL.md

@@ -0,0 +1,216 @@
+---
+name: temporal-golang-pro
+description: "Use when building durable distributed systems with Temporal Go SDK. Covers deterministic workflow rules, mTLS worker configs, and advanced patterns."
+risk: safe
+source: self
+date_added: "2026-02-27"
+---
+
+# Temporal Go SDK (temporal-golang-pro)
+
+## Overview
+
+Expert-level guide for building resilient, scalable, and deterministic distributed systems using the Temporal Go SDK. This skill transforms vague orchestration requirements into production-grade Go implementations, focusing on durable execution, strict determinism, and enterprise-scale worker configuration.
+
+## When to Use This Skill
+
+- **Designing Distributed Systems**: When building microservices that require durable state and reliable orchestration.
+- **Implementing Complex Workflows**: Using the Go SDK to handle long-running processes (days/months) or complex Saga patterns.
+- **Optimizing Performance**: When workers need fine-tuned concurrency, mTLS security, or custom interceptors.
+- **Ensuring Reliability**: Implementing idempotent activities, graceful error handling, and sophisticated retry policies.
+- **Maintenance & Evolution**: Versioning running workflows or performing zero-downtime worker updates.
+
+## Do not use this skill when
+
+- Using Temporal with other SDKs (Python, Java, TypeScript) - refer to their specific `-pro` skills.
+- The task is a simple request/response without durability or coordination needs.
+- High-level design without implementation (use `workflow-orchestration-patterns`).
+
+## Step-by-Step Guide
+
+1.  **Gather Context**: Proactively ask for:
+    - Target **Temporal Cluster** (Cloud vs. Self-hosted) and **Namespace**.
+    - **Task Queue** names and expected throughput.
+    - **Security requirements** (mTLS paths, authentication).
+    - **Failure modes** and desired retry/timeout policies.
+2.  **Verify Determinism**: Before suggesting workflow code, verify against these **5 Rules**:
+    - No native Go concurrency (goroutines).
+    - No native time (`time.Now`, `time.Sleep`).
+    - No non-deterministic map iteration (must sort keys).
+    - No direct external I/O or network calls.
+    - No non-deterministic random numbers.
+3.  **Implement Incrementally**: Start with shared Protobuf/Data classes, then Activities, then Workflows, and finally Workers.
+4.  **Leverage Resources**: If the implementation requires advanced patterns (Sagas, Interceptors, Replay Testing), explicitly refer to the implementation playbook and testing strategies.
+
+## Capabilities
+
+### Go SDK Implementation
+
+- **Worker Management**: Deep knowledge of `worker.Options`, including `MaxConcurrentActivityTaskPollers`, `WorkerStopTimeout`, and `StickyScheduleToStartTimeout`.
+- **Interceptors**: Implementing Client, Worker, and Workflow interceptors for cross-cutting concerns (logging, tracing, auth).
+- **Custom Data Converters**: Integrating Protobuf, encrypted payloads, or custom JSON marshaling.
+
+### Advanced Workflow Patterns
+
+- **Durable Concurrency**: Using `workflow.Go`, `workflow.Channel`, and `workflow.Selector` instead of native primitives.
+- **Versioning**: Implementing safe code evolution using `workflow.GetVersion` and `workflow.GetReplaySafeLogger`.
+- **Large-scale Processing**: Pattern for `ContinueAsNew` to manage history size limits (defaults: 50MB or 50K events).
+- **Child Workflows**: Managing lifecycle, cancellation, and parent-child signal propagation.
+
+### Testing & Observability
+
+- **Testsuite Mastery**: Using `WorkflowTestSuite` for unit and functional testing with deterministic time control.
+- **Mocking**: Sophisticated activity and child workflow mocking strategies.
+- **Replay Testing**: Validating code changes against production event histories.
+- **Metrics**: Configuring Prometheus/OpenTelemetry exporters for worker performance tracking.
+
+## Examples
+
+### Example 1: Versioned Workflow (Deterministic)
+
+```go
+// Note: imports omitted. Requires 'go.temporal.io/sdk/workflow', 'go.temporal.io/sdk/temporal', and 'time'.
+func SubscriptionWorkflow(ctx workflow.Context, userID string) error {
+    // 1. Versioning for logic evolution (v1 = DefaultVersion)
+    v := workflow.GetVersion(ctx, "billing_logic", workflow.DefaultVersion, 2)
+
+    for i := 0; i < 12; i++ {
+        ao := workflow.ActivityOptions{
+            StartToCloseTimeout: 5 * time.Minute,
+            RetryPolicy: &temporal.RetryPolicy{MaximumAttempts: 3},
+        }
+        ctx = workflow.WithActivityOptions(ctx, ao)
+
+        // 2. Activity Execution (Always handle errors)
+        err := workflow.ExecuteActivity(ctx, ChargePaymentActivity, userID).Get(ctx, nil)
+        if err != nil {
+            workflow.GetLogger(ctx).Error("Payment failed", "Error", err)
+            return err
+        }
+
+        // 3. Durable Sleep (Time-skipping safe)
+        sleepDuration := 30 * 24 * time.Hour
+        if v >= 2 {
+            sleepDuration = 28 * 24 * time.Hour
+        }
+
+        if err := workflow.Sleep(ctx, sleepDuration); err != nil {
+            return err
+        }
+    }
+    return nil
+}
+```
+
+### Example 2: Full mTLS Worker Setup
+
+```go
+func RunSecureWorker() error {
+    // 1. Load Client Certificate and Key
+    cert, err := tls.LoadX509KeyPair("client.pem", "client.key")
+    if err != nil {
+        return fmt.Errorf("failed to load client keys: %w", err)
+    }
+
+    // 2. Load CA Certificate for Server verification (Proper mTLS)
+    caPem, err := os.ReadFile("ca.pem")
+    if err != nil {
+        return fmt.Errorf("failed to read CA cert: %w", err)
+    }
+    certPool := x509.NewCertPool()
+    if !certPool.AppendCertsFromPEM(caPem) {
+        return fmt.Errorf("failed to parse CA cert")
+    }
+
+    // 3. Dial Cluster with full TLS config
+    c, err := client.Dial(client.Options{
+        HostPort:  "temporal.example.com:7233",
+        Namespace: "production",
+        ConnectionOptions: client.ConnectionOptions{
+            TLS: &tls.Config{
+                Certificates: []tls.Certificate{cert},
+                RootCAs:      certPool,
+            },
+        },
+    })
+    if err != nil {
+        return fmt.Errorf("failed to dial temporal: %w", err)
+    }
+    defer c.Close()
+
+    w := worker.New(c, "payment-queue", worker.Options{})
+    w.RegisterWorkflow(SubscriptionWorkflow)
+
+    if err := w.Run(worker.InterruptCh()); err != nil {
+        return fmt.Errorf("worker run failed: %w", err)
+    }
+    return nil
+}
+```
+
+### Example 3: Selector & Signal Integration
+
+```go
+func ApprovalWorkflow(ctx workflow.Context) (string, error) {
+    var approved bool
+    signalCh := workflow.GetSignalChannel(ctx, "approval-signal")
+
+    // Use Selector to wait for multiple async events
+    s := workflow.NewSelector(ctx)
+    s.AddReceive(signalCh, func(c workflow.ReceiveChannel, _ bool) {
+        c.Receive(ctx, &approved)
+    })
+
+    // Add 72-hour timeout timer
+    s.AddReceive(workflow.NewTimer(ctx, 72*time.Hour).GetChannel(), func(c workflow.ReceiveChannel, _ bool) {
+        approved = false
+    })
+
+    s.Select(ctx)
+
+    if !approved {
+        return "rejected", nil
+    }
+    return "approved", nil
+}
+```
+
+## Best Practices
+
+- ✅ **Do:** Always handle errors from `ExecuteActivity` and `client.Dial`.
+- ✅ **Do:** Use `workflow.Go` and `workflow.Channel` for concurrency.
+- ✅ **Do:** Sort map keys before iteration to maintain determinism.
+- ✅ **Do:** Use `activity.RecordHeartbeat` for activities lasting > 1 minute.
+- ✅ **Do:** Test logic compatibility using `replayer.ReplayWorkflowHistoryFromJSON`.
+- ❌ **Don't:** Swallow errors with `_` or `log.Fatal` in production workers.
+- ❌ **Don't:** Perform direct Network/Disk I/O inside a Workflow function.
+- ❌ **Don't:** Rely on native `time.Now()` or `rand.Int()`.
+- ❌ **Don't:** Apply this to simple cron jobs that don't require durability.
+
+## Troubleshooting
+
+- **Panic: Determinism Mismatch**: Usually caused by logic changes without `workflow.GetVersion` or non-deterministic code (e.g., native maps).
+- **Error: History Size Exceeded**: History limit reached (default 50K events). Ensure `ContinueAsNew` is implemented.
+- **Worker Hang**: Check `WorkerStopTimeout` and ensure all activities handle context cancellation.
+
+## Limitations
+
+- Does not cover Temporal Cloud UI navigation or TLS certificate provisioning workflows.
+- Does not cover Temporal Java, Python, or TypeScript SDKs; refer to their dedicated `-pro` skills.
+- Assumes Temporal Server v1.20+ and Go SDK v1.25+; older SDK versions may have different APIs.
+- Does not cover experimental Temporal features (e.g., Nexus, Multi-cluster Replication).
+- Does not address global namespace configuration or multi-region failover setup.
+- Does not cover Temporal Worker versioning via the `worker-versioning` feature flag (experimental).
+
+## Resources
+
+- [Implementation Playbook](resources/implementation-playbook.md) - Deep dive into Go SDK patterns.
+- [Testing Strategies](resources/testing-strategies.md) - Unit, Replay, and Integration testing for Go.
+- [Temporal Go SDK Reference](https://pkg.go.dev/go.temporal.io/sdk)
+- [Temporal Go Samples](https://github.com/temporalio/samples-go)
+
+## Related Skills
+
+- `grpc-golang` - Internal transport protocol and Protobuf design.
+- `golang-pro` - General Go performance tuning and advanced syntax.
+- `workflow-orchestration-patterns` - Language-agnostic orchestration strategy.

package/templates/.agent/skills/temporal-golang-pro/resources/implementation-playbook.md

@@ -0,0 +1,242 @@
+# Temporal Go Implementation Playbook
+
+This playbook provides production-ready patterns and deep technical guidance for implementing durable orchestration with the Temporal Go SDK.
+
+## Table of Contents
+
+1. [The Deterministic Commandments](#the-deterministic-commandments)
+2. [Workflow Versioning](#workflow-versioning)
+3. [Activity Design & Idempotency](#activity-design--idempotency)
+4. [Worker Configuration for Scale](#worker-configuration-for-scale)
+5. [Context & Heartbeating](#context--heartbeating)
+6. [Interceptors & Observability](#interceptors--observability)
+
+---
+
+## 1. The Deterministic Commandments
+
+In Go, workflows are state machines that must replay identically. Violating these rules causes "Determinism Mismatch" errors.
+
+### ❌ Never Use Native Go Concurrency
+
+- **Wrong:** `go myFunc()`
+- **Right:** `workflow.Go(ctx, func(ctx workflow.Context) { ... })`
+- **Why:** `workflow.Go` allows the Temporal orchestrator to track and pause goroutines during replay.
+
+### ❌ Never Use Native Time
+
+- **Wrong:** `time.Now()`, `time.Sleep(d)`, `time.After(d)`
+- **Right:** `workflow.Now(ctx)`, `workflow.Sleep(ctx, d)`, `workflow.NewTimer(ctx, d)`
+
+### ❌ Never Use Non-Deterministic Map Iteration
+
+- **Wrong:** `for k, v := range myMap { ... }`
+- **Right:** Collect keys, sort them, then iterate.
+- ```go
+  keys := make([]string, 0, len(myMap))
+  for k := range myMap { keys = append(keys, k) }
+  sort.Strings(keys)
+  for _, k := range keys { v := myMap[k]; ... }
+  ```
+
+### ❌ Never Perform Direct External I/O
+
+- **Wrong:** `http.Get("https://api.example.com")` or `os.ReadFile("data.txt")` inside a workflow.
+- **Right:** Wrap all I/O in an Activity and call it with `workflow.ExecuteActivity`.
+- **Why:** External calls are non-deterministic; their results change between replays.
+
+### ❌ Never Use Non-Deterministic Random Numbers
+
+- **Wrong:** `rand.Int()`, `uuid.New()` inside a workflow.
+- **Right:** Pass random seeds or UUIDs as workflow input arguments, or generate them inside an Activity.
+- **Why:** `rand.Int()` produces different values on each replay, causing a determinism mismatch.
+
+---
+
+## 2. Workflow Versioning
+
+When you need to change logic in a running workflow, you MUST use `workflow.GetVersion`.
+
+### Pattern: Safe Logic Update
+
+```go
+const VersionV2 = 1
+
+func MyWorkflow(ctx workflow.Context) error {
+    v := workflow.GetVersion(ctx, "ChangePaymentStep", workflow.DefaultVersion, VersionV2)
+
+    if v == workflow.DefaultVersion {
+        // Old logic: kept alive until all pre-existing workflow runs complete.
+        return workflow.ExecuteActivity(ctx, OldActivity).Get(ctx, nil)
+    }
+    // New logic: all new and resumed workflow runs use this path.
+    return workflow.ExecuteActivity(ctx, NewActivity).Get(ctx, nil)
+}
+```
+
+### Pattern: Cleanup After Full Migration
+
+Once you have confirmed **no running workflow instances** are on `DefaultVersion` (verify via Temporal Web UI or `tctl`), you can safely remove the old branch:
+
+```go
+func MyWorkflow(ctx workflow.Context) error {
+    // Pin minimum version to V2; histories from before the migration will
+    // fail the determinism check (replay error) if they replay against this code.
+    // Only remove the old branch after confirming zero running instances on DefaultVersion.
+    workflow.GetVersion(ctx, "ChangePaymentStep", VersionV2, VersionV2)
+    return workflow.ExecuteActivity(ctx, NewActivity).Get(ctx, nil)
+}
+```
+
+---
+
+## 3. Activity Design & Idempotency
+
+Activities can execute multiple times. They must be idempotent.
+
+### Pattern: Upsert instead of Insert
+
+Instead of a simple `INSERT`, use `UPSERT` or "Check-then-Act" with an idempotency key (like `WorkflowID` or `RunID`).
+
+```go
+func (a *Activities) ProcessPayment(ctx context.Context, req PaymentRequest) error {
+    info := activity.GetInfo(ctx)
+    // Use info.WorkflowExecution.ID as part of your idempotency key in DB
+    return a.db.UpsertPayment(req, info.WorkflowExecution.ID)
+}
+```
+
+---
+
+## 4. Worker Configuration for Scale
+
+### Optimized Worker Options
+
+```go
+w := worker.New(c, "task-queue", worker.Options{
+    MaxConcurrentActivityExecutionSize:      100, // Limit based on resource constraints
+    MaxConcurrentWorkflowTaskExecutionSize:  50,
+    WorkerActivitiesPerSecond:               200, // Rate limit for this worker cluster
+    WorkerStopTimeout:                       time.Minute, // Allow activities to finish
+})
+```
+
+---
+
+## 5. Context & Heartbeating
+
+### Propagating Metadata
+
+Use `Workflow Interceptors` or custom `Header` propagation to pass tracing ID or user identity along the call chain.
+
+### Activity Heartbeating
+
+Mandatory for long-running activities to detect worker crashes before the `StartToCloseTimeout` expires.
+
+```go
+func LongRunningActivity(ctx context.Context) error {
+    for i := 0; i < 100; i++ {
+        activity.RecordHeartbeat(ctx, i) // Report progress
+
+        select {
+        case <-ctx.Done():
+            return ctx.Err() // Handle cancellation
+        default:
+            // Do work
+        }
+    }
+    return nil
+}
+```
+
+---
+
+## 6. Interceptors & Observability
+
+### Custom Workflow Interceptors
+
+Use interceptors to inject structured logging (Zap/Slog) or perform global error classification.
+The interceptor must be wired via a root `WorkerInterceptor` that Temporal instantiates per workflow task.
+
+```go
+// Step 1: Implement the root WorkerInterceptor (registered on worker.Options)
+type MyWorkerInterceptor struct {
+    interceptor.WorkerInterceptorBase
+}
+
+func (w *MyWorkerInterceptor) InterceptWorkflow(
+    ctx workflow.Context,
+    next interceptor.WorkflowInboundInterceptor,
+) interceptor.WorkflowInboundInterceptor {
+    return &myWorkflowInboundInterceptor{next: next}
+}
+
+// Step 2: Implement the per-workflow inbound interceptor
+type myWorkflowInboundInterceptor struct {
+    interceptor.WorkflowInboundInterceptorBase
+    next interceptor.WorkflowInboundInterceptor
+}
+
+func (i *myWorkflowInboundInterceptor) ExecuteWorkflow(
+    ctx workflow.Context,
+    input *interceptor.ExecuteWorkflowInput,
+) (interface{}, error) {
+    workflow.GetLogger(ctx).Info("Workflow started", "type", workflow.GetInfo(ctx).WorkflowType.Name)
+    result, err := i.next.ExecuteWorkflow(ctx, input)
+    if err != nil {
+        workflow.GetLogger(ctx).Error("Workflow failed", "error", err)
+    }
+    return result, err
+}
+
+// Step 3: Register on the worker
+w := worker.New(c, "task-queue", worker.Options{
+    Interceptors: []interceptor.WorkerInterceptor{&MyWorkerInterceptor{}},
+})
+```
+
+---
+
+## Anti-Patterns to Avoid
+
+1.  **Massive Workflows:** Keeping too much state in a single workflow. Use `ContinueAsNew` if event history exceeds 50K events.
+2.  **Fat Activities:** Doing orchestration inside an activity. Activities should be unit-of-work.
+3.  **Global Variables:** Using global variables in workflows. They will not be preserved across worker restarts.
+4.  **Native Concurrency in Workflows:** Using `go` routines, `mutexes`, or `channels` will cause race conditions and determinism errors during replay.
+
+---
+
+## 7. SideEffect and MutableSideEffect
+
+Use `workflow.SideEffect` when you need a **single non-deterministic value** captured once and replayed identically — for example, generating a UUID or reading a one-time config snapshot inside a workflow.
+
+```go
+// SideEffect: called only on first execution; result is recorded in history and
+// replayed deterministically on all subsequent replays.
+// Requires: "go.temporal.io/sdk/workflow"
+encodedID := workflow.SideEffect(ctx, func(ctx workflow.Context) interface{} {
+    return uuid.NewString()
+})
+
+var requestID string
+if err := encodedID.Get(&requestID); err != nil {
+    return err
+}
+```
+
+**When to use `MutableSideEffect`**: When the value may change across workflow tasks but must still be deterministic per history event (e.g., a feature flag that updates while the workflow is running).
+
+```go
+// MutableSideEffect: re-evaluated on each workflow task, but only recorded in
+// history when the value changes from the previous recorded value.
+encodedFlag := workflow.MutableSideEffect(ctx, "feature-flag-v2",
+    func(ctx workflow.Context) interface{} {
+        return featureFlagEnabled // read from workflow-local state, NOT an external call
+    },
+    func(a, b interface{}) bool { return a.(bool) == b.(bool) },
+)
+var enabled bool
+encodedFlag.Get(&enabled)
+```
+
+> **Warning:** Do NOT use `SideEffect` as a workaround to call external APIs (HTTP, DB) inside a workflow. All external I/O must still go through Activities.