How to use @owlmeans/client-wl — the reserved platform-neutral slot in the white-label stack, currently empty. Auto-invoked when a dependency names client-wl or when deciding where shared white-label UI belongs.
Scanned 9/22/2026
Install to Claude Code
npx -y skills add owlmeans/common --skill client-wl --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Client Wl?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/owlmeans-client-wl)More formats (shields.io, HTML) on the badges page.
---
name: client-wl
description: How to use @owlmeans/client-wl — the reserved platform-neutral slot in the white-label stack, currently empty. Auto-invoked when a dependency names client-wl or when deciding where shared white-label UI belongs.
user-invocable: false
---
# @owlmeans/client-wl
**Layer:** Client
**Install:** `"@owlmeans/client-wl": "^0.1.18-rc.22"` in `dependencies`
## Key Exports
None. The package builds and publishes, and its entry point exports nothing.
It holds the place a platform-neutral white-label layer would occupy — the tier between the shared
contract and a rendering target. Nothing depends on it, and `@owlmeans/web-wl` reaches
`@owlmeans/wled` directly rather than through it.
## Where to put white-label code instead
| Concern | Package |
|---------|---------|
| Record shapes, schemas, the `WL_PROVIDE` declaration | `@owlmeans/wled` |
| Serving a white-label set, provider services | `@owlmeans/server-wl` |
| Reading it in a browser, `WlLogo` | `@owlmeans/web-wl` |
Add to this package only for code that is genuinely React-free and target-independent; anything that
renders belongs in a target package.
## Depends On
- `react` (peer) — declared for the components this tier is reserved for; nothing here uses it
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!