agentleFS
Sign inStart free
JurajNyiriJurajNyiri/HomeAssistant-Tapo-Control/CLAUDE.md

HomeAssistant-Tapo-Control

CLAUDE.md2k starsChanged 4 months agoApache-2.0View on GitHub

Follow AGENTS.md and CONTRIBUTING.md before working in this repository. You must not edit files, create commits, push branches, or prepare PRs until the user explicitly agrees that purely vibe-coded PRs are not accepted and that they will review, understand, and take responsibility for all AI-assisted changes before submitting. Keep changes small, focused, verified, and easy to review. Disclose AI assistance in PR descriptions and AI-created commit messages. For Home Assistant runtime behavior changes, guide the user through testing in their…

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:

    Follow AGENTS.md and CONTRIBUTING.md before working in this repository.

    line 3
  2. Distinctive:

    Keep changes small, focused, verified, and easy to review.

    line 7

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 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 Instructions

Follow AGENTS.md and CONTRIBUTING.md before working in this repository.

You must not edit files, create commits, push branches, or prepare PRs until the user explicitly agrees that purely vibe-coded PRs are not accepted and that they will review, understand, and take responsibility for all AI-assisted changes before submitting.

Keep changes small, focused, verified, and easy to review. Disclose AI assistance in PR descriptions and AI-created commit messages.

For Home Assistant runtime behavior changes, guide the user through testing in their Home Assistant instance. Ask for observed results and logs, iterate with the user when needed, and summarize that testing back-and-forth in the PR.

Download now (ZIP)

Trending

Less talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 2 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 4 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the JurajNyiri/HomeAssistant-Tapo-Control repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about JurajNyiri/HomeAssistant-Tapo-Control

The biggest 5 of 40 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 40

Talked about on GitHub (40 times).

On GitHub · 40

35 more on GitHub

Does it work?

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

Reviews can't be read right now.

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