Open-source design-method engine for Claude Code, Codex & Cursor. 23 agent skills for fixed design judgment, multiple grammars, semantic palettes, reference compilation, and evidence-verified UI. MIT.
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 79%
Response Time: 5d
First Timer Success: -
bitjaru/styleseed has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in bitjaru/styleseed respond to incoming external pull requests in approximately 113.1 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 51.0 places bitjaru/styleseed in the B tier.
The external contributor pull request merge rate for bitjaru/styleseed is 78.9%, based on public PR activity from non-core contributors.
bitjaru/styleseed currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source design-method engine for Claude Code, Codex & Cursor. 23 agent skills for fixed design judgment, multiple grammars, semantic palettes, reference compilation, and evidence-verified UI. MIT.
Collaborative maintainer environment in bitjaru/styleseed. Reviews community pull requests with focus on project quality.
Discussions in bitjaru/styleseed focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/bitjaru/styleseed?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~73 hours (96% approval). Large PRs (>500 lines) take ~543 hours (36% approval). Keep your diff compact for rapid review.
Why Skins are the smallest visual extension surface in StyleSeed: one metadata file and one semantic-token stylesheet. An original community skin is a useful first visual contribution and creates a result the contributor can share. Scope Create one original, generically named skin at: skins/<your-skin>/skin.json skins/<your-skin>/theme.css Start from skins/arc/ only as a file-shape reference. Choose a distinct but reusable visual posture—for example archival, botanical, high-contrast editorial, or technical monochrome. Acceptance criteria The name is generic and does not use another company's trademark as the skin identity. No logos, copied product layouts, proprietary assets, or protected brand material. Required semantic surface, text, action, status, focus, radius, and shadow tokens are present for light and dark modes. Contrast remains readable and status colors keep stable meanings. npm run build --prefix demo-pricing and git diff --check pass. Attach a current screenshot from
Why Roadmap issue #9 will define the full public adapter specification. The existing document-report profile explains the principles but lacks the copy-paste lock example already available for social-carousel. Scope Add one concrete document-report lock example to engine/ADAPTERS.md that declares: artifact type and paper size margins, header/footer, and reading measure editable source and PDF export page-by-page render evidence widows/orphans, clipped tables, links, page numbers, and accessibility checks Add one short failing example showing a web-layout assumption that should not cross into a paginated report. Acceptance criteria The example follows the existing adapter authority boundary: StyleSeed owns judgment; the renderer owns physical output constraints. It is renderer-neutral and does not require one commercial document tool. It does not invent a new adapter schema or close the parent specification issue. Run node demo-pricing/scripts/build-llms.mjs, node scripts/validate-en
Why Roadmap issue #8 covers Korean typography and UX writing broadly. This is one small, reviewable slice: examples where Hangul, Latin product names, numerals, money, and units appear in the same UI string. Scope Extend engine/UX-WRITING.md with a short mixed-script section containing at least three source-backed before/after examples, such as: Hangul copy with an English product or plan name Korean currency or percentage text with tabular numerals A CTA or status message containing a number and unit Explain the reusable decision behind each example. Do not turn one product's house style into a universal rule. Acceptance criteria Each example has Do / Don't / Why. At least one primary Korean-language typography or UX-writing source is linked. Applicability and one counterexample are stated. The existing Toss-derived section remains clearly attributed. Run node demo-pricing/scripts/build-llms.mjs, node scripts/validate-engine.mjs, and git diff --check. Commit any regenerated mirrors
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 bitjaru/styleseed, 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 bitjaru/styleseed acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.9% were successfully merged into the primary branch.
bitjaru/styleseed has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 days+. 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 51.0 places bitjaru/styleseed in the Solid tier.
The external pull request merge rate is 78.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, bitjaru/styleseed currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for bitjaru/styleseed 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.