Figma Plugin Template

Contributing

How to contribute to this template — branches, commits, and pull requests.

Getting set up

git clone https://github.com/bromso/figma-plugin-template.git
cd figma-plugin-template
bun install
bun run build

Branch naming

PrefixPurposeExample
feat/New featuresfeat/color-picker-plugin
fix/Bug fixesfix/icon-render-crash
chore/Maintenancechore/update-dependencies
docs/Documentationdocs/add-api-guide

Commit messages

Use conventional commits:

feat: add color picker component
fix: resolve icon rendering in dark mode
chore: update dependencies
docs: add plugin testing guide

Pull request workflow

  1. Create a feature branch: git checkout -b feat/my-feature
  2. Make your changes
  3. Run checks: bun run build && bun run types && bun run test && bun run lint
  4. Add a changeset: bun changeset (if your change affects users)
  5. Push and open a PR against master
  6. CI runs automatically — wait for green checks
  7. Pre-commit hooks auto-format your code via Biome

CI pipeline

Every push to master and every pull request against it runs:

  • Biome linting
  • TypeScript type-checking
  • bun test suites (more than 130 tests)
  • Plugin build
  • Storybook build

Dependency updates arrive as Renovate pull requests every Monday: one grouped PR for minor and patch updates, and one PR per major (packages from the same monorepo, such as React or Storybook, move together). The root package.json has one overrides entry pinning @radix-ui/react-dialog to the version radix-ui depends on, so the UI ships a single dialog layer stack; move that pin whenever radix-ui is bumped.

Code style

  • Biome handles formatting and linting automatically
  • Pre-commit hooks run on every commit via Husky
  • TypeScript strict mode is enabled everywhere
  • Use @repo/* imports for cross-package references

On this page