agentleFS
Sign inStart free
oocxoocx/tfplan2md/.claude/skills/website-visual-assets/SKILL.md

website-visual-assets

Skill174 starsChanged 2 months agoMITView on GitHub

Generate website HTML exports and screenshots using the repo's HtmlRenderer and ScreenshotGenerator tools.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Place the generated screenshots in website/src/assets/screenshots/.

    line 65
  2. Distinctive:

    Update the consuming page or content source so it references the new screenshot asset.

    line 66
  3. Very specific:

    Verify the relevant page in website/dist/ uses the correct light or dark asset variants and that any lightbox or screenshot wrapper still …

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill Instructions

Purpose

Provide a repeatable workflow to generate HTML exports and screenshots for the website using real repository artifacts.

Hard Rules

Must

  • Use src/tools/Oocx.TfPlan2Md.HtmlRenderer to generate HTML from markdown reports.
  • Use src/tools/Oocx.TfPlan2Md.ScreenshotGenerator (Playwright) to generate screenshots from those HTML exports.
  • Store website screenshots under website/src/assets/screenshots/.
  • Update the consuming website source when screenshot assets change (for example the relevant page in website/src/pages/ or shared content data in website/src/_data/).

Must Not

  • Do not hand-edit screenshots or create “mock” screenshots that aren’t generated from real HTML exports.

Golden Example

# Preferred Method: Use the automated script
scripts/generate-screenshot.sh \
  --plan examples/firewall-with-static-analysis/plan.json \
  --output-prefix firewall-example \
  --selector "details:has(summary:has-text('azurerm_firewall_network_rule_collection'))" \
  --thumbnail-width 580 --thumbnail-height 400 \
  --lightbox-width 1200 --lightbox-height 900 \
  --render-target azdo \
  --open-details-selector "details"

# This generates 12 screenshot variants automatically:
# - Thumbnail and lightbox crops
# - Light and dark themes
# - 1x and 2x DPI versions
# - Azure DevOps rendering style

# Manual Method (for advanced use cases):
# 1) Generate HTML (Azure DevOps flavor, wrapped)
dotnet run --project src/tools/Oocx.TfPlan2Md.HtmlRenderer -- \
  --input artifacts/comprehensive-demo.md \
  --flavor azdo \
  --template src/tools/Oocx.TfPlan2Md.HtmlRenderer/templates/azdo-wrapper.html \
  --output artifacts/comprehensive-demo.azdo.html

# 2) Capture a screenshot with details expanded
DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1 dotnet run --project src/tools/Oocx.TfPlan2Md.ScreenshotGenerator -- \
  --input artifacts/comprehensive-demo.azdo.html \
  --output website/src/assets/screenshots/full-report-azdo.png \
  --open-details "details" \
  --full-page

Actions

  1. Pick the markdown report under artifacts/ to use as the source.
  2. Generate the required HTML exports with src/tools/Oocx.TfPlan2Md.HtmlRenderer.
  3. Generate screenshots from the exported HTML with src/tools/Oocx.TfPlan2Md.ScreenshotGenerator.
  4. Place the generated screenshots in website/src/assets/screenshots/.
  5. Update the consuming page or content source so it references the new screenshot asset.
  6. Verify the relevant page in website/dist/ uses the correct light or dark asset variants and that any lightbox or screenshot wrapper still works.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free