Developer data
Fix invalid JSON or API data
Use this when a payload is hard to read, fails parsing, or needs to move between JSON, YAML, CSV, tokens, and regex extraction.
- Format and validate the raw JSON first.
- Convert YAML or CSV only after the base shape is known.
- Test regex extraction against positive and negative examples.
- Decode Base64 or JWT samples without pasting live secrets.
Done when: the final payload validates, the expected keys are present, and the edge-case sample still behaves correctly.
Do not use when: the sample contains production private keys, live session tokens, regulated records, or credentials.
Documents
Prepare a PDF packet for sending
Use this when multiple documents need to become one sendable file with the right order, size, and readable content.
- Convert HTML, spreadsheet, or presentation sources first.
- Merge only final source files and keep originals untouched.
- Extract text or images if you need a review copy.
- Compress after the packet is final, then open the output.
Done when: the PDF opens, page order is correct, file size is acceptable, and important text/images remain readable.
Do not use when: you need legal redaction, certified signatures, or forensic document handling.
Images
Make an image smaller for a page or form
Use this before uploading large photos, screenshots, product images, or document visuals.
- Resize to the real display size before compressing.
- Choose WebP or JPG for photos; keep PNG for transparency.
- Compress last and compare the result at 100% zoom.
- Use a fallback format if the upload form requires it.
Done when: the image is meaningfully smaller and still preserves text, faces, product edges, and important details.
Do not use when: the image needs print-grade archival quality or legally meaningful metadata retention.
Writing
Check copy before publishing
Use this for landing copy, emails, documentation, social text, or article snippets before they go live.
- Measure words, characters, lines, and reading time.
- Check readability without removing useful detail.
- Summarize source notes as a draft, not a fact check.
- Convert Markdown or casing only after wording is stable.
Done when: the text fits the channel, reads clearly, has no broken formatting, and avoids unsupported claims.
Do not use when: the copy needs legal, medical, or financial review by a qualified professional.
Design
Choose readable UI colors
Use this when a color needs to work in a real interface, not just look good in isolation.
- Pick the real base color from the design or image.
- Generate palette options that match the UI role.
- Check contrast for normal text, small text, and dark surfaces.
- Export CSS after accessibility checks pass.
Done when: text remains readable, status colors are not the only cue, and the exported CSS matches the intended surface.
Do not use when: brand, compliance, or accessibility review requires an audited design system.
Security
Generate safe technical values
Use this for random passwords, UUIDs, hashes, encoded URLs, and token structure inspection with clear boundaries.
- Generate passwords and store real account values in a password manager.
- Use UUIDs as identifiers, not as authentication secrets.
- Normalize whitespace before comparing hashes.
- Decode JWTs only to inspect structure, not to verify trust.
Done when: the generated value is copied to the correct secure destination and no sensitive sample remains on the page.
Do not use when: you need enterprise key management, secret rotation, or compliance logging.
Finance estimates
Estimate loan and interest scenarios
Use this to compare assumptions before a spreadsheet or professional finance discussion is needed.
- Write down the principal, rate, term, and contribution assumptions.
- Change one variable at a time so the driver is visible.
- Compare monthly payment and total cost, not payment alone.
- Keep results as estimates, not advice.
Done when: the assumption and result are captured together, with clear rounding and scenario labels.
Do not use when: tax, lending, investment, or legal decisions require personalized professional advice.
Quick math
Run quick unit and percentage checks
Use this when a simple number question should not turn into a spreadsheet.
- Normalize units before comparing values.
- Round only at the final step.
- Use scientific mode for expressions that need parentheses or powers.
- Capture the input with the result so the answer can be checked later.
Done when: the units, input, formula, and final rounded answer are all clear.
Do not use when: the calculation controls a safety-critical, medical, legal, or engineering decision.
Code snippets
Clean code snippets before sharing
Use this when CSS, JavaScript, HTML, or SQL snippets need to be readable, smaller, or easier to review.
- Beautify first if the goal is review or debugging.
- Minify only after the snippet is correct.
- Keep an original copy before transforming code.
- Do not paste secrets, production credentials, or private URLs.
Done when: the cleaned snippet is readable or compressed for the target use and still behaves the same.
Do not use when: the code needs build-system validation, dependency analysis, or production deployment checks.
Sharing
Create a QR or encoded link
Use this when a URL needs to be shared in print, slides, forms, support notes, or a message.
- Encode reserved characters before building query strings.
- Create a QR code only from the final URL.
- Test the QR code with a real device before publishing.
- Keep sensitive or private links out of public QR codes.
Done when: the URL opens correctly, the QR scans quickly, and the destination is safe to expose.
Do not use when: the link contains access tokens, private documents, or temporary session data.
Office to PDF
Convert office files into PDFs
Use this when spreadsheet, deck, or HTML content needs a simple PDF copy for review or sharing.
- Check the source layout before converting.
- Choose page size and orientation based on the final reader.
- Open the PDF after export and inspect page breaks.
- Compress only after the final PDF looks correct.
Done when: tables, slides, and headings remain readable and the output opens on another device.
Do not use when: exact enterprise document fidelity or tracked-change preservation is required.
Publishing
Publish a page without obvious quality gaps
Use this before publishing a page, article, support note, or lightweight documentation update.
- Measure length and reading time so the page fits the job.
- Improve readability without deleting necessary details.
- Compress images and check color contrast before launch.
- Use the Quality Lab to confirm the page belongs in the public index.
Done when: the page answers a real task, links to useful next steps, and avoids thin or duplicated filler.
Do not use when: the topic needs original research, legal review, medical review, or specialized expertise you do not have.