pencil-mcp-get-style-guide
Tools
This skill is designed to call the Pencil MCP tool:
get_style_guide
If your client namespaces MCP tools, it may appear as mcp__pencil__get_style_guide.
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.
CRITICAL PREREQUISITE: You must ONLY use this skill when the user EXPLICITLY mentions "Pencil".
ALWAYS use this skill when:
- You have selected a specific style (from tags) and need its Details for Pencil.
- You need the color palette or font stack of a specific "Look and Feel".
- The user says "Use the 'Cyberpunk' style" in Pencil.
Trigger phrases include:
- "Get Pencil style details" (获取 Pencil 风格详情)
- "Apply style X in Pencil" (在 Pencil 中应用风格 X)
- "Retrieve Pencil style guide" (检索 Pencil 风格指南)
Input Parameters
id(string, optional): The Style Guide ID.tags(array, optional): 5-10 tags matching the desired style (fromget_style_guide_tags).
How to use this skill
- Prerequisite: Usually call
get_style_guide_tagsfirst to know what's available. - Call Tool:
get_style_guide(tags=["Modern", "SaaS"])orget_style_guide(id="..."). - Apply: Use the returned metadata (colors, fonts) in your
batch_designorset_variablescalls.
Examples
1. Simple: Get by ID
Retrieve a specific style guide using its unique identifier.
{
"id": "style:12345"
}
2. Medium: Search by Single Tag
Find a style guide that matches a specific keyword (e.g., "Modern").
{
"tags": ["Modern"]
}
3. Complex: Multi-Tag Search
Find a style guide that fits a complex criteria (e.g., "Dark" mode "SaaS" dashboard).
{
"tags": ["Dark", "SaaS", "Dashboard"]
}
Keywords
English keywords: get style guide, style details, visual specs, color palette, font rules, apply theme
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.
68electron
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.
38ascii-image-to-ascii
“Convert an image into ASCII art (readable + detail variants, width/charset controls, optional ANSI), for terminal previews and plain-text image substitutes.”
34ant-design-vue
Provides comprehensive guidance for Ant Design Vue (AntDV) component library for Vue 3. Covers installation, usage, API reference, templates, and all component categories. Use when building enterprise-class UI with Vue 3 and Ant Design.
33