view-writer

Generate typed Page Object Model view classes for Decentraland Explorer UI automation.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/decentraland/explorer-automation --skill view-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: view-writer
Source: https://github.com/decentraland/explorer-automation/tree/main/.claude/skills/view-writer
Command: npx skills add https://github.com/decentraland/explorer-automation --skill view-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the repetitive, error-prone work of hand-coding Page Object Model (POM) view classes for the Decentraland Explorer UI by giving you a consistent way to define locators and typed interactions for every screen, panel, dialog, and overlay.

Core Features & Use Cases

  • Creates and updates POM views for Explorer UI test automation, including full screens, standalone panels, dialogs, and overlays.
  • Builds panel tab/section views using the BaseSection pattern so tests can switch and interact with sub-areas cleanly.
  • Defines typed element fields (Locatable, Readable, Clickable, Writable) and adds helper methods with Allure steps for higher-level actions.
  • Supports nested sub-views for repeated UI structures (like grid items or slot collections) using BaseClickableView and parent-passed locators.
  • Chooses stable locator strategies (prefers By.ID, then By.NAME, then By.PATH) and can request locator discovery from the running instrumented Explorer.

Quick Start

Trigger the view-writer skill and tell it which Explorer UI area you need (e.g., panel + tab) plus any known element names/IDs you already have.

Frequently Asked Questions about view-writer

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

FAQPage Schema
How do I create Page Object Model view classes for Decentraland Explorer UI automation?

Page Object Model view classes for Decentraland Explorer UI automation are generated by translating UI elements into typed locators and interaction primitives using BaseView, BaseSection, and BaseClickableView structures with region-ordered C# output.

What locator strategies should I use for Unity Explorer UI test automation?

For Unity Explorer UI test automation, stable locator strategies prefer By.ID first, then By.NAME, then By.PATH. You can also request locator discovery from the running instrumented Explorer via the alttester-explorer agent.

How do I structure nested sub-views for repeated UI elements like grid items in Explorer panels?

Nested sub-views for repeated UI structures like grid items use the BaseClickableView pattern with parent-passed locators, allowing clean interaction with repeated elements within Explorer screens and dialogs.

Can I build panel tab and section views for Explorer dialogs using the Page Object Model?

Yes, panel tab and section views are built using the BaseSection pattern, enabling tests to switch and interact with sub-areas cleanly within Explorer dialogs and standalone panels.

Do I need YAML frontmatter to generate Explorer UI view classes?

Yes, YAML frontmatter discovery info is required to generate Explorer UI view classes, along with selecting the correct BaseView, BaseSection, or BaseClickableView structure for the target screen or dialog.

What typed element fields are available when automating Explorer UI screens with NUnit?

Typed element fields available for Explorer UI automation include Locatable, Readable, Clickable, and Writable, with helper methods that add Allure steps for higher-level actions within NUnit test suites.