trim-library

To keep code-to-design component mappings in sync, invoke the trim-library Skill with the 'sync' option to perform drift corrections and reconcile tracked items. It automatically aligns drifted code components with their corresponding Penpot design assets.

To list tracked components and check their sync status, simply invoke the Skill without the sync option. It reads the local .trim/components.json file to display all tracked code and Penpot components and their current alignment state.

A Penpot component library drifts from code components when bidirectional updates occur independently without coordination. The Skill detects this drift by comparing local git timestamps and component states against the stored .trim configuration.

Yes, you need a local .trim/config and a .trim/components.json file to manage bidirectional component synchronization. The Skill relies on these local files to determine the current state of tracked code and Penpot components.

Yes, you can audit mappings between code and Penpot components offline. The Skill supports offline listing of all tracked components and their sync status by reading the local .trim/components.json file without requiring an active connection.

The best way to reconcile drifted design assets and code components is to run a single sync operation using the trim-library Skill. It coordinates plugin resolution, git timestamps, and MCP-based syncing to correct drift in one step.