Design Award Match

Design Award Match

Purpose

Identify the most defensible award, program, track, and category for a design project. Treat fit scores as transparent decision aids, never as probabilities of winning.

Scope

• Extract decision-relevant project facts.
• Pre-filter the configured award allowlist with stable eligibility gates.
• Verify all dynamic requirements on current official pages.
• Compare project evidence with published criteria and observable winner trends.
• Score, rank, and explain strategic fit.
• Stop after recommendation; do not audit every submission file or redesign the project.

Use $design-award-search for verified same-category winners. Route file format, size, naming, declarations, and upload completeness to $design-submission-check.

Input Contract

Accept a brief, images, PDF, portfolio page, or structured JSON. Extract or request only facts that can change the recommendation:

• primary function, target user, and use context;
• innovation and supporting evidence;
• project state and completion, launch, or release date;
• applicant type, student status, country or region;
• candidate awards, intended cycle, budget, and geographic constraints.

Use the canonical values in references/category-crosswalk.json. If the primary function is unclear, ask one short question. If an eligibility fact is missing, continue with Eligibility: Unknown; never assume a pass.

Offer this template when the user asks how to use the skill:

Project: {name and one-sentence description}
Primary function: {job performed or problem solved}
Target user / context: {optional}
Innovation and evidence: {optional}
Development status / launch date: {optional}
Applicant: {student, individual, studio, company; country/region}
Candidate awards: {optional; omit to search the supported allowlist}
Submission cycle / constraints: {optional year, region, budget}