agentleFS
saleorsaleor/saleor-dashboard/.claude/skills/saleor-dashboard-detail-pages/SKILL.md

saleor-dashboard-detail-pages

Skill1.1k starsChanged 8 days agoBSD-3-ClauseView on GitHub

Patterns for Saleor Dashboard entity detail views (channels, products, collections, customers, shipping zones, warehouses, models/pages). Use when building or refactoring detail pages, moving metadata out of the main form, or aligning TopNav actions. For the full update language (sidebar ops, settings cards, checklist), see saleor-dashboard-entity-detail skill.

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 5 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 33 mentionsJul 2026: 3 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the saleor/saleor-dashboard repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about saleor/saleor-dashboard

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add "view-metadata" to the entity URL dialog union (urls.ts).

    line 59
  2. Very specific:

    Create <Entity>MetadataDialog using PageDetailsDocument (or entity query doc) as refetchDocument.

    line 60
  3. Very specific:

    Remove inline <Metadata> from page content.

    line 63
  4. Very specific:

    Create views: keep inline <Metadata> + createMetadataCreateHandler (no entity id yet).

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Saleor Dashboard Detail Pages

Conventions for DetailPageLayout entity views under src/<feature>/.

Start here for broader refresh: saleor-dashboard-entity-detail — page anatomy, Detail* vs Settings*, refactor checklist (e.g. collections).

Foldable sections

For expandable sections (advanced settings, rate rows, postal ranges, etc.) use DetailGroupBox with Title2 — documented in saleor-dashboard-styles. Do not introduce new UI with the legacy @dashboard/components/Accordion.

Section nav layout

Long detail pages with DetailSectionNav (4+ scroll sections) use DetailPageSectionLayout — nav rail at 25% width (min 10rem) + main column with gap={4}. Do not nest DetailPageContent inside (that component is for single-column pages only). See saleor-dashboard-entity-detail for the full table and example.

Settings sections (DetailSettingsCard)

On entity detail pages, group fields in DetailSettingsCard (not DashboardCard or nested cards). Full language:

  • Primary vs secondary sidebar card headers (Inventory / Delivery pattern)
  • intro row for leading description (Payment gateways pattern)
  • Card vs open section — when to skip the border
  • Channel availability tiers, foldables, SEO unwrapped
  • SEO last in the main column by default (identity → primary content → SEO)
  • Fixed-at-creation fields — FixedAtCreationField (disabled Input + lock + “Fixed at creation. …” helper), never a disabled Combobox
  • Vercel design restraint rules (earn a surface, no nesting)

→ saleor-dashboard-entity-detail

Metadata in Header Modal

Edit views — metadata lives in a header modal, not the main form.

LayerResponsibility
*MetadataDialogMetadataDialog + useMetadataForm + useHandleMetadataSubmit
View (*Details.tsx)URL dialog state via createDialogActionHandlers, renders dialog
*DetailsPageTopNav.MetadataButton → onShowMetadata
FormNo metadata fields on update; create flows may keep inline <Metadata>

Reference implementations

  • src/products/components/ProductMetadataDialog/
  • src/customers/components/CustomerMetadataDialog/
  • src/warehouses/components/WarehouseMetadataDialog/
  • src/modeling/components/PageMetadataDialog/

Checklist (edit view)

  1. Add "view-metadata" to the entity URL dialog union (urls.ts).
  2. Create <Entity>MetadataDialog using PageDetailsDocument (or entity query doc) as refetchDocument.
  3. View: openModal("view-metadata") / closeModal; remove createMetadataUpdateHandler.
  4. Page: TopNav.MetadataButton with data-test-id="show-<entity>-metadata".
  5. Remove inline <Metadata> from page content; skip metadata in update submit data.
  6. Create views keep inline <Metadata> + createMetadataCreateHandler (no entity id yet).

URL dialog wiring

const [openModal, closeModal] = createDialogActionHandlers(
  navigate,
  params => entityUrl(id, params),
  params,
);

<EntityMetadataDialog
  open={params.action === "view-metadata" && !!entity}
  onClose={closeModal}
  entity={entity}
/>;

MetadataDialog component

Shared UI: src/components/MetadataDialog/. Entity dialogs are thin wrappers — copy an existing one and swap the GraphQL document + title message.

TopNav Actions

  • TopNav.MetadataButton — metadata (edit views only)
  • TranslationsButton — when MANAGE_TRANSLATIONS
  • TopNav.Menu — extensions → entity actions → related settings hub (if any) → GraphiQL → Delete last (see entity-detail skill)
  • Set actionsGap={3} when multiple header actions

Further Reading

  • saleor-dashboard-entity-detail — update language for daily entity details
  • rules/metadata-modal.md — step-by-step migration from inline metadata
  • saleor-dashboard-styles skill — layout and Macaw UI patterns

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.