trees
Skill194 starsChanged 46 days agoMITView on GitHub
Use when changing Palot file-tree behavior built on @pierre/trees, especially
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- Amronos/skillsedited, first seen Nov 15, 2026
- pierrecomputer/pierreedited, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- pierrecomputer/pierre★ 6.5k77% same
- Amronos/skills★ 177% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- diffsSkill
- opencode-coverageSkill
- opencode-runtimeSkill
- palot-designSkill
- palot-desktop-devSkill
- palot-performanceSkill
- shadcnSkill
- test-palot-desktopSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 14
Use @pierre/trees for an interactive file tree.
- Very specific: line 23
Run the install command from apps/desktop.
≈ “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.
Files
@pierre/trees
Modified by Palot contributors for Palot-specific scope and Vite+ installation guidance. See NOTICE.md for the pinned upstream source and LICENSE.md for the Apache-2.0 license.
Use @pierre/trees for an interactive file tree. Public state and callbacks use
path strings.
Install
vp add @pierre/treesRun the install command from apps/desktop. Install react and react-dom when the app uses the React entry.
Select an API reference
| Entry | Reference |
@pierre/trees | Core API |
@pierre/trees/react | React API |
@pierre/trees/ssr | SSR API |
@pierre/trees/web-components | Web components API |
Select a recipe
| Task | Recipe |
| Render and update a tree in React | Use React |
| Render and update a tree without React | Use vanilla JavaScript |
| Preload a tree on the server | Use SSR |
| Apply a resolved Shiki or VS Code theme | Apply a theme |
| Configure search, rename, drag and drop, and git status | Add interactions |
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
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.