trezor
- 35 skills
- 0 followers
- yesterday last updated
- ▌ Performance Scheduling · trezorDeferring non-essential work with requestIdleCallback. Use when a startup path blocks interaction, or when scheduling analytics, prefetch or other background work.
- ▌ Page Objects · trezorPage 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 React Hooks · trezorReact 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 dependency array, or when a component re-renders or refetches more than it should.
- ▌ Performance Code Splitting · trezorCode splitting for Trezor Suite web and desktop — what belongs behind `import()` or `React.lazy`, where the boundary goes, how a failed chunk load and its retry behave, and the production-build measurement that proves a split. Use when adding a dependency or a feature that not every user opens, when writing `import()` or `React.lazy`, or when checking how a change affects bundle size.
- ▌ Analytics And Sentry Privacy · trezorRules 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.
- ▌ Agentic Test Creation · trezorDiscovery-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.
- ▌ Skills And Code Style Contribution · trezorHow to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when proposing code style changes.
- ▌ Trezor MCP · trezor bundleTrigger 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.
- ▌ Typescript · trezorTypeScript-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.
- ▌ Basic Syntax · trezorIf-else formatting, spacing, function parameters, and conditional rendering rules for the Trezor Suite codebase. Use when writing or reviewing TypeScript/React code.
- ▌ Common Tasks · trezorDependency management, package creation, and troubleshooting commands for the Trezor Suite monorepo. Use when managing dependencies or debugging build issues.
- ▌ Tests Common · trezorTDD 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.
- ▌ Tests Native · trezorUse when writing component or hook tests in suite-native and need to choose between renderWithBasicProvider, renderWithStoreProvider, or store helpers like createStoreFromPreloadedState, createLightStore, or mergePreloadedState.
- ▌ Github Issues · trezorHow 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.
- ▌ Import Export · trezorNamed export conventions and barrel file usage rules for the Trezor Suite codebase. Use when writing imports, exports, or deciding on module structure.
- ▌ Idb Migrations · trezorHow to create and implement IndexedDB storage migrations in the Trezor Suite web app. Use when writing migrations that transform persisted data between Suite versions.
- ▌ Publish Config · trezorpublishConfig rules for public npm packages in the Trezor Suite monorepo. Use when adding or editing publishConfig, exports, or preparing a package for npm publishing.
- ▌ Performance Dom · trezorBrowser 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 writing a CSS transition. Web and desktop only.
- ▌ Security Headers · trezorGenerated 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.
- ▌ Project Structure · trezorOverview of the Trezor Suite monorepo structure and key directories. Use when navigating the codebase or deciding where to place new code.
- ▌ Retries · trezorAwait 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 · trezorTest 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.
- ▌ Locators · trezorLocator 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.
- ▌ Dependency Injection · trezorDependency Injection pattern for service definitions, factories, and composition roots. Use when working with packages that use the DI pattern.
- ▌ Development Commands · trezorCommands for running apps, linting, testing, and building in the Trezor Suite monorepo. Use when you need to run, build, or check code quality.
- ▌ Assertions · trezorAssertion rules for Suite E2E tests: custom matchers, translation validation, display assertions. Use every time you write an expect() call or wait for a condition.
- ▌ Defensive Programming · trezorType 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 replacing an element (indexed assignment) in an array you did not create.
- ▌ Performance Complexity · trezorCollection-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.
- ▌ Redux · trezorRedux Toolkit patterns including slices, selectors, thunks, and middleware conventions for Trezor Suite. Use when writing or reviewing Redux state management code.
- ▌ Naming · trezorNaming conventions for variables, functions, booleans, components, and domain-specific terms in Trezor Suite. Use when naming anything in the codebase.
- ▌ Comments · trezorComment 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.
- ▌ Packages · trezorHow to create and structure packages in the Trezor Suite monorepo, including scopes and sizing guidance. Use when creating new packages or resolving cyclic dependencies.
- ▌ QA Notes · trezorHow to write the Notes for QA section of a Trezor Suite pull request. Use when creating or editing a pull request description.
- ▌ Pr Review · trezor bundleReview pull requests using the GitHub CLI with agent and model attribution on every comment; never approve or merge.
- ▌ Components · trezorReact component file structure and patterns for Trezor Suite. Use when creating, refactoring or reviewing React components, including prop passing, component organization and directory layout.