sessions

Implement the Agent Sessions UI layout and chat widget in ShadowCode.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agent Sessions architecture and guidelines provide a structured blueprint for implementing, maintaining, and evolving the Sessions window in ShadowCode, ensuring a consistent, chat-first UX across desktop and browser builds.

Core Features & Use Cases

  • Layered architecture and dependency rules enabling clean separation of concerns between core workbench, agent sessions window, and contributions.
  • Comprehensive folder structure and authoritative docs (LAYOUT.md, AI_CUSTOMIZATIONS.md, AGENTS_CHAT_WIDGET.md) to guide development and ensure spec-sync.
  • Clear development workflow: validation commands, window visibility semantics, and contribution registration to support reliable feature delivery.

Quick Start

Follow the Agent Sessions layout and spec guidelines to begin implementing or updating features in the Sessions window.

Frequently Asked Questions about sessions

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

FAQPage Schema
How do I structure an agent sessions UI for a consistent chat-first experience?

Use a layered architecture separating core workbench, agent sessions window, and contributions to maintain a consistent chat-first UX across desktop and browser builds.

What documentation specs do I need to maintain when updating the agent sessions window?

You must maintain authoritative docs including LAYOUT.md, AI_CUSTOMIZATIONS.md, and AGENTS_CHAT_WIDGET.md, enforcing the rule to update specs whenever changes are made to the sessions window.

Does the ShadowCode agent sessions architecture support both browser and desktop builds?

Yes, the agent sessions architecture provides integration guidelines and window visibility semantics that explicitly support reliable feature delivery across both browser and desktop builds.

How do I register new contributions in the agent sessions workbench?

Follow the clear development workflow provided by the architecture, which includes validation commands, window visibility semantics, and contribution registration steps to support reliable feature delivery.

What's the best way to enforce clean separation of concerns in agent sessions development?

Apply the layered architecture and dependency rules outlined in the folder structure specs, ensuring clean separation between the core workbench, agent sessions window, and external contributions.