ux-architect

Designs request flows, form behavior, states, and acceptance criteria for an auto-parts landing page.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/prostoali2207-gif/auto-parts-landing --skill ux-architect-prostoali2207-gif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-architect
Source: https://github.com/prostoali2207-gif/auto-parts-landing/tree/main/.agents/skills/ux-architect
Command: npx skills add https://github.com/prostoali2207-gif/auto-parts-landing --skill ux-architect-prostoali2207-gif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an approved conversion requirement into a concrete, implementation-ready interaction design for the Das Motors UAE auto-parts request landing page, ensuring customers can submit a valid part request that the CRM integration actually accepts. ## Core Features & Use Cases - Information Requirements Modeling: Separates system-required, task-required, alternative-identifier, and optional data such as VIN versus make/model/year and OEM number versus photo. - Form, States & Recovery Design: Specifies field validation, error behavior, data preservation, photo upload handling, and post-submission states for mobile-first traffic. - Use Case: After a Conversion Agent defines a problem with the part-request form, use this Skill to produce the exact flow, field rules, mobile stress test, and frontend handoff contract, then review the rendered result with a PASS/REVISE/BLOCK verdict. ## Quick Start Use the ux-architect skill to design the Find My Part request flow for the landing page based on the conversion contract and produce the frontend handoff.

Frequently Asked Questions about ux-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a part request form for an auto-parts landing page?

Start from the conversion contract, define the user job, then model information requirements separating system-required fields from alternatives like VIN or make/model/year. Specify validation, states, recovery, and mobile behavior before handing off to frontend.

How should VIN and vehicle identification work in a request form?

Support alternative valid evidence: VIN or make plus model plus year. Explain what a VIN is near the field, allow normal paste and typing, and preserve the value after unrelated validation or network errors.

Does this Skill handle visual design or styling decisions?

No, it owns only how the interaction works. Decorative styling belongs to the Visual Director, commercial diagnosis to the Conversion Agent, and implementation to the Frontend Agent.

When should I not change an existing UX flow?

Output NO UX CHANGE when the Conversion Agent has not established a material interaction problem, the current flow is validated, or the issue is purely visual styling or downstream sales operations.

What makes a form submission count as a real success?

Success requires the downstream CRM request to be accepted, not just a browser success state. The post-submission experience must confirm receipt, explain next steps, and avoid unconfirmed promises about response times.