pencil-mcp-get-guidelines
Tools
This skill is designed to call the Pencil MCP tool:
get_guidelines
If your client namespaces MCP tools, it may appear as mcp__pencil__get_guidelines.
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 need instructions on How to design for a specific system in Pencil.
- You are generating code (
topic='code'). - You are building a landing page (
topic='landing-page'). - You need to know the
.penschema details.
Trigger phrases include:
- "Get Pencil design guidelines" (获取 Pencil 设计指南)
- "How to use Tailwind in Pencil?" (怎么在 Pencil 里用 Tailwind?)
- "Pencil coding rules" (Pencil 编码规则)
- "Pencil landing page best practices" (Pencil 落地页最佳实践)
Input Parameters
topic(string, required): The topic to retrieve.design-system: Composing screens with components.code: Code generation rules.tables: Working with tables.tailwind: Tailwind CSS specs.landing-page: High-conversion page design.
How to use this skill
- Select Topic: Choose the relevant topic based on user intent.
- Call Tool:
get_guidelines(topic='design-system'). - Read & Apply: Use the returned text as instructions for your subsequent
batch_designcalls.
Examples
1. Simple: Design System Guidelines
Understand how to use the available components.
{
"topic": "design-system"
}
2. Medium: Code Handoff Guidelines
Get rules for generating code from the design, useful for "Code Handoff" tasks.
{
"topic": "code"
}
3. Complex: Landing Page Best Practices
Get specific guidelines for designing high-conversion landing pages when the user asks for a marketing site.
{
"topic": "landing-page"
}
Keywords
English keywords: get guidelines, design rules, best practices, coding specs, documentation, how-to
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