UI/UX system for Claude Code: 71 plugins, 93 agents, 74 skills. Design mastery, archetypal design, accessibility, and frontend workflows in one validated plugin marketplace.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
HermeticOrmus/LibreUIUX-Claude-Code has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in HermeticOrmus/LibreUIUX-Claude-Code respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 7.5 places HermeticOrmus/LibreUIUX-Claude-Code in the D tier.
The external contributor pull request merge rate for HermeticOrmus/LibreUIUX-Claude-Code is 0.0%, based on public PR activity from non-core contributors.
HermeticOrmus/LibreUIUX-Claude-Code currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in HermeticOrmus/LibreUIUX-Claude-Code welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/HermeticOrmus/LibreUIUX-Claude-Code?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Source: pantry/2026-09-30-pantry-queue.md, atom #1. Menu: pantry/MENU.md. How to contribute: CONTRIBUTING.md in this repo (Ways to contribute). Done when advanced/mcp-servers/chrome-devtools/README.md exists, so the README's "Set up Chrome DevTools MCP" link resolves; it gives a claude mcp add command for chrome-devtools-mcp whose flags match claude mcp add --help and the upstream client guide, and one worked loop (the prompt, the screenshot step, the fix) that names the mcp-integrations:browser-devtools-mcp skill Verify on repo. Verify skill in repo: none in repo Evidence Map: Chrome DevTools MCP, OneRedOak design review. Matrix: Checks the rendered page in a browser (Us P). X: gmchande, AnandChowdhary, marcospereeira, shao__meng Take this Anyone can take this. Comment that you are on it, then open a pull request that says Closes #<this issue>. CI validates every plugin and runs a clean install on your PR. Questions are welcome in this repo's Discussions. Rules Any branch (default me
Menu atom ui-commands-plugin on this repo's Menu (pantry/MENU.md, arriving with #9). Its Done-when below is what a pull request is checked against. What .claude/commands/ (ui-critique, ui-modern, ui-responsive, ui-review, ui-synth) and .claude/agents/synthesis-master.md sit outside every plugin, so /plugin install never delivers them. Done when A new plugins/<name>/ holds ui-modern, ui-critique, ui-responsive, ui-review, ui-synth and the synthesis-master agent, each with a routing description; claude plugin validate --strict plugins/<name> passes; after a clean-config install, claude plugin details <name>@libreuiux lists all six; the root .claude/ files stay where they are; advanced/slash-commands/README.md exists and documents both install paths Take this Anyone can take this. Comment that you are on it, then open a pull request that says Closes #<this issue>. CI validates every plugin and runs a clean install on your PR. Questions are welcome in this repo's Discussions. New here? Se
What: the README links advanced/mcp-servers/chrome-devtools/ and advanced/slash-commands/, and neither exists. Done when: advanced/mcp-servers/chrome-devtools/ explains connecting a Chrome DevTools MCP server with claude mcp add and using it with the UI agents for live inspection, and advanced/slash-commands/ explains writing a command in a plugin (commands/<name>.md with frontmatter). Every command shown is checked against claude --help / claude mcp add --help. The README links resolve. New here? See CONTRIBUTING.md. Comment that you are taking this, then open a pull request that says Closes #<this issue>. CI validates the plugins and runs a clean install on your PR. Tracking: this issue spans two atoms on the Menu (pantry/MENU.md, arriving with #9): browser-loop-guide (the Chrome DevTools MCP guide) and ui-commands-plugin (which also writes advanced/slash-commands/README.md, see #8). If you take one part, say which, and its Menu issue will point back to your PR.
Menu atom case-studies on this repo's Menu (pantry/MENU.md, arriving with #9). Its Done-when below is what a pull request is checked against. What the README links intermediate/examples/saas-dashboard/ and intermediate/examples/ecommerce-product/, and neither folder exists. Done when intermediate/examples/saas-dashboard/README.md and intermediate/examples/ecommerce-product/README.md exist, so both "See full case study" links resolve; each shows the exact prompts, the template or design-system file it started from, and before and after code or screenshots a reader can reproduce with the plugins it names Take this Anyone can take this. Comment that you are on it, then open a pull request that says Closes #<this issue>. CI validates every plugin and runs a clean install on your PR. Questions are welcome in this repo's Discussions. New here? See CONTRIBUTING.md. Comment that you are taking this, then open a pull request that says Closes #<this issue>. CI validates the plugins and runs a c
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to HermeticOrmus/LibreUIUX-Claude-Code, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of HermeticOrmus/LibreUIUX-Claude-Code acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
HermeticOrmus/LibreUIUX-Claude-Code has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 7.5 places HermeticOrmus/LibreUIUX-Claude-Code in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, HermeticOrmus/LibreUIUX-Claude-Code currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for HermeticOrmus/LibreUIUX-Claude-Code are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.