Skip to main content
Exécutez n'importe quel Skill dans Manus
en un clic
brandtnewlabs
Profil créateur GitHub

brandtnewlabs

Vue par dépôt de 3 skills collectés dans 1 dépôts GitHub.

skills collectés
3
dépôts
1
mis à jour
2026-07-15
carte des dépôts

Où se trouvent les skills

Principaux dépôts par nombre de skills collectés, avec leur part dans ce catalogue créateur et leur couverture métier.

explorateur de dépôts

Dépôts et skills représentatifs

publish-library
Développeurs de logiciels

Publish the react-native-livechart library to npm from this monorepo. Use this whenever the user wants to publish, ship, or release the package to npm — including the first-ever publish — or asks how publishing works here. Covers the workspace-scoping gotcha (a bare `npm publish` targets the Expo example app, not the library), the `private: false` gate, the source-shipping/prepack model, dry-run verification, and the required post-publish steps (push, tag, and a GitHub Release). Trigger even if the user just says "push it to npm", "can we publish now", or "ship the package" without naming the skill. For deciding a version bump + CHANGELOG first, see the update-library skill.

2026-07-15
skia-paths
Développeurs de logiciels

Use when building or changing Skia paths in this repo — anything touching SkPath, PathBuilder, per-frame path construction in worklets/useDerivedValue, drawSpline, the `.reset()` + ping-pong path-pool pattern, or the react-native-skia path-migration (immutable SkPath / PathBuilder). Covers the installed 2.6.4 mutable API, the PathBuilder API, the static path factories, the worklet per-frame patterns, and how the repo's useChartPaths pool/ping-pong optimization maps onto the new model. Trigger on "Skia path", "SkPath", "PathBuilder", "build a path each frame", "migrate path building", or a Skia upgrade.

2026-07-15
update-library
Développeurs de logiciels

Cut and release a NEW version of the react-native-livechart library: choose the semver bump, update the version field, update the CHANGELOG, verify, then publish. Use this whenever the user wants to release a new version, bump the version, ship an update/patch/minor/major, publish changes since the last release, or "cut a release" of the package — even if they don't name the skill. This skill owns the versioning + changelog decisions; for the npm publish mechanics themselves it hands off to the publish-library skill.

2026-07-15
1 dépôts affichés sur 1
Tous les dépôts sont affichés