trezor/trezor-suite

pr-review

Review pull requests using the GitHub CLI with agent and model attribution on every comment; never approve or merge.

idb-migrations

How to create and implement IndexedDB storage migrations in the Trezor Suite web app. Use when writing migrations that transform persisted data between Suite versions.

import-export

Named export conventions and barrel file usage rules for the Trezor Suite codebase. Use when writing imports, exports, or deciding on module structure.

components

React component file structure and patterns for Trezor Suite. Use when creating, refactoring or reviewing React components, including prop passing, component organization and directory layout.

performance-react-hooks

React render performance for Trezor Suite — memoization under React Compiler, referentially stable hook dependencies, minimal dependency arrays, and telling a wasted memo from a render loop. Use when adding useMemo, useCallback or memo, when writing a…

agentic-test-creation

Discovery-first workflow for writing a new Playwright e2e test from a user story, feature description or bug report. Use before writing any new Suite E2E test.

assertions

Assertion rules for Suite E2E tests: custom matchers, translation validation, display assertions. Use every time you write an expect() call or wait for a condition.

fixtures

Playwright fixture architecture in Suite E2E tests: scope, dependency injection, mocks lifecycle. Use whenever tests need shared setup, teardown or reusable resources.

locators

Locator strategy for Suite E2E tests: reuse page objects, getByTestId convention, parameterization, naming rules. Use every time you need to find an element on the page.

retries

Await and retry strategy for Suite E2E tests: Playwright auto-waiting, expect polling, Redux waits, flakiness prevention. Use every time a test is flaky due to timing.

tagging

Test tagging and Playwright project selection for Suite E2E tests: device model, platform and execution scope tags. Use when writing or editing tests to control where they run.

typescript

TypeScript-specific conventions including ts-expect-error usage, unknown vs any, typed helpers instead of `as` casts on native API results, const assertions, and type vs interface preferences. Use when writing TypeScript code.

analytics-and-sentry-privacy

Rules for keeping confidential data out of analytics events and Sentry reports (incl. `console.error`, tags, extras and breadcrumbs). Use when adding or changing an analytics event or its payload, or any code that reports to Sentry.

defensive-programming

Type safety practices including exhaustive checks, explicit return types, Result-based error handling, and non-mutating array methods. Use when writing TypeScript logic that handles multiple cases or error conditions, or when sorting, reversing, splicing, or…

project-structure

Overview of the Trezor Suite monorepo structure and key directories. Use when navigating the codebase or deciding where to place new code.

packages

How to create and structure packages in the Trezor Suite monorepo, including scopes and sizing guidance. Use when creating new packages or resolving cyclic dependencies.

security-headers

Generated code must be aligned with security headers (e.g. no unsave JS eval). The permissions policy is especially relevant when changing any code related with the `navigator` object.

common-tasks

Dependency management, package creation, and troubleshooting commands for the Trezor Suite monorepo. Use when managing dependencies or debugging build issues.

git-and-commit-guidelines

Conventional Commits format, commit types, scopes, submodule bumps, and PR best practices for Trezor Suite. Use when committing code, bumping submodule, or creating pull requests.

page-objects

Page object structure and patterns for Suite E2E tests: naming suffixes, composition, @step decorators, fixture registration. Use when building locators or actions for test scenarios.

performance-complexity

Collection-handling performance for Trezor Suite — indexing before iteration, O(1) sort comparators, and reduce accumulators that don't allocate. Use when writing a loop, sort or reduce over accounts, tokens, transactions or UTXOs.

github-issues

How to file a GitHub issue on trezor-suite. Short bug and feature bodies, issue types, live labels, and Suite project fields. Use when the user explicitly asks to create a GitHub issue.

redux

Redux Toolkit patterns including slices, selectors, thunks, and middleware conventions for Trezor Suite. Use when writing or reviewing Redux state management code.

tests

Test style guidelines including naming conventions, mock organization, translation handling, and file structure. Use when writing or organizing tests in the Trezor Suite codebase.

qa-notes

How to write the Notes for QA section of a Trezor Suite pull request. Use when creating or editing a pull request description.

common-issues

Known issues and their solutions in the Trezor Suite monorepo. Use when encountering build failures, test failures, or environment problems.

development-commands

Commands for running apps, linting, testing, and building in the Trezor Suite monorepo. Use when you need to run, build, or check code quality.

dependency-injection

Dependency Injection pattern for service definitions, factories, and composition roots. Use when working with packages that use the DI pattern.

trezor-mcp

Trigger on any mention of Trezor wallet interaction, crypto addresses, sending crypto, checking balances, signing messages, or hardware wallet operations via MCP. Also trigger when users mention configuring or troubleshooting the Trezor MCP server connection.

tests-native

Use when writing component or hook tests in suite-native and need to choose between renderWithBasicProvider, renderWithStoreProvider, or store helpers like createStoreFromPreloadedState, createLightStore, or mergePreloadedState.

basic-syntax

If-else formatting, spacing, function parameters, and conditional rendering rules for the Trezor Suite codebase. Use when writing or reviewing TypeScript/React code.

performance-dom

Browser rendering performance for Trezor Suite — forced synchronous layout from geometry reads, observer APIs instead of measuring an element, and transitioning only compositor properties. Use when measuring, scrolling or animating a DOM element, or when…

performance-scheduling

Deferring non-essential work with requestIdleCallback. Use when a startup path blocks interaction, or when scheduling analytics, prefetch or other background work.

comments

Comment conventions for Trezor Suite — prefer self-documenting code, and how to write and format a comment when one is actually needed. Use when writing or reviewing code comments.

tests-common

TDD practices and test utilities for suite-common packages, including Red-Green-Refactor workflow and @suite-common/test-utils usage. Use when writing tests for suite-common packages.

publish-config

publishConfig rules for public npm packages in the Trezor Suite monorepo. Use when adding or editing publishConfig, exports, or preparing a package for npm publishing.

naming

Naming conventions for variables, functions, booleans, components, and domain-specific terms in Trezor Suite. Use when naming anything in the codebase.

setup-requirements

Prerequisites and initial environment setup for the Trezor Suite monorepo, including Node.js, Yarn, Git LFS, and submodules. Use when setting up or troubleshooting the development environment.

skills-and-code-style-contribution

How to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when proposing code style changes.

tests-commands

Commands for running unit tests in the Trezor Suite monorepo. Use when you need to run tests for specific packages or the entire project.