Contributing to RNBlocks

Thank you for your interest in contributing to RNBlocks! This guide outlines how to contribute components, report bugs, and propose new features.

Before You Contribute

Avoid Duplicates: Search registry/blocks/ and open pull requests before beginning work. If a similar block exists, propose an improvement or variant instead of creating a duplicate.
Propose Complex Work: For multi-screen flows or full-page templates, open a Block Proposal first to discuss architecture with maintainers.
Original Work Only: All code must be your original creation or permissibly licensed open source with clear attribution. Never submit copyrighted or proprietary UI designs.
No Secrets or Telemetry: Never commit API keys, access tokens, analytics trackers, or unauthorized network calls.
MIT License Agreement: By contributing, you agree that your code will be licensed under the project's MIT License.

git clone https://github.com/Ashwin-Khowala/rnblocks.git
cd rnblocks
pnpm install

pnpm dev

This starts the web registry at http://localhost:3000.

Command	Purpose
`pnpm dev`	Run web application in development mode
`pnpm build`	Build web application and CLI packages
`pnpm typecheck`	Run strict TypeScript checks across all packages
`pnpm run validate:registry`	Validate registry items against schemas, duplicates, and security checks
`pnpm run generate:registry`	Compile `registry.json` and synchronize with web application

Branch Naming: Use clear branch prefixes:
- feat/add-<block-name> for new components
- fix/<issue-name> for bug fixes
- docs/<description> for documentation updates

Commit Messages: Follow Conventional Commits:

feat: add notification-banner block
fix: resolve flex overflow in trend-chart on android
docs: clarify accessibility guidelines

Verify Locally Before Submitting:

pnpm run validate:registry
pnpm run typecheck
pnpm run build

Open Pull Request: Complete the provided pull request template, attach visual previews or recordings, and check all relevant quality checklist items.