shade-imports
Import Shade from layer-specific subpaths (primitives, components, patterns, page-templates, utils), never the root barrel. Trigger when editing TSX/TS in Shade-consuming apps.
Source facts
- Repository
- TryGhost/Ghost
- Last source activity
- August 5, 2026 at 14:15
- Detected SKILL.md language
- English
- Stars
- 55,544
- Forks
- 11,995
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- Shade imports
- description
- Import Shade from layer-specific subpaths (primitives, components, patterns, page-templates, utils), never the root barrel. Trigger when editing TSX/TS in Shade-consuming apps.
- autoTrigger
- [{"fileEdit":"apps/{shade,admin,admin-x-framework,activitypub}/**/*.{ts,tsx}"}]
# Shade imports
Always import Shade from its **layer-specific subpath**. Never from the root barrel `@tryghost/shade`.
## Correct
```ts
import {Stack, Inline, Box, Grid, Container, Text} from '@tryghost/shade/primitives';
import {Button, Input, Dialog} from '@tryghost/shade/components';
import {PageHeader, KpiCard, Filters} from '@tryghost/shade/patterns';
import {ListPage} from '@tryghost/shade/page-templates';
import {cn, formatNumber} from '@tryghost/shade/utils';
import {ShadeApp} from '@tryghost/shade/app';
```
**Note:** `ListPage` is in `@tryghost/shade/page-templates`, not `/patterns`. Page templates are top-level page wrappers; patterns are the building blocks they compose.
## Incorrect
```ts
// BAD — root barrel
import {Button, Stack} from '@tryghost/shade';
// BAD — deep path into source
import {Button} from '@tryghost/shade/src/components/ui/button';
```
## Inside Shade itself
When editing files under `apps/shade/src/**`, use the `@/` alias for cross-file imports:
```ts
import {cn} from '@/lib/utils';
import {inputSurface} from '@/components/ui/input-surface';
```
## Why
Subpath imports make the layer (primitive/component/pattern) visible at the call site, which is the first piece of information a reader needs. The root barrel hides that and encourages cross-layer drift.
View on GitHub