AUTHORITATIVE REFERENCE for WebWorks ePublisher projects. Use when working with .wep/.wrp/.wxsp project files, understanding project structure, file resolver hierarchy, target configurations, or source document groups.
/plugin marketplace add quadralay/webworks-claude-skills/plugin install webworks-claude-skills@webworks-claude-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/file-resolver-guide.mdreferences/project-parsing-guide.mdreferences/user-interaction-patterns.mdreferences/version-compatibility.mdscripts/copy-customization.pyscripts/manage-sources.shscripts/parse-targets.pyCore knowledge about WebWorks ePublisher projects, file structure, and conventions. This skill provides foundational understanding without automation or format-specific details. </objective>
<overview>WebWorks ePublisher transforms source documents (Word, FrameMaker, DITA, Markdown) into multiple output formats (Reverb, PDF, CHM, etc.) using a project-based workflow. </overview>
<related_skills>
This skill provides foundational knowledge used by other skills in this plugin:
| Skill | When to Use |
|---|---|
| automap | After understanding project structure, use automap to execute builds |
| reverb | After building Reverb output, use reverb skill to test and customize |
Typical workflow:
</related_skills>
<key_concepts>
An ePublisher project (.wep file) contains:
ePublisher resolves files through a 4-level hierarchy (highest to lowest priority):
[Project]/Targets/[TargetName]/[Project]/Formats/[FormatName]/[Project]/Formats/[FormatName].base/C:\Program Files\WebWorks\ePublisher\[version]\Formats\For complete details, see: references/file-resolver-guide.md
The .wep file is XML containing target definitions:
<Format Name="WebWorks Reverb 2.0"
TargetID="abc123"
TargetName="Help Output">
<OutputDirectory>Output\Help</OutputDirectory>
<FormatConfiguration>
<FormatSetting Name="toolbar-generate" Value="true"/>
<FormatSetting Name="header-generate" Value="false"/>
</FormatConfiguration>
</Format>
Documents are organized into groups within projects:
<Group Name="User Guide" GroupID="grp123">
<Document Name="chapter1.docx" DocumentID="doc456"/>
<Document Name="chapter2.docx" DocumentID="doc789"/>
</Group>
</key_concepts>
<scripts>Extract target information from a project file:
./parse-targets.sh <project-file>
Returns JSON with target names, IDs, formats, and output directories.
List and manage source document groups:
./manage-sources.sh <project-file> [list|add|remove]
Copy format files from installation to project with structure validation:
./copy-customization.py --source <install-file> --destination <project-file>
Validates parallel folder structure and creates directories as needed. </scripts>
<references>file-resolver-guide.md - Complete file resolution hierarchyproject-parsing-guide.md - Detailed project file structureuser-interaction-patterns.md - UX patterns for ePublisher workflowsversion-compatibility.md - Supported versions and breaking changes
</references>
<common_tasks>
./scripts/parse-targets.sh /path/to/project.wep
Check the file resolver hierarchy:
[Project]/Formats/[FormatName]/[Project]/Formats/[FormatName].base/./scripts/manage-sources.sh /path/to/project.wep list
</common_tasks>
<troubleshooting>Cause: Project file doesn't contain <Format> elements.
Solutions:
Cause: Path is incorrect or file doesn't exist.
Solutions:
C:\projects\my-proj\my-proj.wep)Cause: File is not a recognized ePublisher project type.
Solutions:
<success_criteria>
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.