
from trezor-suite1,019
Guidelines and workflows for proposing and contributing code style changes to the Trezor Suite repository.
Provides step-by-step guidance for contributors who want to propose or implement code style changes in the Trezor Suite monorepo. It explains when to open a proposal issue versus submitting a PR and outlines the review workflow and ownership expectations.
Use this skill when preparing to change the project's code style rules or when you need a clear process for proposing formatting, linting, or stylistic updates to Trezor Suite. Activate it before opening an issue or creating a PR that affects style guidance.
Best used with developer-assistant agents that can create issues and PRs (GitHub-enabled agent tooling such as Copilot/GPT/Claude with repo access).
A minimal contribution guideline skill for proposing code style changes to the Trezor Suite repo. Contains only a short SKILL.md with two contribution paths (issue proposal vs PR). No bundled scripts or automation. Safe but shallow — lacks depth, detail, and any executable tooling.
Pure documentation skill with no scripts, no network calls, no security concerns. Very thin content — essentially a README fragment. Not malicious, but limited value as an agent skill.
Security Headers Compliance
Ensures generated code aligns with security headers and permissions policies, specifically for navigator object interactions.
Trezor Suite — Naming Conventions
Coding and naming conventions for Trezor Suite: guidance on variable, function, boolean, component names and project-specific conventions.