Skip to main content
Ejecuta cualquier Skill en Manus
con un clic
Repositorio de GitHub

palatro

palatro contiene 6 skills recopiladas de nemesiscodex, con cobertura ocupacional por repositorio y páginas de detalle dentro del sitio.

skills recopiladas
6
Stars
1
actualizado
2026-03-05
Forks
0
Cobertura ocupacional
1 categorías ocupacionales · 100% clasificado
explorador de repositorios

Skills en este repositorio

integration-javascript-node
Desarrolladores de software

PostHog integration for server-side Node.js applications using posthog-node

2026-03-05
integration-tanstack-start
Desarrolladores de software

PostHog integration for TanStack Start full-stack applications

2026-03-05
wiiz-yaml-author
Desarrolladores de software

Generate .wiiz/wizard.yaml and .wiiz/values.example.json for repository onboarding with wiiz. Use when a user wants to create or update onboarding wizard config from an existing repository's setup requirements, environment variables, and developer workflows.

2026-03-03
turborepo
Desarrolladores de software

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

2026-03-03
vercel-composition-patterns
Desarrolladores de software

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

2026-03-03
vercel-react-best-practices
Desarrolladores de software

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

2026-03-03