skills/pencil-skills/pencil-mcp-replace-all-matching-properties/SKILL.md
Batch replace matching style properties (colors, fonts, sizes) across nodes in a Pencil .pen file via the replace_all_matching_properties MCP tool. Use when the user explicitly mentions Pencil and needs to globally swap colors, update font families, migrate to a new brand style, or batch-adjust spacing across frames.
npx skillsauth add partme-ai/full-stack-skills pencil-mcp-replace-all-matching-propertiesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill is designed to call the Pencil MCP tool:
replace_all_matching_propertiesIf your client namespaces MCP tools, it may appear as mcp__pencil__replace_all_matching_properties.
Even if a trigger phrase matches, you must verify the user's intent:
If the answer is NO, do NOT use this skill. (e.g., "Replace properties" might refer to refactoring code).
CRITICAL PREREQUISITE: You must ONLY use this skill when the user EXPLICITLY mentions "Pencil".
ALWAYS use this skill when:
Trigger phrases include:
filePath (string, optional).parents (array, required): IDs of parent nodes to search within.properties (array, required): List of replacement rules.
property, match (value to find), and replace (new value).fills: #FF0000, Replace with fills: #0000FF".replace_all_matching_properties(...).get_screenshot to verify the global change.Replace all instances of Red (#FF0000) with Blue (#0000FF) across the entire document.
{
"properties": [
{
"property": "fills",
"from": { "color": "#FF0000" },
"to": { "color": "#0000FF" }
}
]
}
Change the font family from "Arial" to "Roboto" only within the Footer section.
{
"parents": ["frame:footer"],
"properties": [
{
"property": "fontFamily",
"from": "Arial",
"to": "Roboto"
}
]
}
Update multiple properties (color and font) simultaneously across several frames to migrate to a new brand style.
{
"parents": ["frame:home", "frame:profile"],
"properties": [
{
"property": "fills",
"from": { "color": "#OLD_COLOR" },
"to": { "color": "#NEW_COLOR" }
},
{
"property": "fontSize",
"from": 12,
"to": 14
}
]
}
English keywords: replace properties, batch update, global change, style refactor, bulk edit, theme switch
Chinese keywords (中文关键词): 替换属性, 批量更新, 全局修改, 样式重构, 批量编辑, 主题切换
development
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.
tools
Creates new uni-app projects via the official CLI or HBuilderX with Vue 2/Vue 3 template selection, manifest.json and pages.json configuration, and directory structure setup. Use when the user wants to scaffold a new uni-app project, initialize project files with a single command, or set up the development environment.
tools
Browses, installs, configures, and manages plugins from the uni-app plugin market (ext.dcloud.net.cn) including component plugins, API plugins, and template plugins with dependency handling. Use when the user needs to find and install uni-app plugins, configure plugin settings, manage plugin dependencies, or integrate third-party components.
tools
Develops native Android and iOS plugins for uni-app including module creation, JavaScript-to-native communication, and plugin packaging for distribution. Use when the user needs to build custom native modules, extend uni-app with native capabilities (camera, Bluetooth, sensors), or create publishable native plugins.