agent-sessions-layout

Enforce Agent Sessions layout guidelines to keep code aligned with sessions/LAYOUT.md.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/DevFlex-AI/devonz-editor-web --skill agent-sessions-layout-devflex-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-sessions-layout
Source: https://github.com/DevFlex-AI/devonz-editor-web/tree/main/.github/skills/agent-sessions-layout
Command: npx skills add https://github.com/DevFlex-AI/devonz-editor-web --skill agent-sessions-layout-devflex-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agent Sessions layout drift and misalignment between code and spec is prevented by providing a centralized set of layout guidelines and a single source of truth.

Core Features & Use Cases

  • Spec-synced implementation aligns code with sessions/LAYOUT.md
  • Predictable grid & visibility enforces fixed layout structure and default states
  • Conformance workflow ensures LAYOUT.md is updated when layout changes occur

Quick Start

Follow the guideline to review the current LAYOUT.md and apply updates to code and docs to keep the spec in sync.

Frequently Asked Questions about agent-sessions-layout

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

FAQPage Schema
How do I prevent layout drift between my frontend implementation and the agent sessions spec?

You can prevent layout drift by enforcing fixed grid structures, default visibility states, and agent-specific storage key compliance that align your codebase directly with the sessions/LAYOUT.md specification.

What are agent sessions workbench layout guidelines for UI development?

Agent sessions workbench layout guidelines define a fixed grid structure, default visibility states, and specific storage keys for browser components, ensuring implementation matches the official LAYOUT.md spec without deviation.

How do I update the Revision History when changing agent sessions layout components?

Update the Revision History in sessions/LAYOUT.md whenever you modify layout structures, visibility states, or agent-specific menus and keys, ensuring the spec remains a single source of truth for the workbench.

Does the agent sessions layout spec require specific storage keys for browser components?

Yes, the layout spec requires using agent-specific parts, keys, and menus for browser components to ensure predictable behavior and maintain compliance with the fixed workbench grid structure.

When do I need to review LAYOUT.md during frontend feature development?

You need to review LAYOUT.md during any feature development or layout changes affecting sessions or browser components to verify grid structure, visibility states, and storage keys match the specification.