Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for design / product engineers who want to run a design workflow directly in their local coding agent (Cursor, Claude Code, Codex, Cline, Roo Code, GitHub Copilot) without going through a hosted design website; for designer-developers who want a SKILL.md + system-prompt.md design methodology that is harness-independent and resolves to the right tool map per environment; for product teams th
Who should use it
Who should skip it
Hold off on JimLiu/baoyu-design until it graduates from watchlist status with stronger evidence.
About this signal
JimLiu/baoyu-design is tracked by RepoRadar as a local design agent skill in the MIT Portable Claude Design Agent Skill (baoyu-de section. It was first seen on 2026-06-25 and last updated on 2026-06-25. The current verdict is 'worth watch' with a Silver tier and review needed setup difficulty. JimLiu/baoyu-design leads on novelty (10.0) and momentum (10.0); its lowest signal is setup ease (6.5), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned JimLiu/baoyu-design a composite score of 7.6 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1855.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Risk explanation
Conditional risk: review permissions, runtime environment, and data boundaries before production use.