@olegkoval/agent-skills 1.14.0 → 1.14.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (14) hide show
  1. package/.claude-plugin/plugin.json +1 -1
  2. package/.cursor-plugin/index.json +1 -1
  3. package/.kiro/steering/open-source-publisher.md +11 -1
  4. package/.windsurf/rules/open-source-publisher.md +11 -1
  5. package/README.md +51 -275
  6. package/catalog/skills.json +1 -1
  7. package/package.json +1 -1
  8. package/packages/software-development/open-source-publisher/SKILL.md +11 -1
  9. package/packages/software-development/open-source-publisher/adapters/claude/plugin.json +1 -1
  10. package/packages/software-development/open-source-publisher/adapters/claude/skills/open-source-publisher/SKILL.md +11 -1
  11. package/packages/software-development/open-source-publisher/adapters/cursor/plugin.json +1 -1
  12. package/packages/software-development/open-source-publisher/adapters/cursor/skills/open-source-publisher/SKILL.md +11 -1
  13. package/packages/software-development/open-source-publisher/adapters/kiro/steering/open-source-publisher.md +11 -1
  14. package/packages/software-development/open-source-publisher/adapters/windsurf/rules/open-source-publisher.md +11 -1
package/.claude-plugin/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "olko-agent-skills",
3
3
  "description": "Agent-agnostic skill catalog for Codex, Claude, Cursor, and other skill-aware tools.",
4
- "version": "1.13.0",
4
+ "version": "1.14.0",
5
5
  "author": {
6
6
  "name": "Oleg Koval"
7
7
  },
package/.cursor-plugin/index.json CHANGED
@@ -59,7 +59,7 @@
59
59
  {
60
60
  "name": "olko:open-source-publisher",
61
61
  "source": "./packages/software-development/open-source-publisher/adapters/cursor",
62
- "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, and optional donation setup."
62
+ "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images."
63
63
  },
64
64
  {
65
65
  "name": "olko:viral-launch",
package/.kiro/steering/open-source-publisher.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  ---
4
4
  inclusion: manual
5
- description: "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, and optional donation setup."
5
+ description: "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images."
6
6
  ---
7
7
 
8
8
  # open-source-publisher
@@ -30,10 +30,12 @@ Use this skill to audit whether an OSS repository is ready to publish, then help
30
30
  5. For existing usable pieces, do not propose replacement by default. Ask a change-oriented question only when useful, for example:
31
31
  - "You already have a terminal-style GitHub Pages site. Do you want to keep it or restyle it?"
32
32
  - "You already have an icon and social card. Do you want a refresh, or should I leave them as-is?"
33
+ - "You already have a static social card. Do you want me to animate it with pixel2motion, or leave it static?"
33
34
  - "You already have release automation. Do you want me to audit only, or also tighten it?"
34
35
  6. Ask only for choices needed to fix missing or weak pieces:
35
36
  - If GitHub Pages is missing or weak, ask for style: `oldschool linux`, `terminal`, `modern`, `brutalist`, `glassmorphism`, `y2k`, `hacker`, or custom.
36
37
  - If donation wiring is missing, ask whether to enable it: `none`, `GitHub Sponsors`, `Ko-fi`, `Buy Me a Coffee`, `Open Collective`, `Thanks.dev`, or custom URL.
38
+ - If the repo has a generated static social image or hero card, ask whether to animate it using `nolangz/pixel2motion`.
37
39
  - If the repo has no clear product essence, ask for a one-sentence positioning statement.
38
40
  7. Implement only approved, missing, or weak work in this order:
39
41
  - OSS governance and support files
@@ -193,6 +195,14 @@ file social-card.png
193
195
 
194
196
  Use `magick` or another renderer when `rsvg-convert` is unavailable.
195
197
 
198
+ ## Motion Preview
199
+
200
+ Some repos benefit from a short animated preview. Keep this opt-in.
201
+
202
+ - If you already generated a static image, ask: `Do you want me to animate the static image using pixel2motion?`
203
+ - If the user says yes, use `nolangz/pixel2motion` as the optional dependency for logo animation, animated HTML demos, and GIF/video previews.
204
+ - Do not auto-animate by default.
205
+
196
206
  ## README Standard
197
207
 
198
208
  Shape the README like the house standard used for Go packages such as `slow-query-detector` and `dcli`.
package/.windsurf/rules/open-source-publisher.md CHANGED
@@ -1,7 +1,7 @@
1
1
  <!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
2
2
 
3
3
  ---
4
- description: "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, and optional donation setup."
4
+ description: "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images."
5
5
  ---
6
6
 
7
7
  # open-source-publisher
@@ -29,10 +29,12 @@ Use this skill to audit whether an OSS repository is ready to publish, then help
29
29
  5. For existing usable pieces, do not propose replacement by default. Ask a change-oriented question only when useful, for example:
30
30
  - "You already have a terminal-style GitHub Pages site. Do you want to keep it or restyle it?"
31
31
  - "You already have an icon and social card. Do you want a refresh, or should I leave them as-is?"
32
+ - "You already have a static social card. Do you want me to animate it with pixel2motion, or leave it static?"
32
33
  - "You already have release automation. Do you want me to audit only, or also tighten it?"
33
34
  6. Ask only for choices needed to fix missing or weak pieces:
34
35
  - If GitHub Pages is missing or weak, ask for style: `oldschool linux`, `terminal`, `modern`, `brutalist`, `glassmorphism`, `y2k`, `hacker`, or custom.
35
36
  - If donation wiring is missing, ask whether to enable it: `none`, `GitHub Sponsors`, `Ko-fi`, `Buy Me a Coffee`, `Open Collective`, `Thanks.dev`, or custom URL.
37
+ - If the repo has a generated static social image or hero card, ask whether to animate it using `nolangz/pixel2motion`.
36
38
  - If the repo has no clear product essence, ask for a one-sentence positioning statement.
37
39
  7. Implement only approved, missing, or weak work in this order:
38
40
  - OSS governance and support files
@@ -192,6 +194,14 @@ file social-card.png
192
194
 
193
195
  Use `magick` or another renderer when `rsvg-convert` is unavailable.
194
196
 
197
+ ## Motion Preview
198
+
199
+ Some repos benefit from a short animated preview. Keep this opt-in.
200
+
201
+ - If you already generated a static image, ask: `Do you want me to animate the static image using pixel2motion?`
202
+ - If the user says yes, use `nolangz/pixel2motion` as the optional dependency for logo animation, animated HTML demos, and GIF/video previews.
203
+ - Do not auto-animate by default.
204
+
195
205
  ## README Standard
196
206
 
197
207
  Shape the README like the house standard used for Go packages such as `slow-query-detector` and `dcli`.
package/README.md CHANGED
@@ -3,7 +3,7 @@
3
3
  <p><strong>Agent-agnostic skill catalog for Codex, Claude, Cursor, Copilot, Windsurf, Kiro, and other skill-aware tools.</strong></p>
4
4
  <p>
5
5
  <img src="https://img.shields.io/badge/license-MIT-16a34a" alt="MIT license">
6
- <img src="https://img.shields.io/badge/skills-19-2563eb" alt="19 skills">
6
+ <img src="https://img.shields.io/badge/skills-23-2563eb" alt="23 skills">
7
7
  <img src="https://img.shields.io/badge/platforms-Codex%20%7C%20Claude%20%7C%20Cursor%20%7C%20Copilot%20%7C%20Windsurf%20%7C%20Kiro-111827" alt="Codex Claude Cursor Copilot Windsurf Kiro">
8
8
  <img src="https://img.shields.io/badge/status-public%20catalog-16a34a" alt="Public catalog">
9
9
  </p>
@@ -11,8 +11,6 @@
11
11
 
12
12
  Agent-agnostic skill collection for Codex, Claude, Cursor, and other skill-aware tools.
13
13
 
14
- Pi and Hermes adapters currently exist for `search-console-indexing-audit` only.
15
-
16
14
  These skills are opinionated by design. They encode working defaults, preferred tools, and repeatable workflows instead of trying to be neutral snippets. Treat them as starting points with taste: useful out of the box, easy to inspect, and specific enough for an agent to execute consistently.
17
15
 
18
16
  ## Structure
@@ -76,87 +74,34 @@ git clone https://github.com/oleg-koval/agent-skills.git
76
74
  claude --plugin-dir /path/to/agent-skills
77
75
  ```
78
76
 
79
- See [Publishing to Marketplaces](#publishing-to-marketplaces) below for full submission details.
80
-
81
77
  </details>
82
78
 
83
79
  <details>
84
80
  <summary><b>Cursor</b></summary>
85
81
 
86
- The repository includes a generated Cursor plugin index at `.cursor-plugin/index.json` and per-package Cursor adapters under `packages/*/*/adapters/cursor/`.
87
-
88
- **For plugin marketplace:**
89
-
90
- Install from Cursor's extension marketplace using the published repository.
91
-
92
- **For a single project:**
93
-
94
82
  Copy the relevant `SKILL.md` or adapter content into `.cursor/rules/`, or reference the full package directory from your Cursor rules.
95
83
 
96
- See [Publishing to Marketplaces](#publishing-to-marketplaces) for registry submission.
97
-
98
84
  </details>
99
85
 
100
86
  <details>
101
87
  <summary><b>GitHub Copilot</b></summary>
102
88
 
103
- Use the generated repository instructions and prompt files:
104
-
105
- ```text
106
- .github/copilot-instructions.md
107
- .github/prompts/*.prompt.md
108
- ```
109
-
110
- **To use in your GitHub workspace:**
111
-
112
89
  Copy `.github/copilot-instructions.md` to your repository and enable Copilot. It will automatically apply skill guidance.
113
90
 
114
- **To customize per-skill:**
115
-
116
- Use files from `.github/prompts/*.prompt.md` in your Copilot configuration.
117
-
118
- See [Publishing to Marketplaces](#publishing-to-marketplaces) for integration details.
119
-
120
91
  </details>
121
92
 
122
93
  <details>
123
94
  <summary><b>Windsurf</b></summary>
124
95
 
125
- The repository includes generated Windsurf Cascade Rules at `.windsurf/rules/`.
126
-
127
- **For a single project:**
128
-
129
96
  Copy the relevant `.windsurf/rules/{skill-name}.md` into your project's `.windsurf/rules/` directory. Windsurf picks them up automatically as Cascade Rules.
130
97
 
131
- **For all skills at once:**
132
-
133
- ```bash
134
- git clone https://github.com/oleg-koval/agent-skills.git
135
- cp agent-skills/.windsurf/rules/*.md /path/to/your/project/.windsurf/rules/
136
- ```
137
-
138
- Each rule file has a `description` frontmatter field that Windsurf displays in the rules panel.
139
-
140
98
  </details>
141
99
 
142
100
  <details>
143
101
  <summary><b>Kiro</b></summary>
144
102
 
145
- The repository includes generated Kiro steering documents at `.kiro/steering/`.
146
-
147
- **For a single project:**
148
-
149
103
  Copy the relevant `.kiro/steering/{skill-name}.md` into your project's `.kiro/steering/` directory.
150
104
 
151
- **For all skills at once:**
152
-
153
- ```bash
154
- git clone https://github.com/oleg-koval/agent-skills.git
155
- cp agent-skills/.kiro/steering/*.md /path/to/your/project/.kiro/steering/
156
- ```
157
-
158
- Each steering doc uses `inclusion: manual` so Kiro only loads it when you explicitly reference it, keeping context lean.
159
-
160
105
  </details>
161
106
 
162
107
  <details>
@@ -168,51 +113,52 @@ Skills are plain Markdown. Use the canonical package file directly:
168
113
  packages/{category}/{skill}/SKILL.md
169
114
  ```
170
115
 
171
- Agent-specific wrappers live under:
172
-
173
- ```text
174
- packages/{category}/{skill}/adapters/
175
- ```
176
-
177
116
  </details>
178
117
 
179
- ## All 19 Skills
118
+ ## All 23 Skills
180
119
 
181
- These packages are the entry points. Each one is a structured workflow with concrete trigger conditions and execution steps. You can reference any skill directly by its `olko:*` lookup name.
120
+ Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup name in a new agent session.
182
121
 
183
- ### Software development
122
+ ### Software development (19)
184
123
 
185
- | Skill | What It Does | Use When |
124
+ | Skill | What it does | Use when |
186
125
  |-------|-------------|----------|
187
- | [docs-index-keeper](packages/software-development/docs-index-keeper/SKILL.md) | Keeps a Markdown docs index in sync through pre-commit, CI, or one-off maintenance flows | A repo has `docs/` and needs `docs/README.md` or another Markdown index updated automatically |
188
- | [semantic-release-beta](packages/software-development/semantic-release-beta/SKILL.md) | Sets up `semantic-release-npm-github-publish` with stable `main` releases and beta prereleases | A Node package needs stable npm publishing plus beta prereleases from a `beta` branch |
189
- | [gh-cli](packages/software-development/gh-cli/SKILL.md) | Guides GitHub CLI usage for repos, PRs, Actions, releases, issues, and related GitHub operations | Working with GitHub from the command line and needing reliable `gh` commands |
190
- | [git-commit](packages/software-development/git-commit/SKILL.md) | Creates conventional commits with diff-aware staging and message generation | The user asks to commit changes or wants a conventional commit message from the current diff |
191
- | [promptctl](packages/software-development/promptctl/SKILL.md) | Uses `promptctl` for reusable prompt templates, scoring, and workflow automation | A project needs prompt conventions, prompt review, prompt scoring, or reusable prompt workflows |
192
- | [product-builder](packages/software-development/product-builder/SKILL.md) | Builds a full-stack web app or SaaS product from a user description using production-oriented defaults | The user asks to build a complete app, SaaS, dashboard, or product rather than a prototype |
193
- | [cloudflare-block-countries](packages/software-development/cloudflare-block-countries/SKILL.md) | Blocks specific countries via Cloudflare WAF Custom Rules using the API | Geo-blocking traffic, setting up WAF country rules, or blocking regions across single or multiple zones |
194
- | [starter-rules](packages/software-development/starter-rules/SKILL.md) | Loads and enforces hard rules for every oleg-koval/* starter | Ensuring 300-line files, E2E tests, pre-commit hooks, Vertical Slice architecture, and KISS/DRY/SOLID |
126
+ | [add-to-my-skills](packages/software-development/add-to-my-skills/SKILL.md) | Copies a newly created skill from another repo into this catalog, refreshes the README and generated manifests, then commits and pushes | Adding a skill you wrote elsewhere into this catalog |
127
+ | [ai-tools-setup](packages/software-development/ai-tools-setup/SKILL.md) | Sets up, repairs, and reports on the RTK + ICM + Vox AI development toolkit — installs missing tools, fixes broken hooks and MCP config | Bootstrapping AI dev tools on a new machine or diagnosing broken integrations |
128
+ | [apple-store-submit](packages/software-development/apple-store-submit/SKILL.md) | Handles App Store rejection emails end-to-end — parses rejection reasons, creates a fix plan, implements code changes, and prepares resubmission | Responding to App Store rejections for privacy strings, entitlements, or guideline violations |
129
+ | [changelog-generator](packages/software-development/changelog-generator/SKILL.md) | Transforms git commits into polished user-facing changelogs by categorising changes and rewriting technical commit messages | Preparing release notes, app store update descriptions, or a public changelog |
130
+ | [cloudflare-block-countries](packages/software-development/cloudflare-block-countries/SKILL.md) | Blocks specific countries via Cloudflare WAF Custom Rules using the API | Geo-blocking traffic or setting up WAF country rules across single or multiple zones |
131
+ | [docs-index-keeper](packages/software-development/docs-index-keeper/SKILL.md) | Keeps a Markdown docs index in sync through pre-commit, CI, or one-off maintenance flows | A repo has `docs/` and needs `docs/README.md` updated automatically |
132
+ | [gh-cli](packages/software-development/gh-cli/SKILL.md) | Guides GitHub CLI usage for repos, PRs, Actions, releases, issues, and all related GitHub operations | Working with GitHub from the command line and needing reliable `gh` commands |
133
+ | [git-commit](packages/software-development/git-commit/SKILL.md) | Creates conventional commits with diff-aware staging and message generation | Asking to commit changes or wanting a conventional commit message from the current diff |
134
+ | [macos-menubar-app](packages/software-development/macos-menubar-app/SKILL.md) | Builds a production-quality macOS menubar or notch app in SwiftUI — MenuBarExtra setup, sandbox entitlements, keyboard shortcuts, sound effects | Building a native macOS utility that lives in the menu bar or Dynamic Island notch |
135
+ | [mvp-oneshot](packages/software-development/mvp-oneshot/SKILL.md) | Takes a rough product idea and produces a scoped, testable MVP plan and initial implementation in a single pass | Going from idea to a shippable one-week MVP without losing scope |
136
+ | [obsidian-pr-sync](packages/software-development/obsidian-pr-sync/SKILL.md) | Fetches open GitHub PRs assigned to you or requesting review and writes a grouped age-sorted section into today's Obsidian daily note | Syncing GitHub review queue to Obsidian at the start of the day or on demand |
137
+ | [obsidian-task-rollover](packages/software-development/obsidian-task-rollover/SKILL.md) | Migrates unchecked tasks from today's Obsidian daily note to the next workday under `## Carried over` | End-of-day bullet-journal task migration |
195
138
  | [open-source-publisher](packages/software-development/open-source-publisher/SKILL.md) | Prepares an open-source repository for public publishing with branding, CI/CD, and release hygiene | Releasing a private project publicly with proper GitHub Pages, README, and social preview |
196
- | [obsidian-pr-sync](packages/software-development/obsidian-pr-sync/SKILL.md) | Fetches open GitHub PRs assigned to you or requesting review, and writes a grouped age-sorted section into today's Obsidian daily note | Syncing GitHub review queue to Obsidian at the start of the day or on demand |
197
- | [obsidian-task-rollover](packages/software-development/obsidian-task-rollover/SKILL.md) | Migrates unchecked tasks from today's Obsidian daily note to the next workday under `## Carried over`, marking source tasks as `[>]` | End-of-day bullet-journal task migration, rolling unfinished work to the next workday |
198
- | [review-past-performance](packages/software-development/review-past-performance/SKILL.md) | Self-improvement loop: pulls 24h of ICM memories, git history, and skill analytics; detects repeated mistakes, slow workflows, and missing coverage; proposes 1-3 concrete fixes | Reviewing a day's coding sessions for patterns, wanting to codify a repeated workflow, or running a daily self-improvement loop |
139
+ | [product-builder](packages/software-development/product-builder/SKILL.md) | Builds a full-stack web app or SaaS product from a user description using production-oriented defaults | Building a complete app, SaaS, dashboard, or product rather than a prototype |
140
+ | [promptctl](packages/software-development/promptctl/SKILL.md) | Uses `promptctl` for reusable prompt templates, scoring, and workflow automation | A project needs prompt conventions, review, scoring, or reusable prompt workflows |
141
+ | [review-past-performance](packages/software-development/review-past-performance/SKILL.md) | Pulls 24h of ICM memories, git history, and skill analytics; detects repeated mistakes and slow workflows; proposes 1-3 concrete fixes | Daily self-improvement loop or codifying a repeated workflow |
142
+ | [semantic-release-beta](packages/software-development/semantic-release-beta/SKILL.md) | Sets up `semantic-release` with stable `main` releases and beta prereleases on a `beta` branch | A Node package needs stable npm publishing plus beta prereleases |
143
+ | [skill-budget-audit](packages/software-development/skill-budget-audit/SKILL.md) | Diagnoses and fixes Claude Code's skill context budget overflow — identifies heavy plugin bundles that exceed the 2% budget | Skills failing to load or Claude hitting context limits from plugin bundles |
144
+ | [starter-rules](packages/software-development/starter-rules/SKILL.md) | Loads and enforces hard rules for every oleg-koval/* starter | Ensuring 300-line files, E2E tests, pre-commit hooks, Vertical Slice architecture, and KISS/DRY/SOLID |
199
145
 
200
- ### Music
146
+ ### Marketing (2)
201
147
 
202
- | Skill | What It Does | Use When |
148
+ | Skill | What it does | Use when |
203
149
  |-------|-------------|----------|
204
- | [fill-music-player](packages/music/fill-music-player/SKILL.md) | Fills a portable music player with a curated random music selection while balancing formats, artists, albums, and capacity | Copying music from a NAS or local library to a Walkman, iPod, USB drive, or similar device |
150
+ | [search-console-indexing-audit](packages/marketing/search-console-indexing-audit/SKILL.md) | Audits Google Search Console Coverage exports against sitemap, robots, canonical, redirect, and noindex signals | Diagnosing GSC indexing issues such as redirects, canonical alternates, and discovered-but-not-indexed pages |
151
+ | [viral-launch](packages/marketing/viral-launch/SKILL.md) | Sets up a project repository and launch plan for shareable marketing, public launch readiness, and growth loops | Preparing a repo, product, open-source package, or creator tool for public launch |
205
152
 
206
- ### Marketing
153
+ ### Music (1)
207
154
 
208
- | Skill | What It Does | Use When |
155
+ | Skill | What it does | Use when |
209
156
  |-------|-------------|----------|
210
- | [viral-launch](packages/marketing/viral-launch/SKILL.md) | Sets up a project repository and launch plan for shareable marketing, public launch readiness, and growth loops | Preparing a repo, product, open-source package, waitlist, or creator tool for public launch |
211
- | [search-console-indexing-audit](packages/marketing/search-console-indexing-audit/SKILL.md) | Audits Google Search Console Coverage exports against sitemap, robots, canonical, redirect, and noindex signals | Diagnosing GSC indexing issues such as redirects, canonical alternates, and discovered but not indexed pages |
157
+ | [fill-music-player](packages/music/fill-music-player/SKILL.md) | Fills a portable music player with a curated random selection while balancing formats, artists, albums, and capacity | Copying music from a NAS or local library to a Walkman, iPod, USB drive, or similar device |
212
158
 
213
- ### Photography
159
+ ### Photography (1)
214
160
 
215
- | Skill | What It Does | Use When |
161
+ | Skill | What it does | Use when |
216
162
  |-------|-------------|----------|
217
163
  | [gallery](packages/photography/gallery/SKILL.md) | Creates photo galleries with AI-assisted layout curation and sequencing | Building a gallery from photos or planning photo layout, sequencing, and curation |
218
164
 
@@ -273,21 +219,18 @@ packages/{category}/{skill}/
273
219
  ├── SKILL.md # Required canonical skill definition
274
220
  ├── references/ # Optional supporting material loaded only when needed
275
221
  └── adapters/ # Agent-specific wrappers (all generated by build-adapters.sh)
276
- ├── codex/ # OpenAI Codex — README.md stub
277
- ├── claude/ # Claude Code — plugin.json + skills/SKILL.md copy
278
- ├── cursor/ # Cursor — plugin.json + skills/SKILL.md copy
279
- ├── pi/ # Pi — README.md stub, where supported
280
- ├── hermes/ # Hermes — README.md stub, where supported
281
- ├── windsurf/ # Windsurf — rules/{name}.md (Cascade Rules format)
282
- └── kiro/ # Amazon Kiro — steering/{name}.md (steering doc format)
222
+ ├── codex/
223
+ ├── claude/
224
+ ├── cursor/
225
+ ├── windsurf/
226
+ └── kiro/
283
227
  ```
284
228
 
285
229
  Key design choices:
286
230
 
287
231
  - Process over prose: skills are workflows agents follow, not generic reference essays.
288
232
  - Progressive disclosure: `SKILL.md` is the entry point; supporting files load only when needed.
289
- - Adapter separation: Codex, Claude, Cursor, Copilot, Windsurf, Kiro, and any package-specific adapters wrap the canonical package instead of forking it.
290
- - Verifiable changes: catalog and manifest changes should pass `./scripts/validate-catalog.sh`.
233
+ - Adapter separation: agent-specific wrappers wrap the canonical package instead of forking it.
291
234
 
292
235
  See [docs/skill-anatomy.md](docs/skill-anatomy.md) for the package format.
293
236
 
@@ -295,166 +238,21 @@ See [docs/skill-anatomy.md](docs/skill-anatomy.md) for the package format.
295
238
 
296
239
  ```text
297
240
  agent-skills/
298
- ├── packages/ # Canonical skill packages
299
- │ ├── software-development/
300
- │ │ ├── docs-index-keeper/
301
- │ │ ├── semantic-release-beta/
302
- │ │ ├── gh-cli/
303
- │ │ ├── git-commit/
304
- │ │ ├── promptctl/
305
- │ │ └── product-builder/
306
- │ ├── music/
307
- │ │ └── fill-music-player/
308
- │ ├── marketing/
309
- │ │ └── viral-launch/
310
- │ └── photography/
311
- │ └── gallery/
312
- ├── catalog/ # Machine-readable package inventory
313
- ├── collections/ # Grouped package bundles
314
- ├── scripts/ # Build, validation, sync, and install helpers
315
- ├── .claude-plugin/ # Generated Claude marketplace manifest
316
- ├── .cursor-plugin/ # Generated Cursor plugin index
317
- ├── .github/prompts/ # Generated GitHub Copilot prompt files
318
- ├── .windsurf/rules/ # Generated Windsurf Cascade Rules
319
- ├── .kiro/steering/ # Generated Kiro steering documents
320
- └── docs/ # Contributor and package format docs
321
- ```
322
-
323
- ## Install and test
324
-
325
- ### Codex
326
-
327
- Install all canonical packages into your local Codex skills directory:
328
-
329
- ```bash
330
- ./scripts/install-codex-symlinks.sh
331
- ```
332
-
333
- This creates symlinks from the package catalog into `${CODEX_HOME:-~/.codex}/skills` using the lookup format `olko:{skill_name}`.
334
-
335
- To test a skill in a fresh Codex session, mention it explicitly:
336
-
337
- ```text
338
- Use the olko:docs-index-keeper skill to set up docs index automation in this repo.
339
- ```
340
-
341
- ```text
342
- Use the olko:semantic-release-beta skill to add prereleases on a beta branch.
343
- ```
344
-
345
- Status: **Stable** — ready for daily use
346
-
347
- ### Claude Code
348
-
349
- The repository includes a generated marketplace manifest at `.claude-plugin/marketplace.json` and per-package Claude adapter stubs under `packages/*/*/adapters/claude/`.
350
-
351
- **Local development:**
352
-
353
- ```bash
354
- git clone https://github.com/oleg-koval/agent-skills.git
355
- claude --plugin-dir /path/to/agent-skills
356
- ```
357
-
358
- **Marketplace installation:**
359
-
360
- See [Publishing to Marketplaces → Claude Marketplace](#claude-marketplace) for submission and user installation instructions.
361
-
362
- Status: **Ready for marketplace** — fully generated manifests, ready to publish
363
-
364
- ### Cursor
365
-
366
- The repository includes a generated plugin index at `.cursor-plugin/index.json` and per-package Cursor adapter stubs under `packages/*/*/adapters/cursor/`.
367
-
368
- See [Publishing to Marketplaces → Cursor Plugin Registry](#cursor-plugin-registry) for submission instructions.
369
-
370
- Status: **Ready for marketplace** — plugin index generated and ready to submit
371
-
372
- ### GitHub Copilot
373
-
374
- The repository includes generated repository instructions at `.github/copilot-instructions.md` and per-skill prompt files under `.github/prompts/`.
375
-
376
- To use in your GitHub workspace, copy `.github/copilot-instructions.md` to your repository.
377
-
378
- See [Publishing to Marketplaces → GitHub Copilot](#github-copilot) for integration details.
379
-
380
- Status: **Ready to use** — copy instructions to any GitHub repository
381
-
382
- ### Source sync
383
-
384
- `./scripts/sync-from-sources.sh` syncs package content only for catalog entries that explicitly define `sourcePath`. If no package has `sourcePath`, the script exits successfully and reports that there is nothing to sync.
385
-
386
- ## Publishing to Marketplaces
387
-
388
- ### Claude Marketplace
389
-
390
- The repository includes a generated marketplace manifest at `.claude-plugin/marketplace.json` that is compatible with Claude Code's plugin system.
391
-
392
- **To submit to Claude marketplace:**
393
-
394
- 1. Ensure the repository is public and contains this structure:
395
- ```
396
- ├── .claude-plugin/
397
- │ └── marketplace.json # Generated from catalog/skills.json
398
- └── packages/
399
- └── {category}/{skill}/
400
- ├── SKILL.md # Required canonical definition
401
- └── adapters/
402
- └── claude/ # Optional Claude-specific wrapper
403
- ```
404
-
405
- 2. Push to GitHub with a public repository:
406
- ```bash
407
- git push origin main
408
- ```
409
-
410
- 3. Submit the repository URL to Claude's plugin marketplace:
411
- - In Claude Code: `/plugin marketplace add oleg-koval/agent-skills`
412
- - Or visit the Claude plugin marketplace and add `https://github.com/oleg-koval/agent-skills`
413
-
414
- 4. The marketplace will:
415
- - Read `.claude-plugin/marketplace.json` for plugin metadata
416
- - Index all skills from `catalog/skills.json`
417
- - Auto-register skills by their `name` field
418
- - Use `adapters: ["claude"]` entries to provide Claude-specific hints
419
-
420
- **After publishing:**
421
- - Users install with: `/plugin install olko-agent-skills@olko-agent-skills`
422
- - All 12 skills become available as `olko:*` lookup names in Claude Code
423
-
424
- ### Cursor Plugin Registry
425
-
426
- Cursor plugin index is generated at `.cursor-plugin/index.json`.
427
-
428
- **To submit to Cursor:**
429
-
430
- 1. Ensure Cursor plugin metadata is present:
431
- - `.cursor-plugin/index.json` (generated)
432
- - `packages/*/*/adapters/cursor/` (optional Cursor-specific guidance)
433
-
434
- 2. Submit the repository to Cursor's plugin marketplace with the `.cursor-plugin/` manifest
435
-
436
- 3. Users install from Cursor's extension marketplace and reference skills by lookup name
437
-
438
- ### GitHub Copilot
439
-
440
- Generated Copilot instructions are at `.github/copilot-instructions.md` and per-skill prompts under `.github/prompts/`.
441
-
442
- **To use in a GitHub workspace:**
443
-
444
- 1. Copy `.github/copilot-instructions.md` to your repository
445
- 2. Copilot reads this file automatically when enabled
446
- 3. Per-skill prompts can be referenced or imported into custom Copilot configurations
447
-
448
- ### Codex
449
-
450
- Codex installation uses symlinks:
451
-
452
- ```bash
453
- ./scripts/install-codex-symlinks.sh
241
+ ├── packages/
242
+ │ ├── software-development/ (19 skills)
243
+ │ ├── marketing/ (2 skills)
244
+ │ ├── music/ (1 skill)
245
+ │ └── photography/ (1 skill)
246
+ ├── catalog/
247
+ ├── collections/
248
+ ├── scripts/
249
+ ├── .claude-plugin/
250
+ ├── .cursor-plugin/
251
+ ├── .github/prompts/
252
+ ├── .windsurf/rules/
253
+ └── .kiro/steering/
454
254
  ```
455
255
 
456
- Codex looks up skills by `olko:*` lookup names from the installed symlink directories.
457
-
458
256
  ## Local validation
459
257
 
460
258
  Rebuild generated manifests:
@@ -474,25 +272,3 @@ Run both before pushing marketplace updates:
474
272
  ```bash
475
273
  ./scripts/build-adapters.sh && ./scripts/validate-catalog.sh
476
274
  ```
477
-
478
- ## Smoke-tested workflows
479
-
480
- The following package workflows have been smoke-tested locally before first push:
481
-
482
- - `docs-index-keeper`
483
- - installed from npm in a temporary git repo
484
- - initialized hook generation with `npx docs-index-keeper init`
485
- - updated `docs/README.md` from a staged Markdown file
486
- - passed `docs-index-keeper check`
487
- - `semantic-release-beta`
488
- - configured a temporary git repo with `main` and `beta` branches
489
- - used `semantic-release-npm-github-publish` as the release preset
490
- - ran `semantic-release --dry-run --no-ci` on `beta`
491
- - verified prerelease calculation to `1.0.0-beta.1`
492
-
493
- The semantic-release smoke test was intentionally self-contained and used a local bare git remote plus a valid `file://` repository URL so dry-run behavior could be validated without real npm or GitHub publishing credentials.
494
-
495
- ## Licensing notes
496
-
497
- - `fill-music-player` includes an MIT license and is safe to carry as-is in this repository.
498
- - `product-builder` now has an MIT license file added in the source repo clone and in this catalog package, matching the existing MIT claim in its README.
package/catalog/skills.json CHANGED
@@ -250,7 +250,7 @@
250
250
  "lookupName": "olko:open-source-publisher",
251
251
  "category": "software-development",
252
252
  "path": "packages/software-development/open-source-publisher",
253
- "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, and optional donation setup.",
253
+ "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images.",
254
254
  "tags": [
255
255
  "open-source",
256
256
  "github",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@olegkoval/agent-skills",
3
- "version": "1.14.0",
3
+ "version": "1.14.1",
4
4
  "private": false,
5
5
  "publishConfig": {
6
6
  "access": "public"
package/packages/software-development/open-source-publisher/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: open-source-publisher
3
- description: Prepare an open-source repository for polished public publishing. Use when a user asks to publish, open-source, launch, polish, package, brand, or make a GitHub project presentable with a minimal project icon, social preview image, GitHub Pages landing page, standardized README, essential shields, CI/CD quality gates, release automation checks, and optional donation setup. Prefer the external `logo-generator` skill for icon generation when available.
3
+ description: Prepare an open-source repository for polished public publishing. Use when a user asks to publish, open-source, launch, polish, package, brand, or make a GitHub project presentable with a minimal project icon, social preview image, GitHub Pages landing page, standardized README, essential shields, CI/CD quality gates, release automation checks, and optional donation setup. Prefer the external `logo-generator` skill for icon generation when available, and `nolangz/pixel2motion` for optional motion previews of generated static images.
4
4
  license: MIT
5
5
  allowed-tools: Bash, Read, Write, Edit, WebSearch, WebFetch
6
6
  compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires a writable git repository; browser or image rendering tools are useful for visual validation.
@@ -43,10 +43,12 @@ Use this skill to audit whether an OSS repository is ready to publish, then help
43
43
  5. For existing usable pieces, do not propose replacement by default. Ask a change-oriented question only when useful, for example:
44
44
  - "You already have a terminal-style GitHub Pages site. Do you want to keep it or restyle it?"
45
45
  - "You already have an icon and social card. Do you want a refresh, or should I leave them as-is?"
46
+ - "You already have a static social card. Do you want me to animate it with pixel2motion, or leave it static?"
46
47
  - "You already have release automation. Do you want me to audit only, or also tighten it?"
47
48
  6. Ask only for choices needed to fix missing or weak pieces:
48
49
  - If GitHub Pages is missing or weak, ask for style: `oldschool linux`, `terminal`, `modern`, `brutalist`, `glassmorphism`, `y2k`, `hacker`, or custom.
49
50
  - If donation wiring is missing, ask whether to enable it: `none`, `GitHub Sponsors`, `Ko-fi`, `Buy Me a Coffee`, `Open Collective`, `Thanks.dev`, or custom URL.
51
+ - If the repo has a generated static social image or hero card, ask whether to animate it using `nolangz/pixel2motion`.
50
52
  - If the repo has no clear product essence, ask for a one-sentence positioning statement.
51
53
  7. Implement only approved, missing, or weak work in this order:
52
54
  - OSS governance and support files
@@ -206,6 +208,14 @@ file social-card.png
206
208
 
207
209
  Use `magick` or another renderer when `rsvg-convert` is unavailable.
208
210
 
211
+ ## Motion Preview
212
+
213
+ Some repos benefit from a short animated preview. Keep this opt-in.
214
+
215
+ - If you already generated a static image, ask: `Do you want me to animate the static image using pixel2motion?`
216
+ - If the user says yes, use `nolangz/pixel2motion` as the optional dependency for logo animation, animated HTML demos, and GIF/video previews.
217
+ - Do not auto-animate by default.
218
+
209
219
  ## README Standard
210
220
 
211
221
  Shape the README like the house standard used for Go packages such as `slow-query-detector` and `dcli`.
package/packages/software-development/open-source-publisher/adapters/claude/plugin.json CHANGED
@@ -1,5 +1,5 @@
1
1
  {
2
2
  "name": "olko-open-source-publisher",
3
- "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, and optional donation setup.",
3
+ "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images.",
4
4
  "skills": "./skills"
5
5
  }
package/packages/software-development/open-source-publisher/adapters/claude/skills/open-source-publisher/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: open-source-publisher
3
- description: Prepare an open-source repository for polished public publishing. Use when a user asks to publish, open-source, launch, polish, package, brand, or make a GitHub project presentable with a minimal project icon, social preview image, GitHub Pages landing page, standardized README, essential shields, CI/CD quality gates, release automation checks, and optional donation setup. Prefer the external `logo-generator` skill for icon generation when available.
3
+ description: Prepare an open-source repository for polished public publishing. Use when a user asks to publish, open-source, launch, polish, package, brand, or make a GitHub project presentable with a minimal project icon, social preview image, GitHub Pages landing page, standardized README, essential shields, CI/CD quality gates, release automation checks, and optional donation setup. Prefer the external `logo-generator` skill for icon generation when available, and `nolangz/pixel2motion` for optional motion previews of generated static images.
4
4
  license: MIT
5
5
  allowed-tools: Bash, Read, Write, Edit, WebSearch, WebFetch
6
6
  compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires a writable git repository; browser or image rendering tools are useful for visual validation.
@@ -44,10 +44,12 @@ Use this skill to audit whether an OSS repository is ready to publish, then help
44
44
  5. For existing usable pieces, do not propose replacement by default. Ask a change-oriented question only when useful, for example:
45
45
  - "You already have a terminal-style GitHub Pages site. Do you want to keep it or restyle it?"
46
46
  - "You already have an icon and social card. Do you want a refresh, or should I leave them as-is?"
47
+ - "You already have a static social card. Do you want me to animate it with pixel2motion, or leave it static?"
47
48
  - "You already have release automation. Do you want me to audit only, or also tighten it?"
48
49
  6. Ask only for choices needed to fix missing or weak pieces:
49
50
  - If GitHub Pages is missing or weak, ask for style: `oldschool linux`, `terminal`, `modern`, `brutalist`, `glassmorphism`, `y2k`, `hacker`, or custom.
50
51
  - If donation wiring is missing, ask whether to enable it: `none`, `GitHub Sponsors`, `Ko-fi`, `Buy Me a Coffee`, `Open Collective`, `Thanks.dev`, or custom URL.
52
+ - If the repo has a generated static social image or hero card, ask whether to animate it using `nolangz/pixel2motion`.
51
53
  - If the repo has no clear product essence, ask for a one-sentence positioning statement.
52
54
  7. Implement only approved, missing, or weak work in this order:
53
55
  - OSS governance and support files
@@ -207,6 +209,14 @@ file social-card.png
207
209
 
208
210
  Use `magick` or another renderer when `rsvg-convert` is unavailable.
209
211
 
212
+ ## Motion Preview
213
+
214
+ Some repos benefit from a short animated preview. Keep this opt-in.
215
+
216
+ - If you already generated a static image, ask: `Do you want me to animate the static image using pixel2motion?`
217
+ - If the user says yes, use `nolangz/pixel2motion` as the optional dependency for logo animation, animated HTML demos, and GIF/video previews.
218
+ - Do not auto-animate by default.
219
+
210
220
  ## README Standard
211
221
 
212
222
  Shape the README like the house standard used for Go packages such as `slow-query-detector` and `dcli`.
package/packages/software-development/open-source-publisher/adapters/cursor/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "olko:open-source-publisher",
3
3
  "version": "0.1.0",
4
- "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, and optional donation setup.",
4
+ "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images.",
5
5
  "skills": "skills/"
6
6
  }
package/packages/software-development/open-source-publisher/adapters/cursor/skills/open-source-publisher/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: open-source-publisher
3
- description: Prepare an open-source repository for polished public publishing. Use when a user asks to publish, open-source, launch, polish, package, brand, or make a GitHub project presentable with a minimal project icon, social preview image, GitHub Pages landing page, standardized README, essential shields, CI/CD quality gates, release automation checks, and optional donation setup. Prefer the external `logo-generator` skill for icon generation when available.
3
+ description: Prepare an open-source repository for polished public publishing. Use when a user asks to publish, open-source, launch, polish, package, brand, or make a GitHub project presentable with a minimal project icon, social preview image, GitHub Pages landing page, standardized README, essential shields, CI/CD quality gates, release automation checks, and optional donation setup. Prefer the external `logo-generator` skill for icon generation when available, and `nolangz/pixel2motion` for optional motion previews of generated static images.
4
4
  license: MIT
5
5
  allowed-tools: Bash, Read, Write, Edit, WebSearch, WebFetch
6
6
  compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires a writable git repository; browser or image rendering tools are useful for visual validation.
@@ -44,10 +44,12 @@ Use this skill to audit whether an OSS repository is ready to publish, then help
44
44
  5. For existing usable pieces, do not propose replacement by default. Ask a change-oriented question only when useful, for example:
45
45
  - "You already have a terminal-style GitHub Pages site. Do you want to keep it or restyle it?"
46
46
  - "You already have an icon and social card. Do you want a refresh, or should I leave them as-is?"
47
+ - "You already have a static social card. Do you want me to animate it with pixel2motion, or leave it static?"
47
48
  - "You already have release automation. Do you want me to audit only, or also tighten it?"
48
49
  6. Ask only for choices needed to fix missing or weak pieces:
49
50
  - If GitHub Pages is missing or weak, ask for style: `oldschool linux`, `terminal`, `modern`, `brutalist`, `glassmorphism`, `y2k`, `hacker`, or custom.
50
51
  - If donation wiring is missing, ask whether to enable it: `none`, `GitHub Sponsors`, `Ko-fi`, `Buy Me a Coffee`, `Open Collective`, `Thanks.dev`, or custom URL.
52
+ - If the repo has a generated static social image or hero card, ask whether to animate it using `nolangz/pixel2motion`.
51
53
  - If the repo has no clear product essence, ask for a one-sentence positioning statement.
52
54
  7. Implement only approved, missing, or weak work in this order:
53
55
  - OSS governance and support files
@@ -207,6 +209,14 @@ file social-card.png
207
209
 
208
210
  Use `magick` or another renderer when `rsvg-convert` is unavailable.
209
211
 
212
+ ## Motion Preview
213
+
214
+ Some repos benefit from a short animated preview. Keep this opt-in.
215
+
216
+ - If you already generated a static image, ask: `Do you want me to animate the static image using pixel2motion?`
217
+ - If the user says yes, use `nolangz/pixel2motion` as the optional dependency for logo animation, animated HTML demos, and GIF/video previews.
218
+ - Do not auto-animate by default.
219
+
210
220
  ## README Standard
211
221
 
212
222
  Shape the README like the house standard used for Go packages such as `slow-query-detector` and `dcli`.
package/packages/software-development/open-source-publisher/adapters/kiro/steering/open-source-publisher.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  ---
4
4
  inclusion: manual
5
- description: "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, and optional donation setup."
5
+ description: "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images."
6
6
  ---
7
7
 
8
8
  # open-source-publisher
@@ -30,10 +30,12 @@ Use this skill to audit whether an OSS repository is ready to publish, then help
30
30
  5. For existing usable pieces, do not propose replacement by default. Ask a change-oriented question only when useful, for example:
31
31
  - "You already have a terminal-style GitHub Pages site. Do you want to keep it or restyle it?"
32
32
  - "You already have an icon and social card. Do you want a refresh, or should I leave them as-is?"
33
+ - "You already have a static social card. Do you want me to animate it with pixel2motion, or leave it static?"
33
34
  - "You already have release automation. Do you want me to audit only, or also tighten it?"
34
35
  6. Ask only for choices needed to fix missing or weak pieces:
35
36
  - If GitHub Pages is missing or weak, ask for style: `oldschool linux`, `terminal`, `modern`, `brutalist`, `glassmorphism`, `y2k`, `hacker`, or custom.
36
37
  - If donation wiring is missing, ask whether to enable it: `none`, `GitHub Sponsors`, `Ko-fi`, `Buy Me a Coffee`, `Open Collective`, `Thanks.dev`, or custom URL.
38
+ - If the repo has a generated static social image or hero card, ask whether to animate it using `nolangz/pixel2motion`.
37
39
  - If the repo has no clear product essence, ask for a one-sentence positioning statement.
38
40
  7. Implement only approved, missing, or weak work in this order:
39
41
  - OSS governance and support files
@@ -193,6 +195,14 @@ file social-card.png
193
195
 
194
196
  Use `magick` or another renderer when `rsvg-convert` is unavailable.
195
197
 
198
+ ## Motion Preview
199
+
200
+ Some repos benefit from a short animated preview. Keep this opt-in.
201
+
202
+ - If you already generated a static image, ask: `Do you want me to animate the static image using pixel2motion?`
203
+ - If the user says yes, use `nolangz/pixel2motion` as the optional dependency for logo animation, animated HTML demos, and GIF/video previews.
204
+ - Do not auto-animate by default.
205
+
196
206
  ## README Standard
197
207
 
198
208
  Shape the README like the house standard used for Go packages such as `slow-query-detector` and `dcli`.
package/packages/software-development/open-source-publisher/adapters/windsurf/rules/open-source-publisher.md CHANGED
@@ -1,7 +1,7 @@
1
1
  <!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
2
2
 
3
3
  ---
4
- description: "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, and optional donation setup."
4
+ description: "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images."
5
5
  ---
6
6
 
7
7
  # open-source-publisher
@@ -29,10 +29,12 @@ Use this skill to audit whether an OSS repository is ready to publish, then help
29
29
  5. For existing usable pieces, do not propose replacement by default. Ask a change-oriented question only when useful, for example:
30
30
  - "You already have a terminal-style GitHub Pages site. Do you want to keep it or restyle it?"
31
31
  - "You already have an icon and social card. Do you want a refresh, or should I leave them as-is?"
32
+ - "You already have a static social card. Do you want me to animate it with pixel2motion, or leave it static?"
32
33
  - "You already have release automation. Do you want me to audit only, or also tighten it?"
33
34
  6. Ask only for choices needed to fix missing or weak pieces:
34
35
  - If GitHub Pages is missing or weak, ask for style: `oldschool linux`, `terminal`, `modern`, `brutalist`, `glassmorphism`, `y2k`, `hacker`, or custom.
35
36
  - If donation wiring is missing, ask whether to enable it: `none`, `GitHub Sponsors`, `Ko-fi`, `Buy Me a Coffee`, `Open Collective`, `Thanks.dev`, or custom URL.
37
+ - If the repo has a generated static social image or hero card, ask whether to animate it using `nolangz/pixel2motion`.
36
38
  - If the repo has no clear product essence, ask for a one-sentence positioning statement.
37
39
  7. Implement only approved, missing, or weak work in this order:
38
40
  - OSS governance and support files
@@ -192,6 +194,14 @@ file social-card.png
192
194
 
193
195
  Use `magick` or another renderer when `rsvg-convert` is unavailable.
194
196
 
197
+ ## Motion Preview
198
+
199
+ Some repos benefit from a short animated preview. Keep this opt-in.
200
+
201
+ - If you already generated a static image, ask: `Do you want me to animate the static image using pixel2motion?`
202
+ - If the user says yes, use `nolangz/pixel2motion` as the optional dependency for logo animation, animated HTML demos, and GIF/video previews.
203
+ - Do not auto-animate by default.
204
+
195
205
  ## README Standard
196
206
 
197
207
  Shape the README like the house standard used for Go packages such as `slow-query-detector` and `dcli`.