Skip to main content
Execute qualquer Skill no Manus
com um clique
Repositório GitHub

react-native-livechart

react-native-livechart contém 3 skills coletadas de brandtnewlabs, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.

skills coletadas
3
Stars
158
atualizado
2026-07-15
Forks
7
Cobertura ocupacional
1 categorias ocupacionais · 100% classificado
explorador de repositórios

Skills neste repositório

publish-library
Desenvolvedores de software

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
Desenvolvedores de software

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
Desenvolvedores de software

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