Context
PR #10298 merged the industry-friction-radar skill, establishing our external sensory organ. The current documentation states the goal is "to systematically ingest State of the Art (SOTA) industry developments."
The Problem
The term "SOTA" (State of the Art) implies established industry standards. In the frontend ecosystem, "industry standards" often equate to widely accepted but architecturally flawed practices (e.g., massive VDOM trees on the main thread, complex hydration payloads, monolithic state management). We do not want to ingest "SOTA"; we want to ingest "Frontier" friction points. Our goal is to look at the bleeding edge, where the current SOTA is failing.
The Architectural Reality
The radar's purpose is to feed the Dream Pipeline with raw friction data, not solutions. If the prompt instructs the agent to look for "SOTA", it risks anchoring the agent's web search to mainstream, highly-SEO-ranked medium articles about React or Vue patterns, effectively bypassing the Engine-Category filter we worked so hard to establish.
The Fix
Update the terminology across the industry-friction-radar documentation (both SKILL.md and the references/industry-friction-radar-workflow.md).
- Replace "State of the Art (SOTA)" with "Bleeding-Edge / Frontier".
- Explicitly document the "SOTA Trap": clarify that industry standards are often anti-patterns in the Neo paradigm, and the radar should focus on where those standards are breaking down (the friction), not the standards themselves.
Acceptance Criteria
Context PR #10298 merged the
industry-friction-radarskill, establishing our external sensory organ. The current documentation states the goal is "to systematically ingest State of the Art (SOTA) industry developments."The Problem The term "SOTA" (State of the Art) implies established industry standards. In the frontend ecosystem, "industry standards" often equate to widely accepted but architecturally flawed practices (e.g., massive VDOM trees on the main thread, complex hydration payloads, monolithic state management). We do not want to ingest "SOTA"; we want to ingest "Frontier" friction points. Our goal is to look at the bleeding edge, where the current SOTA is failing.
The Architectural Reality The radar's purpose is to feed the Dream Pipeline with raw friction data, not solutions. If the prompt instructs the agent to look for "SOTA", it risks anchoring the agent's web search to mainstream, highly-SEO-ranked medium articles about React or Vue patterns, effectively bypassing the Engine-Category filter we worked so hard to establish.
The Fix Update the terminology across the
industry-friction-radardocumentation (bothSKILL.mdand thereferences/industry-friction-radar-workflow.md).Acceptance Criteria
SKILL.mdupdated to remove "SOTA" terminology.industry-friction-radar-workflow.mdupdated to remove "SOTA" terminology.