GitShow/thedaviddias/ux-patterns-for-developers
thedaviddias

ux-patterns-for-developers

๐Ÿงฉ Developer ecosystem for UX patterns: comprehensive docs, ready-to-use components, and real-world examples

by thedaviddias
best-practicesdocumentation-websitefrontendpatternsuxux-designux-patternsweb-design
Star on GitHubForkWebsite

MDX

215 stars17 forks3 contributorsActive ยท 1d agoSince 2024

Meet the team

See all 3 on GitHub โ†’
thedaviddias
thedaviddias311 contributions
dependabot[bot]Bot
dependabot[bot]10 contributions
Lowkaze
Lowkaze1 contribution

Languages

View on GitHub โ†’
MDX49.2%
TypeScript43.9%
JavaScript6.2%
Handlebars0.4%
CSS0.3%

Commit activity

Last 12 weeks ยท 15 commits

Full graph โ†’

Community health

4 of 6 standards met

Community profile โ†’
100
โœ“READMEโœ“Licenseโœ“Contributingโœ“Code of Conductโ—‹Issue Templateโ—‹PR Template

Recent PRs & issues

Active ยท 3 in progress ยท Last activity 1d ago
See all on GitHub โ†’
rohan-tessl
feat: improve skill generation scores and add Tessl review workflowOpenPR

Hey @thedaviddias ๐Ÿ‘‹ I ran your skills through at work and found some targeted improvements. Since your skills are auto-generated via , I improved the generation script () rather than editing SKILL.md files directly โ€” so improvements persist through regeneration and benefit all 93 skills. Here's the before/after for the 5 lowest-scoring skills: This PR improves all 93 generated skill(s) in the repo by targeting the generation source. What changed in the generation script (pattern-skills-lib.mjs) Added to frontmatter for all generated skills Added array derived from slug, title, and aliases for better discoverability Improved description quality โ€” descriptions now include the first sentence from frontmatter (the "what") plus a "Use when..." clause (the "when"), and alias trigger terms when available Fixed description grammar โ€” changed fallback from "Use when implementing..." to "Use when you need to..." which reads correctly with verb-based summaries Added inline code examples โ€” extracts the first code block from the MDX "Examples" section and includes it as a "Quick-start example" in the SKILL.md body Merged "When to use" and "When to avoid" into a single compact section Improved implementation workflow โ€” 5 concrete steps referencing with specific validation checkpoints instead of abstract directives Added early progressive disclosure โ€” blockquote at top directing to for full examples What changed in the test (pattern-skills-lib.test.mjs) Updated description assertion regex to accommodate the richer description format Added assertions for and in generated output Tessl Skill Review GitHub Action โœ… I've also included a GitHub Action () that automatically reviews any changed in future PRs and posts scores as a PR comment. What this gives you: ๐Ÿ” Automatic runs on every PR touching ๐Ÿ’ฌ One updated PR comment with scores and improvement feedback ๐Ÿ”“ Zero extra accounts โ€” contributors don't need a Tessl login; only is used โœ… Non-blocking by default* โ€” feedback-only, no surprise red CI (add later if you want a hard gate) ๐Ÿ“ˆ Covers future skills incrementally as contributors edit them Note: this workflow complements your existing โ€” it reviews skill quality on PRs, while your existing workflow verifies generated files stay in sync. Want automatic AI optimization on every SKILL.md change? ๐Ÿš€ The action I've added gives you review scores on PRs. We also have a more powerful variant โ€” โ€” that can: Run AI-powered optimization suggestions on every PR (requires adding as a repo secret) Let contributors accept suggested improvements by commenting Still works in review-only mode with zero secrets Interested? Tick the box and I'll raise a follow-up PR: [ ] Yes please! Add the action so every SKILL.md PR gets AI optimization suggestions + the flow [ ] No thanks โ€” the review scores action is enough for now Honest disclosure โ€” I work at @tesslio where we build tooling around skills like these. Not a pitch โ€” just saw room for improvement and wanted to contribute. Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at this Tessl guide and ask it to optimize your skill. Ping me โ€” @rohan-tessl โ€” if you hit any snags. Thanks in advance ๐Ÿ™ Summary by CodeRabbit Release Notes New Features Pattern skill pages now include automatically extracted Quick-start code examples. Enhanced skill metadata with invocability markers and computed trigger information. Documentation* Consolidated "When to use" and "When to avoid" sections with improved clarity and labeling. Updated skill descriptions to include trigger alias information for better context.

rohan-tessl ยท 2mo ago

Recent fixes

View closed PRs โ†’
thedaviddias
feat(web): remove pattern view countsMergedPR

Why The "X views" badge on pattern pages fetched (OpenPanel) client-side on every page view โ€” a function invocation per view with no real value, and the upstream call was failing auth () so it always showed 0 anyway. Changes : drop the view count, the fetch, and the React hooks. It's now a plain (non-client) component that renders only the frontmatter-driven popularity badge. Delete the now-unused route and its function entry. Effect Removes the per-view invocations entirely (further GB-Hrs reduction). Makes the OpenPanel "enable Export" todo moot. ๐Ÿค– Generated with Claude Code Summary by CodeRabbit Refactor Simplified pattern stats display to focus on popularity badges only. Removed view-count loading and formatting from the stats UI. Bug Fixes Removed the page stats endpoint, eliminating an extra stats fetch and related error states for missing page data. Chores** Streamlined serverless configuration by removing the dedicated stats function settings.

thedaviddias ยท 1d ago
thedaviddias
fix(web): narrow MCP host blocking to scanners onlyMergedPR

Why PR #256 added bad-bot blocking on , but it reused the general bad-bot list which matches generic HTTP clients (, , , ) โ€” exactly what legitimate MCP callers use. That would 403 real programmatic clients. Fix Add (matches ) to . On the MCP host, hard-block only those scanners; rely on the existing per-IP rate limit (30/window) to contain abuse from everything else. Main-site (non-MCP) traffic still uses the full bad-bot list unchanged. ๐Ÿค– Generated with Claude Code

thedaviddias ยท 1d ago
thedaviddias
perf(web): let content page regens finish instead of 504-loopingMergedPR

Problem Cold ISR regenerations of MDX pages (glossary/patterns/pattern-guide) exceed the 15s function ceiling and 504. A timed-out regen writes nothing to cache, so the next request re-runs the same cold render and times out again โ€” an unbounded loop of 15s renders that never caches. This is the core driver of the deploy-day GB-Hrs spikes (verified post-#256: ). Fix Give the MDX-rendering page functions max CPU + duration headroom in so the regen completes and populates the cache: , : (~2ร— CPU), : , : , After the first successful regen the page serves as static HTML (no function), so the higher memory is only paid on rare post-deploy/weekly regenerations โ€” net GB-Hrs drop because the retry loop is broken. Follow-up (not in this PR) Eliminate runtime MDX compilation entirely (render velite-precompiled body) โ€” bigger change, 6 files depend on runtime mdxScope. OpenPanel returns 401 "Client is not allowed to export" โ€” enable Export on the OpenPanel client (dashboard). ๐Ÿค– Generated with Claude Code Summary by CodeRabbit Chores** Updated route-specific runtime settings for several web pages, including memory and execution time limits, to improve reliability for high-load pages.

thedaviddias ยท 1d ago
Structured data for AI agents

Repository: thedaviddias/ux-patterns-for-developers. Description: ๐Ÿงฉ Developer ecosystem for UX patterns: comprehensive docs, ready-to-use components, and real-world examples Stars: 215, Forks: 17. Primary language: MDX. Languages: MDX (49.2%), TypeScript (43.9%), JavaScript (6.2%), Handlebars (0.4%), CSS (0.3%). Homepage: https://uxpatterns.dev Topics: best-practices, documentation-website, frontend, patterns, ux, ux-design, ux-patterns, web-design, web-development. Open PRs: 3, open issues: 0. Last activity: 1d ago. Community health: 100%. Top contributors: thedaviddias, dependabot[bot], Lowkaze.

ยท@ofershap

Replace github.com with gitshow.dev