Repository navigation
[Feature] Add curated UI source adapters and stack compatibility resolver #142
Description
Parent: #120
Migrated from: EagleFox31/appfactory-project-automation#97
Goal
Let AppFactory choose the safe adoption mode for vetted UI sources instead of treating every repository like the same stack.
Initial source classes
- external discovery/MCP adapters such as 21st.dev;
- reviewed copy/adapt sources such as Magic UI, UI Layouts and beUI;
- compatible registry/block sources such as shadcn/Tailark;
- guideline/reference sources such as Web Interface Guidelines.
Scope
- resolve native, adapt, reference-only, unsupported;
- separate external adapters from code-copy sources;
- block registry installs when the required stack is absent;
- avoid duplicate animation runtimes;
- expose source selection as pure/testable logic;
- keep external services optional.
Proof of Done
- React/Vite+CSS chooses adaptation/reference rather than installing Tailwind;
- React/Next+Tailwind can use approved registry sources;
- non-React consumers get reference-only unless an adapter exists;
- no arbitrary upstream install command executes;
- compatibility tests cover the initial allowlist.
Activity
EagleFox31 commentedon Oct 10, 2026
Delivered — 2026-10-10
Merged PR #148 into
main, commit0ab983a26d4e1740fbc64690d6fb8758de544b23.Evidence
ui-registry/wow-adapters.json+ schema and pureui-registry/wow-resolver.mjs.native/adapt/reference-only) is separated from central legal/policy disposition, producingreference-onlyorunsupportedwhere permissions are missing.scripts/wow-frontend-plan.mjsnow includesadapterResolutions, tested throughnpm run test:ui-registry.Limit: #142 delivers selection/planning, not actual third-party code installation, connected hosted tool execution, or visual browser QA. The next acceptance gates are rendered QA in Project Automation #99 and the Commerce Factory pilot #143; reusable native motion recipes live in the landing template #6.