agentleFS
forcedotcomforcedotcom/salesforcedx-vscode/.claude/skills/lit-components/SKILL.md

lit-components

Skill1k starsChanged 26 days agoBSD-3-ClauseView on GitHub

Create or edit Lit components in this repository, including reactive properties and internal state.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about forcedotcom/salesforcedx-vscode

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

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Lit's standard decorators with TypeScript auto-accessors.

    line 9
  2. Very specific:

    Import decorators from their individual lit/decorators/<name>.js modules.

    line 11
  3. Very specific:

    Use { attribute: false } for object or array inputs that must not map to HTML attributes.

    line 14
  4. Very specific:

    Do not use the legacy static properties plus declare pattern for reactive members, or enable experimentalDecorators/legacy class-field …

    line 15
  5. Distinctive:

    Verify the component with its package compile, lint, unit tests, and focused browser tests when behavior or rendering changes.

    line 16

≈ “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

Lit components

Use Lit's standard decorators with TypeScript auto-accessors.

  • Import decorators from their individual lit/decorators/<name>.js modules.
  • Declare public reactive inputs with @property(...) public accessor and internal render state with @state() private accessor.
  • Initialize accessors inline when they have defaults. Use a definite-assignment assertion for required inputs supplied by the host.
  • Use { attribute: false } for object or array inputs that must not map to HTML attributes. Specify type when an attribute needs Lit conversion.
  • Do not use the legacy static properties plus declare pattern for reactive members, or enable experimentalDecorators/legacy class-field semantics.
  • Verify the component with its package compile, lint, unit tests, and focused browser tests when behavior or rendering changes.

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.