polystella-contributor

Guide PolyStella contributors through contract-safe package source modifications with required tests and documentation updates.

8|2|Updated May 18, 2026
One-click install
npx skills add https://github.com/cloudflare/polystella --skill polystella-contributor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polystella-contributor
Source: https://github.com/cloudflare/polystella/tree/main/skills/polystella-contributor
Command: npx skills add https://github.com/cloudflare/polystella --skill polystella-contributor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps contributors safely modify PolyStella’s core translation pipeline, adapters, CLI, providers, cache hashing, and runtime APIs without breaking invariants or consumer compatibility.

Core Features & Use Cases

  • File-format adapter development: implement and register new parsing/extraction/application logic with required contracts and tests.
  • CLI and translation provider changes: add subcommands and new translator implementations following the package’s dispatcher and provider contracts.
  • Cache contract and UI-string maintenance: update cache hashing rules and i18n drift/sync/AI-fill behavior with coordinated documentation and test updates.

Quick Start

Use the polystella-contributor skill to generate a step-by-step patch plan for adding a new file-format adapter and the corresponding test suite.

Frequently Asked Questions about polystella-contributor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new file-format adapter to an i18n translation pipeline?

To add a new file-format adapter, implement the parsing and extraction logic and register it following the deterministic adapter interface. You must also generate a corresponding test suite to enforce internal contracts and prevent regressions.

What's the best way to extend a CLI with new translation provider subcommands?

Extending a CLI with translation provider subcommands requires following the package's dispatcher and provider contracts. Implement new translator logic safely by adhering to orchestrator boundaries to avoid breaking consumer compatibility.

How does cache contract modification affect translation pipeline behavior?

Cache contract modifications directly impact cache hashing rules and i18n string synchronization. Changing these contracts requires coordinated documentation and test updates to maintain the integrity of AI-fill and drift behaviors.

Do I need to update tests when changing runtime APIs for internationalization?

Yes, editing runtime APIs and UI-string handling requires mandatory test and documentation updates. Enforcing these internal contracts ensures deterministic adapter interfaces and prevents regressions across the translation pipeline.

When should I avoid modifying core translation package internals directly?

You should avoid bypassing internal contracts when implementing adapters or changing cache hashing rules. Failing to use guided patch plans risks breaking orchestrator boundaries, provider contracts, and overall consumer compatibility.

Can I integrate a custom translation provider into an Astro adapter?

Yes, you can integrate a custom translation provider by implementing the translator logic according to the package's provider contracts. This ensures the new implementation works correctly within the existing dispatcher and runtime API boundaries.