[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754YBTZ4K4794H7J2R4FFQA":3,"skill-same:01M754YBTZ4K4794H7J2R4FFQA":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},"01M754YBTZ4K4794H7J2R4FFQA","recursica-skill-hover-card-popover",null,"Rules for the Recursica hover card and popover — richer content beside a target, choosing a read-only hover card or a click-opened interactive popover, and the accessibility each needs. Use for preview cards, profile previews, and popovers. Not for a short label — see recursica-skill-tooltip; not for a list of actions — see recursica-skill-menu.","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-hover-card-popover\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: recursica-skill-hover-card-popover\ndescription: Rules for the Recursica hover card and popover — richer content beside a target, choosing a read-only hover card or a click-opened interactive popover, and the accessibility each needs. Use for preview cards, profile previews, and popovers. Not for a short label — see recursica-skill-tooltip; not for a list of actions — see recursica-skill-menu.\nlicense: MIT\nmetadata:\n  author: hi@borderux.com\n  version: 0.2.0\n---\n\n# Hover card and popover\n\nA hover card or a popover shows richer content in a box beside a trigger. A trigger is the element that opens the hover card or popover, such as an avatar or a link.\n\n## When to use a hover card or popover\n\n- **A preview saves the persona from opening the full content.** One example is a mini profile from an avatar or a username. Other examples are a product summary from a product name and a page preview from a link.\n- **The content is richer than a phrase.** The content runs to more than one line, holds an image, or lists a few structured details.\n- **Every piece of content in the hover card or popover is optional.** A persona who never opens the hover card or popover loses nothing.\n\n## When not to use a hover card or popover\n\n| Situation                                                        | Use instead                                                                                        |\n| ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |\n| A short text label for an icon-only control                      | A tooltip. See `recursica-skill-tooltip`.                                                          |\n| The persona needs the content to finish the task                 | The page. Put the content in view on the page.                                                     |\n| The content is a list of actions or options                      | A menu. See `recursica-skill-menu`.                                                                |\n| The persona must make a decision before continuing               | A modal. See `recursica-skill-modal`.                                                              |\n| The persona needs the content while working in the page          | A panel, or a region on the page. See `recursica-skill-panel`.                                     |\n| The content is a form, or any form control                       | A page or a modal. See `recursica-skill-forms`.                                                    |\n| The screen needs a place for a primary action                    | A button in view, outside the hover card or popover. See `recursica-skill-buttons-links`.          |\n| The hover card or popover would be the only place a value exists | The page shows the value. A hover card or popover may also show the value, as an optional preview. |\n\n**The most common hover card or popover mistake is content or a control that only a pointer can reach.** For example, a card opens on hover and holds a button, a link, or a value found nowhere else.\n\n- A persona using the keyboard cannot reach the button, link or value.\n- A persona on a touch screen cannot use the button, link or value.\n\n`recursica-skill-discoverability` forbids hiding any content or control the persona would want to reach. Hiding the content or control behind hover is the worst case.\n\n## Variants\n\n**Use only the hover card and popover variants and options that the knowledge MCP server lists for the theme (the design a designer sets in Theme Forge: the token values, the components, and each component's variants, states and sizes).** 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 name each part and option by role, such as \"the beak\". The names in the standard UI kit (the unchanged UI kit in the official Recursica release) are examples only.\n\n- **A hover card or popover has two parts:** a content area and a beak. The beak is the pointed tip that connects the hover card or popover to the trigger.\n- **If the theme has a placement option, use the placement option.** Otherwise, never set a position for the hover card or popover. Never position the beak by hand. See the open questions.\n- **Put content that does not fit inside the width limits of a hover card or popover on the page.** The theme sets a minimum width and a maximum width for a hover card or popover. If the theme has a size variant, use the size variant.\n- **If the theme has a content-type variant, use the content-type variant.** If the theme has no custom content type, confirm with the user before showing custom content. See the open questions.\n- **If the theme has a variant for the hover card or the popover, use that variant.** The house rules treat a hover card and a popover as two different components. The build's behavior decides whether the build is a hover card or a popover. The choice between a hover card and a popover sets every accessibility requirement below.\n\n|                      | **Hover card**                                         | **Popover**                                                                                               |\n| -------------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------- |\n| Opens on             | The pointer entering the trigger                       | A click or a tap, always                                                                                  |\n| May contain controls | **No**                                                 | **Yes** — buttons and links, never a form control                                                         |\n| Closes when          | The pointer leaves both the trigger and the hover card | A click outside the popover, a second click on the trigger, or Escape                                     |\n| Focus                | Never moves                                            | Moves to the first control when the popover opens, and **returns to the trigger** when the popover closes |\n| On a touch device    | Not available, because a touch screen has no hover     | The pattern that replaces a hover card                                                                    |\n\n**A popover is a non-modal dialog** (a window that leaves the page behind the window usable). A popover does not block the page, and a popover does not trap focus.\n\n## Rules\n\n**Before building, decide whether the build is a hover card or a popover, and state the choice.** Only two choices are valid. A hover card and a popover have different requirements:\n\n- **Hover card.** A hover card opens when the pointer hovers over the trigger. A hover card is a read-only preview and nothing else, such as a mini profile. A hover card contains no control. A control is a button, a link, a form control, or any other element the persona can operate. A hover card holds no content the persona needs.\n- **Popover.** A popover opens when the persona clicks a real trigger, or presses Enter or Space on the trigger. A popover may contain controls, such as buttons and links. A persona using a keyboard can use every part of a popover. Focus returns to the trigger when the popover closes.\n\nA card that opens on hover and holds a control is a failed build, not a third option.\n\n**Any control in the card makes the card a popover.** One link inside the card is enough. Build the card as a popover:\n\n- Use a real button as the trigger.\n- Make the popover open from the keyboard.\n- Move focus into the popover when the popover opens.\n- Move focus back to the trigger when the popover closes.\n\nOnly a persona using a pointer can reach a button inside a hover card.\n\n**Keep content the persona needs out of a hover card. Put required content on the page.** A hover card never holds:\n\n- the only copy of a value\n- an action\n- an explanation the persona needs to move forward\n\n**Never make a hover card or popover the only place a piece of information exists.** For example, when a hover card shows a customer's email address, the page shows the email address too. `recursica-skill-design-system-conventions` forbids meaning that depends on a single channel (color, shape, position or text, each a separate signal). A card that appears only on hover is the narrowest channel of all.\n\n**Do not put a form, a form section, or a single form control inside a hover card or popover.** The rule has no exception.\n\n**Do not wrap the content of a hover card or popover in a card.** The hover card or popover is the container. See `recursica-skill-card`.\n\n**A short delay before a hover card or popover shows stops the hover card or popover from opening by accident.** Without the delay, a pointer crossing the trigger toward another part of the screen opens the hover card or popover. See the open questions.\n\n**Closing a hover card or popover must be possible and obvious.**\n\n- A popover closes on Escape, on a click outside the popover, and on a second click of the trigger.\n- A hover card closes when the pointer leaves both the trigger and the hover card.\n\n**A hover card cannot open on a touch device, because a touch screen has no hover.** If the content matters on a touch screen, build a popover, not a hover card that also opens on tap.\n\n**Keep the primary action out of a hover card or popover.** Use one primary action per page, panel, modal, table row, or other container, in view in that container. See `recursica-skill-buttons-links`.\n\n**Choose between a tooltip and a hover card or popover by the content, not by the look.** The standard UI kit has two different components, `tooltip` and `hover-card-popover`, and the two look almost the same.\n\n- A tooltip is a short text label for a control with no visible label. For example, the tooltip on a trash-can icon button says \"Delete invoice\".\n- A hover card or popover holds richer content, such as a mini profile.\n- Neither component may hold content the persona needs to finish a task.\n- Neither component may be the only place a piece of information exists.\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\n**Name whether the build is a hover card or a popover, then meet every requirement for the named component.** No build halfway between the two is safe. A build that meets half the requirements of each leaves content that only a pointer can reach.\n\n### Screen readers\n\n- **A popover's trigger must announce that the trigger opens a popover, and whether the popover is open now.** Without the open state, pressing the trigger seems to do nothing.\n- **A popover needs an accessible name** (the name a screen reader reads out for a control). Use the popover's heading, or the name of the trigger that opened the popover. The accessible name tells a persona who lands in the popover which popover the persona is in.\n- **If a hover card's content has any meaning at all, connect the content to the trigger as a description.** A screen reader reads unconnected content beside a trigger as unrelated text, or does not read the content at all.\n- **The design must still work when a hover card's content goes unread.** A hover card's content might go unread, so a hover card may hold no content the persona needs. Put content the persona must read on the page.\n- **Every control in a popover needs a real accessible name**, exactly as on the page.\n- **Never put meaning in a hover card or popover that exists nowhere else.** `recursica-skill-design-system-conventions` requires a second channel for any meaning the persona must receive.\n- **Do not announce a hover card or popover as an alert.** The card shows content the persona asked for, and does not interrupt the persona.\n- **An image in a hover card or popover needs alternative text**, or must be marked as decorative. Otherwise, a profile preview made only of an avatar tells a persona using a screen reader nothing.\n\n### Keyboard and non-mouse navigation\n\n- **A popover must open from the keyboard.** The popover's trigger is a real button in the tab order, and Enter or Space opens the popover. If a popover opens only on hover, a persona using a keyboard cannot reach any control in the popover.\n- **Focus moves into the popover when the popover opens, and returns to the trigger when the popover closes.** Every way of closing the popover returns focus to the trigger. Ways of closing include Escape, using a control in the popover, and clicking outside the popover.\n- **Escape closes the popover**, and returns focus to the trigger.\n- **Every control in a popover is a tab stop (a place the Tab key lands), in visual order.** No control may sit in a card that only a pointer can reach.\n- **Do not trap focus.** A popover does not block the page. A modal blocks the page, and a modal is the only component that traps focus. See `recursica-skill-modal`.\n- **A hover card must contain no tab stops at all.** A hover card has none of the popover focus behavior above. Put content that needs a tab stop in a popover.\n- **If the trigger can receive focus, a hover card must also appear when the trigger receives keyboard focus.** For example, tabbing to a username link opens the username's hover card. The hover card must close with Escape without moving focus.\n- **A hover card must stay open while the pointer moves from the trigger into the hover card.** A persona cannot read a hover card that disappears in the gap between the trigger and the hover card. A persona with unsteady pointer control can never read the hover card.\n- **A hover card never takes focus.** Hovering never moves the persona's focus.\n- **No content, control or action the persona needs may appear only on hover.** The whole hover card or popover component depends on this one rule.\n\n## Styling set by tokens\n\n**Never set or override the hover card or popover's styling.** The theme sets every visual property of the hover card or popover, such as size, spacing, borders, colors and animation. Do not add extra containers or spacers to change the hover card or popover's look. If the theme does not give a look the design needs, report the missing look as a design-system gap. See `recursica-skill-design-router`.\n\n**The beak is part of the hover card or popover.** Do not draw a separate beak, and do not move the beak on the hover card or popover.\n\n## Related skills\n\n- `recursica-skill-discoverability` — progressive disclosure, and the three cases where hiding content is not safe. `recursica-skill-discoverability` also says progressive disclosure never justifies a dark pattern.\n- `recursica-skill-design-system-conventions` — never show meaning in a single channel, and a hidden affordance must stay reachable by keyboard and by assistive technology.\n\n### Only if used on the same screen\n\n- `recursica-skill-tooltip` — the tooltip, for a short text label on a control with no visible label. `recursica-skill-tooltip` also explains why a tooltip and a hover card or popover are not interchangeable. The two components look almost the same.\n- `recursica-skill-menu` — where a list of actions or options goes, and the menu's rules for returning focus.\n- `recursica-skill-panel` — the panel, for content the persona needs while working in the page.\n\n## Open questions\n\n- **Placement.** The design-system website shows four positions (top, left, right and bottom) and three beak alignments (start, middle and end). Do not rely on a position or a beak alignment without confirming with the user. Confirm a position or a beak alignment with the user only when the theme has no placement option. With or without a placement option, no rule covers what happens at the edge of the viewport.\n- **Delays and the grace period.** No rule sets the delay before showing or the delay before hiding. No rule sets the grace period while the pointer crosses from the trigger to the card.\n- **Custom content.** The design-system website shows two content types, text and custom. Do not rely on custom content without confirming with the user. Confirm with the user only when the theme has no custom content type.\n- **Behavior on touch.** A touch screen has no hover, and no rule sets a different pattern for touch.\n- **Whether a popover may open from inside a menu, a modal, or another popover.** `recursica-skill-modal` forbids stacking modals, but no rule covers a popover.\n\n## Pre-flight checklist\n\n- [ ] The build is named as either a hover card or a popover.\n- [ ] The content is richer than a phrase, and every short label uses `recursica-skill-tooltip` instead.\n- [ ] No content in the hover card or popover is needed to finish a task.\n- [ ] No content exists only in the hover card or popover.\n- [ ] No form, form control, primary action, or list of actions is in the hover card or popover.\n- [ ] No card wraps the content.\n- [ ] **Hover card:** the hover card holds no control and no tab stops, and never takes focus.\n- [ ] **Hover card:** the hover card appears when a trigger that can take focus receives focus, and closes with Escape.\n- [ ] **Hover card:** the hover card stays open as the pointer crosses the gap between the trigger and the hover card.\n- [ ] **Popover:** the trigger is a real button in the tab order, and Enter or Space opens the popover.\n- [ ] **Popover:** the trigger announces what the trigger opens and whether the popover is open.\n- [ ] **Popover:** the popover has an accessible name.\n- [ ] **Popover:** focus moves into the popover on opening, and returns to the trigger on every way of closing.\n- [ ] **Popover:** Escape closes the popover, and focus is not trapped.\n- [ ] Every control in a popover is a tab stop, in visual order, with a real accessible name.\n- [ ] Any hover card content that has any meaning at all is connected to the trigger as a description.\n- [ ] The hover card is acceptable to leave unread.\n- [ ] Every image in a hover card or popover has alternative text, or is marked as decorative.\n- [ ] No content, control or action the persona needs appears only on hover, and the focus ring is intact everywhere.\n- [ ] Every variant and option is one the knowledge MCP server lists for the theme.\n- [ ] No placement, size, or content variant is invented.\n- [ ] No styling is set or overridden on the hover card or popover.\n- [ ] No container or spacer is added to change the hover card or popover's look.\n- [ ] Open questions were asked about, not decided: placement, the show and hide delays and the grace period, custom content, behavior on touch, and a popover opened from a menu, a modal, or another popover.\n","# Hover card and popover\n\nA hover card or a popover shows richer content in a box beside a trigger. A trigger is the element that opens the hover card or popover, such as an avatar or a link.\n\n## When to use a hover card or popover\n\n- **A preview saves the persona from opening the full content.** One example is a mini profile from an avatar or a username. Other examples are a product summary from a product name and a page preview from a link.\n- **The content is richer than a phrase.** The content runs to more than one line, holds an image, or lists a few structured details.\n- **Every piece of content in the hover card or popover is optional.** A persona who never opens the hover card or popover loses nothing.\n\n## When not to use a hover card or popover\n\n| Situation                                                        | Use instead                                                                                        |\n| ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |\n| A short text label for an icon-only control                      | A tooltip. See `recursica-skill-tooltip`.                                                          |\n| The persona needs the content to finish the task                 | The page. Put the content in view on the page.                                                     |\n| The content is a list of actions or options                      | A menu. See `recursica-skill-menu`.                                                                |\n| The persona must make a decision before continuing               | A modal. See `recursica-skill-modal`.                                                              |\n| The persona needs the content while working in the page          | A panel, or a region on the page. See `recursica-skill-panel`.                                     |\n| The content is a form, or any form control                       | A page or a modal. See `recursica-skill-forms`.                                                    |\n| The screen needs a place for a primary action                    | A button in view, outside the hover card or popover. See `recursica-skill-buttons-links`.          |\n| The hover card or popover would be the only place a value exists | The page shows the value. A hover card or popover may also show the value, as an optional preview. |\n\n**The most common hover card or popover mistake is content or a control that only a pointer can reach.** For example, a card opens on hover and holds a button, a link, or a value found nowhere else.\n\n- A persona using the keyboard cannot reach the button, link or value.\n- A persona on a touch screen cannot use the button, link or value.\n\n`recursica-skill-discoverability` forbids hiding any content or control the persona would want to reach. Hiding the content or control behind hover is the worst case.\n\n## Variants\n\n**Use only the hover card and popover variants and options that the knowledge MCP server lists for the theme (the design a designer sets in Theme Forge: the token values, the components, and each component's variants, states and sizes).** 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 name each part and option by role, such as \"the beak\". The names in the standard UI kit (the unchanged UI kit in the official Recursica release) are examples only.\n\n- **A hover card or popover has two parts:** a content area and a beak. The beak is the pointed tip that connects the hover card or popover to the trigger.\n- **If the theme has a placement option, use the placement option.** Otherwise, never set a position for the hover card or popover. Never position the beak by hand. See the open questions.\n- **Put content that does not fit inside the width limits of a hover card or popover on the page.** The theme sets a minimum width and a maximum width for a hover card or popover. If the theme has a size variant, use the size variant.\n- **If the theme has a content-type variant, use the content-type variant.** If the theme has no custom content type, confirm with the user before showing custom content. See the open questions.\n- **If the theme has a variant for the hover card or the popover, use that variant.** The house rules treat a hover card and a popover as two different components. The build's behavior decides whether the build is a hover card or a popover. The choice between a hover card and a popover sets every accessibility requirement below.\n\n|                      | **Hover card**                                         | **Popover**                                                                                               |\n| -------------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------- |\n| Opens on             | The pointer entering the trigger                       | A click or a tap, always                                                                                  |\n| May contain controls | **No**                                                 | **Yes** — buttons and links, never a form control                                                         |\n| Closes when          | The pointer leaves both the trigger and the hover card | A click outside the popover, a second click on the trigger, or Escape                                     |\n| Focus                | Never moves                                            | Moves to the first control when the popover opens, and **returns to the trigger** when the popover closes |\n| On a touch device    | Not available, because a touch screen has no hover     | The pattern that replaces a hover card                                                                    |\n\n**A popover is a non-modal dialog** (a window that leaves the page behind the window usable). A popover does not block the page, and a popover does not trap focus.\n\n## Rules\n\n**Before building, decide whether the build is a hover card or a popover, and state the choice.** Only two choices are valid. A hover card and a popover have different requirements:\n\n- **Hover card.** A hover card opens when the pointer hovers over the trigger. A hover card is a read-only preview and nothing else, such as a mini profile. A hover card contains no control. A control is a button, a link, a form control, or any other element the persona can operate. A hover card holds no content the persona needs.\n- **Popover.** A popover opens when the persona clicks a real trigger, or presses Enter or Space on the trigger. A popover may contain controls, such as buttons and links. A persona using a keyboard can use every part of a popover. Focus returns to the trigger when the popover closes.\n\nA card that opens on hover and holds a control is a failed build, not a third option.\n\n**Any control in the card makes the card a popover.** One link inside the card is enough. Build the card as a popover:\n\n- Use a real button as the trigger.\n- Make the popover open from the keyboard.\n- Move focus into the popover when the popover opens.\n- Move focus back to the trigger when the popover closes.\n\nOnly a persona using a pointer can reach a button inside a hover card.\n\n**Keep content the persona needs out of a hover card. Put required content on the page.** A hover card never holds:\n\n- the only copy of a value\n- an action\n- an explanation the persona needs to move forward\n\n**Never make a hover card or popover the only place a piece of information exists.** For example, when a hover card shows a customer's email address, the page shows the email address too. `recursica-skill-design-system-conventions` forbids meaning that depends on a single channel (color, shape, position or text, each a separate signal). A card that appears only on hover is the narrowest channel of all.\n\n**Do not put a form, a form section, or a single form control inside a hover card or popover.** The rule has no exception.\n\n**Do not wrap the content of a hover card or popover in a card.** The hover card or popover is the container. See `recursica-skill-card`.\n\n**A short delay before a hover card or popover shows stops the hover card or popover from opening by accident.** Without the delay, a pointer crossing the trigger toward another part of the screen opens the hover card or popover. See the open questions.\n\n**Closing a hover card or popover must be possible and obvious.**\n\n- A popover closes on Escape, on a click outside the popover, and on a second click of the trigger.\n- A hover card closes when the pointer leaves both the trigger and the hover card.\n\n**A hover card cannot open on a touch device, because a touch screen has no hover.** If the content matters on a touch screen, build a popover, not a hover card that also opens on tap.\n\n**Keep the primary action out of a hover card or popover.** Use one primary action per page, panel, modal, table row, or other container, in view in that container. See `recursica-skill-buttons-links`.\n\n**Choose between a tooltip and a hover card or popover by the content, not by the look.** The standard UI kit has two different components, `tooltip` and `hover-card-popover`, and the two look almost the same.\n\n- A tooltip is a short text label for a control with no visible label. For example, the tooltip on a trash-can icon button says \"Delete invoice\".\n- A hover card or popover holds richer content, such as a mini profile.\n- Neither component may hold content the persona needs to finish a task.\n- Neither component may be the only place a piece of information exists.\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\n**Name whether the build is a hover card or a popover, then meet every requirement for the named component.** No build halfway between the two is safe. A build that meets half the requirements of each leaves content that only a pointer can reach.\n\n### Screen readers\n\n- **A popover's trigger must announce that the trigger opens a popover, and whether the popover is open now.** Without the open state, pressing the trigger seems to do nothing.\n- **A popover needs an accessible name** (the name a screen reader reads out for a control). Use the popover's heading, or the name of the trigger that opened the popover. The accessible name tells a persona who lands in the popover which popover the persona is in.\n- **If a hover card's content has any meaning at all, connect the content to the trigger as a description.** A screen reader reads unconnected content beside a trigger as unrelated text, or does not read the content at all.\n- **The design must still work when a hover card's content goes unread.** A hover card's content might go unread, so a hover card may hold no content the persona needs. Put content the persona must read on the page.\n- **Every control in a popover needs a real accessible name**, exactly as on the page.\n- **Never put meaning in a hover card or popover that exists nowhere else.** `recursica-skill-design-system-conventions` requires a second channel for any meaning the persona must receive.\n- **Do not announce a hover card or popover as an alert.** The card shows content the persona asked for, and does not interrupt the persona.\n- **An image in a hover card or popover needs alternative text**, or must be marked as decorative. Otherwise, a profile preview made only of an avatar tells a persona using a screen reader nothing.\n\n### Keyboard and non-mouse navigation\n\n- **A popover must open from the keyboard.** The popover's trigger is a real button in the tab order, and Enter or Space opens the popover. If a popover opens only on hover, a persona using a keyboard cannot reach any control in the popover.\n- **Focus moves into the popover when the popover opens, and returns to the trigger when the popover closes.** Every way of closing the popover returns focus to the trigger. Ways of closing include Escape, using a control in the popover, and clicking outside the popover.\n- **Escape closes the popover**, and returns focus to the trigger.\n- **Every control in a popover is a tab stop (a place the Tab key lands), in visual order.** No control may sit in a card that only a pointer can reach.\n- **Do not trap focus.** A popover does not block the page. A modal blocks the page, and a modal is the only component that traps focus. See `recursica-skill-modal`.\n- **A hover card must contain no tab stops at all.** A hover card has none of the popover focus behavior above. Put content that needs a tab stop in a popover.\n- **If the trigger can receive focus, a hover card must also appear when the trigger receives keyboard focus.** For example, tabbing to a username link opens the username's hover card. The hover card must close with Escape without moving focus.\n- **A hover card must stay open while the pointer moves from the trigger into the hover card.** A persona cannot read a hover card that disappears in the gap between the trigger and the hover card. A persona with unsteady pointer control can never read the hover card.\n- **A hover card never takes focus.** Hovering never moves the persona's focus.\n- **No content, control or action the persona needs may appear only on hover.** The whole hover card or popover component depends on this one rule.\n\n## Styling set by tokens\n\n**Never set or override the hover card or popover's styling.** The theme sets every visual property of the hover card or popover, such as size, spacing, borders, colors and animation. Do not add extra containers or spacers to change the hover card or popover's look. If the theme does not give a look the design needs, report the missing look as a design-system gap. See `recursica-skill-design-router`.\n\n**The beak is part of the hover card or popover.** Do not draw a separate beak, and do not move the beak on the hover card or popover.\n\n## Related skills\n\n- `recursica-skill-discoverability` — progressive disclosure, and the three cases where hiding content is not safe. `recursica-skill-discoverability` also says progressive disclosure never justifies a dark pattern.\n- `recursica-skill-design-system-conventions` — never show meaning in a single channel, and a hidden affordance must stay reachable by keyboard and by assistive technology.\n\n### Only if used on the same screen\n\n- `recursica-skill-tooltip` — the tooltip, for a short text label on a control with no visible label. `recursica-skill-tooltip` also explains why a tooltip and a hover card or popover are not interchangeable. The two components look almost the same.\n- `recursica-skill-menu` — where a list of actions or options goes, and the menu's rules for returning focus.\n- `recursica-skill-panel` — the panel, for content the persona needs while working in the page.\n\n## Open questions\n\n- **Placement.** The design-system website shows four positions (top, left, right and bottom) and three beak alignments (start, middle and end). Do not rely on a position or a beak alignment without confirming with the user. Confirm a position or a beak alignment with the user only when the theme has no placement option. With or without a placement option, no rule covers what happens at the edge of the viewport.\n- **Delays and the grace period.** No rule sets the delay before showing or the delay before hiding. No rule sets the grace period while the pointer crosses from the trigger to the card.\n- **Custom content.** The design-system website shows two content types, text and custom. Do not rely on custom content without confirming with the user. Confirm with the user only when the theme has no custom content type.\n- **Behavior on touch.** A touch screen has no hover, and no rule sets a different pattern for touch.\n- **Whether a popover may open from inside a menu, a modal, or another popover.** `recursica-skill-modal` forbids stacking modals, but no rule covers a popover.\n\n## Pre-flight checklist\n\n- [ ] The build is named as either a hover card or a popover.\n- [ ] The content is richer than a phrase, and every short label uses `recursica-skill-tooltip` instead.\n- [ ] No content in the hover card or popover is needed to finish a task.\n- [ ] No content exists only in the hover card or popover.\n- [ ] No form, form control, primary action, or list of actions is in the hover card or popover.\n- [ ] No card wraps the content.\n- [ ] **Hover card:** the hover card holds no control and no tab stops, and never takes focus.\n- [ ] **Hover card:** the hover card appears when a trigger that can take focus receives focus, and closes with Escape.\n- [ ] **Hover card:** the hover card stays open as the pointer crosses the gap between the trigger and the hover card.\n- [ ] **Popover:** the trigger is a real button in the tab order, and Enter or Space opens the popover.\n- [ ] **Popover:** the trigger announces what the trigger opens and whether the popover is open.\n- [ ] **Popover:** the popover has an accessible name.\n- [ ] **Popover:** focus moves into the popover on opening, and returns to the trigger on every way of closing.\n- [ ] **Popover:** Escape closes the popover, and focus is not trapped.\n- [ ] Every control in a popover is a tab stop, in visual order, with a real accessible name.\n- [ ] Any hover card content that has any meaning at all is connected to the trigger as a description.\n- [ ] The hover card is acceptable to leave unread.\n- [ ] Every image in a hover card or popover has alternative text, or is marked as decorative.\n- [ ] No content, control or action the persona needs appears only on hover, and the focus ring is intact everywhere.\n- [ ] Every variant and option is one the knowledge MCP server lists for the theme.\n- [ ] No placement, size, or content variant is invented.\n- [ ] No styling is set or overridden on the hover card or popover.\n- [ ] No container or spacer is added to change the hover card or popover's look.\n- [ ] Open questions were asked about, not decided: placement, the show and hide delays and the grace period, custom content, behavior on touch, and a popover opened from a menu, a modal, or another popover.\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-hover-card-popover",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-hover-card-popover",{"tool":41,"command":42},"bunx","bunx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-hover-card-popover",{"tool":44,"command":45},"pnpm","pnpm dlx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-hover-card-popover","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fcomponents\u002Frecursica-skill-hover-card-popover\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",[],[]]