forge-living-ui-modern-ide

Implements resizable living-chat UI patterns for Forge Terminal and Chat Unify IDE surfaces.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill forge-living-ui-modern-ide-noetfield-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-living-ui-modern-ide
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/.cursor/skills/forge-living-ui-modern-ide
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill forge-living-ui-modern-ide-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Forge Terminal and Chat Unify chat interfaces can feel robotic, cramped, or static — raw JSON replies, fixed-height chat areas, broken Connect iframe tabs, and unreadable founder-facing output. This Skill provides the patterns and wiring rules to turn them into a modern, resizable, founder-readable workbench. ## Core Features & Use Cases - Founder-readable reply pipeline: Keeps the chain from chat_turn through translate_for_founder and response_for_display() wired so users see four-section prose with an inline quality chip instead of raw JSON. - Modern IDE layout patterns: Cursor/Replit/Lovable-style workbench grid, resizable dock with persisted height, flex-filling chat thread, embed mode for iframes, and keyboard shortcuts (Enter send, ⌘J dock toggle). - Connect shell and Chat Unify fixes: Ensures the forge-ide tab is registered in the router, iframes size correctly, founder textareas are resizable, and quality gates persist across reloads. - Use Case: When upgrading the Forge IDE chat UX, apply the layout checklist to remove the 42vh chat cap, add a drag-resizable dock, and render founder sections so a non-technical founder sees Bottom line → What this means → Blockers → Next step. ## Quick Start Use the forge-living-ui-modern-ide skill to fix the Forge Terminal chat layout so replies render as founder-readable sections in a resizable chat column.

Frequently Asked Questions about forge-living-ui-modern-ide

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

FAQPage Schema
How do I make Forge Terminal chat replies founder-readable?

Keep the reply pipeline wired: chat_turn calls translate_for_founder with prefer_ai=True, then response_for_display() returns display_response, and terminal.js renders it via renderFounderSections. Never show raw JSON in chat bubbles.

How do I make the Forge IDE chat area resizable?

Remove the max-height 42vh cap and set the chat thread to flex: 1 with min-height: 0. Add a drag handle on the dock that updates a --dock-h CSS variable persisted in localStorage.

Why does the Forge IDE tab fall back to Home in the Connect shell?

The switchTab() tabs array in apps/forge-terminal-connect-v1/app.js is missing forge-ide, so clicks fall back to the Home tab. Add forge-ide to the router and set it as the default tab.

Does the quality gate chip persist after reloading the chat?

Yes, if the quality_gate verdict is stored in the thread metadata via append_turn in forge_terminal_desktop_mesh_v1.py. Without persistence, the chip only appears on live turns and the UI feels static on reload.

What are common anti-patterns when building the Forge living chat UI?

Avoid rules-only founder translation producing generic boilerplate, rendering raw JSON responses, monospace fonts in chat, tiny max-heights on founder textareas, and duplicate topbars when embedding the IDE in an iframe.