---
url: /guide/skills.md
description: >-
  Select, install, and verify the nine Wow Agent Skills for downstream
  applications.
---

# Agent Skills

This page answers: **which Primary Skill should a downstream Wow task use, and how is completion proved?**

The Wow repository owns Skill source and validation fixtures; the distribution repository and client own installation and discovery. Skills provide workflows, architectural invariants, authorization boundaries, and evidence gates. They do not replace target-version APIs, configuration, or generated contracts.

V9 is the current maintenance baseline and default terminology. The three day-to-day Skills still support V8 downstream tasks, but they must first resolve the actual Wow version from the target build and dependency graph. Only `wow-migrate` keeps V8-to-V9 type, configuration, and behavior mappings; version-specific conclusions remain unverified when the version cannot be confirmed.

## Select one Primary Skill

Choose once from the user's primary requested outcome, then let that Skill own the complete task:

| Skill | Select when | Do not select when |
|---|---|---|
| `wow-migrate` | Cross-major or known breaking source/config/generated/runtime change, or a Wow-managed store/history cutover | First adoption without history conversion; routine same-major non-breaking upgrade |
| `wow-debug` | There is a failure, hang, bad state, or reproducer and the outcome is root cause; fix only after authorization | Proactive development, ordinary diff review, or data cutover |
| `wow-review` | The outcome is findings, merge readiness, or review-and-fix | Symptom-driven diagnosis, proactive feature work, or a breaking migration review |
| `wow-develop` | Design, implement, test, refactor, or explain downstream Wow behavior, including first adoption | Existing-diff review, existing-failure diagnosis, or breaking migration |
| `wow-generator` | Generate TypeScript models and Wow CQRS clients from an OpenAPI document with the `wow-generator` CLI, or move from `@ahoo-wang/fetcher-generator` | Hand-written runtime client code, or Kotlin/Java service work |
| `wow-client` | Write TypeScript command, query, and React query-hook code with `@ahoo-wang/wow-client` and `@ahoo-wang/wow-react`, or move from `@ahoo-wang/fetcher-wow` | OpenAPI code generation, or Kotlin/Java service work |
| `wow-data-query` | Answer a business data question from a running service: read its query capability descriptor and run read-only queries; the deliverable is the answer, not code | Writing query code (`wow-client`), diagnosing a rejected query or a wrong result (`wow-debug`) |
| `wow-view-definition` | Decide and write `@ahoo-wang/wow-view-engine` view definitions with `defineView` over the committed query capability descriptor: which fields, in what words, what is narrowed, system record and analysis views, boards; self-checked with the engine's `admit` | Integrating the host (`wow-view-host`), runtime client code (`wow-client`), answering data questions (`wow-data-query`), changing the view engine itself |
| `wow-view-host` | Integrate the view engine into a host: one engine with its resources and store (`MemoryViewStore`, `localStorageSnapshot`, `WowViewStore` behind the CoSec gateway), `ViewHost`, `bind` and routes, and Wow commands declared as actions; self-checked with `actionHarness`, `resolveNavigation` and `admit` | What a definition declares (`wow-view-definition`), client code outside the engine (`wow-client`), changing the view engine itself |

Do not activate these Skills for generic Kotlin, Gradle, dashboard, documentation, or DDD/CQRS work without scoped `me.ahoo.wow` imports, `wow-*` dependencies, or an explicit downstream Wow request. The Wow framework repository itself, including development of the packages under `typescript/`, is also outside every Skill's target scope, with one exception: the view definitions in this repository (the Storybook scenarios and stories under `typescript/storybook/stories/view-engine/`, and the compensation console's `compensation/dashboard/src/views/`) may activate `wow-view-definition`, and their host wiring (the engine and resources, `ViewHost`, routes, the store and declared actions, such as the console's `src/views/engine.ts`, `routes.ts`, `executionActions.ts`, `viewStore.ts` and `src/features/App/ConsoleHost.tsx`) may activate `wow-view-host`. Changing the view engine itself, or the `@ahoo-wang/wow-view-store` package, activates none.

The first four Skills cover Kotlin/Java services. `wow-generator` and `wow-client` cover downstream TypeScript applications that call those services: choose `wow-generator` when the outcome is generated code or generator configuration, and `wow-client` for code that uses the clients at runtime. `wow-data-query` delivers answers from a running service's data: it reads the descriptor first and queries only within it, uses a development or staging service by default, and queries production only with the user's explicit consent. `wow-view-definition` delivers view definitions and teaches only the choices: the facts come from the committed descriptor through `defineView`, the definition lists and words what its audience needs and narrows only for that audience, every word is a key said at the leaf, and the engine's `admit` over the committed descriptor is the self-check. `wow-view-host` delivers the integration: one engine, the store, `ViewHost` with its routes, and each command a person issues on a record declared as an action whose `run` resolves once the read model shows it.

Source contracts: [`skills/README.md`](https://github.com/Ahoo-Wang/Wow/blob/main/skills/README.md), [`wow-develop`](https://github.com/Ahoo-Wang/Wow/tree/main/skills/wow-develop), [`wow-review`](https://github.com/Ahoo-Wang/Wow/tree/main/skills/wow-review), [`wow-debug`](https://github.com/Ahoo-Wang/Wow/tree/main/skills/wow-debug), [`wow-migrate`](https://github.com/Ahoo-Wang/Wow/tree/main/skills/wow-migrate), [`wow-client`](https://github.com/Ahoo-Wang/Wow/tree/main/skills/wow-client), [`wow-generator`](https://github.com/Ahoo-Wang/Wow/tree/main/skills/wow-generator), [`wow-data-query`](https://github.com/Ahoo-Wang/Wow/tree/main/skills/wow-data-query), [`wow-view-definition`](https://github.com/Ahoo-Wang/Wow/tree/main/skills/wow-view-definition), and [`wow-view-host`](https://github.com/Ahoo-Wang/Wow/tree/main/skills/wow-view-host).

## Ownership and installation boundary

| Boundary | Owner | Usage |
|---|---|---|
| Skill behavior and references | Wow repository `skills/` | Edit here and run the local validator; do not edit generated copies in the aggregation repository |
| Distributable plugin manifest | Wow repository [`skills/plugins.json`](https://github.com/Ahoo-Wang/Wow/blob/main/skills/plugins.json) | The current manifest includes only the nine Primary Skills; `agents/openai.yaml` supplies client display metadata and default prompts |
| Aggregation and distribution | [Ahoo-Wang/skills](https://github.com/Ahoo-Wang/skills) | Install or refresh `ahoo-wow-skills` from the aggregate marketplace; do not treat it as the source-content edit point |
| Current installation instructions | [Ahoo Skills](https://skills.ahoo.me/) | Follow the page for the relevant client; commands and publication state may evolve independently |
| Generic format | [Agent Skills specification](https://agentskills.io/) | Defines the generic Skill format; it does not prove Wow Skill behavior |

This repository does not install Agent Skills through an application build. Successful installation proves only that a client discovered the plugin, not that a task selected the right Skill or produced a reliable result.

## Usage request

Provide at least four inputs:

```text
Goal: add cancellation behavior to Order
Scope: change only the downstream order-domain module
Authorization: code and test edits allowed; release not allowed
Evidence: run :order-domain:test and report compatibility plus missing runtime evidence
```

The Skill should then establish facts from the target checkout: read definitions, consumers, tests, configuration, and generated contracts; write only within authorization; run the narrowest valid check; and report results plus missing evidence accurately.

Rediscover complete annotation parameters, DSL methods, configuration keys, defaults, and backend lists from the target version. References provide stable decisions and discovery methods, not a frozen API manual.

## Completion evidence

A Skill task is complete only when its final report includes:

* actual target version, scope, and authorization boundary;
* behavior read or changed and its fact sources;
* exact commands, exit results, and failure counts;
* public, generated, data, or runtime compatibility impact;
* unexecuted external, production, data, release, or rollback validation marked as missing evidence.

`wow-review` remains read-only without authorization; `wow-debug` reproduces and locates before fixing; `wow-migrate` treats code, data, cutover, and release authority separately.

## Maintainer validation

After changing Skills in this repository, run:

```bash
python3 -S scripts/validate_wow_skills.py
python3 -S -m unittest scripts.test_validate_wow_skills
```

These commands validate metadata, agent manifests, plugin includes, local resource paths, and eval JSONL structure. They do not execute behavior cases or prove natural-language activation, target APIs, or production migration. Evaluate behavior in fresh tasks against real diffs and command results.

## Prioritized next path

1. Select one Primary Skill and include scope, authorization, and evidence in the request.
2. For first adoption, establish a runnable baseline with [Getting Started](./getting-started.md).
3. For breaking contracts or historical data, read [Migration](./migration.md) and pin exact source and target versions first.