compact-landing ยท v6.0.0 ยท 2026-10-07 ยท sha256 ab4a677d2100509c
compact-landing v6.0.0A
Immutable. This exact content never changes and is served at /api/v1/blob/ab4a677d2100509c.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2i6ohgdc7fr4n6la/ab4a677d2100509c722881f212b6fa7570dad21c78498c041f656185fe27876b.json
Then /plugin install compact-landing@markdownregistry-2i6ohgdc7fr4n6la in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: compact-landing description: "Use when building, styling, optimizing, and auditing compact landing components, responsive layouts, design systems, and frontend state." version: 6.0.0 last-updated: 2026-09-29 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 inputs: task: "string" target_file: "string" outputs: result: "string" verification_status: "boolean" trigger: - "compact" - "landing" --- # Compact Landing โ Premium Minimalist Landing Pages ## Mandatory Pre-Flight Context Inspection Before reading, generating, or refactoring 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 building, styling, optimizing, and auditing compact landing components, responsive layouts, design systems, and frontend state. - **DO NOT activate when:** The task falls outside the `compact-landing` domain or is managed by a different dedicated specialist agent. ## ๐ Multi-Pass Execution Protocol | Pass | Phase | Core Action | Adaptive Depth | |:---|:---|:---|:---| | **Pass 1** | **Understand** | Deconstruct the user's explicit objective, implicit requirements, and platform constraints. | Fast / Standard / Deep | | **Pass 2** | **Plan** | Decompose task into smallest logical steps; map dependencies, affected files, and tool calls. | Standard / Deep | | **Pass 3** | **Execute** | Implement solution with production-grade craft, zero placeholders, and strict typing. | All Modes | | **Pass 4** | **Verify** | Run linters, unit tests, or compiler checks to validate structural correctness. | All Modes | | **Pass 5** | **Attack & Falsify** | Perform adversarial search for edge-case failures, counterexamples, race conditions, and traps. | Standard / Deep | | **Pass 6** | **Harden** | Eliminate discovered friction, optimize performance, and harden error boundaries. | Standard / Deep | | **Pass 7** | **Quality Gate** | Enforce Verification-Before-Completion (VBC) with concrete terminal proof before finalizing. | All Modes | --- ## ๐ ๏ธ 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 | Production Mitigation | |:---|:---|:---| | **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 | ## ๐๏ธ Tribunal Verification & Guardrails **Active Reviewers:** `frontend-reviewer` ยท `type-safety` ยท `ui-ux-auditor` ยท `complexity-reviewer` **Slash Command:** `/review` or `/tribunal-full` ### ๐ฌ Evidence Standard (Tri-State Verification) Every finding, audit statement, or completion claim must classify its factual certainty: - **`[OBSERVED]`**: Directly confirmed in the codebase or verified via executed terminal command. - **`[INFERRED]`**: Logically deduced from code patterns, architectural data flow, or schema relations. - **`[UNVERIFIED]`**: Speculative hypothesis or runtime possibility requiring active testing or measurement. ### โ 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 navigation, contrast ratio >= 4.5:1) 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.