implement-experience-layer

Coordinate long-running user journeys as checkpointed workflows with signal-triggered progression.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill implement-experience-layer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-experience-layer
Source: https://github.com/firefly-oss/firefly-oss-claude-skills/tree/main/skills/implement-experience-layer
Command: npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill implement-experience-layer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Experience Layer coordinates long-running user journeys across multiple domain services while keeping intermediate states hidden from users, enabling reliable progress, auditability, and seamless recovery after interruptions.

Core Features & Use Cases

  • Stateful, signal-driven workflows model end-to-end journeys (onboarding, approvals, KYC) as atomic steps behind stable REST endpoints.
  • No in-process database; journey state persists in the orchestration framework, enabling checkpointing, replay, and cross-step observability.
  • Suitable for multi-channel frontends that require resume-from-last-step and centralized monitoring of journey progress.

Quick Start

Create a new exp-{name} module, define a single long-running workflow with signal gates, and expose REST endpoints to drive progress.

Frequently Asked Questions about implement-experience-layer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate long-running user journeys across microservices?

You orchestrate long-running user journeys across microservices by modeling them as resilient, checkpointed workflows. This approach handles onboarding and approvals using signal-triggered progression without exposing intermediate states to users.

What is the best way to build a multi-channel onboarding workflow that can resume from the last step?

Building a multi-channel onboarding workflow with resume capability requires stateful, signal-driven orchestration. It persists journey state in the orchestration framework, enabling seamless recovery and resume-from-last-step functionality without an in-process database.

How do I implement stateless steps while maintaining persistent workflow state for end-to-end recoverability?

To maintain persistent workflow state for end-to-end recoverability, leverage an orchestration framework for checkpointing and replay. This allows individual workflow steps to remain stateless while the overall journey state persists externally.

Does this workflow orchestration approach work for identity verification and KYC processes?

Yes, this workflow orchestration approach effectively handles identity verification and KYC processes. It models end-to-end journeys as atomic steps behind stable REST endpoints, enabling explicit signal-triggered progression and centralized status queries.

When should I use signal-driven workflow orchestration instead of standard synchronous API calls?

Use signal-driven workflow orchestration instead of synchronous API calls when coordinating long-running user journeys that require auditability, cross-step observability, and seamless recovery after interruptions across multiple domain services.