Contributing

frogg is Apache-2.0 and developed at github.com/frogg-app/frogg. It is an independently maintained fork of Paseo; keep the LICENSE, NOTICE and existing license headers intact.

Workflow

1. Fork the repository and create a branch from main.

2. Set up the monorepo: development setup.

3. Make the change with tests: testing, coding standards.

4. Update the docs in the same pull request if users will notice the change: writing docs.

5. Check your change:

   node scripts/ci/verify.mjs --changed
   npm run typecheck

6. Open a pull request against frogg-app/frogg main and complete the template checklist.

If you maintain a branded fork, build upstream contributions from upstream/main, not from your product branch: contribute features back.

Pull request checklist

The template asks for:

• the root package.json version bumped and workspace versions synced (npm run version:sync-internal),
• a CHANGELOG.md entry under the new version,
• npm run typecheck, npm run lint and npm run format:check passing,
• docs updated, or a note that none were needed.

Agent roles

The repository includes role instructions for AI coding agents in .claude/agents/ (daemon-dev, client-dev, desktop-dev, dev-tooling, docs-writer) and task skills in skills/. Human contributors can read them as checklists for each area.

Development setupBuild order, dev daemon and app, worktrees.

ArchitectureDaemon, clients, protocol and code map.

TestingTest categories and what CI runs.

Coding standardsFormatting, branding literals, i18n, protocol.

Release processVersions, tags and the release workflow.

Writing docsWhere docs live, style, screenshots, preview.