πŸ”Œ

wf-fake

πŸ”ŒPlugin

pavel-rp/wf-plugin

Installation

Add marketplace in Claude Code:
$/plugin marketplace add pavel-rp/wf-plugin
Step 2. Install plugin:
$/plugin install wf-fake@wf-marketplace
VibeIndex|
What it does
|

wf hermetic fixture-provider pack: the fake capability owning BOTH the wf capability-registry's delivery AND tracker surfaces with an in-memory, scripted, op-recording binding. Every abstract delivery/tracker op returns a scripted response from a fixture-local scripts file and appends its invocation to a machine-readable op log; no network, git, gh, or tracker MCP is ever reached (a static no-egress self-check enforces it). Registered only inside fixture registries as the sole owner of both surfaces (real-project co-registration correctly trips the overlap validation). The C016 skill-eval test seam. Ships /wf-fake:init for one-command self-registration.

πŸͺ

Part of

pavel-rp/wf-plugin

development
0
-
AddedAug 17, 2026

More from this repository10

πŸ”Œ
wf-gitπŸ”ŒPlugin

wf delivery-provider pack: the git capability owning the wf capability-registry's delivery surface (branch/commit/push/PR git+gh bindings). Ships /wf-git:init for one-command self-registration.

πŸ”Œ
wf-adoπŸ”ŒPlugin

wf tracker-provider pack: the ado capability owning the wf capability-registry's tracker surface (Azure DevOps work-item get/create/update/list-children/comment/status bindings and status/milestone/cycle queries, plus the AB#<id> PR-link autolink). Ships /wf-ado:init for one-command self-registration.

πŸ”Œ
wfπŸ”ŒPlugin

wf:* skill chain: spec/plan/implement, verify, QA (gen/run/auto/followup), classify, triage, branch/commit/pr. Domain-free, tracker-agnostic core β€” tracker/delivery integrations register via capability packs (wf-ado, wf-git, ...). Stack/domain capabilities (browser-qa, angular test-host, node-ts) each ship in their own plugin.

πŸ”Œ
wf-core-authoringπŸ”ŒPlugin

wf core-authoring pack: the core-authoring capability, carrying the knowledge for authoring the wf core plugin itself β€” the domain-free skill spine, the frozen contracts under the core plugin's _contracts folder, and the repository authoring rules its CI gates enforce. Declared kind: both; it ships its own skills and is authored to attach phase fragments. Its first contribution is the distilled authoring-vocabulary article it declares as constitution articles, so a session in this repository starts with those rules in its injected context; it also carries the craft-C4 authoring lint its own fixtures runner gates in CI, and it fills the new-skill.constraints composition point declared by /wf-author-caps:new-skill with this repository's core-only authoring rules, so a skill scaffolded here is core-compliant as it is emitted. Ships /wf-core-authoring:init for one-command self-registration of the capability, /wf-core-authoring:new-contract to scaffold a core contract pair that is green under the repository's contract-shape guard on its first run, /wf-core-authoring:add-term to land one authoring-glossary term together with the parse-contract entry that makes it enforceable, and /wf-core-authoring:preview-edit to see what a pending, uncommitted capability-manifest, registry, or taxonomy-contract edit would do before it reaches a commit.

πŸ”Œ
wf-angularπŸ”ŒPlugin

wf Angular stack pack: the angular capability owning the wf capability-registry's qa-execution host surface. Ships /wf-angular:qa-host (routed Angular test-host scaffolder + ephemeral backend-controller analog) and /wf-angular:test-page (browser-run black-box DI-level test harness). Every project-specific token in the scaffolded output is profile-slot-driven, so scaffolding a differently-named app emits no borrowed identifiers; surface: host composes with browser-qa's surface: engine with no partition collision. Tracker-agnostic (requires: git only). Ships /wf-angular:init for one-command self-registration.

πŸ”Œ
wf-node-tsπŸ”ŒPlugin

wf Node/TypeScript stack pack: the node-ts capability owning a dependency-free unit-test harness for pure TS helpers (parsers, formatters, coercion helpers) that need no Angular runtime. Ships /wf-node-ts:test-node; the implement phase aggregates its test-authoring guidance when registered. Tracker-agnostic (requires: git only). Ships /wf-node-ts:init for one-command self-registration.

πŸͺ
pavel-rp/wf-pluginπŸͺMarketplace

Marketplace

πŸ”Œ
wf-auditπŸ”ŒPlugin

wf audit pack: the audit capability (five domain-free adversarial verify lenses plus an optional composite retrospective report) co-located with the sr capability (a lightweight pre-commit adversarial self-review lens reusing the audit correctness rubric intra-plugin). Dependency-free (no requires) β€” composes in bare-core mode. Ships /wf-audit:init for one-command self-registration of both capabilities.

πŸ”Œ
wf-reviewπŸ”ŒPlugin

wf PR-review feature pack: the pr-review feature capability shipping the user-invoked /wf-review:address-pr and /wf-review:review-pr skills. Reads/verifies/addresses review comments and CI failures and posts verified findings entirely through the delivery provider's PR-interaction operations (pr-comments-read/pr-comment-post/checks-read/review-thread-resolve), treating review-tool output as hypothesis. Composes natively on install for its two skills; ships /wf-review:init for one-command self-registration of the pr-review capability ahead of its first contribution fragment.

πŸ”Œ
wf-browser-qaπŸ”ŒPlugin

wf browser-QA feature pack: the browser-qa capability owning the wf capability-registry's qa-execution engine surface. Ships /wf-browser-qa:qa-engine, a stack-agnostic in-thread browser-automation QA engine that drives any web app, reaches browser-level preconditions, captures console/network, screenshots on FAIL, and emits per-scenario verdict blocks; core's /wf:qa-auto dispatches the per-scenario browser drive to it. Tracker-agnostic (requires: git only). Ships /wf-browser-qa:init for one-command self-registration.