OpenParable
Skip to content
← Back to skills

Development Commands

Development
development-commands

Development Commands is an Agent Skill for development published in the trezor/trezor-suite repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/trezor/trezor-suite/blob/HEAD/skills/development-commands/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/development-commands, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Development Commands

Running Applications

yarn suite:dev             # Web app at http://localhost:8000
yarn suite:dev:desktop     # Desktop Electron app
yarn suite:dev:vite        # Development with Vite (faster hot reload)

Code Quality

yarn format                # Format code with Prettier
yarn lint:styles --no-tui  # Lint CSS styles (check logs only if exit status is not 0)
yarn lint:js:fix --no-tui  # Auto-fix linting issues (check logs only if exit status is not 0)
yarn type-check --no-tui   # TypeScript type checking (allow 15 minutes, check logs only if exit status is not 0)
yarn nx run @package-scope/package-name:type-check  # Package-level TypeScript integration check

For isolated changes, rely on IDE TypeScript diagnostics and focused tests, formatting, and linting; do not run a type-check command. Batch changes and run yarn nx run <package>:type-check at most once near final validation, only for integration risk or on request. It may check the full dependency graph and take minutes, so warn first. Never run affected or repo-wide type-checks unless requested.

Testing

yarn test:unit             # Run unit tests (allow 15 minutes, check logs only if exit status is not 0)
yarn workspace @package-scope/package-name test:unit  # Test specific package

Build Commands

yarn build:libs            # Build all libraries (required after dependency changes)
yarn suite:build:web       # Production web build