trim-push

Name: trim-push
Availability: InStock
Author: yoshisada

Push code components to Penpot and update component mappings.

Updated Mar 26, 2026

Search Tags:#automation #workflow #mcp #push #design-system #ui-components #penpot

Ready to run

npx skills add https://github.com/yoshisada/ai-repo-template --skill trim-push

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trim-push
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-trim/skills/trim-push
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill trim-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pushes code components to Penpot to keep design assets in sync with the source code. Analyzes code structure and styles, and creates or updates Penpot components via MCP, while updating component mappings across the design system.

Core Features & Use Cases

Automated synchronization between code components and Penpot components, including updates to existing assets and creation of new ones.
Mappings management: keeps .trim/components.json in sync with Penpot state.
Workflow-driven: supports running as a wheel workflow with deterministic steps (read-config, detect-framework, scan-components, classify-files, read-mappings, resolve-trim-plugin, push-to-penpot, discover-flows, update-mappings).

Quick Start

Run the trim-push workflow to push all UI components to Penpot and generate/update mappings.

Frequently Asked Questions about trim-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I sync UI components from source code to Penpot?▼

The trim-push workflow pushes code components to Penpot by reading the .trim/config, detecting the UI framework, scanning components by convention, and using MCP to create or update Penpot elements while managing mappings.

How does component mapping work when pushing code to Penpot?▼

Component mapping reads and updates the .trim/components.json file to maintain synchronization between source code components and Penpot representations, ensuring design assets reflect the latest code structure and styles.

Do I need a specific UI framework to push components to Penpot?▼

No specific framework is required. The workflow automatically detects your UI framework by validating the .trim/config and scanning components by framework conventions before pushing them to Penpot.

What is the workflow for automating Penpot design system updates?▼

The workflow follows deterministic steps: read-config, detect-framework, scan-components, classify-files, read-mappings, resolve-trim-plugin, push-to-penpot, discover-flows, and update-mappings to automate design system synchronization.

Can I update existing Penpot components instead of creating duplicates?▼

Yes, the workflow reads existing mappings before pushing and uses MCP to update existing Penpot elements when a component is already mapped, creating new elements only for unmapped components.

Why are my code components not showing up in Penpot after sync?▼

Sync failures often occur when the .trim/config is invalid, the UI framework cannot be detected, or component files do not match framework scanning conventions, preventing the MCP from creating or updating Penpot elements.