Results for “packages”

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.

The English summary is being prepared. Showing the original description.

| 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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Search, suggest, add, and browse third-party audio packages. Handles "suggest packages", "add a package", "what packages are available", "search for pitch detection", and package browsing.

The English summary is being prepared. Showing the original description.

Unity 6 packages and services guide. Use when working with Package Manager, installing/updating packages, scoped registries, or Unity Gaming Services (Authentication, Cloud Save, Analytics, Leaderboards, Matchmaker). Covers essential packages list and version compatibility. Based on Unity 6.3 LTS documentation.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Detects typosquatting attacks in npm and PyPI package registries by analyzing package name similarity using Levenshtein distance and other string metrics, examining publish date heuristics to identify recently created packages mimicking established ones, and flagging download count anomalies where suspicious packages have disproportionately low usage compared to their legitimate targets. The analyst queries the PyPI JSON API and npm registry API to gather package metadata for automated comparison. Activates for requests involving package typosquatting detection, dependency confusion analysis, malicious package identification, or software supply chain threat hunting in package registries.

The English summary is being prepared. Showing the original description.

Create an HTML presentation showing a photography studio's signature work, process, and pricing packages. A coordinated black and electric-yellow template helps prospective clients review the studio's work and consider a commission.

• Presenting a photography studio's portfolio
• Explaining packages and rates to prospective clients
• Preparing a creative agency pitch

Update all Storybook packages in a project to a chosen release or canary, an early development build. Use it to test changes in external apps, reproduce bugs, and keep package versions aligned while handling peer dependencies.

• Test a canary build in an external app
• Reproduce a bug with a specific Storybook release
• Update all Storybook packages to the latest stable release

Audit project dependencies for known vulnerabilities and outdated packages. Organize findings by severity, review proposed package changes before optional automatic fixes, and rerun the audit to check whether the reported vulnerability count decreased.

• Auditing third-party packages before a release
• Checking dependencies after installation or lockfile changes
• Investigating reported CVE advisories

Test omo Codex Light edition in an isolated environment using real Codex and a local mock model. Verify installation, plugin hooks, and terminal startup, with captured evidence and no calls to a real model API.

• Verify installation and config.toml changes in isolation
• Confirm plugin hooks run during a real Codex turn
• Check terminal interface startup

Set up a Python environment inside the project and install its packages. Follow existing environment tools when present, avoid changing the system Python, and provide commands that work from a fresh shell.

• Set up an environment for a new Python project
• Install packages into an existing project environment
• Resolve an externally-managed-environment installation error

Update Remotion and its related packages while respecting the project's package manager and workspace structure. The workflow aligns package versions, updates the lockfile and installed Remotion skills, and checks the resulting dependency changes.

• Updating Remotion to the latest stable release
• Aligning versions across related packages
• Updating dependencies across workspaces

Structure an evidence-based comparison of shortlisted accounting packages using 57 fields for capabilities, costs, and evaluator judgments. Request empty templates in CSV, SQL DDL, JSON Schema, or Notion mapping while keeping the final decision with the business.

• Prepare a common comparison template for accounting packages
• Define shared tests for vendor demonstrations
• Organize quoted costs for first-year and three-year comparisons

Configure Turborepo builds for projects containing multiple apps and shared packages. Set task dependencies, reuse saved build outputs locally or remotely, limit runs to affected packages, and investigate why cached results are not being reused.

• Setting up build tasks in a new Turborepo project
• Sharing cached build outputs between local machines and CI
• Running builds only for affected packages

Migrate the database access layer of a .NET/C# application from Oracle to PostgreSQL with Npgsql. Update packages, connection settings, parameter types, SQL, and stored procedure calls, then build the copied project and track completed migration tasks.

• Migrate C# database access from Oracle to PostgreSQL
• Replace Oracle packages and connection settings
• Review parameter types and stored procedure calls

Screen dependency names on npm, PyPI, and crates.io before installation to find lookalikes of legitimate packages. This skill compares spelling patterns and registry metadata, helping review AI-generated lists, lockfile changes, and new dependencies in CI/CD.

• Screening a new dependency before installation
• Reviewing dependency lists generated by AI
• Checking lockfile changes for swapped packages

Inspect npm packages and dependency files for malicious installation scripts, credential theft, and self-spreading behavior. Use GuardDog scanning, source inspection, known-malicious version checks, and isolated execution to produce an evidence-based assessment.

• Vetting a new npm dependency before adoption
• Reviewing dependency files during code review
• Checking lockfiles against known-malicious versions

Extend a NanoClaw agent's own environment with packages, external tools, or specialist agents. The skill chooses the workflow for each change, edits memory and standing instructions, and delegates source changes to a builder for review.

• Adding an external tool for reading RSS feeds
• Installing persistent system or global npm packages
• Updating memory or standing behavior instructions

Implement or change behavior in Composio’s TypeScript SDK, the library used to integrate Composio into applications. Covers tools, sessions, authentication settings, connected accounts, and generated interfaces in @composio/core and shared TypeScript packages.

• Change tool or toolkit behavior
• Implement session or authentication changes
• Update connected account handling

Navigate the Composio SDK monorepo, a repository containing multiple packages, and follow its shared development rules. Use it to decide where changes belong, handle generated files and release metadata, and prepare branches and pull requests.

• Planning changes across multiple packages
• Deciding where code belongs
• Checking generated-file and release metadata rules

Create a dedicated test project linked to the current worktree and check Agent Builder through APIs and browser interactions. It covers agent and skill management, permissions, defaults, and related features, with selectable test sections.

• Validate an Agent Builder feature branch before review
• Check role-based permissions and authentication
• Test agent and skill management through APIs and the UI

Guide changes to the published @kortix/sdk package with rules for preserving public APIs, writing failing tests before behavior changes, keeping the core independent of frameworks, and checking package installation. It also covers exports, streaming transport, and release version handling.

• Adding a public SDK feature or export
• Renaming public types while preserving compatibility
• Changing streaming or transport behavior