trim-edit

Edit Penpot designs from natural-language descriptions via MCP and log changes to .trim/changes.md.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill trim-edit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trim-edit
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-trim/skills/trim-edit
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill trim-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Penpot design edits often require manual, repetitive steps and a clear history is hard to maintain. This Skill enables editing by describing changes in natural language and logs the results locally without code changes.

Core Features & Use Cases

  • Natural language editing of Penpot designs via MCP, enabling quick layout, component, and style tweaks.
  • Edits are logged to .trim/changes.md with a timestamp and summary, preserving an audit trail.
  • Changes stay in Penpot and do not modify code until you run a pull, ensuring safe, reviewable updates.

Quick Start

Describe the exact Penpot design changes you want with /trim:trim-edit <description>.

Frequently Asked Questions about trim-edit

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

FAQPage Schema
How do I edit Penpot designs using natural language?

You can edit Penpot designs using natural language by describing the exact layout, component, or style changes you want, which the Skill applies through Penpot MCP tooling without touching your code.

Can I use natural language to modify Penpot layouts without writing code?

Yes, natural language Penpot modifications are applied directly to the design project and do not modify your codebase automatically, ensuring safe and reviewable design updates until you pull changes.

What do I need to set up before applying natural language edits to Penpot?

You need Penpot MCP tooling configured in your environment to connect to your projects before you can apply natural language design edits and log the resulting changes.

Does the trim-edit Skill keep a changelog of Penpot design updates?

Yes, the Skill logs all natural language design changes to a .trim/changes.md file with a timestamp and summary, preserving a local audit trail of your Penpot modifications.

How does input validation work for Penpot natural language design editing?

Input validation ensures your natural language descriptions are processed safely before applying edits through Penpot MCP, preventing invalid commands from altering your design project.

What are the limitations of using natural language for Penpot design editing?

The Skill applies edits strictly within Penpot via MCP and does not change code automatically; you must run a pull to update your codebase, meaning design and code remain separate until reviewed.