agentsclimarketplace

Dmc best practices

Skill BjornMelin/dev-skills/skills/dmc-best-practices

AgentSkills library: reusable skills for AI coding agents (AI SDK, Codex, LangGraph, Supabase, Docker, Vitest, pytest, Streamlit, Zod).

Install
npx -y skills add BjornMelin/dev-skills --skill dmc-best-practices

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Dash Mantine Components (DMC) best practices and performance optimization guidelines. Use this skill when writing, reviewing, or refactoring Dash apps with DMC to ensure optimal patterns. Triggers on: DMC components, Mantine styling, Dash callbacks, dcc.Store, theming, or performance optimization in Plotly Dash applications.

SKILL.md

5.8 KB, ~1.4k tokens by cl100k_base, as published. Nobody here has run it

DMC Best Practices

Definitive best practices for building Dash applications with Dash Mantine Components. Rules are organized by impact level and category.

Priority Categories

PriorityCategoryImpactPrefixRules
1ArchitectureCRITICALarch-4
2CallbacksCRITICAL/HIGHcallback-6
3StylingHIGH/MEDIUMstyle-5
4Data ManagementHIGHdata-4
5PerformanceMEDIUM-HIGHperf-3
6Forms & ValidationMEDIUMform-2
7ThemingMEDIUMtheme-3
8DMC v2.x MigrationsMEDIUMv2-2
9AccessibilityMEDIUMa11y-1

Top 10 Critical Rules

  1. Wrap layout in MantineProvider - All DMC components require it
  2. Never modify global variables in callbacks - Breaks multi-worker deployments
  3. Use State not Input for values that shouldn't trigger callbacks
  4. Define callbacks before app.run() - Registration must happen first
  5. Prevent circular callbacks - Outputs feeding inputs cause infinite loops
  6. Return JSON-serializable values - Only dict, list, str, number, bool, None
  7. Use static CSS selectors - Never target .m_* dynamic classes
  8. Custom colors need 10 shades - Exactly 10 (0=lightest, 9=darkest)
  9. Use dcc.Store for client data - Not global variables
  10. Debounce text inputs - Limit callback firing on rapid changes

Rules Index

Architecture (CRITICAL)

Callbacks (CRITICAL/HIGH)

Styling (HIGH/MEDIUM)

Data Management (HIGH)

Performance (MEDIUM-HIGH)

Forms & Validation (MEDIUM)

Theming (MEDIUM)

DMC v2.x Migrations (MEDIUM)

Accessibility (MEDIUM)

Full Reference

See AGENTS.md for the complete compiled reference with all rules expanded.

UI Audit Contract

When DMC review output needs machine-readable evidence, shape findings as ui_audit.v1:

  • target.framework: dmc
  • id: dmc.<rule-id> such as dmc.arch-mantine-provider
  • category: map DMC rule families deterministically: architecture -> layout, callbacks -> state, styling -> layout, data -> state, performance -> performance, forms -> interaction, theming -> visual, migration -> migration, and accessibility -> accessibility
  • severity: CRITICAL and HIGH rules become error; MEDIUM-HIGH and MEDIUM rules become warning; lower-risk notes become info
  • locations: repo-relative files or components when known
  • docs: the relevant rule markdown path plus external component docs when the rule cites them

Use observations for inventory facts such as detected DMC version, theme configuration, or callback counts that do not by themselves require a fix.

What ships with it: 32 files

100.5 KB alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.