documentation: add penpot skill design and implementation plan docs #218

Merged

david merged 1 commit from documentation/2026-09-15/penpot-skill-design-and-implementation-plan into main

2026-09-14 23:20:07 +00:00

david commented

2026-09-14 23:16:47 +00:00

Owner

Adds the design and implementation-plan documents for a proposed penpot skill + pi extension pair that lets an agent create editable Penpot designs over the access-token RPC API.

What's included

File	Purpose
`docs/PENPOT_SKILL_DESIGN.md`	Design doc: goal, constraints (no MCP in pi, internal unversioned RPC API), architecture (skill + extension mirroring `forgejo`), the three creation paths (design system / greenfield screen / SVG / image), and a validation section recording results from a live Penpot 2.17 instance.
`docs/PENPOT_SKILL_IMPLEMENTATION_PLAN.md`	Companion implementation plan: deliverables table (extension files, skill, vendored OpenAPI docs, `package.json`/`README` updates) and the milestone breakdown (M0 auth skeleton onward), each ending in live-instance validation.

Why now

The Penpot RPC API surface — auth, shape payloads, auto-layout fields, asset payloads, the binfile round trip and component instancing — has just been validated end-to-end against a live instance (Penpot 2.17). Capturing that before it goes stale lets the feature be planned and implemented from confirmed specifics rather than guesses.

These are working documents: the design doc is intended to be retired once the design settles into the skill and extension; the plan is a scratch artifact that can be deleted after implementation.

Notes

Docs only — no code, no config changes. Implementation is tracked separately as a feature (issue TBD).
No closing reference: documentation is a no-issue, date-driven change.

Adds the design and implementation-plan documents for a proposed `penpot` skill + pi extension pair that lets an agent create editable Penpot designs over the access-token RPC API. ## What's included | File | Purpose | |---|---| | `docs/PENPOT_SKILL_DESIGN.md` | Design doc: goal, constraints (no MCP in pi, internal unversioned RPC API), architecture (skill + extension mirroring `forgejo`), the three creation paths (design system / greenfield screen / SVG / image), and a validation section recording results from a live Penpot 2.17 instance. | | `docs/PENPOT_SKILL_IMPLEMENTATION_PLAN.md` | Companion implementation plan: deliverables table (extension files, skill, vendored OpenAPI docs, `package.json`/`README` updates) and the milestone breakdown (M0 auth skeleton onward), each ending in live-instance validation. | ## Why now The Penpot RPC API surface — auth, shape payloads, auto-layout fields, asset payloads, the binfile round trip and component instancing — has just been validated end-to-end against a live instance (`Penpot 2.17`). Capturing that before it goes stale lets the feature be planned and implemented from confirmed specifics rather than guesses. These are working documents: the design doc is intended to be retired once the design settles into the skill and extension; the plan is a scratch artifact that can be deleted after implementation. ## Notes - Docs only — no code, no config changes. Implementation is tracked separately as a `feature` (issue TBD). - No closing reference: `documentation` is a no-issue, date-driven change.

david added the

documentation

label

2026-09-14 23:16:47 +00:00

david added 1 commit

2026-09-14 23:16:47 +00:00