[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7551TN2AGCZXG9EJSV1EYCC":3,"skill-same:01M7551TN2AGCZXG9EJSV1EYCC":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7551TN2AGCZXG9EJSV1EYCC","recursica-skill-tree",null,"Rules for the Recursica tree — when data is a real hierarchy, collapsed by default, depth limits, why indentation alone is not enough, and tree keyboard and screen-reader behavior. Use for folder structures, category trees, and nested lists. Not for flat records — see recursica-skill-table; not for single-level sections — see recursica-skill-accordion.","borderux\u002Frecursica-knowledge","borderux","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14911137?v=4","01M754SG94XX2Y7176KM2WGZG3","Border LLC","01M754SGA9E7YSNK6NWVMKMHYC",1,"MIT","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fcomponents\u002Frecursica-skill-tree\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: recursica-skill-tree\ndescription: Rules for the Recursica tree — when data is a real hierarchy, collapsed by default, depth limits, why indentation alone is not enough, and tree keyboard and screen-reader behavior. Use for folder structures, category trees, and nested lists. Not for flat records — see recursica-skill-table; not for single-level sections — see recursica-skill-accordion.\nlicense: MIT\nmetadata:\n  author: hi@borderux.com\n  version: 0.2.0\n---\n\n# Tree\n\nA tree shows items inside other items, such as folders inside folders. A parent item holds child items. The persona opens a parent item to see the parent item's children. The persona opens only the parent items the persona needs.\n\n## When to use a tree\n\n- **The data is a true hierarchy.** The meaning of a node (one item in the tree) depends on the node's parent. For example, a folder sits inside a folder, or a category sits inside a category. A \"2026\" folder inside \"Invoices\" holds the invoices from 2026.\n- **The hierarchy goes deeper than two levels, or the depth varies.** A hierarchy that is only ever two levels deep is an accordion.\n- **The depth of the hierarchy varies, and the persona needs to see where an item sits in the hierarchy.** For example, the persona needs to know that a file sits in \"Invoices\", then \"2026\". Knowing only that an item exists is not enough for the persona.\n- **The persona is exploring, not comparing.** A tree helps the persona find one item. A table helps the persona compare many items.\n- **Content must show and hide at more than one level.** For example, a section opens to show subsections, and a subsection opens to show pages. `recursica-skill-navigation` states that an accordion has one level unless the theme (the design a designer sets in Theme Forge: the token values, the components, and each component's variants, states and sizes) has a nesting option. When the content has several levels, use a tree.\n\n## When not to use a tree\n\n| Situation                                                                                                         | Use instead                                                                                                                                                    |\n| ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| The records are peers (objects of the same kind, such as rows in a list), with no parent records or child records | A table. See `recursica-skill-table`.                                                                                                                          |\n| Sections of content are stacked at one level, such as the questions on a help page                                | An accordion. See `recursica-skill-accordion`.                                                                                                                 |\n| The persona moves between areas of the application, such as Orders and Settings                                   | Navigation. See `recursica-skill-navigation`.                                                                                                                  |\n| The persona chooses one value in a form, and the values form a hierarchy, such as product categories              | A dropdown or an autocomplete, unless the hierarchy itself is the point of the choice. Confirm with the user whether the hierarchy is the point of the choice. |\n| The hierarchy is only ever two levels deep                                                                        | An accordion. See `recursica-skill-accordion`.                                                                                                                 |\n| The persona moves items between two sets                                                                          | A transfer list. See `recursica-skill-transfer-list`.                                                                                                          |\n\n**When no item has children, the data is not a tree.** Flat data shown in a tree is a list with indentation that means nothing.\n\n## Variants\n\n**Use only the tree variants and options that the knowledge MCP server lists for the theme.** A designer can add variants and options in Theme Forge, so each theme can differ. Get the list with the server's `component_api` tool, and use the names the code uses. Never invent a variant or an option.\n\nThe rules below describe each variant and option by role, such as \"the selected option\". The names in the standard UI kit (the unchanged UI kit in the official Recursica release) are examples only.\n\n- **A node is selected or not selected.** In the standard UI kit, the variant is `selection-states`, with the options `unselected` and `selected`.\n- **A node's expand control is separate from the node's label.** The expand control opens and closes the node. Selecting a node and expanding a node are different actions, with a mouse and with the keyboard. The two actions differ because the expand control is separate from the label.\n- **If the theme has an expanded state or a collapsed state, use the theme's state.** Otherwise, do not invent a rotation or a second icon token (a named design value, such as a color or a size, set by the design system) to show an open node. See \"Open questions\".\n\n## Rules\n\n**Show every node collapsed by default.** Open only the nodes the persona needs for the current task.\n\n- `recursica-skill-navigation` sets the collapsed-by-default rule for trees and accordions.\n- Opening every node adds no value, because the parent node labels then have no reason to exist.\n\n**Let the data set how many nodes each level shows.** Sort the nodes at each level so the persona can scan the nodes. A tree is for finding one item, and the 7 ± 2 guideline does not apply to finding. A level that grows very long can be grouped one level deeper. See chunking in `recursica-skill-working-memory`.\n\n**Label a node with what the node is, not where the node sits.** Do not label a node \"Level 2\". Name what the node is instead, such as \"Invoices\". Do not add numbers that repeat the node's place in the nesting, such as \"2.3.1\".\n\n**A node label must be clear enough to choose the node while the node's children are hidden.** For example, a node labeled \"Misc\" makes the persona open the node to learn what the node holds. If the persona has to expand a node to learn what the node holds, rewrite the label.\n\n**Use a tree for a real hierarchy, and an accordion for showing and hiding sections at one level.** For example, a folder structure uses a tree, and the questions on a help page use an accordion. `recursica-skill-navigation` states that an accordion has one level unless the theme has a nesting option. The navigation skill also states that content with several levels uses a tree.\n\n- Never nest an accordion to look like a tree.\n- Never put a tree inside an accordion panel.\n- If the sections are peers at one level, use an accordion. See `recursica-skill-accordion`.\n\nThe choice between a tree and an accordion is settled. Every case is one or the other.\n\n**Do not put a form, a table, or a card inside a tree node.** A node is a label, not a container.\n\n**Do not calculate indentation by hand.** The theme sets how far each level of the tree is indented.\n\n**Never show depth with indentation alone.** Indentation is one visual channel (color, shape, position or text, each a separate signal). `recursica-skill-design-system-conventions` requires a second channel. In a tree, the second channel is each node's level, set in the code.\n\n**In a tree used for navigation, make every node that has a page a link with a real URL.** A parent node with no page expands in place, as `recursica-skill-navigation` says. The tree follows `recursica-skill-navigation`, including the rule that a sub-level opens on click, never on hover.\n\n## Accessibility\n\nThe rules below add to the accessibility baseline in `recursica-skill-design-system-conventions`, including the focus ring, which every Recursica component follows.\n\nThe tree has the most specific keyboard rules of any component, and the keyboard rules most often ignored. A persona using a keyboard or a screen reader cannot use a tree of clickable nested `div` elements. A tree built that way has no level, no expand state, and no keyboard access.\n\n### Screen readers\n\n- **A screen reader must announce the tree as a tree, and each node as a tree item.** The nesting must be real structure in the code, not only indentation on screen.\n- **Each node must report the node's level, and the node's position among the nodes at the same level**, as in \"level 3, 2 of 7\". A persona using a screen reader cannot see indentation. Without the level and the position, the persona cannot tell where the current node sits in the tree.\n- **A node with children must report whether the node is expanded or collapsed.** A node with no children must not report that the node can expand.\n- **The selected state must be set in code**, never shown only by the selected node's fill or color.\n- **An expand control that is separate from the node needs a separate accessible name** (the name a screen reader reads out for a control). The expand control's accessible name must include the node's label, as in \"Expand Marketing\", not \"Expand\".\n- **Announce the change when a node expands.** Announce how many child nodes appeared, as in \"Marketing expanded, 4 items\". At the least, announce that the node is expanded.\n- **A node's icon is decorative and must be hidden from screen readers.** The expand state tells a persona using a screen reader that a node has children. A folder icon does not.\n- **The tree needs an accessible name** that says which hierarchy the tree shows, as in \"Product categories\".\n\n### Keyboard and non-mouse navigation\n\n- **The tree is a single tab stop** (a place the Tab key lands). Tab moves focus into the tree, and then out of the tree. Do not make every node a tab stop, and do not add tabindex to nodes.\n- **The Up Arrow and Down Arrow keys move focus between the visible nodes, across levels.** Which nodes are visible depends on which nodes are expanded.\n- **The Right Arrow key expands a collapsed node, then moves focus into the node. The Left Arrow key collapses an expanded node, then moves focus to the node's parent.** Do not change what the arrow keys do. Personas know the Right Arrow and Left Arrow key behavior from trees in other tools.\n- **Home moves focus to the first visible node, and End moves focus to the last visible node.**\n- **Enter activates the focused node.** Enter selects the node, or opens the link when the node is a link. The persona must be able to tell expanding a node apart from activating a node. Telling the two actions apart matters because the expand control and the node are separate controls.\n- **Never move focus automatically** when a node expands. Focus stays on the node the persona acted on.\n- **Never show a node's actions or the node's expand control only on hover.**\n\n## Styling set by tokens\n\n**Never set or override the tree's styling.** The theme sets every visual property of the tree, such as size, spacing, borders, colors and animation. Do not add extra containers or spacers to change the tree's look. If the design needs a look the theme does not give, report the missing look as a design-system gap. See `recursica-skill-design-router`.\n\n## Related skills\n\n- `recursica-skill-navigation` covers six topics:\n  - nodes collapsed by default\n  - sub-levels that open on click and not on hover\n  - the rule that an accordion has one level unless the theme has a nesting option\n  - the rule that content with several levels uses a tree\n  - routing when the tree is navigation\n  - permissions\n- `recursica-skill-working-memory` — the reason for the limit on visible nodes at each level.\n- `recursica-skill-design-system-conventions` — never show meaning in only one channel.\n\n### Only if used on the same screen\n\n- `recursica-skill-accordion` — the alternative for sections at one level, and when to use an accordion instead of a tree.\n- `recursica-skill-table` — the alternative when the data turns out to be flat.\n\n## Open questions\n\n- **The look of an expanded node compared with a collapsed node.** The look of an expanded node is the biggest open question about the tree. Confirm with the user only when the theme has no expanded state.\n- **Choosing several items in a tree**, with or without checkboxes. The design rules do not cover choosing several items in a hierarchy. Confirm with the user only when the theme has no option for choosing several items.\n- **A maximum depth.** No rule sets a maximum number of levels. A tree with no limit on levels is a real usability problem.\n- **Selecting a parent node.** No rule says whether a parent node can be selected, or only a node with no children.\n- **Loading children only when a node opens**, and what the node shows while the children load. When the theme has a loading state, confirm with the user only whether children load when a node opens.\n- **Dragging to reorder nodes or move a node to a new parent.** If dragging is allowed, `recursica-skill-design-system-conventions` also requires a way to reorder and move nodes without dragging.\n- **The empty state of the tree**, and what an expanded node with no children shows.\n- **Treat every open question above as a question nobody has answered.** Never treat an open question as a decision that someone forgot to write down. The design-system website adds nothing about the tree. Unlike most component skills, the tree skill has the UI kit (the token file, `recursica_ui-kit.json`, that says which variants and states each component has) as the only source.\n\n## Pre-flight checklist\n\n- [ ] The data is a true hierarchy. No flat list is shown indented as a tree.\n- [ ] Nodes are collapsed by default, and only the nodes the persona needs for the current task are open.\n- [ ] The nodes at each level are sorted so the persona can scan the nodes.\n- [ ] Each node label names what the node is. Each node label is clear enough to choose the node while the node is collapsed.\n- [ ] A real hierarchy uses a tree, and sections at one level use an accordion, as in `recursica-skill-accordion`. No accordion is nested to look like a tree, and no form, table, or card is inside a node.\n- [ ] A screen reader announces the tree as a tree, with an accessible name. Each node reports the node's level, position, and expanded state.\n- [ ] A node with no children does not report that the node can expand.\n- [ ] The selected state is set in code, not shown only by color. The expand control's accessible name includes the node's label.\n- [ ] The tree is a single tab stop. Up Arrow and Down Arrow move focus. Right Arrow expands, and Left Arrow collapses.\n- [ ] Home and End move focus to the first and last visible nodes. Enter activates the focused node.\n- [ ] Focus stays on a node when the node expands. The focus ring is visible, and looks different from the selected state.\n- [ ] No part of the tree appears only on hover. Sub-levels open on click.\n- [ ] No styling is set or overridden on the tree. No container or spacer is added to change the tree's look.\n- [ ] Indentation comes from the theme, and no expanded state or icon was invented.\n- [ ] Every variant, option, and state is one the knowledge MCP server lists for the theme. No variant or option is invented.\n- [ ] Open questions were asked about, not decided: the look of an expanded node, choosing several items, a maximum depth, selecting a parent node, loading children when a node opens, dragging to reorder or move a node, and the empty state.\n","# Tree\n\nA tree shows items inside other items, such as folders inside folders. A parent item holds child items. The persona opens a parent item to see the parent item's children. The persona opens only the parent items the persona needs.\n\n## When to use a tree\n\n- **The data is a true hierarchy.** The meaning of a node (one item in the tree) depends on the node's parent. For example, a folder sits inside a folder, or a category sits inside a category. A \"2026\" folder inside \"Invoices\" holds the invoices from 2026.\n- **The hierarchy goes deeper than two levels, or the depth varies.** A hierarchy that is only ever two levels deep is an accordion.\n- **The depth of the hierarchy varies, and the persona needs to see where an item sits in the hierarchy.** For example, the persona needs to know that a file sits in \"Invoices\", then \"2026\". Knowing only that an item exists is not enough for the persona.\n- **The persona is exploring, not comparing.** A tree helps the persona find one item. A table helps the persona compare many items.\n- **Content must show and hide at more than one level.** For example, a section opens to show subsections, and a subsection opens to show pages. `recursica-skill-navigation` states that an accordion has one level unless the theme (the design a designer sets in Theme Forge: the token values, the components, and each component's variants, states and sizes) has a nesting option. When the content has several levels, use a tree.\n\n## When not to use a tree\n\n| Situation                                                                                                         | Use instead                                                                                                                                                    |\n| ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| The records are peers (objects of the same kind, such as rows in a list), with no parent records or child records | A table. See `recursica-skill-table`.                                                                                                                          |\n| Sections of content are stacked at one level, such as the questions on a help page                                | An accordion. See `recursica-skill-accordion`.                                                                                                                 |\n| The persona moves between areas of the application, such as Orders and Settings                                   | Navigation. See `recursica-skill-navigation`.                                                                                                                  |\n| The persona chooses one value in a form, and the values form a hierarchy, such as product categories              | A dropdown or an autocomplete, unless the hierarchy itself is the point of the choice. Confirm with the user whether the hierarchy is the point of the choice. |\n| The hierarchy is only ever two levels deep                                                                        | An accordion. See `recursica-skill-accordion`.                                                                                                                 |\n| The persona moves items between two sets                                                                          | A transfer list. See `recursica-skill-transfer-list`.                                                                                                          |\n\n**When no item has children, the data is not a tree.** Flat data shown in a tree is a list with indentation that means nothing.\n\n## Variants\n\n**Use only the tree variants and options that the knowledge MCP server lists for the theme.** A designer can add variants and options in Theme Forge, so each theme can differ. Get the list with the server's `component_api` tool, and use the names the code uses. Never invent a variant or an option.\n\nThe rules below describe each variant and option by role, such as \"the selected option\". The names in the standard UI kit (the unchanged UI kit in the official Recursica release) are examples only.\n\n- **A node is selected or not selected.** In the standard UI kit, the variant is `selection-states`, with the options `unselected` and `selected`.\n- **A node's expand control is separate from the node's label.** The expand control opens and closes the node. Selecting a node and expanding a node are different actions, with a mouse and with the keyboard. The two actions differ because the expand control is separate from the label.\n- **If the theme has an expanded state or a collapsed state, use the theme's state.** Otherwise, do not invent a rotation or a second icon token (a named design value, such as a color or a size, set by the design system) to show an open node. See \"Open questions\".\n\n## Rules\n\n**Show every node collapsed by default.** Open only the nodes the persona needs for the current task.\n\n- `recursica-skill-navigation` sets the collapsed-by-default rule for trees and accordions.\n- Opening every node adds no value, because the parent node labels then have no reason to exist.\n\n**Let the data set how many nodes each level shows.** Sort the nodes at each level so the persona can scan the nodes. A tree is for finding one item, and the 7 ± 2 guideline does not apply to finding. A level that grows very long can be grouped one level deeper. See chunking in `recursica-skill-working-memory`.\n\n**Label a node with what the node is, not where the node sits.** Do not label a node \"Level 2\". Name what the node is instead, such as \"Invoices\". Do not add numbers that repeat the node's place in the nesting, such as \"2.3.1\".\n\n**A node label must be clear enough to choose the node while the node's children are hidden.** For example, a node labeled \"Misc\" makes the persona open the node to learn what the node holds. If the persona has to expand a node to learn what the node holds, rewrite the label.\n\n**Use a tree for a real hierarchy, and an accordion for showing and hiding sections at one level.** For example, a folder structure uses a tree, and the questions on a help page use an accordion. `recursica-skill-navigation` states that an accordion has one level unless the theme has a nesting option. The navigation skill also states that content with several levels uses a tree.\n\n- Never nest an accordion to look like a tree.\n- Never put a tree inside an accordion panel.\n- If the sections are peers at one level, use an accordion. See `recursica-skill-accordion`.\n\nThe choice between a tree and an accordion is settled. Every case is one or the other.\n\n**Do not put a form, a table, or a card inside a tree node.** A node is a label, not a container.\n\n**Do not calculate indentation by hand.** The theme sets how far each level of the tree is indented.\n\n**Never show depth with indentation alone.** Indentation is one visual channel (color, shape, position or text, each a separate signal). `recursica-skill-design-system-conventions` requires a second channel. In a tree, the second channel is each node's level, set in the code.\n\n**In a tree used for navigation, make every node that has a page a link with a real URL.** A parent node with no page expands in place, as `recursica-skill-navigation` says. The tree follows `recursica-skill-navigation`, including the rule that a sub-level opens on click, never on hover.\n\n## Accessibility\n\nThe rules below add to the accessibility baseline in `recursica-skill-design-system-conventions`, including the focus ring, which every Recursica component follows.\n\nThe tree has the most specific keyboard rules of any component, and the keyboard rules most often ignored. A persona using a keyboard or a screen reader cannot use a tree of clickable nested `div` elements. A tree built that way has no level, no expand state, and no keyboard access.\n\n### Screen readers\n\n- **A screen reader must announce the tree as a tree, and each node as a tree item.** The nesting must be real structure in the code, not only indentation on screen.\n- **Each node must report the node's level, and the node's position among the nodes at the same level**, as in \"level 3, 2 of 7\". A persona using a screen reader cannot see indentation. Without the level and the position, the persona cannot tell where the current node sits in the tree.\n- **A node with children must report whether the node is expanded or collapsed.** A node with no children must not report that the node can expand.\n- **The selected state must be set in code**, never shown only by the selected node's fill or color.\n- **An expand control that is separate from the node needs a separate accessible name** (the name a screen reader reads out for a control). The expand control's accessible name must include the node's label, as in \"Expand Marketing\", not \"Expand\".\n- **Announce the change when a node expands.** Announce how many child nodes appeared, as in \"Marketing expanded, 4 items\". At the least, announce that the node is expanded.\n- **A node's icon is decorative and must be hidden from screen readers.** The expand state tells a persona using a screen reader that a node has children. A folder icon does not.\n- **The tree needs an accessible name** that says which hierarchy the tree shows, as in \"Product categories\".\n\n### Keyboard and non-mouse navigation\n\n- **The tree is a single tab stop** (a place the Tab key lands). Tab moves focus into the tree, and then out of the tree. Do not make every node a tab stop, and do not add tabindex to nodes.\n- **The Up Arrow and Down Arrow keys move focus between the visible nodes, across levels.** Which nodes are visible depends on which nodes are expanded.\n- **The Right Arrow key expands a collapsed node, then moves focus into the node. The Left Arrow key collapses an expanded node, then moves focus to the node's parent.** Do not change what the arrow keys do. Personas know the Right Arrow and Left Arrow key behavior from trees in other tools.\n- **Home moves focus to the first visible node, and End moves focus to the last visible node.**\n- **Enter activates the focused node.** Enter selects the node, or opens the link when the node is a link. The persona must be able to tell expanding a node apart from activating a node. Telling the two actions apart matters because the expand control and the node are separate controls.\n- **Never move focus automatically** when a node expands. Focus stays on the node the persona acted on.\n- **Never show a node's actions or the node's expand control only on hover.**\n\n## Styling set by tokens\n\n**Never set or override the tree's styling.** The theme sets every visual property of the tree, such as size, spacing, borders, colors and animation. Do not add extra containers or spacers to change the tree's look. If the design needs a look the theme does not give, report the missing look as a design-system gap. See `recursica-skill-design-router`.\n\n## Related skills\n\n- `recursica-skill-navigation` covers six topics:\n  - nodes collapsed by default\n  - sub-levels that open on click and not on hover\n  - the rule that an accordion has one level unless the theme has a nesting option\n  - the rule that content with several levels uses a tree\n  - routing when the tree is navigation\n  - permissions\n- `recursica-skill-working-memory` — the reason for the limit on visible nodes at each level.\n- `recursica-skill-design-system-conventions` — never show meaning in only one channel.\n\n### Only if used on the same screen\n\n- `recursica-skill-accordion` — the alternative for sections at one level, and when to use an accordion instead of a tree.\n- `recursica-skill-table` — the alternative when the data turns out to be flat.\n\n## Open questions\n\n- **The look of an expanded node compared with a collapsed node.** The look of an expanded node is the biggest open question about the tree. Confirm with the user only when the theme has no expanded state.\n- **Choosing several items in a tree**, with or without checkboxes. The design rules do not cover choosing several items in a hierarchy. Confirm with the user only when the theme has no option for choosing several items.\n- **A maximum depth.** No rule sets a maximum number of levels. A tree with no limit on levels is a real usability problem.\n- **Selecting a parent node.** No rule says whether a parent node can be selected, or only a node with no children.\n- **Loading children only when a node opens**, and what the node shows while the children load. When the theme has a loading state, confirm with the user only whether children load when a node opens.\n- **Dragging to reorder nodes or move a node to a new parent.** If dragging is allowed, `recursica-skill-design-system-conventions` also requires a way to reorder and move nodes without dragging.\n- **The empty state of the tree**, and what an expanded node with no children shows.\n- **Treat every open question above as a question nobody has answered.** Never treat an open question as a decision that someone forgot to write down. The design-system website adds nothing about the tree. Unlike most component skills, the tree skill has the UI kit (the token file, `recursica_ui-kit.json`, that says which variants and states each component has) as the only source.\n\n## Pre-flight checklist\n\n- [ ] The data is a true hierarchy. No flat list is shown indented as a tree.\n- [ ] Nodes are collapsed by default, and only the nodes the persona needs for the current task are open.\n- [ ] The nodes at each level are sorted so the persona can scan the nodes.\n- [ ] Each node label names what the node is. Each node label is clear enough to choose the node while the node is collapsed.\n- [ ] A real hierarchy uses a tree, and sections at one level use an accordion, as in `recursica-skill-accordion`. No accordion is nested to look like a tree, and no form, table, or card is inside a node.\n- [ ] A screen reader announces the tree as a tree, with an accessible name. Each node reports the node's level, position, and expanded state.\n- [ ] A node with no children does not report that the node can expand.\n- [ ] The selected state is set in code, not shown only by color. The expand control's accessible name includes the node's label.\n- [ ] The tree is a single tab stop. Up Arrow and Down Arrow move focus. Right Arrow expands, and Left Arrow collapses.\n- [ ] Home and End move focus to the first and last visible nodes. Enter activates the focused node.\n- [ ] Focus stays on a node when the node expands. The focus ring is visible, and looks different from the selected state.\n- [ ] No part of the tree appears only on hover. Sub-levels open on click.\n- [ ] No styling is set or overridden on the tree. No container or spacer is added to change the tree's look.\n- [ ] Indentation comes from the theme, and no expanded state or icon was invented.\n- [ ] Every variant, option, and state is one the knowledge MCP server lists for the theme. No variant or option is invented.\n- [ ] Open questions were asked about, not decided: the look of an expanded node, choosing several items, a maximum depth, selecting a parent node, loading children when a node opens, dragging to reorder or move a node, and the empty state.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"hi@borderux.com","0.2.0","main","110b382bfe525d171ba33c7074d6ad1f3762548f","skills\u002Fcomponents\u002Frecursica-skill-tree",0,"https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge","https:\u002F\u002Fgithub.com\u002Fborderux","https:\u002F\u002Fborderux.com","2026-11-09 16:39:27",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-tree",{"tool":41,"command":42},"bunx","bunx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-tree",{"tool":44,"command":45},"pnpm","pnpm dlx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-tree","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fcomponents\u002Frecursica-skill-tree\u002FSKILL.md",true,[],[50,58,65,72,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":54,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7556E67F3DCE39P7ZTVT5TA","recursica-skill-template","Replace with a description of the skill and its purpose.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Ftemplate\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Ftemplate\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M75569FCJXWWGXRVMTJFBK0W","recursica-skill-working-memory","The research behind Recursica's item-count limits, with citations — Miller's 7 ± 2, Cowan's 4, chunking, and recognition versus recall. Use when a decision turns on how many options, navigation items, or chips to show at once, or to justify or challenge a count. Not for choosing a control — see recursica-skill-selection-controls.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fpsychology\u002Frecursica-skill-working-memory\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M75564EC5E5QKBPNWARQVDBC","recursica-skill-discoverability","The research behind Recursica's rule that rarely needed settings get a real but unpromoted entry point — the paradox of the active user, satisficing (settling for the first method that is good enough), and progressive disclosure, with citations. Use when deciding whether to hide, promote, or build a configuration or customization feature, or to justify that choice. Not for item counts — see recursica-skill-working-memory.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fpsychology\u002Frecursica-skill-discoverability\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7555Z2YRG9YSM01KMYT1FY5","recursica-skill-design-router","Start here for any Recursica screen work. The router says what to decide in what order, which skill owns each decision, which rule wins when two rules conflict, and when to confirm with the user instead of guessing. Load the router first to design, build, review, or refactor a screen, page, panel, or flow, or when rules seem to disagree or no rule applies. The router routes, and the owning skill holds the rules.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fmeta\u002Frecursica-skill-design-router\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7555RYHBH6XM48V2420Z66X","recursica-skill-undo","House rules for undo — when an action gets an undo instead of a confirmation, where the undo goes (on the page, in place, or in a toast), when a toast is needed at all, and the Undo button's accessible name. Use whenever an action can be reversed, or when choosing between an undo and a confirmation. Not for building the toast that holds an Undo button — see recursica-skill-toast. Not for the confirmation modal — see recursica-skill-buttons-links.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-rules\u002Frecursica-skill-undo\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7555K4E6TKJ9E9P7GCQYJZ8","recursica-skill-typography-semantics","House rules for type and semantic markup — real elements instead of styled divs, one H1 per page, type styles from tokens only, loading the brand typefaces, hidden headings, emphasis with em and strong, abbreviations, and AP style. Use for headings, body copy, emphasis, and the markup under a visual hierarchy. Not for naming — see recursica-skill-names-and-terms.","https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fdesign-rules\u002Frecursica-skill-typography-semantics\u002FSKILL.md",[],[]]