# Import Export

> Import Export 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.

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

- Skill name: `import-export`
- Category: [Development](https://www.openparable.com/skill/development/1)
- Source: https://github.com/trezor/trezor-suite/blob/HEAD/skills/import-export/SKILL.md
- Repository: trezor/trezor-suite (1,020 GitHub stars when collected)

## SKILL.md

# Import/Export

## Use named export only

1. **Consistency.** With named exports you can always be sure that the exported value will not be renamed at one point. It's much easier to refactor with named exports because you can mass-replace and be more confident that it covered everything. Same goes for searching for a value.
2. **Tree-shaking.** With named exports, Webpack can recognize which exported values are unused and eliminate them. If you want to import all exports from a file and not use default exports, – use:

    ```tsx
    import * as colorUtils from './utils.js';
    ```

## Barrel (index.ts) files

Use them in packages to define public interface.

Do not use them inside a module to export from directory. If you feel it shall be separated, create a new package. They can introduce accidental circular dependencies and may hurt tree-shaking.

---

Source: https://www.openparable.com/skill/development/import-export (OpenParable). Cite the canonical URL above.
