pi-mono-figma 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +9 -0
- package/README.md +12 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -12,6 +12,15 @@
|
|
|
12
12
|
- Updated tool descriptions, README, and skill guidance to prefer processed tools and keep raw JSON tools as debugging escape hatches.
|
|
13
13
|
- Added response caps, truncation metadata, and next-step suggestions for summarized node output.
|
|
14
14
|
|
|
15
|
+
## 0.1.2
|
|
16
|
+
|
|
17
|
+
### Patch Changes
|
|
18
|
+
|
|
19
|
+
### Fixed: package extension entrypoint
|
|
20
|
+
|
|
21
|
+
- Added the package root `index.ts` extension entrypoint so pi can load the Figma tools from the published package manifest.
|
|
22
|
+
- Documented the extension's benefits over Figma MCP in the package README.
|
|
23
|
+
|
|
15
24
|
## 0.1.1
|
|
16
25
|
|
|
17
26
|
### Patch Changes
|
package/README.md
CHANGED
|
@@ -2,6 +2,18 @@
|
|
|
2
2
|
|
|
3
3
|
A pi extension and skill package that exposes native Figma tools for design exploration and design-to-code workflows. The default tools return compact, LLM-ready design context instead of raw Figma JSON.
|
|
4
4
|
|
|
5
|
+
## Benefits over Figma MCP
|
|
6
|
+
|
|
7
|
+
This package is Pi-native and uses Figma's REST API directly, with tools designed specifically for LLM-friendly design exploration and design-to-code workflows.
|
|
8
|
+
|
|
9
|
+
- **No hosted Figma MCP quota path:** the extension calls Figma's REST API directly instead of using a hosted Claude/Figma connector quota path. It is still subject to Figma API limits, and the client smooths calls with a fixed 1s limiter plus a 5-minute TTL cache.
|
|
10
|
+
- **Better LLM-shaped output:** `figma_get_node_summary`, `figma_explain_node`, and `figma_get_implementation_context` avoid raw Figma JSON by default. They cap depth, skip hidden nodes, vector internals, and component internals unless requested, and return `metadata.nextSteps` when follow-up inspection would help.
|
|
11
|
+
- **Design-to-code specialization:** `figma_get_implementation_context` extracts fields, buttons, layout measurements, typography, colors, spacing, assets, and a React-friendly component hierarchy instead of simply relaying generic server output.
|
|
12
|
+
- **Safer local auth UX:** `figma_configure_auth` uses masked local prompting and stores the token in Pi auth storage. The model never sees the token.
|
|
13
|
+
- **Good raw escape hatches:** raw `figma_get_file` and `figma_get_nodes` tools are available for debugging, while tool descriptions steer agents toward processed tools first.
|
|
14
|
+
- **Local asset handling:** `figma_render_nodes` can download rendered images into an OS temp directory or a user-provided directory, which is useful for implementation and visual QA.
|
|
15
|
+
- **Broader inspection surface:** styles, variables, components, component sets, component search, metadata, text extraction, rendering, summaries, explanations, and implementation context are exposed as separate native tools.
|
|
16
|
+
|
|
5
17
|
## Tools
|
|
6
18
|
|
|
7
19
|
### Processed, LLM-ready tools (preferred)
|