compact-landing ยท diff

v5.0.0 to v5.0.0

21 added, 21 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
name: compact-landing
description: Use when Build compact, premium landing pages with clear CTA hierarchy, quiet typography, restrained visual noise, and high conversion flow.
version: 5.0.0
last-updated: 2026-09-13
skills:
- landing-page
- quieter
- baseline-ui
tools: Read, Grep, Glob, Bash, Edit, Write
scripts-binding:
- .agent/scripts/lint_runner.js
- .agent/scripts/verify_all.js
---
# Compact Landing โ€” Premium Minimalist Landing Pages
## Mandatory Pre-Flight Context Inspection
Before generating, refactoring, or reviewing code in the `compact-landing` domain, inspect these 5 critical parameters:
1. **System Boundaries & Dependencies**: Verify that all required dependencies exist in target package manifests and environment paths.
2. **Runtime Context & Platform Invariants**: Confirm target platform constraints (Node.js, Browser, Mobile OS, Edge runtime) before applying APIs.
3. **Execution Guardrails**: Identify potential side-effects, state mutations, and unhandled asynchronous exceptions.
4. **Validation & Type Contracts**: Validate input data schemas and strict type constraints across all module interfaces.
5. **Observability & Proof of Execution**: Ensure execution produces tangible verification signals (terminal output, tests, metrics).
## Activation Boundaries
- **Activate when:** Use when Build compact, premium landing pages with clear CTA hierarchy, quiet typography, restrained visual noise, and high conversion flow.
- **DO NOT activate when:** The task falls outside the `compact-landing` domain or is managed by a different dedicated specialist.
## ๐Ÿ” Multi-Pass Execution Protocol
Execute all non-trivial tasks through this 7-pass cognitive loop:
- | Pass | Phase | Core Action |
- |:---|:---|:---|
- | **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. |
- | **Pass 2** | **Plan** | Decompose the task into smallest logical steps; map dependencies and required tool calls. |
- | **Pass 3** | **Execute** | Implement the solution with production-grade craft, zero placeholders, and strict typing. |
- | **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. |
- | **Pass 5** | **Attack** | Perform an adversarial review searching for edge-case failures, race conditions, and traps. |
- | **Pass 6** | **Improve** | Eliminate discovered friction, optimize performance, and harden error boundaries. |
+ | Pass | Phase | Core Action |
+ | :--------- | :--------------- | :------------------------------------------------------------------------------------------- |
+ | **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. |
+ | **Pass 2** | **Plan** | Decompose the task into smallest logical steps; map dependencies and required tool calls. |
+ | **Pass 3** | **Execute** | Implement the solution with production-grade craft, zero placeholders, and strict typing. |
+ | **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. |
+ | **Pass 5** | **Attack** | Perform an adversarial review searching for edge-case failures, race conditions, and traps. |
+ | **Pass 6** | **Improve** | Eliminate discovered friction, optimize performance, and harden error boundaries. |
| **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. |
---
## ๐Ÿ› ๏ธ Technical Architecture & Reference Recipes
---
-
---
## 4 Compact Landing Rules
### 1. The Single Viewport Value Pitch
- Above-the-fold content must answer 3 questions instantly within 1 single screen viewport:
1. _What is it?_ (Clear, un-hypey headline + subhead)
2. _What does it look like?_ (Crisp UI screenshot or interactive preview component)
3. _How do I get it?_ (Unambiguous primary CTA input/button)
### 2. Quiet Typographic Hierarchy
- Use subdued monochrome typography (`oklch(0.95 0.005 240)` background with `oklch(0.20 0.01 240)` body copy).
- Keep display font sizes restrained (`clamp(1.75rem, 4vw, 2.75rem)`) rather than giant 5rem text blocks.
### 3. Tight Spatial Grid
- Limit total page section count to max 4 sections:
1. Hero + Primary CTA + Product Preview
2. Social Proof / Logo Bar
3. Feature Grid (3 core benefits max)
4. Conversion Footer Card
### 4. Zero Unnecessary Visual Noise
- Omit decorative background shapes, floating 3D spheres, and rainbow gradients. Let contrast and typography drive visual quality.
---
## ๐Ÿšจ Edge-Case & Failure Mode Matrix
- | Scenario | Risk | Mitigation Strategy |
- |:---|:---|:---|
- | **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
- | **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
- | **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
- | **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
- | **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
+ | Scenario | Risk | Mitigation Strategy |
+ | :------------------------------------- | :--------------------------------------------------- | :------------------------------------------------------------------------------ |
+ | **Empty or Null Inputs** | Unhandled exception or unexpected rendering collapse | Enforce fallback guards, optional chaining, and explicit empty state handlers |
+ | **Network Timeout / Latency** | Hanging operations or duplicate side-effects | Implement bounded abort controllers, exponential backoff, and idempotency keys |
+ | **Concurrency / Race Conditions** | Stale state overwrite or inconsistent data mutations | Use atomic transactions, mutex locking, or cancel-on-resubmit controls |
+ | **Invalid Schema / Malformed Payload** | Downstream runtime errors or security injection | Validate boundary payloads with Zod/Pydantic schemas prior to execution |
+ | **Resource / Memory Saturation** | OOM errors, frame drops, or memory leaks | Clean up listeners, cancel active timers, and enforce pagination/virtualization |
---
## ๐Ÿค– LLM-Specific Traps Table
- | Anti-Pattern | What AI Commonly Does Wrong | What Is Actually Correct |
- |:---|:---|:---|
- | **Uncontrolled Re-render Loop** | Mutating state inside render bodies or omitting hook dependencies | Wrap effects with explicit deps and isolate reactive derivations in useMemo |
- | **Accessibility Neglect** | Interactive <div> without role="button", tabIndex, or onKeyDown | Use semantic <button> or provide ARIA role, keyboard handlers, and focus ring |
- | **Layout Shift Flash** | Images/dynamic content without aspect-ratio or explicit dimensions | Enforce aspect-ratio or skeleton placeholders to guarantee zero CLS |
+ | Anti-Pattern | What AI Commonly Does Wrong | What Is Actually Correct |
+ | :------------------------------ | :----------------------------------------------------------------- | :---------------------------------------------------------------------------- |
+ | **Uncontrolled Re-render Loop** | Mutating state inside render bodies or omitting hook dependencies | Wrap effects with explicit deps and isolate reactive derivations in useMemo |
+ | **Accessibility Neglect** | Interactive <div> without role="button", tabIndex, or onKeyDown | Use semantic <button> or provide ARIA role, keyboard handlers, and focus ring |
+ | **Layout Shift Flash** | Images/dynamic content without aspect-ratio or explicit dimensions | Enforce aspect-ratio or skeleton placeholders to guarantee zero CLS |
---
## ๐Ÿ›๏ธ Tribunal Verification & Guardrails
**Active Reviewers:** `frontend-reviewer` ยท `type-safety` ยท `ui-ux-auditor` ยท `complexity-reviewer`
**Slash Command:** `/review` or `/tribunal-full`
### โœ… Pre-Flight Self-Audit Checklist
```
โœ… Are all component props strictly typed with zero implicit "any"?
โœ… Are responsive breakpoints, fluid typography, and optical balance verified?
โœ… Is accessibility (ARIA labels, keyboard focus, contrast) validated?
โœ… Are re-renders minimized and state lifecycles cleanly separated?
โœ… Did I verify all imported UI components and icon sets actually exist?
```
### ๐Ÿ›‘ Verification-Before-Completion (VBC) Protocol
**CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
+
- โŒ **Forbidden:** Declaring a task complete because the output "looks correct."
- โœ… **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing test suites, compiler success, or equivalent operational proof) that your output works as intended.