Release v0.2.0: Add comprehensive ESLint plugin integration

Added official @yfiles/eslint-plugin documentation and guidance across multiple skills:

Skills Updated:
- yfiles-init: Comprehensive ESLint setup guide with examples and configuration
- yfiles-nodestyle-*: Added BaseClass() rule notes for interface implementation
- yfiles-interactivity: Added event listener rule notes
- yfiles-graphbuilder: Added setter methods rule warning

Documentation:
- Added complete ESLint configuration examples (flat config and legacy)
- Documented all 8 yFiles ESLint rules with explanations
- Added TypeScript configuration guidance for typed linting
- Updated README with ESLint feature
- Created CLAUDE.md for repository guidance

This release enhances the plugin's ability to help LLMs and developers
write correct yFiles 3.0 code by leveraging the official ESLint plugin
that catches common mistakes from deprecated yFiles 2.6 patterns.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: yGuy

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "yfiles",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Comprehensive skills for developing yFiles for HTML applications including initialization, graph building, layouts, custom styling, and interactivity features",
   "author": {
     "name": "yFiles Team",

CHANGELOG.md

@@ -5,6 +5,24 @@ All notable changes to the yFiles Claude Plugin will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.2.0] - 2026-02-10
+
+### Added
+- ESLint plugin documentation in `yfiles-init` skill
+  - Comprehensive ESLint configuration guide in reference.md covering installation, flat config, and legacy .eslintrc
+  - Detailed explanation of all 8 yFiles ESLint rules
+  - Complete eslint.config.mjs example in examples.md
+  - TypeScript configuration guidance for typed linting
+  - Added ESLint setup to implementation checklist
+- ESLint rule notes across multiple skills:
+  - `yfiles-nodestyle-basic`, `yfiles-nodestyle-configure`, `yfiles-nodestyle-interaction`, `yfiles-nodestyle-advanced`: Note about `@yfiles/fix-implements-using-baseclass` rule
+  - `yfiles-interactivity`: Note about `@yfiles/replace-legacy-event-listeners` rule for correct event handling
+  - `yfiles-graphbuilder`: Warning about `@yfiles/suggest-setter-methods` rule for readonly properties
+- ESLint integration feature in README.md
+
+### Changed
+- Updated `yfiles-init` skill implementation steps to include ESLint configuration as recommended Step 4
+
 ## [0.1.0] - 2026-02-09
 
 ### Added
@@ -104,4 +122,5 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## Version History
 
+- **0.2.0** (2026-02-10) - Added comprehensive ESLint plugin integration
 - **0.1.0** (2026-02-09) - Initial release with 8 comprehensive skills

CLAUDE.md

@@ -0,0 +1,228 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## About This Repository
+
+This is a **Claude Code plugin** for yFiles for HTML development. It provides 8 specialized skills that help developers create yFiles applications more effectively. This is NOT a traditional software project - it's a collection of skill definitions, examples, and documentation.
+
+## Repository Structure
+
+```
+yfiles-claude-plugin/
+├── .claude-plugin/
+│   └── plugin.json           # Plugin metadata and MCP server configuration
+├── skills/                    # Skill definitions (8 skills)
+│   ├── yfiles-init/
+│   ├── yfiles-graphbuilder/
+│   ├── yfiles-layout/
+│   ├── yfiles-nodestyle-basic/
+│   ├── yfiles-nodestyle-configure/
+│   ├── yfiles-nodestyle-interaction/
+│   ├── yfiles-nodestyle-advanced/
+│   └── yfiles-interactivity/
+├── .github/workflows/
+│   └── validate.yml          # GitHub Actions validation
+├── README.md                 # User-facing documentation
+├── QUICKREF.md              # Quick reference for all skills
+├── CONTRIBUTING.md          # Development guidelines
+├── CHANGELOG.md             # Version history
+└── SETUP.md                 # GitHub publishing guide
+```
+
+## Skill Architecture
+
+Each skill directory follows a consistent structure:
+
+- **SKILL.md** - Main skill definition with frontmatter metadata (name, description, triggers)
+- **examples.md** - 7-15 complete code examples from official yFiles demos
+- **reference.md** - Detailed API documentation and patterns
+- **patterns.md** (optional) - Common implementation patterns
+- **algorithms.md** (optional) - Algorithm-specific guidance (layout skill)
+- **advanced.md** (optional) - Advanced topics
+
+### Skill Frontmatter Format
+
+```markdown
+---
+name: skill-name
+description: Brief description with rich trigger keywords for auto-activation
+---
+```
+
+The description field is critical - it contains keywords that Claude uses to automatically activate the skill.
+
+## Development Workflow
+
+### Viewing/Testing the Plugin
+
+This plugin is consumed by Claude Code, not run directly. To test:
+
+```bash
+# Install plugin locally
+/plugin install yfiles@dir@/home/muellese/html-package/yfiles-3.0.0.4/yfiles-claude-plugin
+
+# Or use with --plugin-dir flag
+claude --plugin-dir /home/muellese/html-package/yfiles-3.0.0.4/yfiles-claude-plugin
+
+# Invoke a skill explicitly
+/yfiles:init
+/yfiles:graphbuilder
+```
+
+### Validating Plugin Structure
+
+The repository includes GitHub Actions validation:
+
+```bash
+# Validation checks:
+# - .claude-plugin/plugin.json exists and is valid JSON
+# - Each skill has SKILL.md with proper frontmatter
+# - All referenced files exist
+# - No common structural issues
+```
+
+There are no local build or test commands - validation happens through GitHub Actions or manual testing with Claude Code.
+
+### Creating a New Skill
+
+1. Create directory under `skills/` with descriptive name (e.g., `yfiles-edge-styles/`)
+2. Add **SKILL.md** with frontmatter and structured content:
+   - Quick Start section
+   - "Before Implementing" section with MCP tool calls
+   - Core Concepts
+   - When to Implement
+   - Cross-references to other skills
+3. Add **examples.md** with 7-15 complete, runnable examples
+4. Add **reference.md** with full API documentation
+5. Update `README.md` to include the new skill
+6. Update `CHANGELOG.md` with the addition
+7. Test with actual yFiles projects
+
+### Modifying Existing Skills
+
+When updating skills:
+
+1. Read the entire skill (SKILL.md, examples.md, reference.md) first
+2. Maintain consistent structure and style with other skills
+3. Verify examples are extracted from official yFiles demos when possible
+4. Update trigger keywords in description if adding new use cases
+5. Cross-reference related skills
+6. Update CHANGELOG.md
+
+## Key Concepts
+
+### MCP Server Integration
+
+This plugin configures the yFiles MCP server in `.claude-plugin/plugin.json`:
+
+```json
+{
+  "mcpServers": {
+    "yfiles": {
+      "command": "npx",
+      "args": ["-y", "yfiles-dev-suite@latest", "--mcp"]
+    }
+  }
+}
+```
+
+All skills are designed to work with the yFiles MCP server for real-time API access. Skills should reference MCP tools using the `yfiles:` prefix (e.g., `yfiles:yfiles_get_symbol_details`).
+
+### Progressive Disclosure Pattern
+
+Skills follow a progressive disclosure pattern:
+- **SKILL.md**: Concise overview (under 100 lines), essential patterns
+- **examples.md**: Complete working examples with comments
+- **reference.md**: Exhaustive API details, configurations, best practices
+
+This prevents overwhelming Claude with too much information upfront while keeping details accessible.
+
+### Trigger-Based Activation
+
+Skills are auto-activated based on trigger keywords in the description field. Include rich keywords covering:
+- Feature names ("GraphBuilder", "HierarchicalLayout")
+- Action verbs ("initialize", "load", "arrange", "customize")
+- Use cases ("create app", "build graph from data")
+- API names ("createVisual", "isHit", "query-item-tool-tip")
+
+### Documentation Extraction
+
+Examples should be extracted from official yFiles demos when possible:
+- Ensures accuracy and best practices
+- Provides real-world, tested code
+- Maintains consistency with yFiles conventions
+- Reference the source demo in comments
+
+## Important Development Rules
+
+### What This Repository Is NOT
+
+- **NOT a yFiles application** - Don't try to run yFiles code here
+- **NOT a build project** - No compilation, bundling, or testing commands
+- **NOT a Node.js package** - No `npm install` or `package.json`
+
+### What This Repository IS
+
+- **A documentation repository** - Markdown files with structured content
+- **A skill library** - Definitions that Claude Code consumes
+- **An MCP integration** - Connects Claude to yFiles documentation
+- **A reference guide** - Examples and patterns for yFiles development
+
+### Guidelines for Modifications
+
+1. **Preserve structure** - Don't reorganize the skill file structure
+2. **Maintain consistency** - Follow patterns from existing skills
+3. **Use official examples** - Extract from yFiles demos, don't invent code
+4. **Test with Claude Code** - Verify skills activate correctly
+5. **Update all related files** - README, CHANGELOG, cross-references
+6. **Keep SKILL.md concise** - Move details to examples.md or reference.md
+7. **Rich trigger keywords** - Add comprehensive keywords to descriptions
+8. **Follow naming conventions** - Skills use `yfiles-feature-name` format
+
+## Version Management
+
+This plugin follows semantic versioning:
+- **MAJOR**: Breaking changes (removed skills, incompatible structure changes)
+- **MINOR**: New skills or backward-compatible features
+- **PATCH**: Bug fixes, documentation improvements, example updates
+
+Update version in `.claude-plugin/plugin.json` when making changes.
+
+## Installation Methods
+
+Users can install this plugin in three ways:
+
+1. **From GitHub** (when published):
+   ```bash
+   /plugin install yfiles@github@yworks/yfiles-for-html-claude-plugin
+   ```
+
+2. **From local directory**:
+   ```bash
+   /plugin install yfiles@dir@/path/to/yfiles-claude-plugin
+   ```
+
+3. **Copy to plugins directory**:
+   ```bash
+   cp -r yfiles-claude-plugin ~/.claude/plugins/yfiles
+   ```
+
+## Related Files
+
+- **SETUP.md** - Complete guide for publishing to GitHub
+- **CONTRIBUTING.md** - Detailed contribution guidelines
+- **QUICKREF.md** - Quick reference for all skills (for users)
+- **README.md** - User-facing documentation
+- **CHANGELOG.md** - Version history
+
+## Working with yFiles Context
+
+This plugin is designed to work within yFiles for HTML projects. When users invoke skills:
+
+1. Skills reference the yFiles MCP server for current API information
+2. Examples assume a yFiles project structure with license.json
+3. Code uses yFiles for HTML 3.0+ API patterns
+4. Import paths follow the package convention: `@yfiles/yfiles`
+
+The plugin itself does NOT contain yFiles code - it provides guidance for writing yFiles code.

README.md

@@ -28,6 +28,7 @@ This plugin includes 8 specialized skills covering all aspects of yFiles for HTM
 ✅ **API References** - Complete documentation for each feature
 ✅ **MCP Integration** - Works with yFiles MCP server for up-to-date API info
 ✅ **Progressive Disclosure** - Main skill files with detailed reference docs
+✅ **ESLint Integration** - Includes guidance for the official @yfiles/eslint-plugin to catch common mistakes
 
 ## Installation
 

skills/yfiles-graphbuilder/SKILL.md

@@ -61,6 +61,8 @@ See [examples.md](examples.md) for full working code.
 - **Provider functions**: For computed values (styles, labels, layouts)
 - **updateGraph()**: Updates existing graph instead of rebuilding
 
+**Important**: Never directly assign to readonly properties like `node.layout`, `edge.sourceNode`, or `edge.targetNode`. Use IGraph methods instead (e.g., `graph.setNodeLayout()`, `graph.setEdgePorts()`). The `@yfiles/eslint-plugin` rule `@yfiles/suggest-setter-methods` warns about these mistakes.
+
 ## After Building
 
 Graph likely needs layout:

skills/yfiles-init/SKILL.md

@@ -25,6 +25,7 @@ Setup Progress:
 - [ ] Create HTML entry point
 - [ ] Create main TypeScript/JavaScript file
 - [ ] Adjust import paths for license
+- [ ] Configure ESLint with yFiles plugin (recommended)
 - [ ] Test in browser
 ```
 
@@ -60,7 +61,17 @@ License path depends on demo location:
 - `demos-ts/category/demo/`: Use `../../../lib/license.json`
 - Adjust depth as needed
 
-**Step 4: Test**
+**Step 4: Configure ESLint (Recommended)**
+
+The official `@yfiles/eslint-plugin` helps catch common mistakes and ensures yFiles 3.0 best practices:
+
+```bash
+npm i -D eslint typescript typescript-eslint @yfiles/eslint-plugin
+```
+
+See [reference.md](reference.md) for complete ESLint configuration.
+
+**Step 5: Test**
 
 ```bash
 npm start

skills/yfiles-init/examples.md

@@ -23,6 +23,60 @@ Complete file templates for initializing yFiles applications.
 </html>
 ```
 
+## ESLint Configuration (Recommended)
+
+### eslint.config.mjs
+
+```javascript
+// eslint.config.mjs
+import tseslint from "typescript-eslint";
+import yfilesconfigs from "@yfiles/eslint-plugin/configs";
+
+export default tseslint.config(
+  // TypeScript rules (type-checked)
+  ...tseslint.configs.recommendedTypeChecked,
+
+  // yFiles plugin preset (type-checked)
+  yfilesconfigs.recommendedTypeChecked,
+
+  // Configure TypeScript project for typed linting
+  {
+    languageOptions: {
+      parserOptions: {
+        project: ["./tsconfig.json"],
+        tsconfigRootDir: import.meta.dirname,
+      },
+    },
+  },
+
+  // Optional: customize individual rules
+  {
+    rules: {
+      // Enforce yFiles 3.0 import syntax
+      "@yfiles/replace-legacy-imports": "error",
+      // Enforce BaseClass() wrapper for interfaces
+      "@yfiles/fix-implements-using-baseclass": "error",
+    },
+  }
+);
+```
+
+### Installation
+
+```bash
+npm i -D eslint typescript typescript-eslint @yfiles/eslint-plugin
+```
+
+### Usage
+
+```bash
+# Lint all files
+npx eslint .
+
+# Auto-fix issues
+npx eslint . --fix
+```
+
 ## TypeScript Template (Minimal)
 
 ```typescript