Open a pull request

#Prepare your change

Fork the repository, create a focused branch, and keep unrelated changes out. Library additions belong in data/libraries.ts with a unique kebab-case slug, canonical URL, factual description, and existing taxonomy values where possible.

Get Screen's agreement before starting a major feature, redesign, or adding a dependency. Keep unfinished pull requests in draft.

#Update docs and discovery

Major features need usage and setup documentation linked from /docs. For library, component, integration, public page, or agent capability changes, verify llms.txt, robots.txt, and the sitemap. Update affected generators, page metadata, and agent guides in the same pull request. Library and integration entries are generated from catalog data.

#Check your changes

Run these from the repository root before you open the pull request.

npm install
npm run typecheck
npm test

Tests include the production build. Check mobile layouts, light and dark modes, and keyboard access when the interface changes. Review your own diff, including any code generated by AI.

#Describe it

Explain what changed, why it changed, and how you verified it. List check results and include screenshots for visible interface changes. For bug fixes, include reproduction steps and expected behavior.

Link every fully resolved issue, including your own, with a separate Closes #123. Use Refs #123 for partial fixes and describe what remains. After Screen merges the PR, verify resolved issues are closed; close any still open with a link to the merged PR.

Your PR title appears in version history after merging into main. Describe the shipped change clearly.