sessions

Document architecture and contribution guidelines for the Agent Sessions window.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/colajacquin-e/ephcode --skill sessions-colajacquin-e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sessions
Source: https://github.com/colajacquin-e/ephcode/tree/main/.github/skills/sessions
Command: npx skills add https://github.com/colajacquin-e/ephcode --skill sessions-colajacquin-e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a centralized, authoritative reference for implementing and maintaining the Agent Sessions window, ensuring consistent architecture, folder structure, and development guidelines across browser and desktop builds.

Core Features & Use Cases

  • Documents layering rules, dependency constraints, entry points, and folder structure for the Agent Sessions UI.
  • Describes contribution workflow, components, and entry points to streamline feature development and bug fixes.
  • Serves as a practical guide for engineers, designers, and reviewers when implementing or updating the Agent Sessions window.

Quick Start

Review the agent sessions layout spec and related contribution guidelines before starting work.

Frequently Asked Questions about sessions

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

FAQPage Schema
How do I structure folders for a sessions-first UI across browser and desktop builds?

Folder structure for sessions-first UI requires following specific layering rules and dependency constraints to ensure consistent architecture across browser and desktop builds. The architectural guide enforces these structural boundaries for the Agent Sessions window.

What are the entry points for implementing the Agent Sessions window?

Entry points for the Agent Sessions window are documented layout specs that define how components initialize and interact within the sessions-first UI. They enforce architecture rules and streamline feature development for both browser and desktop.

How do I contribute new features to the Agent Sessions window without breaking architecture rules?

Contributions to the Agent Sessions window require following documented contribution conventions, architecture rules, and testing workflows before submitting changes. The guide describes the workflow to streamline feature development and bug fixes.

Does the Agent Sessions architecture guide cover chat widget and menu implementation?

The Agent Sessions architecture guide covers chat widget and menu implementation by documenting layering rules, component dependencies, and layout specs. This ensures consistent development guidelines across both browser and desktop builds.

When do I need to review layout specs before updating the sessions-first UI?

Review layout specs before starting any work on the sessions-first UI to ensure compliance with architecture rules, folder structure, and contribution conventions. This prevents architectural inconsistencies during feature development and bug fixes.