Mobile First Website Design

Mobile-First Website Design

Create evidence-led marketing surfaces with style-free structure, a separate identity phase, exact image prompts, smallest-to-largest implementation, and replayable release proof.

When to Use

Use for landing pages, campaign pages, product launches, and marketing websites that need evidence-led responsive design, implementation, or release validation. Use product-interface skills for application task flows and broader design skills for cross-media systems.

Start contract

Resource gate: run mise run validate before using package files named here.

Normalize the brief, factual claims, conversion event, audience, visitor state, section obligations, assets, integrations, release target, and every supported width into canonical JSON. Missing facts are null plus a blocker. Never invent them.

Load brief and research and integrations at job start.

Fixed workflow

1. Diagnose the visitor state and freeze one five-part conversion narrative.
2. Define every section's question, answer, proof, action, image job, and accessibility obligation.
3. Research every section through available Refero, Mobbin, Lazyweb, and direct first-party web routes in fixed order.
4. Record route status, source ID, visible mechanism, relevance, adaptation, and fallback.
5. Produce exactly three style-free wireframe sequences at the smallest width.
6. Recompose each sequence through every larger breakpoint in ascending order.
7. Score complete sequences, run available judgement skills, choose by score and stable-ID tie break, and freeze wireframe_sha256.
8. Only after that hash exists, create and score three visual identity directions.
9. Convert every placeholder into a named image job.
10. Select one exact prompt YAML record and one available tool route per image job.
11. Generate or edit candidates with an available image capability, inspect rendered pixels with an available pixel-inspection capability, and freeze selected asset bytes.
12. Style and implement the smallest width first.
13. Advance through every larger breakpoint, validating each width before the next.
14. Add one repeated motion thesis with interruptible behavior and reduced-motion parity.
15. Sweep every integer CSS width and inspect every breakpoint boundary.
16. Run access, Web Vitals, external judgement, browser, native vision, and replay gates.
17. Permit at most two bounded repair passes, then emit a full, degraded, or blocked release state.

Structure and style gate

Wireframes may contain hierarchy, section order, copy density, proof placement, action priority, semantic order, layout topology, responsive reflow, and image-job placeholders. They may not contain color, typeface, image treatment, texture, gradients, shadows, decorative motifs, icon style, logo treatment, or motion styling.

Run mise run validate-packet before identity work. Styling must cite the approved wireframe hash. Load wireframe, then visual identity.

Mobile-first gate

• Start structure, style, implementation, motion, and validation at the smallest width.
• Process every unique positive integer width in strictly ascending order.
• Record every adaptation or the literal status UNCHANGED.
• A larger width may add space, columns, scale, or peripheral detail. It may not remove required content or weaken the primary action.
• Duplicate, descending, skipped, or unrecorded widths return BLOCKED_BREAKPOINT_ORDER.

Image gate

Resource gate: run mise run validate before using package files named here.

The package carries all 1,000 public prompt strings as uncompressed UTF-8 YAML records under assets/prompts/. Each public string is deterministically punctuation-normalized from the byte-exact native source retained in committed evidence. The source prompt path remains the canonical ID. Select domain, lane, and perspective from normalized job fields, load the exact public YAML prompt scalar, verify its byte count and SHA-256, then choose a route from assets/tool-registry.json.

Use an available direct image generation or editing capability for supported work. Use Flora search_docs and approved Flora execute when its current model, canvas, project, technique, or action workflow is required. Use ComfyUI for a local node workflow. Never choose a provider or model on the user's behalf. Load image routing.

Integration and degradation gate

Resource gate: run mise run validate before using package files named here.

Check Refero, Mobbin, Lazyweb, Flora, Impeccable, TasteSkill, and applicable Emil procedures independently. Allowed unavailable statuses are UNAVAILABLE_AUTH, UNAVAILABLE_TRANSPORT, UNAVAILABLE_SCHEMA, UNAVAILABLE_SKILL, and UNAVAILABLE_DISABLED.

Run every named fallback. Never borrow an unavailable tool's verdict. Research, visual, judgement, and performance floors remain mandatory. Use PASS_RELEASE when all routes pass, PASS_RELEASE_DEGRADED when fallbacks satisfy every floor, and BLOCKED_CAPABILITY_FLOOR otherwise.

Flora uses https://agents.flora.ai/mcp with native HTTP OAuth. Its top-level tools are search_docs and execute. Charged generation requires explicit approval naming cost, batch, workspace, and export effects. Load integrations and Emil procedures.

Implementation and performance gate

Resource gate: run mise run validate before using package files named here.

Implement the smallest width without a media-query dependency, then add ascending min-width rules only when content needs them. Run the all-width sweep, keyboard and pixel checks, accessibility checks, and lab metrics at every declared breakpoint.

At the 75th percentile require LCP <=2.5s, INP <=200ms, CLS <=0.1, and the declared FCP and TTFB budgets. Keep CrUX or PageSpeed field data separate. Record UNAVAILABLE_FIELD_DATA when absent. Load implementation and performance.

Judgement and motion

Resource gate: run mise run validate before using package files named here.

Apply the locked design-engineering, animation, vocabulary, Apple-oriented, opportunity, improvement, prototype, review, UI-library, and toast procedures when their triggers match. Motion must support state, causality, orientation, feedback, or one restrained delight moment. Load composition and motion and judgement.

Determinism

Use sorted UTF-8 JSON, stable IDs, fixed query limits, integer scores, UTF-8 byte-order tie breaks, bounded repair, source locks, and SHA-256. Freeze selected generated bytes. Provider reruns are not replay proof. Never store secrets or fabricate web, browser, vision, validator, access, or performance results.

Package map

• validation owns fixtures, evidence, repair, and replay.
• source coverage owns revisions, authority, drift, and privacy.
• mise run breakpoint-rules enforces ascending completeness.
• mise run prompt-corpus verifies and retrieves exact public prompt bytes.
• assets/schemas.json defines packet structure.
• assets/source-lock.json fixes revisions and endpoints.
• assets/tool-registry.json names triggers and fallbacks.
• assets/prompt-manifest.json and the uncompressed YAML shards under assets/prompts/ bind every prompt.
• assets/fixtures/ contains full, degraded, and named failing packets.
• evals/ binds the eight native fixtures to public behavior, trigger, speed, contract, rubric, mapping, and lineage records.
• Run the one-entry local gate with mise run ci; see release validation, failure rejection, and prompt-corpus verification for complete command evidence.

Release

Release only when links and locks resolve, full and degraded fixtures replay byte-identically, every negative fixture returns its named block code, every prompt and tool route verifies, available external validators have no veto, native fallbacks cover unavailable routes, every breakpoint has browser, pixel, access, and performance proof, and the frozen artifact replays without a provider rerun.

Factory execution contract

The accepted outcome is: Design and verify a mobile-first page whose conversion path remains usable across responsive breakpoints. Preserve current mobile-first page behavior while changing its smallest owner.

1. Freeze the current package with mise run ci and record its digest.
2. Run mise run domain-research-policy, then judge the current mobile-first page sources and counterevidence.
3. Run mise run agentic-request for the named mobile-first page operation. Keep semantic choices with the model.
4. Run mise run decision-policy, mise run ci, and the behavioral evals. Return to the lowest failed owner.
5. Run mise run invocation-policy -- <receipt> and account for every task or its domain-specific non-use.
6. Optionally run mise run improvement-policy. Keep one changed dimension only if no protected dimension regresses.

Load assets/use-case-contract.json through mise run use-case-policy and evals/evals.json through mise run evals only when their contracts are needed.

Mise owns repeatable mechanics, ordering, receipts, and checks. The model owns interpretation, causal judgment, creative work, and direct perception that code cannot supply. Stop on missing authority, stale evidence, or a failed gate.