new-plugin

Solid

Factory line for adding a new HAR verification plugin (like playwright or rocketsim) for any framework — research the framework docs, build the template under src/templates/plugins/, register it everywhere, validate on a real repository, and open a PR. Use when asked to add/create a plugin, plugin template, or framework integration (e.g. "add a Cypress plugin", "support Maestro", "new plugin for vitest browser mode").

Testing & QA 88 stars 11 forks Updated 3 days ago Apache-2.0

Install

View on GitHub

Quality Score: 85/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# New HAR plugin factory line > **Instance of the [factory-line](../factory-line/SKILL.md) template.** > Program data: [`new-plugin.line.json`](../factory-line/examples/new-plugin.line.json). > Stations here are sequential phases, not GitHub issues. The product is a > plugin, not a runtime migration — that is why this line exists as a second > instance. Ship a new verification plugin `<id>` for framework `<framework>` end-to-end: research → template → registration → local validation → real-repo validation → PR. A plugin is an installable bundle under `src/templates/plugins/<id>/` applied by `har env add-plugin <id>`. It registers **generic stage kinds** (`test`, `verify`, `custom`, …) in the target repo's `.har/stages.json`. Philosophy (AGENTS.md): *plugins install stages; agents only talk to the stage registry.* Never add stack-specific MCP tools or core stages. Reference implementations: `src/templates/plugins/playwright/` (web e2e, package.json merge, CI workflow) and `src/templates/plugins/rocketsim/` (external-tool flows, no package merge). Pick whichever is closer to `<framework>` as your baseline. ## Phase 0 — Inputs Establish before doing anything (ask the user only if not inferable): - **Plugin id** — short lowercase slug (`cypress`, `maestro`, `k6`). - **Framework** — what it tests and on which stack (web, iOS, API, load…). - **Stage id** — what the stage does, not the brand (`browser-e2e`, `mobile-flows`, `load-test`). Brand goes in the description and doc...

Details

Author: os-factory
Repository: os-factory/har
Created: 2 months ago
Last Updated: 3 days ago
Language: TypeScript
License: Apache-2.0

Integrates with

GitHub · DevTools Vitest · Testing Playwright · Testing Model Context Protocol · AI

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

plugin-factory

Scaffold a new plugin for this marketplace. Use this whenever the user wants to create, add, bootstrap, or start a new plugin — phrases like "new plugin", "scaffold a plugin", "add a plugin to the marketplace", or "I want to build a plugin that…". It runs a deterministic generator that emits a valid, wired-in, red-by-default skeleton, then guides the invariant-first interview to fill it in.

1 Updated today

JRichlen

Web & Frontend Solid

build-cli-plugin

Build a plugin or adapter for a CLI tool using the abstract base class pattern. Covers defining the contract (static fields, required methods), choosing an installation strategy (symlink, copy, append-to-file), implementing detection, install/uninstall with idempotency, listing, auditing, and registering the plugin. Use when adding support for a new framework to a CLI installer, building a plugin system for any multi-target tool, or extending an existing adapter architecture.

33 Updated today

pjt222

AI & Automation Listed

create-plugin

Build a Clodex plugin end to end - scaffold it, wire the surfaces it needs, and verify it against the real loader. Usage - /clodex-plugin-builder:create-plugin <id> [what it should do]

50 Updated today

avirtual