module-svg-icon

Creates a house-style SVG icon and applies it as a module's package icon in .application.config.

23|10|Updated Aug 31, 2017
One-click install
npx skills add https://github.com/IntentArchitect/Intent.Modules --skill module-svg-icon-intentarchitect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: module-svg-icon
Source: https://github.com/IntentArchitect/Intent.Modules/tree/main/Tests/ModuleBuilderSkills/.opencode/skills/module-svg-icon
Command: npx skills add https://github.com/IntentArchitect/Intent.Modules --skill module-svg-icon-intentarchitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting an Intent Architect module's package icon requires embedding a large base64 data URI into the module's .application.config file, which is error-prone and wasteful when passed through an agent's context. This Skill crafts the SVG and applies it via script so the encoded payload never needs manual handling. ## Core Features & Use Cases - House-Style SVG Authoring: Generates a circular badge icon with a gradient fill and white glyph following a defined default style guide. - Script-Based Application: Updates only the root <icon> and <iconType> elements in .application.config via a shell script, asserting exactly one match before writing. - Safe Verification: Confirms changes through file diffs without ever reading or reproducing the base64 payload. - Use Case: A maintainer says "create an icon showing a database cylinder for this module" — the Skill drafts the SVG, encodes it, updates the config, regenerates the .imodspec iconUrl via the Software Factory, and cleans up the temp file. ## Quick Start Create and apply a module icon depicting a shield with a checkmark for this module's package.

Frequently Asked Questions about module-svg-icon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set a module's package icon in Intent Architect?▼

Set the root <icon> element in the module's .application.config to a base64 SVG data URI and set <iconType> to UrlImagePath. Run the Software Factory afterward so it regenerates the .imodspec <iconUrl> from that value.

Why should the module icon be applied with a script instead of editing files directly?▼

The icon value is a base64 data URI often tens of thousands of characters long, which risks transcription corruption if passed through an agent's context. A script computes and writes the encoding directly so the payload is never read or reproduced manually.

Can I edit the .imodspec iconUrl directly to change the module icon?▼

No. The .imodspec <iconUrl> is generated by the Software Factory from the .application.config icon value, so hand-edits are silently discarded on the next run. Always update .application.config and regenerate.

Does this skill decide what the module icon should look like?▼

No. It requires the caller to supply the icon's intended visual description and uses it exactly as given. It only crafts the SVG from that description and applies it, never inventing or sourcing the concept itself.

What is the difference between the module package icon and element icons in .application.config?▼

The package icon is the single attribute-less root <icon> element paired with <iconType>. Other <icon type="..." source="..."> entries configure per-designer-element icons and must be left alone; those are handled by a different mechanism.