saleor-dashboard
AGENTS.md1.1k starsChanged 8 days agoBSD-3-ClauseView on GitHub
- Use @saleor/macaw-ui-next components and tokens; do not add usages of legacy @saleor/macaw-ui, Material-UI, or makeStyles. - Import icons directly from lucide-react; Macaw icons are deprecated. - Use CSS Modules (.module.css) for custom styles. - Write new code with strict TypeScript checking; do not add // @ts-strict-ignore. - Use named exports and direct imports. Do not introduce barrel exports; route entry points named index.tsx are allowed. - Prefer destructured object parameters and typed declarations over type assertions. Explicitly type test…
- Reads credentials
Trending
Less talk lately.about the whole repository
Who's talking about saleor/saleor-dashboard
- saleor/saleor“Unable to update Company info from Dashboard”GitHub · May 31, 2022 · 2 reactions
- saleor/apps“Implement logo field in AppManifest”GitHub · Feb 22, 2023 · 1 reactions
- saleor/saleor“Support for payment transaction actions”GitHub · Aug 11, 2022 · 1 reactions
- saleor/saleor“feat(attribute): add staff-only internalDescription to Attribute”GitHub · Oct 15, 2026
- waelhe/app-java-v3“docs(admin): plan Saleor Dashboard adaptation for marketplace”GitHub · Oct 15, 2026
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
- May 31, 2022Unable to update Company info from Dashboard — saleor/saleor2 reactions · 3 comments
- Feb 22, 2023Implement logo field in AppManifest — saleor/apps1 reaction · 3 comments
- Aug 11, 2022Support for payment transaction actions — saleor/saleor1 reaction · 27 comments
- Oct 15, 2026feat(attribute): add staff-only internalDescription to Attribute — saleor/saleor0 reactions · 1 comment
- Oct 15, 2026docs(admin): plan Saleor Dashboard adaptation for marketplace — waelhe/app-java-v30 reactions · 3 comments
45 more on GitHub
- Jul 31, 2026feat(avatax): add tax code action to Dashboard command palette — saleor/apps0 reactions · 5 comments
- Jul 13, 2026Add reason for price override — saleor/saleor0 reactions · 1 comment
- Jul 8, 2026Improved Gift Card APIs — saleor/saleor0 reactions · 1 comment
- Jun 9, 2026[Feature] Support pasting boolean values in other that English — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026Fix Background task provider tests — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Missing filter when calling exportGiftCards mutation for selected giftcards — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Variant view, no scroll on warehouse list and only first 50 warehouses displayed for the user — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: `requestPasswordReset` mutation returns incorrect error when user is not staff user — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Missed info about no access to the channels — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026 `create order` button should be disabled in case of no permissions — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026User can create group with permission from plugin but cannot assign members via UI — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Enhancement]: Misleading UI when charge is pending — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Modal leave without saving after logout — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Feature]: Change navigation structure — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Only first 50 warehouses are loaded in the grid — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Weight rate create - not consistent error messages — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Price rate and weight base availability button inactive — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Changing attribute value on product triggers SKU fail — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Restrict order weight in shipping method not saved — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Datagrids jump to end when resizing column — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Enable refunding specific product lines — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Deleting variant attribute changes variant name — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Column picker refinement — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026No information about required fields in product variant form — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Error handling in product variant page - user can delete required field and still be able to save - then success banner shows up followed by error banner — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Remove add product — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Not all attributes are validated — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Error label misplaced — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Error messages missmatch — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Epic]: Improve UX flow for order refunds using Transactions API — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Can not refund fulfilled order — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Incorrect background in label cell — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: City and Postal code is getting cleared while modifying and saving the country field and country area in warehouse modification — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]:Error displayed while selecting Category name header checkbox and click pagination in category Listing Page — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: dashboard not using all settings field in query (Can't set limitQuantityPerCheckout) — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 3, 2026Add support for editorJS table syntax — saleor/saleor0 reactions · 1 comment
- May 5, 2026HOMEPAGE_WIDGETS types for manifest — saleor/app-sdk0 reactions · 2 comments
- Mar 25, 2026Fix LSP not loading `.js` and `.ts` files correctly — graphql/graphiql0 reactions · 5 comments
- Mar 13, 2026Add proper gift card events when gift card is used as a payment method — saleor/saleor0 reactions · 1 comment
- Mar 12, 2026Fix smoke tests - add prefix for artifact upload — saleor/apps0 reactions · 3 comments
- Mar 6, 2026Introduce password login mode — saleor/saleor0 reactions · 2 comments
- Mar 5, 2026Add SaleorGiftcardPaymentMethodDetails to transaction — saleor/saleor0 reactions · 2 comments
- Feb 25, 2026Fix failing smoke tests workflow — saleor/apps0 reactions · 3 comments
- Feb 13, 2026document payment method details in dashboard — saleor/saleor-docs0 reactions · 1 comment
- Feb 10, 2026Refund reasons phase 2 (POC) — saleor/saleor0 reactions · 1 comment
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository15 other files it gives its agents.
- pinactSkill
- saleor-dashboard-cloud-extensionsSkill
- saleor-dashboard-detail-pagesSkill
- saleor-dashboard-entity-detailSkill
- saleor-dashboard-feedbackSkill
- saleor-dashboard-formsSkill
- saleor-dashboard-github-workflowsSkill
- saleor-dashboard-graphql-batchingSkill
- saleor-dashboard-listsSkill
- saleor-dashboard-loadingSkill
- saleor-dashboard-microcopySkill
- saleor-dashboard-pr-quality-checkSkill
- saleor-dashboard-security-auditSkill
- saleor-dashboard-smooth-shadowSkill
- saleor-dashboard-stylesSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
25 rules. About 0 are common, 8 are distinctive, and 17 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
17
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 5
Use @saleor/macaw-ui-next components and tokens.
- Very specific: line 7
Import icons directly from lucide-react.
- Very specific: line 8
Use CSS Modules (.module.css) for custom styles.
- Very specific: line 9
Write new code with strict TypeScript checking.
- Very specific: line 10
Use named exports and direct imports.
- Distinctive: line 12
Prefer destructured object parameters and typed declarations over type assertions.
- Very specific: line 16
Add a colocated ComponentName.stories.tsx for new UI components.
- Distinctive: line 25
Read documentation when its subject is relevant to the task:
- Distinctive: line 28
Use its dashboard-facing names even when API names differ.
- Very specific: line 37
Read current commands, dependencies, and runtime requirements from package.json, including packageManager and engines.
- Very specific: line 44
Put dependency overrides in pnpm-workspace.yaml under overrides, never in package.json under pnpm.overrides.
- Very specific: line 46
After changing GraphQL operations, fragments, or schemas, run pnpm run generate for both main and staging schemas.
- Very specific: line 48
After changing react-intl messages, run pnpm run extract-messages.
- Very specific: line 51
Run pnpm run dev in the background.
- Very specific: line 65
Use pnpm run test:quiet <file_path> for individual Jest files.
- Distinctive: line 67
Add or update unit tests for changed utility behavior and complex components.
- Very specific: line 69
When changing dependencies, exports, or file organization, run pnpm run knip.
- Distinctive: line 81
Do not manually merge generated content.
- Distinctive: line 90
When adding a substantial product feature, implement PostHog tracking for its key user interactions and outcomes, following existing …
- Distinctive: line 92
Do not add tracking for bug fixes, removals, refactors, or other maintenance-only changes.
- Distinctive: line 96
Use the changesets CLI for user-facing features, enhancements, and bug fixes.
- Very specific: line 99
Follow scope policy in .github/CONTRIBUTING.md (Pull requests section) and title and description requirements in …
- Very specific: line 101
Run the saleor-dashboard-pr-quality-check skill when planning (to keep the planned scope to one PR) and when work is done, including after …
- Very specific: line 105
Prefer the gh CLI for GitHub operations.
- Very specific: line 106
No agent-driven issue tracker is configured.
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md 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.
Files
Saleor Dashboard
Conventions
- Use
@saleor/macaw-ui-nextcomponents and tokens; do not add usages of legacy@saleor/macaw-ui, Material-UI, ormakeStyles. - Import icons directly from
lucide-react; Macaw icons are deprecated. - Use CSS Modules (
.module.css) for custom styles. - Write new code with strict TypeScript checking; do not add
// @ts-strict-ignore. - Use named exports and direct imports. Do not introduce barrel exports;
route entry points named
index.tsxare allowed. - Prefer destructured object parameters and typed declarations over type assertions. Explicitly type test fixtures.
- Internationalize user-facing text with
react-intl. Checksrc/intl.tsand nearby component messages for reusable messages before defining new ones. - Add a colocated
ComponentName.stories.tsxfor new UI components. - In tests, use
// Arrange,// Act, and// Assertcomments. Mock GraphQL operations with typed fixtures. - For lists that can contain 50+ items, keep navigation and controls usable and selected items discoverable. Choose scrolling, pagination, or virtualization to suit the component. Use skeletons for loading and handle empty states.
Task-specific context
Read documentation when its subject is relevant to the task:
CONTEXT.mdfor product terminology, especially modeling and navigation pins. Use its dashboard-facing names even when API names differ.- Relevant decisions in
docs/adr/when changing the behavior they govern. Surface conflicts with those decisions rather than silently overriding them. docs/multi-schema.mdfor GraphQL operations, generation, or schema selection.docs/configuration.mdand.env.templatewhen configuring or running the app.docs/running-tests.mdwhen running Playwright tests..claude/skills/saleor-dashboard-cloud-extensions/SKILL.mdwhen touchingsrc/cloud-extensionsor the submodule pointer.
Read current commands, dependencies, and runtime requirements from package.json,
including packageManager and engines; read aliases from tsconfig.json.
Conditional workflows
- Install dependencies when missing or when dependency inputs change. Run
pnpm installafter modifyingpackage.jsonor workspace dependency settings. - Put dependency overrides in
pnpm-workspace.yamlunderoverrides, never inpackage.jsonunderpnpm.overrides. - After changing GraphQL operations, fragments, or schemas, run
pnpm run generatefor both main and staging schemas. Do not hand-edit.generated.tsfiles. - After changing
react-intlmessages, runpnpm run extract-messages. - Set up a backend only when the task needs a running application or integration tests. Setup and code generation are not prerequisites for unrelated edits.
- Run
pnpm run devin the background. If background execution is unavailable, ask the user how to proceed. Itspredevhook already runs code generation.
Verification
Match verification to the affected code. Complete relevant checks before handing back implementation work, and report any checks that could not run.
- Documentation-only changes: format the changed files with oxfmt; application tests, type checks, and knip are unnecessary.
- Code changes: run oxlint with auto-fix and oxfmt on the changed files before
manually fixing lint errors. ESLint only runs GraphQL rules
(
eslint.config.mjs); run it on changed GraphQL operations. Run affected tests and the relevantcheck-types:*scripts frompackage.json. - Use
pnpm run test:quiet <file_path>for individual Jest files. Switch topnpm run test:debug <file_path>when debugging requires console or DOM output. - Add or update unit tests for changed utility behavior and complex components; use Playwright coverage for critical user flows.
- When changing dependencies, exports, or file organization, run
pnpm run knip. - For changes spanning application code, Playwright, and scripts, run
pnpm run check-types. Usepnpm run lintfor repository-wide lint, formatting, and changeset validation; it auto-fixes and formats files across the repository. - Rerun affected checks after fixes. Broaden verification when shared behavior, configuration changes, or failures warrant it; avoid repeating successful checks without new changes or evidence.
Conflict resolution and review
- Resolve source conflicts first, then regenerate derived files:
pnpm installforpnpm-lock.yaml, andpnpm run generatefor GraphQL outputs. Do not manually merge generated content. - Resolve package-version conflicts against intended dependency constraints and preserve deliberate pins. Do not turn conflict resolution into an unrelated upgrade to the latest registry release.
- During code review, skip inspecting
.generated.tscontents; review the source operations and generation configuration instead.
Analytics
- When adding a substantial product feature, implement PostHog tracking for its key user interactions and outcomes, following existing analytics patterns.
- Do not add tracking for bug fixes, removals, refactors, or other maintenance-only changes.
Contributions
- Use the changesets CLI for user-facing features, enhancements, and bug fixes. Explain the user-visible behavior; for fixes, describe what failed and what works now. Skip changesets for internal refactors, style, tests, CI/CD, and internal docs.
- Follow scope policy in
.github/CONTRIBUTING.md(Pull requests section) and title and description requirements in.github/PULL_REQUEST_TEMPLATE.md. - Run the
saleor-dashboard-pr-quality-checkskill when planning (to keep the planned scope to one PR) and when work is done, including after each commit. Without an open PR it checks the local branch. If it recommends a split, surface that to the user before continuing. - Prefer the
ghCLI for GitHub operations. - No agent-driven issue tracker is configured. Return issue or triage findings in
the conversation; see
docs/agents/issue-tracker.mdwhen a skill expects a tracker.
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
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.

