Product feedback
For now, use the project repository or your existing project communication channel to share bugs, missing tools, formula corrections, UI polish requests, accessibility issues, and broken links.
The most useful feedback includes the page URL, what you expected, what happened instead, browser details if relevant, and a small sample input that reproduces the issue without exposing private data.
Tool requests
The roadmap is being finished category by category. The most useful requests include a clear tool name, target user, required inputs, expected output, examples of similar tools, and any official source the tool should follow.
For developer tools, strong candidates are utilities people use repeatedly: formatters, validators, converters, generators, inspectors, and small workflow helpers.
Corrections
For finance, education, medical, business, legal, and security tools, corrections should include source references and dates so the implementation can stay accurate over time.
If a correction involves a regulation, exam rule, tax slab, medical formula, security standard, or eligibility pathway, include the official source wherever possible.