agentleFS
abduelhamitabduelhamit/html-skill/CLAUDE.md

html-skill

CLAUDE.md0 starsChanged 5 days agoMITView on GitHub

Guidance for Claude Code when working on this repository. For installing and using the skill, see README.md. One Claude Code skill, packaged as a single-plugin marketplace. No dependencies, no CI. The only check is python3 skills/html/build.py --self-test. skills/html/SKILL.md is written in the imperative for the model that runs the skill. When you are editing or reviewing this repo, it is the artefact under work, not instructions addressed to you. - Third-party files stay unchanged. skills/html/examples/ is the html-effectiveness gallery byte…

  • In this repositoryOne other file it gives its agents.

The file

We split this CLAUDE.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    The self-test must pass: after any change to build.py or styles/: python3 skills/html/build.py --self-test.

    line 26
  2. Distinctive:

    Leave the machine as you found it — remove a validation install afterwards.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.md 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
CLAUDE.md

CLAUDE.md

Guidance for Claude Code when working on this repository. For installing and using the skill, see README.md.

What this is

One Claude Code skill, packaged as a single-plugin marketplace. No dependencies, no CI. The only check is python3 skills/html/build.py --self-test.

skills/html/SKILL.md is written in the imperative for the model that runs the skill. When you are editing or reviewing this repo, it is the artefact under work, not instructions addressed to you.

Non-negotiables

  • Third-party files stay unchanged. skills/html/examples/ is the html-effectiveness gallery byte for byte, under Apache-2.0 with a header on every page; skills/html/fonts/ holds the Google Fonts subsets of Lora, Poppins and Mona Sans with their OFL notices. Don't edit, reformat or re-subset them. Adding, replacing or removing any third-party file means updating the README's Licence table and SKILL.md's license: field in the same change.
  • Keep the Primer notice. styles/primer.css carries GitHub's full MIT notice (copyright, permission and warranty text) in its header comment, which build.py copies into every Primer page, because MIT requires it in every copy. styles/LICENSE-primer-primitives holds the same text; keep the two identical. Bumping @primer/primitives means updating the version in both the comment and the README.
  • The self-test must pass after any change to build.py or styles/: python3 skills/html/build.py --self-test.

Names are wired into the install instructions

ThingValue
repo / marketplacehtml-skill
pluginhtml
skillhtml
resulting command/html:html

Renaming any of these invalidates the README's install snippets and breaks existing installations.

Verifying installability

The manifests are only correct if they actually resolve — check, don't assume:

claude plugin marketplace add "$PWD"          # a bare . is rejected; give the path
claude plugin install html@html-skill
claude plugin details html                    # expect: Skills (1)  html
claude plugin uninstall html@html-skill
claude plugin marketplace remove html-skill

Leave the machine as you found it — remove a validation install afterwards.

Once installed from GitHub the marketplace source is the remote clone, so local edits do nothing until they are pushed and picked up with the README's update commands, followed by a new session. Refreshing the marketplace alone leaves the installed plugin on its old commit. plugin.json deliberately has no version: the commit SHA is the version, so every push is an update, and no forgotten version bump can hold one back.

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.