unional/unional-skills

Add a website to one of unional's TypeScript packages or monorepos — an Astro + Starlight docs site in apps/website, deployed to GitHub Pages, matching the cyberuni house layout (base path, cyber-* icon system, Linear theme). Use when asked to 'add a website', 'add a docs site', 'add an astro website', 'set up documentation for this package', 'follow cyber-mux', or 'publish docs to GitHub Pages'.

Bring one of unional's repos or organizations up to the standard baseline — branch protection ruleset, merge and Actions settings, security toggles, and the CI/release file layout. Use when setting up a new repo, when asked to 'update branch protection', 'require all-checks', 'apply my repo settings', 'set up this repo like the others', or to audit which repos have drifted from the baseline.

Sweep an owner's repos to find which ones stopped publishing, classify each failure by root cause, and report the evidence needed to fix them. Use when asked 'which of my repos are broken?', 'is anything not publishing?', 'audit my releases', 'find repos that need modernizing', or before running modernize-repo so you know which repos to run it on.

Decide what to do with one of unional's repos still on a legacy CI shape — a single nodejs.yml calling typescript-build.yml/typescript-test.yml/npm-release.yml, or inlined yarn steps — and then archive it, drop its CI, or migrate it to the pull-request.yml + release.yml split. Use before **apply-repo-baseline** touches a repo, when a ruleset would require code / all-checks on a pipeline that cannot produce it, when asked to 'migrate the old workflows', 'fix nodejs.yml', 'why is this PR unmergeable', or when auditing which repos are on the old pipeline.

Bring one repo fully current: settings baseline, a release that publishes without long-lived tokens, dependency PRs that merge themselves, and proof it all works. Use this skill when asked to 'modernize this repo', 'bring it up to standard', 'fix everything about this repo', or after a sweep flags a repo as broken.

Replace a TypeScript library's build, lint, test and dependency stack in one pass — tsdown for the build, biome for lint, turbo for tasks, vitest for tests — instead of upgrading tools that the swap deletes. Use when asked to 'modernize the toolchain', 'bring the deps current', 'replace webpack/eslint/jest', 'upgrade to TypeScript 7', or when a repo's dependency list is long and mostly obsolete.

Move a package's release off long-lived NPM_TOKEN/PAT secrets onto OIDC trusted publishing, migrating it to pnpm + changesets on the way, and keep dependency PRs merging themselves. Use this skill when a release publishes with a token, has silently stopped publishing, fails with 401 on /-/whoami or ENONPMTOKEN, or when asked to 'fix releases', 'remove NPM_TOKEN', or 'set up trusted publishing'.

Ship a pending changesets release: find the repo's open Version Packages PR, approve the workflow run GitHub is holding for approval, verify the required check goes green, merge, and confirm the version actually advanced on the registry. Use when asked to 'ship it', 'release', 'ship', or 'publish' a package, when a Version Packages PR is stuck BLOCKED with no failing check, when a release PR has been open for days, or when gh pr merge refuses because a required context never ran.

Apply a consistent documentation standard: controlled plain prose, one home per fact, and every external claim backed by a source. Use when writing or revising documentation, READMEs, or skill bodies; when deciding where a document belongs; when moving, renaming, or splitting a page; when a draft reads as generated and needs its rhythm, filler words, or em dashes fixed; or on requests like 'improve the docs', 'audit the docs', 'this page is too long', 'this sounds like AI', 'humanize this', 'remove the em dashes', or 'where should this be documented'.

Move a repo from a personal namespace into an organization without breaking its release — re-registers the npm trusted publisher that pins owner/repo, fixes package metadata and badges, and turns on the merge queue that only org-owned repos can have. Use when asked to 'transfer this repo', 'move it to the org', 'give it org-level secrets', or when modernize-repo phase 2 decides the repo's home.