DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to draw a leave plan or a pay breakdown as a clear diagram with See Code

Ask your agent to chart a year of leave or where your pay goes, and share the result as one file.

Who it is forAn individual planning time off or reviewing a monthly budget who wants a visual that is easier to read than a spreadsheet.

The problemLeave dates and money flows are hard to scan in a table, and sharing the numbers with a partner or manager is awkward.

The outcomeA timeline of leave or a Sankey chart of pay, shared as a single HTML file or exported as an image.

What you need first

  • A coding agent that supports Agent Skills, such as Claude Code, Cursor, Codex or OpenCode
  • Node.js, needed for the command-line SVG export
  • Chrome or Edge, needed only for command-line PNG, GIF or MP4 export

Steps

  1. Install See Code in your agent with npx skills add Aryanutkarsh/seecode -g or the Claude Code plugin commands
  2. Ask your agent for a timeline of your leave dates, or a Sankey chart of where your pay goes
  3. Give the dates or amounts in plain words or in a CSV or JSON file
  4. Open the HTML file in a browser and check the totals against your records
  5. Export it as PNG or SVG if you want to share it outside the browser

Prompt for your agent

Use the SeeCode skill from the Aryanutkarsh/SeeCode repo to draw <a timeline of my leave or a Sankey of my pay> from <the plain-words description or CSV path>. Expected output: one diagram file. Verify that the totals in the diagram match the source numbers.

Caveat. See Code draws the numbers you provide, so check the totals against your own records before you rely on the chart.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page