Agent skill

Wfa Post Port Evolve

by tautcony in tautcony/ChapterTool

Phase F of a WinForms-to-Avalonia migration: evolve the Avalonia trunk after cutover without reintroducing WinForms coupling or bypassing established layers.

GPL-3.0Auto-check passed

Install Wfa Post Port Evolve

skills CLI
$ npx skills add tautcony/ChapterTool --skill wfa-post-port-evolve -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tautcony/ChapterTool wfa-post-port-evolve --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tautcony/ChapterTool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/wfa-post-port-evolve .claude/skills/wfa-post-port-evolve && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
wfa-post-port-evolve
GitHub stars
113
Token cost
~914 tokens
SKILL.md length
375 words
Files
2 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
GPL-3.0

At a glance

Phase F of a WinForms-to-Avalonia migration: evolve the Avalonia trunk after cutover without reintroducing WinForms coupling or bypassing established layers.

  • Works in 6 steps: Spec with clear non-goals and firm… → Failing tests first with the smallest… → Implement inside existing layers; clean… → …
  • SKILL.md covers Preconditions, Tracks (select only from…, Workflow and Deliverables, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Wfa Post Port Evolve is an agent skill from tautcony/ChapterTool. Phase F of a WinForms-to-Avalonia migration: evolve the Avalonia trunk after cutover without reintroducing WinForms coupling or bypassing established layers. Use only when an explicit migration has an active Avalonia trunk and a concrete product backlog, or when the orchestrator routes here. Select work from repository evidence; do not assume particular entry points, integrations, settings, or extension mechanisms exist.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/evolution-tracks.md`).

It works with Avalonia. The repository describes itself as: Cross-platform chapter editing and conversion toolkit for desktop, CLI, WebAssembly, and Node.js, with support for Blu-ray and common media chapter formats. The licence is GPL-3.0.

Example prompts

  • “/wfa-post-port-evolve”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Spec with clear non-goals and firm decisions (no “may remain…” hedges)
  2. Failing tests first with the smallest representative fixtures or scenarios
  3. Implement inside existing layers; clean cut when replacing dual models
  4. Surface compile/runtime errors to UI and logs
  5. Focused + full solution tests (no screenshot-only tasks)
  6. Sync long-lived requirements

What it can do on your machine

Read from SKILL.md and the folder at commit 75dd863. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Wfa Post Port Evolve loads about 914 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 375 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~111
When it runs · the whole SKILL.md, loaded when a task matches
~914
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tautcony/ChapterTool at commit 75dd863, republished under its GPL-3.0 licence (© tautcony). 375 words, ~914 tokens.

Download SKILL.mdSave it as .claude/skills/wfa-post-port-evolve/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
wfa-post-port-evolve
description
Phase F of a WinForms-to-Avalonia migration: evolve the Avalonia trunk after cutover without reintroducing WinForms coupling or bypassing established layers. Use only when an explicit migration has an active Avalonia trunk and a concrete product backlog, or when the orchestrator routes here. Select work from repository evidence; do not assume particular entry points, integrations, settings, or extension mechanisms exist.

Phase F — Post-port product evolution

Improve the Avalonia line without reintroducing WinForms coupling. First ship (A–E) is not the end.

Read evolution tracks to classify a discovered backlog item; do not implement tracks that are absent from the product.

Preconditions

  • Avalonia is the active trunk (or dual-running with legacy frozen)
  • Layering exists
  • Prefer one SDD/spec change per capability

Tracks (select only from repository evidence)

F1. Deferred capability restoration

Restore a deferred behavior in its owning layer with contract and regression evidence. Do not place application rules solely in a ViewModel because that is the easiest entry point.

F2. Boundary or integration replacement

Replace an adapter only after documenting semantics, failure modes, supported environments, resource ownership, and cutover behavior. A fallback is a product decision, not a default.

F3. Additional host or entry point
  • Define the host's explicit scope, lifecycle, input binding, result, and failure protocol.
  • Reuse application services and composition definitions where their lifetimes are compatible.
  • Keep host-specific parsing/transport thin and test application behavior independently.
  • Ensure one host does not accidentally start another host's lifetime.
F4. Presentation and operational quality
  • Externalize user-facing text when localization is in scope.
  • Preserve structured diagnostics and render them at the presentation boundary.
  • Add accessibility, observability, and supportability requirements discovered after cutover.
F5. Persisted state evolution
text
legacy stores -> typed versioned state, when the product persists state
  validated migrators; reject unsupported future versions
  preserve predecessor and last known-good data
  coordinated atomic updates

Define edit/apply/cancel behavior from the product contract. Do not create a new persistence stack for each UI surface.

Show full SKILL.md (146 more words)Show less
F6. Extension mechanisms

When the product supports user-extensible or dynamically evaluated behavior, define capabilities, resource budgets, trust boundaries, lifecycle, and diagnostics before implementation.

F7. Workflow discoverability

Make supported actions discoverable, define intentional empty/disabled states, and turn required hidden gestures into accessible command surfaces.

Workflow

  1. Spec with clear non-goals and firm decisions (no “may remain…” hedges)
  2. Failing tests first with the smallest representative fixtures or scenarios
  3. Implement inside existing layers; clean cut when replacing dual models
  4. Surface compile/runtime errors to UI and logs
  5. Focused + full solution tests (no screenshot-only tasks)
  6. Sync long-lived requirements

When the user says not to confirm mid-flight, apply autonomously and report at the end.

Deliverables

  • Feature on Avalonia trunk with tests
  • No new WinForms statics or UI algorithms in Core
  • Composition and every affected host updated if shared services changed

Handoff

Structure/security debt → wfa-harden-decompose Legacy delete → wfa-parity-verify

© tautcony, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .codex/skills/wfa-post-port-evolve of tautcony/ChapterTool.

  • SKILL.md
  • references/evolution-tracks.md

Open the folder on GitHubat commit 75dd863

Compare with similar skills

Wfa Post Port Evolve next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Wfa Post Port Evolve compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wfa Post Port Evolve this skilltautcony/ChapterTool113—~914Automated safety check: PassGPL-3.0
Translation Source SyncDevolutions/UniGetUI26k—~1.2kAutomated safety check: PassMIT
Docs Style LintAvaloniaUI/avalonia-docs166—~4.6kAutomated safety check: PassNone
Format StylePixeval/Pixeval3.2k—~1.2kAutomated safety check: PassGPL-3.0
Docusaurus StylingAvaloniaUI/avalonia-docs166—~3.3kAutomated safety check: PassNone
Code StylePixeval/Pixeval3.2k—~730Automated safety check: PassGPL-3.0

Similar skills

  • Translation Source Sync

    Devolutions/UniGetUI

    Synchronizes the UniGetUI English language file with source-code usage, identifies missing translation keys, removes unused entries, reports localization drift, and can reorder locale files to match…

    26k GitHub stars~1.2k tokensUpdated today
    Writing & ContentAuto-check passed
  • Docs Style Lint

    AvaloniaUI/avalonia-docs

    Reviews and lints Avalonia documentation pages against house style rules, content boundaries, anti-marketing standards, accessibility, and SEO.

    166 GitHub stars~4.6k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Format Style

    Pixeval/Pixeval

    工程代码格式化风格指引

    3.2k GitHub stars~1.2k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Docusaurus Styling

    AvaloniaUI/avalonia-docs

    Style Docusaurus sites to match Avalonia Customer Portal theme using TailwindCSS, CSS variables, and component swizzling.

    166 GitHub stars~3.3k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Code Style

    Pixeval/Pixeval

    工程代码编写风格指引(不含简单的格式化风格)

    3.2k GitHub stars~730 tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • A skill your agent uses when changing AtomUI or Avalonia resource bindings, DynamicResource, TokenResourceBinder, non-Visual AvaloniaObject lifecycle, IResourceHost/IThemeVariantHost…

    842 GitHub stars~1.4k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from tautcony/ChapterTool

All 9 skills in this repo
  • Reclaim Code Entropy

    tautcony/ChapterTool

    Find, rank, and safely remove accidental codebase complexity by proving real consumers, dynamic entrypoints, compatibility obligations, duplicate representations, speculative surfaces, and lifecycle…

    113 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Wfa Harden Decompose

    tautcony/ChapterTool

    Phase G of a WinForms-to-Avalonia migration: decompose oversized UI state and orchestration, harden asynchronous workflows and external boundaries, preserve composition lifetimes, keep Headless…

    113 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Winforms To Avalonia

    tautcony/ChapterTool

    Orchestrate a phased WinForms-to-Avalonia migration: behavior contracts, UI-independent application logic, platform adapters, MVVM shell, parity/cutover, evolution, and hardening.

    113 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Wfa Avalonia UI

    tautcony/ChapterTool

    Phase D of a WinForms-to-Avalonia migration: build the Avalonia UI shell with composition, MVVM state and commands, responsive XAML, accessibility, localization boundaries, and behavior-focused…

    113 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Wfa Capture Contracts

    tautcony/ChapterTool

    Phase A of a WinForms-to-Avalonia migration: inventory the legacy application, split responsibilities, capture command and state contracts, build a coverage matrix, and define acceptance evidence…

    113 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Wfa Extract Domain

    tautcony/ChapterTool

    Phase B of a WinForms-to-Avalonia migration: extract UI-independent application behavior, state rules, use cases, and boundary contracts with TDD and no WinForms/Avalonia references.

    113 GitHub stars~862 tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Wfa Post Port Evolve

What does Wfa Post Port Evolve do?

Phase F of a WinForms-to-Avalonia migration: evolve the Avalonia trunk after cutover without reintroducing WinForms coupling or bypassing established layers. Wfa Post Port Evolve is an agent skill from tautcony/ChapterTool. Phase F of a WinForms-to-Avalonia migration: evolve the Avalonia trunk after cutover without reintroducing WinForms coupling or bypassing established layers.

How do I install Wfa Post Port Evolve in Claude Code?

Run `npx skills add tautcony/ChapterTool --skill wfa-post-port-evolve -a claude-code`. Or copy the skill folder (.codex/skills/wfa-post-port-evolve in tautcony/ChapterTool) into .claude/skills/wfa-post-port-evolve in your project. Claude Code loads it when a task matches its description.

How do I install Wfa Post Port Evolve in Codex?

Run `npx skills add tautcony/ChapterTool --skill wfa-post-port-evolve -a codex`. Or copy the skill folder (.codex/skills/wfa-post-port-evolve in tautcony/ChapterTool) into .agents/skills/wfa-post-port-evolve in your project. Codex loads it when a task matches its description.

Can I use Wfa Post Port Evolve in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tautcony/ChapterTool --skill wfa-post-port-evolve -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wfa-post-port-evolve, .gemini/skills/wfa-post-port-evolve, .github/skills/wfa-post-port-evolve and .opencode/skills/wfa-post-port-evolve in your project.

What does Wfa Post Port Evolve need to run?

SKILL.md names no scripts, command-line tools or credentials: Wfa Post Port Evolve is instructions for the agent only.

Does Wfa Post Port Evolve access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Wfa Post Port Evolve safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Wfa Post Port Evolve use?

Wfa Post Port Evolve is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wfa Post Port Evolve use?

About 914 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 444 tokens, read only when the agent opens those files.

What are the alternatives to Wfa Post Port Evolve?

Skills that share tags, products or a category with Wfa Post Port Evolve: Translation Source Sync (Devolutions/UniGetUI, 26k stars), Docs Style Lint (AvaloniaUI/avalonia-docs, 166 stars), Format Style (Pixeval/Pixeval, 3.2k stars) and Docusaurus Styling (AvaloniaUI/avalonia-docs, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wfa Post Port Evolve?

tautcony (a GitHub user) maintains it in tautcony/ChapterTool, which has 113 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.

Source: tautcony/ChapterTool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.