Funding Steward
Treat funding as a transparent community-support surface and keep every link and
claim consistent across the repository and live profiles.
Canonical Repository Surfaces
- GitHub Funding:
.github/FUNDING.yml
- README support section:
README.md under Help Maintenance
- Buy Me a Coffee account:
hyochan
- PayPal destination:
https://paypal.me/dooboolab
Verify the live destination before changing canonical values. Do not introduce
OpenCollective, GitHub Sponsors, Patreon, or another platform unless the user
confirms the project uses it.
Workflow
- Establish the requested surface: funding configuration, README CTA, badge or
image, supporter acknowledgement, or a live update.
- Read
AGENTS.md, the current funding config, and every README occurrence.
- Draft evidence-backed copy before any public write. Keep the tone warm,
specific, and builder-to-builder.
- For live profile or update edits, use the user's existing signed-in browser
session only after the user authorizes publication. Hand sign-in and any
payment/account verification back to the user.
- Verify the saved public URL and then update repository links if the canonical
destination changed.
Guardrails
- Never expose account emails, payout details, tokens, balances, private donor
data, or browser authentication state.
- Never promise release dates, response times, or sponsor benefits that are not
documented and operational.
- Do not imply that a past donor opted into a new program.
- Distinguish recurring sponsorship, one-time support, and non-financial
contribution accurately.
- Keep funding changes local unless commit, push, PR, or publication authority
is explicit.
Update Pattern
Use a concise structure unless the user provides exact copy:
- Thank supporters and state the concrete milestone.
- List shipped maintenance, compatibility, docs, CI, or issue-triage work.
- Explain what support enables without inflating impact.
- Name near-term work without overcommitting.
- Link the repository and the intended funding destination.
After an edit, check Markdown rendering, image accessibility text, HTTPS links,
and consistency between .github/FUNDING.yml and README.
1---2name: funding-steward3description: Maintain react-native-nitro-sound funding links, GitHub Funding configuration, Buy Me a Coffee and PayPal calls to action, supporter acknowledgements, and transparent maintainer updates. Use when editing sponsor copy or assets, checking funding-link consistency, or drafting or publishing supporter-facing updates.4---56# Funding Steward78Treat funding as a transparent community-support surface and keep every link and9claim consistent across the repository and live profiles.1011## Canonical Repository Surfaces1213- GitHub Funding: `.github/FUNDING.yml`14- README support section: `README.md` under `Help Maintenance`15- Buy Me a Coffee account: `hyochan`16- PayPal destination: `https://paypal.me/dooboolab`1718Verify the live destination before changing canonical values. Do not introduce19OpenCollective, GitHub Sponsors, Patreon, or another platform unless the user20confirms the project uses it.2122## Workflow23241. Establish the requested surface: funding configuration, README CTA, badge or25 image, supporter acknowledgement, or a live update.262. Read `AGENTS.md`, the current funding config, and every README occurrence.273. Draft evidence-backed copy before any public write. Keep the tone warm,28 specific, and builder-to-builder.294. For live profile or update edits, use the user's existing signed-in browser30 session only after the user authorizes publication. Hand sign-in and any31 payment/account verification back to the user.325. Verify the saved public URL and then update repository links if the canonical33 destination changed.3435## Guardrails3637- Never expose account emails, payout details, tokens, balances, private donor38 data, or browser authentication state.39- Never promise release dates, response times, or sponsor benefits that are not40 documented and operational.41- Do not imply that a past donor opted into a new program.42- Distinguish recurring sponsorship, one-time support, and non-financial43 contribution accurately.44- Keep funding changes local unless commit, push, PR, or publication authority45 is explicit.4647## Update Pattern4849Use a concise structure unless the user provides exact copy:50511. Thank supporters and state the concrete milestone.522. List shipped maintenance, compatibility, docs, CI, or issue-triage work.533. Explain what support enables without inflating impact.544. Name near-term work without overcommitting.555. Link the repository and the intended funding destination.5657After an edit, check Markdown rendering, image accessibility text, HTTPS links,58and consistency between `.github/FUNDING.yml` and README.
hyochan