Switch UX/UI design tool from Penpot to Figma

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
curo1305
2026-04-17 11:40:15 +02:00
parent c4f0c7ad49
commit 2e629d55c5
4 changed files with 52 additions and 40 deletions
+7 -6
View File
@@ -1,12 +1,13 @@
# TODO
## UX/UI — Penpot setup
## UX/UI — Figma setup
- [ ] **Spin up Penpot LXC** — separate LXC container on the server (~24 GB RAM), Docker Compose from https://github.com/penpot/penpot; expose via subdomain behind nginx proxy manager
- [ ] **Create Penpot project** register on the self-hosted instance, create project `destroying_sap`, create initial design file
- [ ] **Generate Penpot access token**Profile → Access tokens; used by the `ux-designer` agent via WebFetch REST API calls
- [ ] **Decide on UI component library** — shadcn/ui (recommended: Tailwind-based, unstyled accessible primitives, white-label friendly) vs MUI vs other; decision affects both Penpot design system and frontend implementation
- [ ] **Connect ux-designer agent** — confirm Penpot API reachable, provide instance URL + token to agent at session start
- [ ] **Create a Figma account** — sign up at https://figma.com (free tier is sufficient to start)
- [ ] **Create Figma project and file** — create project `destroying_sap` and an initial design file inside it
- [ ] **Generate Figma personal access token**Account Settings → Personal access tokens → Generate new token; used by the `ux-designer` agent via WebFetch REST API calls
- [ ] **Note your file key** — open the design file; the URL is `https://www.figma.com/file/<FILE_KEY>/...`; record the key
- [ ] **Decide on UI component library** — shadcn/ui (recommended: Tailwind-based, unstyled accessible primitives, white-label friendly) vs MUI vs other; decision affects both Figma design system and frontend implementation
- [ ] **Connect ux-designer agent** — provide file key + token to agent at session start (`"Use Figma file <KEY> with token: <token>"`)
## Auth / session security