Use when a component has a `disabled` state/variant, or when building a compound component that owns a disabled state — inherit/provide it via the shared disabled context so state flows from parent to sub-components.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add LedgerHQ/lumen --skill disabled-context --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Disabled Context?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ledgerhq-disabled-context)More formats (shields.io, HTML) on the badges page.
---
name: disabled-context
description: >-
Use when a component has a `disabled` state/variant, or when building a
compound component that owns a disabled state — inherit/provide it via the
shared disabled context so state flows from parent to sub-components.
paths: "libs/**/*.tsx"
---
# Shared disabled context
Source of truth: `libs/utils-shared/src/lib/context/disabledContext.tsx`
- **Consumers**: Any component with a `disabled` state/variant must use the shared disabled context so it inherits disabled state from parent components. Follow existing consumers (e.g. `BaseButton`, `Switch`) for the pattern.
- **Providers**: Compound components that own a disabled state must provide it via the shared disabled context so sub-components inherit it automatically. If the compound component already has its own context provider, add disabled to that context instead of nesting a separate provider.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.