enterprise-web-library

Configure opencode on a new development machine for EWL work by creating the global AGENTS.md and granting access to the EWL source, EWL System Manager source, EWL folder, and EWL client systems directory. Use when setting up opencode on a new machine, or when the user asks to bootstrap, initialize, or configure global opencode for EWL.

Run local EWL Development Utility (DU) operations on EWL systems. Use when asked to run DU operations such as sync or update-data against a particular path or system.

Database schema migration using FluentMigrator with the EWL Data Migrator project

Inspect and troubleshoot EWL systems hosted in Azure — locating an installation's App Service, Container App Job, and Log Analytics workspace, and reliably reading Container App (data migrator) console and system logs. Use when checking whether a deploy's data migrator ran, reading container logs for a hosted installation, or investigating an installation's Azure resources. Companion to ewl-azure-pipelines, which covers the build/deploy pipelines that create these resources.

Test changes to EWL agent rules, subagents, skills, OpenCode plugins, and MCP tools by driving OpenCode headlessly, capturing transcripts, and cleaning up afterwards. Load this skill when verifying changes to anything under Library\Files\Agent Rules.md, Library\Files\Agents\, Library\Files\Agent Skills\, Library\Files\OpenCode Plugins\, or Library\Files\OpenCode Tools\.

Azure Pipelines CI/CD for EWL systems including build templates, deploy templates, and pipeline code generation

EWL generated data access layer including table retrievals, modifications, row constants, sequences, and caching

Create and configure EWL pages with parameters, URL routing, parent hierarchy, and access control

Create server-side console apps and call them from EWL web apps or other apps in the system. Use when creating a new console app, background worker, bulk operations worker, batch job, scheduled task, background job, background process, worker process, offline job, offline processor, or Exe project in an EWL system.

Set up EWL user management with database schema, roles, identity providers, and the SystemUserManagementProvider

Drive a locally running EWL web application in a headed/headless browser (Playwright .NET) to verify flows, smoke-test pages, and reproduce UI bugs. Use when asked to navigate an EWL Web App as a specific user, exercise a page or form flow, or reproduce a UI issue locally. Tests are ad-hoc: edit a single throwaway Playwright .NET driver, run it, report results with screenshots, then tear down. Covers the no-hang process-launch patterns required to start EWL/Kestrel and IIS Express servers from an agent tool without wedging the call.

Class inventory of EWL and TEWL abstractions for identifying missed usage in code reviews

Mercurial version control for EWL systems; load this skill when a .hg directory is present instead of using Git commands

Advanced EWL page patterns including forms, PostBack, validation, client-side modification, and component state

Build data tables with EwfTable including pagination, sorting, row activation, selection, and group actions