mirror of
https://github.com/trezor/trezor-suite.git
synced 2026-02-19 16:22:25 +01:00
ba6e673d2f
feat: implement requirement that checks the AGENTS.md to verify it has all the skills linked fix: add it to CI demonstrate failure fix: AI adressing the comments fix: remove unnecessary parseArgs, use node native fix: bit of refactoring, introduce DI to test stuff fix: remove fix implmentation its too messy and I ddo not want to commit AI slop fix: di for report test with console feat: requirements uses nx-afected fix: refactor the requre affectd so it is not a slop fix: esm saddness fix: ignore pacakges fix: affected correcty test: intentionlly break it fix: CI for affected fix: revert, 'nrwl/nx-set-shas@v4' shall do the job fix: CI trial & error fix: ai slop to verify fix: comments stripping fix: try default fetch fix: strip fix: backfix the testing errors fix: missing components link fix: missing depcheck for analytics-docs fix: review fix: move tests fix: new ignored package local skill
2.2 KiB
2.2 KiB
Skills
All skills are mandatory reading before making changes.
- Basic Syntax – If-else, ternaries, and other syntax rules
- Code Style Guide – How to contribute code style proposals
- Comments – Comment formatting conventions
- Common Issues – Known issues and their solutions
- Components – React component file structure and patterns
- Common Tasks – Dependency management, package creation, and troubleshooting
- Defensive Programming – Exhaustive checks and safe defaults
- Development Commands – Running apps, linting, testing, and building
- Git and Commit Guidelines – Conventional Commits format and best practices
- Import/Export – Named exports and import ordering
- Naming – Naming conventions for variables, functions, and files
- Packages – How to create and structure packages
- Project Overview – What Trezor Suite is and how the monorepo is organized
- Redux – Redux Toolkit patterns and best practices
- Setup Requirements – Prerequisites and initial environment setup
- Tests – Test style guidelines and best practices
- Tests Commands – Running tests and test-related guidelines
- Tests – Test style guidelines and best practices
- TypeScript – TypeScript-specific conventions
Formatting (mandatory)
After any code changes, run formatting on changed files before finishing:
yarn g:prettier --write <changed-files>yarn g:eslint --fix <changed-files>
Other Notes
- Build times: Initial setup takes 15-20 minutes; builds can take 10-15 minutes
- Windows: Use Git Bash instead of cmd/PowerShell; consider WSL for better performance
- Testing: Some tests may time out in CI environments without network access
- Hardware wallets: Use trezor/trezor-user-env emulator for development