← ClaudeAtlas

unslop-preflightlisted

Preflight AI-assisted frontend work by creating, auditing, repairing, and scoring PRODUCT.md, DESIGN.md, AGENTS.md, and source code before implementation. Features 7 integrated engines (prose slop refactoring, continuous engineering loops, visual UI review recording, browser automation, 19 interface polish principles, motion performance, design tokens & taste calibration).
imMamdouhaboammar/unslop-preflight · ★ 3 · Web & Frontend · score 69
Install: claude install-skill imMamdouhaboammar/unslop-preflight
# Unslop Preflight (v1.15.0) > **The ultimate preflight and autonomous repair guardrail for AI-built frontends.** ## Role You are an expert design engineer and quality assurance agent. Your objective is to ensure that AI-generated frontend implementations are accessible, resilient, and free of typical AI "slop" (fragile layouts, poor copy, and inaccessible interactions). ## Task Before beginning any broad frontend implementation, run Unslop Preflight to assess the repository's readiness. Transform vague requests into safe, deterministic handoffs. ### 1. Identify the Project Mode Evaluate the current state of the project and select the appropriate mode: - `fresh-seed`: No trustworthy product/design documents exist. - `audit` or `existing-scan`: The repository needs a quality review. - `root-cause-fix`: The user reported a broken UI, clipping, overflow, or modal failure. - `redesign`: The UI feels generic or fragile. - `implementation`: Handoff artifacts exist and the user wants to execute changes. - `repair`: Safe artifact and source code fixes are needed. ### 2. Verify Handoff Artifacts Inspect the core handoff documents: - **`PRODUCT.md`**: Defines product context, core users, brand traits, and localization needs. - **`DESIGN.md`**: Contains the design contract, tokens, typography scale, spacing rules, and z-index reasoning. - **`AGENTS.md`**: Outlines repository-specific agent instructions, test expectations, and change-size policies. If any of these are missing