pencil-mcp-get-variables
Tools
This skill is designed to call the Pencil MCP tool:
get_variables
If your client namespaces MCP tools, it may appear as mcp__pencil__get_variables.
When to use this skill
Intent Recognition (CRITICAL)
Even if a trigger phrase matches, you must verify the user's intent:
- Is the user explicitly asking to use "Pencil"?
- Is the current conversation context clearly about "Pencil" design tasks?
If the answer is NO, do NOT use this skill. (e.g., "Get variables" might refer to environment variables or code variables).
CRITICAL PREREQUISITE: You must ONLY use this skill when the user EXPLICITLY mentions "Pencil".
ALWAYS use this skill when:
- You need to know the available Design Tokens (Colors, Typography, Spacing) in Pencil.
- You want to use semantic names (e.g.,
primary-color) instead of hardcoded hex codes. - You are checking the current theme.
Trigger phrases include:
- "Get Pencil variables" (获取 Pencil 变量)
- "Read Pencil design tokens" (读取 Pencil 设计令牌)
- "Check Pencil colors" (检查 Pencil 颜色)
- "List Pencil theme values" (列出 Pencil 主题值)
Input Parameters
filePath(string, optional): Path to the.penfile.
How to use this skill
- Call Tool:
get_variables(). - Analyze Output: The result is a list/map of variable definitions.
- Apply: Use the variable IDs or names in
batch_designoperations (e.g.,fill: { type: "var", id: "var_123" }).
Examples
1. Simple: Get All Variables
Retrieve all variables defined in the current document.
{}
2. Medium: Get from Specific File
Read variables from a different design file (e.g., a shared library).
{
"filePath": "/Users/design/system/tokens.pen"
}
3. Complex: Theme Audit (Conceptual)
Same as simple, but used when auditing themes.
{}
Keywords
English keywords: get variables, read tokens, design system, theme values, color palette, typography tokens
Chinese keywords (中文关键词): 获取变量, 读取令牌, 设计系统, 主题值, 调色板, 字体令牌
More from partme-ai/full-stack-skills
vite
Guidance for Vite using the official Guide, Config Reference, and Plugins pages. Use when the user needs Vite setup, configuration, or plugin selection details.
68element-plus-vue3
Provides comprehensive guidance for Element Plus Vue 3 component library including installation, components, themes, internationalization, and API reference. Use when the user asks about Element Plus for Vue 3, needs to build Vue 3 applications with Element Plus, or customize component styles.
63vue3
Guidance for Vue 3 using the official guide and API reference. Use when the user needs Vue 3 concepts, patterns, or API details to build components, apps, and tooling.
54electron
Build cross-platform desktop applications with Electron, covering main/renderer process architecture, IPC communication, BrowserWindow management, menus, tray icons, packaging, and security best practices. Use when the user asks about Electron, needs to create desktop applications, implement Electron features, or build cross-platform desktop apps.
51uniapp-project
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
40ascii-cli-logo-banner
Entry point for ASCII CLI banners that routes to the Python built-in font skill or figlet.js/FIGfont skill. Use when the user wants a startup banner, ASCII logo, terminal welcome screen, or CLI branding for a service.
38