Design Intelligence Engine Research Report

Open source or product claim? The audit checks the repo, license and releases, tests BM25 retrieval, and separates self-description from reproducible results.

Try Deep Research

Loading preview...

Start from this prompt

Assesses whether UI-UX-Pro-Max-Skill is an existing open-source skill, a design framework or an unverified product claim, and re-checks its design generation pipeline.

Audit the knowledge base and reasoning

Changes only the evaluation axis: audit how the asset library, rules, retrieval ranking, anti-pattern filtering and conditional decisions are implemented in code, and check recommendation consistency with reproducible queries.

Try Deep Research

Assess whether UI-UX-Pro-Max-Skill is an existing open-source skill, a design framework or an unverified product claim, and re-check its design generation pipeline. Use the code repository, version releases, license, install docs, configuration and examples accessible on the day of execution as primary evidence; verify the maintaining entity, versions, tech stack, knowledge-base size, BM25 or other retrieval logic, industry rules, anti-pattern filtering, output formats and supported platforms; note the query time for stars, compatibility counts and capability figures. Keep the project's self-description, mechanisms visible in code, reproducible experiment results, the Serenity Spa demo and editorial design judgment separate; do not declare verified intelligent reasoning or cross-platform quality just because templates or examples exist.

Deliver a project identity and version dossier, an input-to-output data-flow diagram, a table of rule and asset sources, reproducible install and invocation records, a cross-stack comparison of the same task, and a requirement—recommendation—implementation trace for the Serenity Spa case. Test information architecture, consistency, responsive layout, error states and maintainability with real tasks; check keyboard, focus, semantics, contrast, zoom and motion against WCAG 2.2 AA. Record the privacy boundaries of telemetry, external models, font or asset requests, prompts and project data, and do not upload real sensitive data. Clearly separate design claims, static rule matching and verified capabilities, and list failure samples and items still to verify.

Compare cross-stack generation quality

Changes only the evaluation axis: for the same interface requirement, compare Web, native mobile and cross-platform outputs on semantics, component structure, state coverage, responsive behavior and maintenance cost.

Try Deep Research

Assess whether UI-UX-Pro-Max-Skill is an existing open-source skill, a design framework or an unverified product claim, and re-check its design generation pipeline. Use the code repository, version releases, license, install docs, configuration and examples accessible on the day of execution as primary evidence; verify the maintaining entity, versions, tech stack, knowledge-base size, BM25 or other retrieval logic, industry rules, anti-pattern filtering, output formats and supported platforms; note the query time for stars, compatibility counts and capability figures. Keep the project's self-description, mechanisms visible in code, reproducible experiment results, the Serenity Spa demo and editorial design judgment separate; do not declare verified intelligent reasoning or cross-platform quality just because templates or examples exist.

Deliver a project identity and version dossier, an input-to-output data-flow diagram, a table of rule and asset sources, reproducible install and invocation records, a cross-stack comparison of the same task, and a requirement—recommendation—implementation trace for the Serenity Spa case. Test information architecture, consistency, responsive layout, error states and maintainability with real tasks; check keyboard, focus, semantics, contrast, zoom and motion against WCAG 2.2 AA. Record the privacy boundaries of telemetry, external models, font or asset requests, prompts and project data, and do not upload real sensitive data. Clearly separate design claims, static rule matching and verified capabilities, and list failure samples and items still to verify.

Review usability, accessibility and privacy

Changes only the evaluation axis: use the Serenity Spa case to review usability, WCAG 2.2 AA, failure states and privacy data flows, separating visual persuasiveness from tested quality.

Try Deep Research

Assess whether UI-UX-Pro-Max-Skill is an existing open-source skill, a design framework or an unverified product claim, and re-check its design generation pipeline. Use the code repository, version releases, license, install docs, configuration and examples accessible on the day of execution as primary evidence; verify the maintaining entity, versions, tech stack, knowledge-base size, BM25 or other retrieval logic, industry rules, anti-pattern filtering, output formats and supported platforms; note the query time for stars, compatibility counts and capability figures. Keep the project's self-description, mechanisms visible in code, reproducible experiment results, the Serenity Spa demo and editorial design judgment separate; do not declare verified intelligent reasoning or cross-platform quality just because templates or examples exist.

Deliver a project identity and version dossier, an input-to-output data-flow diagram, a table of rule and asset sources, reproducible install and invocation records, a cross-stack comparison of the same task, and a requirement—recommendation—implementation trace for the Serenity Spa case. Test information architecture, consistency, responsive layout, error states and maintainability with real tasks; check keyboard, focus, semantics, contrast, zoom and motion against WCAG 2.2 AA. Record the privacy boundaries of telemetry, external models, font or asset requests, prompts and project data, and do not upload real sensitive data. Clearly separate design claims, static rule matching and verified capabilities, and list failure samples and items still to verify.