sourcea-landing-agentic-ui

Guides execution-first upgrades to the sourcea.app landing page HTML, CSS, and JavaScript.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents stale, call-first positioning from creeping back into the sourcea.app landing page by enforcing an execution-first agentic UI strategy with mandatory production audits and mechanical validators before any edit. ## Core Features & Use Cases - Positioning enforcement: Demotes "book a call" CTAs below self-serve paths like Forge Terminal, sandbox, and Brain chat, using a positioning SSOT JSON and denylist gates. - Agentic UI layers: Coordinates Brain chat, Site Pulse analytics/feedback FAB, and the Tools dock across landing HTML, config JSON, and Cloudflare workers. - Validation workflow: Runs mechanical and live-production validator scripts before and after every deploy to block stale copy. - Use Case: Before editing founder-home.html hero copy, run the anti-staleness ritual, update sourcea-site-interact-v1.json config first, then validate and publish via the deploy script. ## Quick Start Ask the agent to audit the sourcea.app landing page against the positioning SSOT and propose an execution-first update to the hero CTA before making any edits.

Frequently Asked Questions about sourcea-landing-agentic-ui

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

FAQPage Schema
How do I update the sourcea.app landing page without breaking positioning?▼

Follow the AG-UI checklist: read the positioning SSOT JSON, edit config JSON files first, then JS/CSS/HTML, and run the mechanical and brain-live validator scripts before publishing with the deploy script.

What is the correct CTA order for the landing page hero?▼

Forge Terminal comes first, followed by sandbox or proof quiz, then Brain chat chips, then pricing, with booking a call last as optional escalation. Call-first hero copy is on the positioning denylist.

How do I check if the live site matches the disk version?▼

Run the brain-live validator script for production truth, then curl the live positioning JSON at sourcea.app and compare it against the disk copy of sourcea-positioning-v1.json.

Why does the offline banner still show when the worker is healthy?▼

The banner stays in the accessibility tree on some pages because syncOfflineBanner is not re-run after the worker responds. Re-check that syncOfflineBanner sets aria-hidden when the worker is online.

When should booking a call appear in the Tools dock?▼

Only as a demoted, optional item at the bottom of the dock, renamed to something like talk to a human. It must never rank equal to Forge Terminal or appear in the top three skills.