@prestyj/cli 5.5.0 → 5.6.0

package/assets/skills/evidence-led-ui/LICENSES.md

@@ -0,0 +1,68 @@
+# Licenses and Attributions
+
+## Distributed third-party material
+
+### VoltAgent/awesome-design-md
+
+- Repository: https://github.com/VoltAgent/awesome-design-md
+- Pinned commit: `664b3e78fd1a298ba11973822da988483256d4b4`
+- License: MIT
+- Copyright: Copyright (c) 2026 VoltAgent
+- Included material: `corpus/awesome-design-md/design-md/*/DESIGN.md`
+- License copy: `corpus/awesome-design-md/LICENSE`
+
+The upstream files are provided “as is.” Their analyses of public websites do not transfer ownership of third-party trademarks, proprietary fonts, brand assets, or visual identities.
+
+## Referenced but not distributed
+
+The following works informed research comparisons. Their source text, assets, databases, and code are not copied into this skill.
+
+### Anthropic frontend-design
+
+- Source: https://github.com/anthropics/skills/tree/main/skills/frontend-design
+- Repository license: Apache License 2.0
+- Use here: process-level comparison only; the resulting workflow and wording are original synthesis.
+
+### Leonxlnx/taste-skill
+
+- Source: https://github.com/Leonxlnx/taste-skill
+- License: MIT
+- Use here: research comparison of common landing-page failure patterns; no files copied.
+
+### NextLevelBuilder/ui-ux-pro-max-skill
+
+- Source: https://github.com/nextlevelbuilder/ui-ux-pro-max-skill
+- License: MIT
+- Use here: research comparison of heuristic-database organization; no files copied.
+
+
+## Standards and policy references
+
+### WCAG 2.2
+
+- Source: https://www.w3.org/TR/WCAG22/
+- Status checked 2026-07-13: W3C Recommendation, 12 December 2024
+- Use here: linked accessibility conformance floor; W3C text is not redistributed.
+
+### WCAG 3.0
+
+- Source: https://www.w3.org/TR/wcag-3.0/
+- Status checked 2026-07-13: W3C Working Draft, 3 March 2026
+- Use here: status clarification only; it is not presented as the conformance target.
+
+### Refero Styles
+
+- Site: https://styles.refero.design/
+- Robots policy checked: https://styles.refero.design/robots.txt on 2026-07-13
+- Included material: none
+- Allowed runtime use: authorized Refero MCP or user-provided licensed/authorized export only
+
+## Icons, fonts, and design-system documentation
+
+Lucide, Material Symbols, Phosphor, Carbon Design System, Google Fonts, and web.dev are linked as implementation references in `references/craft-rulings.md` and `references/provenance.md`. No icon package source, font binary, design-system source, or documentation text from those projects is bundled in this skill. Implementations must follow the selected package/font license and the host project's dependency, privacy, CSP, and attribution policies.
+
+W3C WAI and Internationalization guidance, WHATWG HTML, MDN, web.dev Baseline and Web Vitals, DTCG, Apple, Android, FTC, OWASP, OpenAI Apps SDK UX guidance, Microsoft HAX, the Agent Skills specification, and Anthropic skill-authoring documentation are linked as production-practice or package-structure references. No source text, example code, platform asset, specification, or report from those sources is redistributed. Short numeric thresholds, standard names, and factual status descriptions are attributed in `references/provenance.md`.
+
+## Original material
+
+`SKILL.md`, `scripts/*.mjs`, `data/observations.json`, `fixtures/briefs.json`, and `references/*.md` are original work produced for this installation, except for factual source names, links, measured corpus excerpts represented as short source slugs, and the third-party corpus listed above.

package/assets/skills/evidence-led-ui/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: evidence-led-ui
+description: Use for web/mobile UI changes or evaluation: pages, components, dashboards, design systems, responsiveness, accessibility, or visual polish, even without explicit design request. Exclude database/API schemas, CLI output, copy-only work, standalone image/SVG generation, and description-only tasks.
+license: See LICENSES.md
+compatibility: Full review requires filesystem inspection and rendered screenshots; web research and browser/device tooling are optional and unavailable checks must be reported honestly.
+---
+
+# Evidence-Led UI
+
+Use this skill for web or mobile interface creation, redesign, implementation, styling, and review.
+
+## Governing rule
+
+Inspect before inventing. Preserve the project's visual language unless the user explicitly requests a redesign. Treat corpus findings as conditional observations, not official brand truth, universal rules, or a house style.
+
+Aesthetic distinction is contextual. Semantic structure, operability, responsive stability, performance, honest content, accessibility, and user trust are the non-negotiable floor.
+
+## Binding craft defaults
+
+Apply these on every UI task. Read `references/craft-rulings.md` when implementing or reviewing their details.
+
+- **No emoji UI:** Never use emoji as icons, bullets, status marks, or decoration unless explicitly requested. Reuse the project icon system; otherwise use one coherent icon package.
+- **Uniform geometry:** Align containers, columns, section edges, baselines, dividers, control heights, and repeated component anatomy. Break alignment only for a clear content reason.
+- **Reuse first:** Search for existing components, variants, tokens, utilities, icon wrappers, focus rings, and motion curves before creating new ones.
+- **Purposeful feedback:** Relevant hover, focus, press, selected, expanded, loading, success, and error states need clear feedback. Avoid abrupt changes when a short transition improves continuity.
+- **No generic hover lift:** Do not default to `translateY`, bobbing, floating, or scale-up on hover. Prefer color, border, underline, icon fill, opacity, or restrained shadow changes.
+- **No `transition: all`:** Name transition properties, reuse duration/easing tokens, and provide a reduced-motion path.
+- **Intentional type:** Reuse the existing type system. For net-new web work, select an appropriate modern family or pairing; do not use Arial, Helvetica, or bare `system-ui` as the aesthetic direction.
+- **Measured contrast:** Meet WCAG 2.2 contrast for text, controls, icons, focus, and meaningful graphics. Muted text must remain readable.
+- **Consistent flow:** Repeated navigation and actions keep the same order, labels, icons, placement, and behavior across sections and pages.
+- **No generated em dashes:** Do not write em dashes in user-facing UI copy unless explicitly requested or exact supplied source text must remain unchanged.
+
+## Reference map
+
+Resolve every path from the installed skill root. Load only what the task needs:
+
+- `references/craft-rulings.md`: implementation detail for the binding defaults above.
+- `references/production-contract.md`: pass/fail semantics, forms, accessibility, performance, resilience, platform, trust, AI, media, theme, and release checks. Read it for broad features, behavior changes, forms, navigation, data/AI interfaces, native work, performance work, or release review.
+- `references/archetypes.md`: surface-specific direction and relevant source slugs. Read for net-new UI, redesigns, or unresolved visual direction.
+- `references/observed-patterns.md`: measured corpus observations. Read only sections that answer a real design question.
+- `references/anti-defaults.md`: transferable AI-generated patterns to challenge. Read for broad visual work or generic-looking output.
+- `references/quality-rubric.md`: rendered scoring and revision gate. Read before critiquing broad output.
+- `references/methodology.md`: extraction method, denominators, and limitations. Read only to audit evidence.
+- `references/provenance.md` and `LICENSES.md`: sources, licenses, standards status, and Refero boundaries.
+
+Do not load `data/observations.json` or the raw corpus by default. Open a raw source only to audit one claim or inspect one selected exemplar. Never load the full corpus into context.
+
+## Workflow
+
+### 1. Inspect the project
+
+Inspect the nearest relevant routes, real content, shared components, semantic controls, tokens, theme, typography, icons, motion, screenshots, tests, responsive conventions, and existing states.
+
+Reuse the local system. Do not add a design library merely to obtain a look. For a net-new project with no neighbors, derive direction from the brief and matching archetype rather than choosing a fashionable default.
+
+### 2. Write a design read
+
+Resolve:
+
+- **Surface:** marketing, application UI, dashboard/data-dense, commerce/marketplace, editorial/content, documentation/developer tool, mobile/native, or one named hybrid with a clear leader.
+- **Audience:** user, expertise, environment, and access needs.
+- **Single job:** the one outcome this screen must make easiest.
+- **Task and risk:** frequency, decision cost, error cost, and time pressure.
+- **Content:** real hierarchy, density, variability, media, data, and longest plausible values.
+- **Platform:** viewport/window, input modes, support policy, navigation behavior, and framework conventions.
+- **Constraints:** existing tokens/assets, redesign scope, performance limits, and required tone.
+
+Infer missing facts from the project and state the inference. Ask only when code cannot resolve a genuine product or taste decision.
+
+### 3. Select evidence only when it helps
+
+For broad net-new work or a redesign, read the matching archetype and usually choose two aligned source slugs plus one contrast. Record why each applies.
+
+For a small change in an established system, local components and tokens may be sufficient. A frequency can support investigation, not automatically become a recommendation. Prefer local product evidence, then archetype evidence, then corpus-wide frequency.
+
+Refero is optional. Use it only through an authorized Refero MCP or user-provided authorized export. Do not scrape Refero, call undocumented endpoints, or access disallowed routes.
+
+### 4. Form one design thesis
+
+State one compact direction:
+
+- semantic color/type/icon/spacing/grid/motion roles and a reuse map;
+- first glance, second glance, primary action, and supporting evidence;
+- composition and uniform alignment rules;
+- reasons for borders, surfaces, shadows, blur, gradients, or imagery;
+- feedback, duration/easing, resting behavior, and reduced-motion equivalent;
+- one memorable device grounded in the subject, content, or interaction.
+
+One thesis leads. Do not combine several aesthetic directions into a mood-board compromise.
+
+### 5. Run the anti-default check
+
+For broad visual work, read `references/anti-defaults.md`. Flag emoji UI, mixed icon families, arbitrary misalignment, duplicated local styling, abrupt interaction, generic hover lift, generic type, generated em dashes, centered gradient heroes, glass cards, equal card grids, decorative eyebrows, random metric blocks, ubiquitous pills, dark-premium assumptions, fake terminals, floating screenshots, bento layouts, ambient motion, icon medallions, and invented proof.
+
+Keep a flagged pattern only after completing: **“This belongs because…”** with a product-specific reason. Replace choices that could survive unchanged in an unrelated product.
+
+### 6. Plan the complete task flow
+
+Plan only relevant states, but include the complete primary path and recovery:
+
+- loading, empty, error, retry, offline, success, disabled, and destructive outcomes;
+- hover, focus-visible, press, selected, expanded, and pending feedback;
+- keyboard order, accessible names/status, overlay focus, and drag alternatives;
+- narrow, intermediate, desktop, wide/resizable, pointer, touch, and no-hover behavior;
+- reduced motion, forced colors, zoom/reflow, long/localized/RTL text, missing media, and realistic data extremes.
+
+For broad behavior, forms, navigation, native, data/AI, performance, or release work, read and apply `references/production-contract.md`. A visual score cannot compensate for a relevant contract failure.
+
+### 7. Document broad work
+
+For a broad page, multi-screen feature, or redesign, create or update `DESIGN.md` with the design read, evidence, thesis, semantic tokens, reused primitives, craft system, components/states, responsive behavior, and applicable production checks. Keep a small component plan in work notes instead.
+
+### 8. Implement the product
+
+Use real project content and data. Label fixtures honestly. Never invent testimonials, customer logos, ratings, metrics, or claims as fact.
+
+Reuse dependencies and primitives. Use one coherent icon system. Maintain semantic controls, visible focus, keyboard operation, measured contrast, readable line lengths, stable adaptive layout, and reduced-motion support. Implement the complete planned flow, not only its first screenshot.
+
+The representative initial state must keep decision-critical information and the primary action visible or one obvious action away on desktop and mobile. Preserve selected context through master-detail recomposition. Keep demo, debug, and state-switching controls subordinate and non-obscuring.
+
+### 9. Critique rendered output once
+
+Capture representative desktop and narrow/mobile output. Score broad work with `references/quality-rubric.md`, record applicable production checks as pass/fail/unverified, remove one unnecessary decorative idea, revise the weakest criterion and any contract failure, then re-capture.
+
+Default to one critique-and-revision cycle. Run another only when evidence still fails the score or production gate. If a check is unavailable, report it as unverified instead of looping or substituting more polish.
+
+Broad work is complete at **20/24 or higher**, with no zero in accessibility, consistency and flow, responsive behavior, state completeness, or content authenticity, and only after applicable production checks pass. A small component must score 2 on every applicable quality-floor criterion.
+
+## Review-only mode
+
+Inspect the project and rendered output. Return findings ordered by impact, cite screenshot/code evidence, name the matching archetype when relevant, and recommend one resolved direction. Distinguish quality-floor defects from aesthetic opportunities.
+
+## Evidence discipline
+
+- Keep a numerator/denominator or numeric sample count with every corpus claim.
+- Treat source slugs as observations of selected public surfaces, not official systems or permission to reproduce a brand.
+- Never recommend a color, font, radius, theme, or layout solely because it is frequent.
+- State corpus gaps plainly. Mobile/native has zero direct documents in this snapshot; use platform guidance and device testing.
+- If local evidence conflicts with corpus evidence, follow the product and record why.

package/{LICENSE → assets/skills/evidence-led-ui/corpus/awesome-design-md/LICENSE}

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 KenKai
+Copyright (c) 2026 VoltAgent
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal