Shared disabled context
SkillDev toolsUse 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Shared disabled context skill
What this skill tells your AI
The instructions your AI receives, as published by ledgerhq/lumen in .claude/skills/disabled-context/SKILL.md and read by ahel’s review.
Source of truth: libs/utils-shared/src/lib/context/disabledContext.tsx
- Consumers: Any component with a
disabledstate/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.
Signals
- GitHub stars
- 23
- Forks
- 5
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
disabled-context- Source
- github.com/ledgerhq/lumen