Claude Code workflow
Host Claude Code explainers where the team can actually open them.
Claude Code can produce a strong explainer, but a local HTML file is not a handoff. Explainers.fyi gives the agent one upload target and returns a URL that works in Slack, pull requests, docs, and post-incident notes.
Best fit
Use this when Claude Code has already summarized a code path, deployment change, incident, or product decision and the next step is distribution, not another document format.
- Publish the generated HTML through the upload API or the companion explainer skill.
- Share one canonical URL instead of screenshots, local files, or copied chat text.
- Keep the explainer crawlable when it is public and private when a Pro workflow needs owner-only access.
What to link from the explainer
A useful Claude Code explainer should point readers back to the evidence it summarizes: PRs, docs, examples, and the artifact that triggered the explanation.
- Add a link to the relevant repository PR, issue, or docs page inside the generated HTML.
- Use the Explainers.fyi examples page to model concise audience and artifact framing.
- Use the quickstart when the agent only needs a direct API call instead of the full skill.
Operational guardrails
Treat the explainer as a public artifact unless you intentionally select a Pro privacy setting. Do not publish secrets, raw customer data, or internal credentials.
- The service scans uploads for unsafe HTML and credential-like content.
- Free-tier pages expire after 30 days and include attribution.
- Pro pages can be unlisted or private, and do not expire by default.