polykybd-kofi-post

Writes ko-fi supporter posts with firmware-rendered GIFs and hero stills for merged PolyKybd features.

5|1|Updated Aug 18, 2023
One-click install
npx skills add https://github.com/thpoll83/PolyKybdHost --skill polykybd-kofi-post-thpoll83
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: polykybd-kofi-post
Source: https://github.com/thpoll83/PolyKybdHost/tree/main/.claude/skills/polykybd-kofi-post
Command: npx skills add https://github.com/thpoll83/PolyKybdHost --skill polykybd-kofi-post-thpoll83

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Announcing a newly merged PolyKybd firmware feature to ko-fi supporters requires a narrative post plus accurate visuals, and hand-drawn mockups drift from the real keymap and misrepresent the product. ## Core Features & Use Cases - Structured post drafting: Produces a ko-fi post following an established shape — concrete title, hero image, prior behavior, breaking case, the exact gesture, GIF with alt text, edge cases, and an under-the-hood section. - Firmware-rendered visuals: Regenerates animated GIFs via demo drivers in tools/ (e.g. intl_remap_demo.py) that read the real keymap, and composes hero stills from board geometry and generated glyph tables. - Verification discipline: Requires confirming the feature merged and was tested on hardware, and visually checking rendered frames against actual firmware behavior. - Use Case: After a PR adding a new Intl layer remap lands, ask for a supporter announcement and receive the post text, a regenerated GIF of the gesture, and a composed hero still. ## Quick Start Write a ko-fi post announcing the feature that just merged in PR 42, with a GIF and hero image rendered from the firmware sources.

Frequently Asked Questions about polykybd-kofi-post

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a ko-fi post announcing a new keyboard firmware feature?▼

Confirm the feature merged and was tested on hardware, then draft the post with a concrete title, the prior behavior, the breaking case, the exact gesture, a GIF, edge cases, and an under-the-hood section. Render visuals from the firmware sources rather than mocking them up.

How do I generate an animated GIF of a PolyKybd keymap layer?▼

Run the existing demo driver in tools/ such as intl_remap_demo.py with the project virtualenv; it reads the current keymap so new keys appear without code changes. If no driver exists, model a new one on intl_remap_demo.py and mirror render_key() rules exactly.

Can I reuse an old GIF when announcing a feature update?▼

No. If the feature added a key, an old GIF renders the board without it and misrepresents the product. Regenerate every animation the post shows, not just the one for the new feature.

What is the difference between a ko-fi post and release notes?▼

A ko-fi post covers one feature narratively for supporters, while release notes enumerate every change in a version. They are separate deliverables and should not be merged into one document.

When should I not use this skill for a feature announcement?▼

Do not use it for features still unmerged or untested on hardware, for GitHub release notes, or for documentation site updates. Those cases belong to other workflows such as polykybd-release-notes or update-polykybd-docs.