[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754ZHXJSN36P8GZVRZV5TTY":3,"skill-same:01M754ZHXJSN36P8GZVRZV5TTY":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},"01M754ZHXJSN36P8GZVRZV5TTY","recursica-skill-panel",null,"Rules for the Recursica panel — when to use a panel beside the page that leaves the page usable, why opening a panel adds no browser history entry, the header, content and footer, and returning focus with no focus trap. Use for panels, drawers, side sheets, and filter panels. Not for blocking decisions — see recursica-skill-modal.","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-panel\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: recursica-skill-panel\ndescription: Rules for the Recursica panel — when to use a panel beside the page that leaves the page usable, why opening a panel adds no browser history entry, the header, content and footer, and returning focus with no focus trap. Use for panels, drawers, side sheets, and filter panels. Not for blocking decisions — see recursica-skill-modal.\nlicense: MIT\nmetadata:\n  author: hi@borderux.com\n  version: 0.2.0\n---\n\n# Panel\n\nA panel shows extra content beside the page. The persona can still use the page while the panel is open.\n\n## When to use a panel\n\n- **The persona needs the page underneath the panel while working in the panel.** Examples are filters, settings, a details view, or editing one item shown on screen. A modal cannot serve this case, because a modal blocks the page.\n- **Secondary settings or details would clutter the main view, but must not cover the main view.**\n- **The content belongs to the current view**, not to a different page or location in the application.\n\n## When not to use a panel\n\n| Situation                                                            | Use instead                                                                                      |\n| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |\n| The task must be finished or given up before the persona continues   | `recursica-skill-modal`                                                                          |\n| The action cannot be undone, and needs a confirmation                | `recursica-skill-modal`                                                                          |\n| Confirming that an action succeeded, or offering undo                | `recursica-skill-toast`                                                                          |\n| A brief alert, or a simple acknowledgment                            | `recursica-skill-toast`                                                                          |\n| The content is a long form, a form with several parts, or a big form | A page, with `recursica-skill-stepper` when the form has several parts                           |\n| The feature is critical, and the persona must find the feature       | The page itself. The panel content does not exist until the persona opens the panel.             |\n| Primary or secondary navigation for the application                  | The application's navigation. `recursica-skill-navigation` sets the rules for hiding navigation. |\n| Separating repeated items of one type, or wrapping a form in a box   | Nothing. A panel is not a card, and a panel never contains a card. See `recursica-skill-card`.   |\n\n**Do not hide critical content in a panel.** A panel saves space on the page, but the persona sees the panel content only after opening the panel. Filters suit a panel. Content the persona must act on to finish the work does not suit a panel.\n\n## Variants\n\n**Use only the panel 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 describe each part and option by role. The names in the standard UI kit (the unchanged UI kit in the official Recursica release) are examples only.\n\n- **A panel has a header with a close control, a content area, and a footer with buttons.** The standard UI kit also defines a divider.\n- **A panel has the same header, content area, footer, and close control as a modal.** The only difference is that the page behind a panel stays usable. The accessibility rules below follow from that difference.\n- **If the theme has a side variant, use the side variant.** Otherwise, the agent or the user chooses the left or right side for each panel, as described below.\n- **If the theme has a size or width variant, use that variant.** Otherwise, do not set a width or a size on the panel.\n\n## Rules\n\n**Open a panel with a button.** Opening a panel adds no entry to the browser history. The persona does not navigate to a panel.\n\n**Give the panel an address whenever possible.** The address opens the page with the panel already open, and keeps the panel open after a refresh. Changing the address adds no history entry. See `recursica-skill-navigation`.\n\n**Write a panel header that says what the panel is for.** Name the object or the task in the header, not \"Panel\" or \"Details\". For example, write \"Filter orders\" or \"Edit shipping address\". The header is the panel's accessible name (the name a screen reader reads out for a control).\n\n**Never wrap the panel content in a card.** Never put a form, a form section, or a single form control in a card either. The edges of the panel separate the panel content from the page. See `recursica-skill-card`.\n\n**In a form in a panel, put every label above the label's field.** A panel is a narrow container. `recursica-skill-forms` sets the test: the width of the container decides when labels stack, not the width of the viewport. The other form rules still apply in a panel:\n\n- a single column\n- one field per row of the form\n\n**Label placement is one decision for the whole form, never for each field.** `recursica-skill-forms` allows labels side by side or stacked, but never both at the same breakpoint. Apply the container-width test once, to the whole form. The result of the test sets the label placement of every field in the form. A panel is exactly the kind of narrow container that makes labels stack. Every field in a form in a panel stacks, not only the fields that look cramped. A short field that would fit beside the field's label stacks too. `recursica-skill-forms` sets this rule.\n\n**Use the application's save mode in a panel, never a separate save mode.** The two save modes differ in save status:\n\n- Saving field by field needs a save status that stays on the page.\n- Saving the whole form at once shows no save status and no sign of unsaved changes.\n\nSee `recursica-skill-forms`.\n\n**Put one primary action at the bottom right of the panel footer.** Put a true alternative directly to the left of the primary action. For example, \"Save\" sits at the bottom right, and \"Cancel\" sits directly to the left of \"Save\". `recursica-skill-buttons-links` sets this rule.\n\n**Closing a panel must be possible and obvious.** The close control in the header closes the panel, and so does the Escape key. Do not build a panel that the persona can leave only by finishing the task in the panel.\n\n**Build a page, not a panel, for a task that needs a stepper or that scrolls a long way.** Give each of the following tasks a separate page with a separate route:\n\n- a process with several steps\n- a task with a lot of data entry\n\n**Do not add a toast when a panel changes the page behind the panel.** The change on the page is the feedback. For example, when filters in a panel narrow a table on the page, the narrower table is the feedback.\n\n**Place a panel flush against the left or right edge of the viewport, at full height.** `recursica-skill-panels-modals` sets the placement rules:\n\n- The panel runs the full height of the viewport, from top to bottom.\n- A panel is never set in from the edge, never floating, and never less than full height.\n- Left and right are both standard sides. The agent or the user chooses the side for each panel.\n- Never open panels on both sides at once.\n- Panels stacked on top of each other all use the same side. Stacked panels may differ in width.\n- A panel on the top or bottom edge is allowed but extremely unusual. The design system has no design for a top or bottom panel. Confirm a top or bottom panel with the user before building one.\n\n**A panel MUST NEVER scroll horizontally.** The rule has no exception. When content needs a horizontal scrollbar, the content does not belong in a panel.\n\n**A panel that scrolls up and down is the sign to move the task to a page.** On the new page, repeat the context the task needed. For example, a page for editing an order repeats which order the persona is editing.\n\n**A panel may open a modal.** A panel does not block the page, so a panel is not a mode. A modal opened from a panel therefore does not stack one mode on another mode. A confirmation for unsaved changes is a modal that the panel opens when the panel closes.\n\n**A panel may be stacked on top of another panel, but stacking is not ideal.**\n\n- The second panel covers the first panel completely.\n- Closing the second panel shows the first panel again.\n- Never nest a panel inside another panel.\n- Any number of panels may stack, with no hard limit. Confirm with the user before stacking more than two panels.\n\n**Close a panel when the route changes.** The exception is a route change that exists only to open another panel or a modal.\n\n**Below the tablet breakpoint, open the panel content as a page instead.** Do not use a narrower panel, or a full-screen overlay styled as a panel. At the tablet breakpoint and above, the panel stays a panel.\n\n**NEVER draw a shader, scrim, or tint behind an open panel.** The rule has no exceptions. A panel sits beside the page so the persona can read and use the page. A scrim dims the page. `recursica-skill-panels-modals` sets this rule. The four settings below keep this rule when an adapter draws an overlay by default.\n\n**Until the adapter's defaults are fixed, turn off four modal defaults explicitly.** An adapter (the Recursica component library for one framework, such as Mantine or Angular Material) may make a panel modal by default. An adapter can build the panel on a drawer from a code library. Most drawers from code libraries turn on four modal defaults:\n\n- the overlay\n- closing on a click outside the panel\n- the focus trap\n- the scroll lock\n\nThe house rule is that a panel leaves the page usable, and a modal panel does the opposite. A panel built on such a drawer with only the adapter's documented settings blocks the page. Nobody notices the blocked page.\n\nLook up the name the code uses for each of the four settings with the knowledge MCP server's `component_api` tool. A build test on one adapter confirmed that all four settings are needed. The modal default is a tracked defect in the adapter. Before assuming the four settings are still needed, check the adapter's current default. When the adapter's default is fixed, delete the four settings.\n\n**A code library's default is not a house rule.** A drawer that blocks the page by default says nothing about what a Recursica panel should do. Never treat the drawer's modal default as a house rule. See `recursica-skill-design-router`.\n\n**A panel is non-modal (the page behind stays usable), and the purpose of a panel is to leave the page usable.** The persona can still move around the application and act on the page behind the panel. `recursica-skill-panels-modals` sets this rule directly. A panel built to block the page is a modal built with the wrong component.\n\n**NEVER put a table inside a panel.** A panel is narrow, and a table needs width. A table in a panel either scrolls horizontally, which is forbidden outright, or truncates every column. Instead, follow two rules:\n\n- Show repeated content as groups of stacked fields.\n- Put secondary material in a second tab, not below the main content.\n\n`recursica-skill-panels-modals` sets this rule.\n\n**When a panel holds unsaved form data, closing the panel asks the persona before throwing the data away.** For example, a persona types a note and presses Escape, and the panel asks before discarding the note. Leaving a page with unsaved changes asks the same way. Do not ask on every close. Ask only about data the persona entered and never saved.\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**A panel is never modal, so build every part of a panel as non-modal.** Almost every accessibility failure in a panel comes from a panel built partly as a modal. Such a panel looks as if the page stays usable. But the panel traps focus like a dialog, or hides the page from assistive technology while the page stays clickable. The page behind a panel stays usable, readable, and reachable.\n\n### Screen readers\n\n- **Connect the panel header to the panel as the panel's accessible name.** A panel with no accessible name is announced as a region with no name. \"Panel\" is not a name.\n- **Give the panel the role of a named region, not the role of a modal dialog.** The persona can browse into and out of a named region. Build a modal instead when the whole page behind the panel must be inert (impossible to reach or read). See `recursica-skill-modal`.\n- **Never mark a panel as modal while the page behind the panel stays usable.** Assistive technology stays inside a modal dialog. A persona using a mouse can still use the page behind the panel. A persona using a screen reader cannot reach the page.\n- **Do not hide the page behind a non-modal panel from assistive technology.** The page behind the panel is not inert. A persona using a screen reader must be able to read the page and get back into the panel.\n- **Place the panel content in the document where the panel appears on screen, not at the end of the document.** The reading order follows the visual order.\n- **Every persona using the panel must be able to tell that the panel opened.** Moving focus into the panel shows that the panel opened. Do not rely on a slide-in animation to show that the panel opened.\n- **Give the close control a real accessible name**, such as \"Close filters\". An icon with no label is announced as nothing.\n- **Announce every change the panel makes outside the panel.** Redrawing the page is not enough. When a filter cuts a table down to four rows, announce the result. A persona using a screen reader inside the panel cannot see the change on the page.\n\n### Keyboard and non-mouse navigation\n\n- **Move focus into the panel when the panel opens.** Put focus on the first meaningful element: the first field, or the panel container. Put focus on the close button only when no other element can take focus. Never leave focus on the element that opened the panel.\n- **Return focus to the element that opened the panel when the panel closes.** Teams skip returning focus more often than any other step. Without returned focus, the persona lands at the top of the document.\n- **Escape closes the panel**, and closing the panel never saves.\n- **Never trap focus in a panel.** The persona can still reach the page behind the panel.\n  - Pressing Tab on the last control in the panel must move focus on into the page, in document order.\n  - Pressing Shift-Tab must move focus back into the panel.\n  - A panel that traps focus while the page stays usable lets a persona using a mouse leave the panel. A persona using a keyboard cannot leave the panel.\n- **Make the tab order inside the panel follow the visual order.** The order is the content, then the footer buttons, then the close control in the place the close control appears. The tab order must not jump between the panel and the page unpredictably.\n- **Never make a pointer, such as a mouse, the only way to close the panel.** Escape and the close control both close the panel, no matter what a click outside the panel does.\n\n## Styling set by tokens\n\n**Never set or override the panel's styling.** The theme sets every visual property of the panel, such as size, spacing, borders, colors and animation. Do not add extra containers or spacers to change the panel'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-panels-modals` — the design-rules skill that sets the panel rules:\n  - choosing a panel, a modal, or a page\n  - the context test\n  - the scrolling threshold\n  - the ban on stacking modes\n  - forms in a panel\n  - protecting unsaved changes\n  - the difference in focus trapping\n- `recursica-skill-navigation` — routes and addresses. A panel gets an address whenever possible, but no browser history entry.\n- `recursica-skill-forms` — the form rules:\n  - one label placement per form, and the container-width test behind the rule\n  - single-column layout\n  - validation\n  - the save mode for any form in the panel\n- `recursica-skill-buttons-links` — the button rules:\n  - the button that opens the panel\n  - one primary action per region that holds content, such as a page, panel, or modal\n  - the placement of footer buttons\n- `recursica-skill-design-system-conventions` — the accessibility baseline every component follows.\n\n### Only if used on the same screen\n\n- `recursica-skill-modal` — the blocking alternative, and the rules on focus trapping and an inert page that a modal follows.\n- `recursica-skill-card` — why no card wraps the panel content, and why no form goes in a card.\n- `recursica-skill-toast` — short confirmations and undo, which never belong in a panel.\n\n## Open questions\n\n- **Opening transition.** The side of the panel is set, and how the panel attaches to the edge is settled. No rule says whether the panel slides in or expands when the panel opens.\n- **Panel width.** Stacked panels may differ in width from each other. No rule says whether a left panel and a right panel share a width. Confirm a wide panel with the user only when the theme has no size variant.\n- **Top or bottom panel design.** A top or bottom panel is allowed but has no design. Confirm a top or bottom panel with the user before building one, because no rule covers the design.\n- **Divider visibility.** No rule says when the divider appears. Only the design-system website shows the \"Standard\" and \"Scrollable\" divider types. Confirm with the user before relying on either divider type, but only when the theme has no type variant.\n- **Loading state.** Confirm with the user how to show a panel whose content is still loading. Confirm only when the theme has no loading state.\n\n## Pre-flight checklist\n\n- [ ] The page underneath the panel is needed while the panel is open. No critical content is hidden in the panel.\n- [ ] Every task that must be finished or given up first is in a modal. Brief feedback is in a toast.\n- [ ] Every variant and option on the panel is one the knowledge MCP server lists for the theme. No side, width, size, or type variant is set unless the theme has that variant. No variant or option is invented.\n- [ ] A button opens the panel, with no browser history entry. The panel has an address whenever possible.\n- [ ] The header names the panel's purpose and is connected as the panel's accessible name.\n- [ ] No card wraps the panel content, and no form, form section, or form control sits inside a card.\n- [ ] Every form in the panel stacks the labels, uses a single column, and follows the application's one save mode.\n- [ ] Label placement is one decision for the whole form. Every field in the form stacks, with no mix of stacked and side-by-side labels at one breakpoint.\n- [ ] The panel footer has one primary action at the bottom right. The alternative sits directly to the left of the primary action.\n- [ ] The panel is non-modal: the panel traps no focus. The page behind the panel stays usable and reachable by assistive technology.\n- [ ] Focus moves into the panel when the panel opens. Focus returns to the element that opened the panel when the panel closes.\n- [ ] Escape closes the panel without saving, and closing the panel is never pointer-only.\n- [ ] Focus is not trapped, and the page behind the panel is not made inert.\n- [ ] The page behind a non-modal panel stays readable and reachable by assistive technology.\n- [ ] The tab order follows the visual order and does not jump unpredictably between the panel and the page.\n- [ ] The close control has a real accessible name, and the focus ring is intact. No control or content the persona needs appears only on hover.\n- [ ] Changes the panel makes to the page are announced, not only redrawn.\n- [ ] No styling is set or overridden on the panel. No container or spacer is added to change the panel's look.\n- [ ] The panel is non-modal: focus is not trapped, and the page behind the panel stays reachable by keyboard. The behavior was checked in the running application, not assumed from the settings in the code.\n- [ ] No panel is nested inside another panel. Each stacked panel covers the first panel completely and uses the same side as the first panel.\n- [ ] The panel sits flush against the left or right edge and runs full height. Panels are open on only one side.\n- [ ] Nothing scrolls horizontally. Content that made the panel scroll up and down is on a page instead. The page repeats the context the content needed.\n- [ ] The panel closes on a route change, unless the navigation only opens another panel or a modal.\n- [ ] Below the tablet breakpoint, the panel opens as a page. More than two stacked panels, and any top or bottom panel, were confirmed with the user before being built.\n- [ ] Every form in the panel uses stacked label placement for every field. No table is inside the panel, and secondary material is in a separate tab.\n- [ ] Closing a panel with unsaved form data asks first. Closing a panel the persona has not changed does not ask.\n- [ ] Open questions were asked about, not decided: the opening transition, panel width, top or bottom panel design, divider visibility, and a loading state.\n","# Panel\n\nA panel shows extra content beside the page. The persona can still use the page while the panel is open.\n\n## When to use a panel\n\n- **The persona needs the page underneath the panel while working in the panel.** Examples are filters, settings, a details view, or editing one item shown on screen. A modal cannot serve this case, because a modal blocks the page.\n- **Secondary settings or details would clutter the main view, but must not cover the main view.**\n- **The content belongs to the current view**, not to a different page or location in the application.\n\n## When not to use a panel\n\n| Situation                                                            | Use instead                                                                                      |\n| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |\n| The task must be finished or given up before the persona continues   | `recursica-skill-modal`                                                                          |\n| The action cannot be undone, and needs a confirmation                | `recursica-skill-modal`                                                                          |\n| Confirming that an action succeeded, or offering undo                | `recursica-skill-toast`                                                                          |\n| A brief alert, or a simple acknowledgment                            | `recursica-skill-toast`                                                                          |\n| The content is a long form, a form with several parts, or a big form | A page, with `recursica-skill-stepper` when the form has several parts                           |\n| The feature is critical, and the persona must find the feature       | The page itself. The panel content does not exist until the persona opens the panel.             |\n| Primary or secondary navigation for the application                  | The application's navigation. `recursica-skill-navigation` sets the rules for hiding navigation. |\n| Separating repeated items of one type, or wrapping a form in a box   | Nothing. A panel is not a card, and a panel never contains a card. See `recursica-skill-card`.   |\n\n**Do not hide critical content in a panel.** A panel saves space on the page, but the persona sees the panel content only after opening the panel. Filters suit a panel. Content the persona must act on to finish the work does not suit a panel.\n\n## Variants\n\n**Use only the panel 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 describe each part and option by role. The names in the standard UI kit (the unchanged UI kit in the official Recursica release) are examples only.\n\n- **A panel has a header with a close control, a content area, and a footer with buttons.** The standard UI kit also defines a divider.\n- **A panel has the same header, content area, footer, and close control as a modal.** The only difference is that the page behind a panel stays usable. The accessibility rules below follow from that difference.\n- **If the theme has a side variant, use the side variant.** Otherwise, the agent or the user chooses the left or right side for each panel, as described below.\n- **If the theme has a size or width variant, use that variant.** Otherwise, do not set a width or a size on the panel.\n\n## Rules\n\n**Open a panel with a button.** Opening a panel adds no entry to the browser history. The persona does not navigate to a panel.\n\n**Give the panel an address whenever possible.** The address opens the page with the panel already open, and keeps the panel open after a refresh. Changing the address adds no history entry. See `recursica-skill-navigation`.\n\n**Write a panel header that says what the panel is for.** Name the object or the task in the header, not \"Panel\" or \"Details\". For example, write \"Filter orders\" or \"Edit shipping address\". The header is the panel's accessible name (the name a screen reader reads out for a control).\n\n**Never wrap the panel content in a card.** Never put a form, a form section, or a single form control in a card either. The edges of the panel separate the panel content from the page. See `recursica-skill-card`.\n\n**In a form in a panel, put every label above the label's field.** A panel is a narrow container. `recursica-skill-forms` sets the test: the width of the container decides when labels stack, not the width of the viewport. The other form rules still apply in a panel:\n\n- a single column\n- one field per row of the form\n\n**Label placement is one decision for the whole form, never for each field.** `recursica-skill-forms` allows labels side by side or stacked, but never both at the same breakpoint. Apply the container-width test once, to the whole form. The result of the test sets the label placement of every field in the form. A panel is exactly the kind of narrow container that makes labels stack. Every field in a form in a panel stacks, not only the fields that look cramped. A short field that would fit beside the field's label stacks too. `recursica-skill-forms` sets this rule.\n\n**Use the application's save mode in a panel, never a separate save mode.** The two save modes differ in save status:\n\n- Saving field by field needs a save status that stays on the page.\n- Saving the whole form at once shows no save status and no sign of unsaved changes.\n\nSee `recursica-skill-forms`.\n\n**Put one primary action at the bottom right of the panel footer.** Put a true alternative directly to the left of the primary action. For example, \"Save\" sits at the bottom right, and \"Cancel\" sits directly to the left of \"Save\". `recursica-skill-buttons-links` sets this rule.\n\n**Closing a panel must be possible and obvious.** The close control in the header closes the panel, and so does the Escape key. Do not build a panel that the persona can leave only by finishing the task in the panel.\n\n**Build a page, not a panel, for a task that needs a stepper or that scrolls a long way.** Give each of the following tasks a separate page with a separate route:\n\n- a process with several steps\n- a task with a lot of data entry\n\n**Do not add a toast when a panel changes the page behind the panel.** The change on the page is the feedback. For example, when filters in a panel narrow a table on the page, the narrower table is the feedback.\n\n**Place a panel flush against the left or right edge of the viewport, at full height.** `recursica-skill-panels-modals` sets the placement rules:\n\n- The panel runs the full height of the viewport, from top to bottom.\n- A panel is never set in from the edge, never floating, and never less than full height.\n- Left and right are both standard sides. The agent or the user chooses the side for each panel.\n- Never open panels on both sides at once.\n- Panels stacked on top of each other all use the same side. Stacked panels may differ in width.\n- A panel on the top or bottom edge is allowed but extremely unusual. The design system has no design for a top or bottom panel. Confirm a top or bottom panel with the user before building one.\n\n**A panel MUST NEVER scroll horizontally.** The rule has no exception. When content needs a horizontal scrollbar, the content does not belong in a panel.\n\n**A panel that scrolls up and down is the sign to move the task to a page.** On the new page, repeat the context the task needed. For example, a page for editing an order repeats which order the persona is editing.\n\n**A panel may open a modal.** A panel does not block the page, so a panel is not a mode. A modal opened from a panel therefore does not stack one mode on another mode. A confirmation for unsaved changes is a modal that the panel opens when the panel closes.\n\n**A panel may be stacked on top of another panel, but stacking is not ideal.**\n\n- The second panel covers the first panel completely.\n- Closing the second panel shows the first panel again.\n- Never nest a panel inside another panel.\n- Any number of panels may stack, with no hard limit. Confirm with the user before stacking more than two panels.\n\n**Close a panel when the route changes.** The exception is a route change that exists only to open another panel or a modal.\n\n**Below the tablet breakpoint, open the panel content as a page instead.** Do not use a narrower panel, or a full-screen overlay styled as a panel. At the tablet breakpoint and above, the panel stays a panel.\n\n**NEVER draw a shader, scrim, or tint behind an open panel.** The rule has no exceptions. A panel sits beside the page so the persona can read and use the page. A scrim dims the page. `recursica-skill-panels-modals` sets this rule. The four settings below keep this rule when an adapter draws an overlay by default.\n\n**Until the adapter's defaults are fixed, turn off four modal defaults explicitly.** An adapter (the Recursica component library for one framework, such as Mantine or Angular Material) may make a panel modal by default. An adapter can build the panel on a drawer from a code library. Most drawers from code libraries turn on four modal defaults:\n\n- the overlay\n- closing on a click outside the panel\n- the focus trap\n- the scroll lock\n\nThe house rule is that a panel leaves the page usable, and a modal panel does the opposite. A panel built on such a drawer with only the adapter's documented settings blocks the page. Nobody notices the blocked page.\n\nLook up the name the code uses for each of the four settings with the knowledge MCP server's `component_api` tool. A build test on one adapter confirmed that all four settings are needed. The modal default is a tracked defect in the adapter. Before assuming the four settings are still needed, check the adapter's current default. When the adapter's default is fixed, delete the four settings.\n\n**A code library's default is not a house rule.** A drawer that blocks the page by default says nothing about what a Recursica panel should do. Never treat the drawer's modal default as a house rule. See `recursica-skill-design-router`.\n\n**A panel is non-modal (the page behind stays usable), and the purpose of a panel is to leave the page usable.** The persona can still move around the application and act on the page behind the panel. `recursica-skill-panels-modals` sets this rule directly. A panel built to block the page is a modal built with the wrong component.\n\n**NEVER put a table inside a panel.** A panel is narrow, and a table needs width. A table in a panel either scrolls horizontally, which is forbidden outright, or truncates every column. Instead, follow two rules:\n\n- Show repeated content as groups of stacked fields.\n- Put secondary material in a second tab, not below the main content.\n\n`recursica-skill-panels-modals` sets this rule.\n\n**When a panel holds unsaved form data, closing the panel asks the persona before throwing the data away.** For example, a persona types a note and presses Escape, and the panel asks before discarding the note. Leaving a page with unsaved changes asks the same way. Do not ask on every close. Ask only about data the persona entered and never saved.\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**A panel is never modal, so build every part of a panel as non-modal.** Almost every accessibility failure in a panel comes from a panel built partly as a modal. Such a panel looks as if the page stays usable. But the panel traps focus like a dialog, or hides the page from assistive technology while the page stays clickable. The page behind a panel stays usable, readable, and reachable.\n\n### Screen readers\n\n- **Connect the panel header to the panel as the panel's accessible name.** A panel with no accessible name is announced as a region with no name. \"Panel\" is not a name.\n- **Give the panel the role of a named region, not the role of a modal dialog.** The persona can browse into and out of a named region. Build a modal instead when the whole page behind the panel must be inert (impossible to reach or read). See `recursica-skill-modal`.\n- **Never mark a panel as modal while the page behind the panel stays usable.** Assistive technology stays inside a modal dialog. A persona using a mouse can still use the page behind the panel. A persona using a screen reader cannot reach the page.\n- **Do not hide the page behind a non-modal panel from assistive technology.** The page behind the panel is not inert. A persona using a screen reader must be able to read the page and get back into the panel.\n- **Place the panel content in the document where the panel appears on screen, not at the end of the document.** The reading order follows the visual order.\n- **Every persona using the panel must be able to tell that the panel opened.** Moving focus into the panel shows that the panel opened. Do not rely on a slide-in animation to show that the panel opened.\n- **Give the close control a real accessible name**, such as \"Close filters\". An icon with no label is announced as nothing.\n- **Announce every change the panel makes outside the panel.** Redrawing the page is not enough. When a filter cuts a table down to four rows, announce the result. A persona using a screen reader inside the panel cannot see the change on the page.\n\n### Keyboard and non-mouse navigation\n\n- **Move focus into the panel when the panel opens.** Put focus on the first meaningful element: the first field, or the panel container. Put focus on the close button only when no other element can take focus. Never leave focus on the element that opened the panel.\n- **Return focus to the element that opened the panel when the panel closes.** Teams skip returning focus more often than any other step. Without returned focus, the persona lands at the top of the document.\n- **Escape closes the panel**, and closing the panel never saves.\n- **Never trap focus in a panel.** The persona can still reach the page behind the panel.\n  - Pressing Tab on the last control in the panel must move focus on into the page, in document order.\n  - Pressing Shift-Tab must move focus back into the panel.\n  - A panel that traps focus while the page stays usable lets a persona using a mouse leave the panel. A persona using a keyboard cannot leave the panel.\n- **Make the tab order inside the panel follow the visual order.** The order is the content, then the footer buttons, then the close control in the place the close control appears. The tab order must not jump between the panel and the page unpredictably.\n- **Never make a pointer, such as a mouse, the only way to close the panel.** Escape and the close control both close the panel, no matter what a click outside the panel does.\n\n## Styling set by tokens\n\n**Never set or override the panel's styling.** The theme sets every visual property of the panel, such as size, spacing, borders, colors and animation. Do not add extra containers or spacers to change the panel'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-panels-modals` — the design-rules skill that sets the panel rules:\n  - choosing a panel, a modal, or a page\n  - the context test\n  - the scrolling threshold\n  - the ban on stacking modes\n  - forms in a panel\n  - protecting unsaved changes\n  - the difference in focus trapping\n- `recursica-skill-navigation` — routes and addresses. A panel gets an address whenever possible, but no browser history entry.\n- `recursica-skill-forms` — the form rules:\n  - one label placement per form, and the container-width test behind the rule\n  - single-column layout\n  - validation\n  - the save mode for any form in the panel\n- `recursica-skill-buttons-links` — the button rules:\n  - the button that opens the panel\n  - one primary action per region that holds content, such as a page, panel, or modal\n  - the placement of footer buttons\n- `recursica-skill-design-system-conventions` — the accessibility baseline every component follows.\n\n### Only if used on the same screen\n\n- `recursica-skill-modal` — the blocking alternative, and the rules on focus trapping and an inert page that a modal follows.\n- `recursica-skill-card` — why no card wraps the panel content, and why no form goes in a card.\n- `recursica-skill-toast` — short confirmations and undo, which never belong in a panel.\n\n## Open questions\n\n- **Opening transition.** The side of the panel is set, and how the panel attaches to the edge is settled. No rule says whether the panel slides in or expands when the panel opens.\n- **Panel width.** Stacked panels may differ in width from each other. No rule says whether a left panel and a right panel share a width. Confirm a wide panel with the user only when the theme has no size variant.\n- **Top or bottom panel design.** A top or bottom panel is allowed but has no design. Confirm a top or bottom panel with the user before building one, because no rule covers the design.\n- **Divider visibility.** No rule says when the divider appears. Only the design-system website shows the \"Standard\" and \"Scrollable\" divider types. Confirm with the user before relying on either divider type, but only when the theme has no type variant.\n- **Loading state.** Confirm with the user how to show a panel whose content is still loading. Confirm only when the theme has no loading state.\n\n## Pre-flight checklist\n\n- [ ] The page underneath the panel is needed while the panel is open. No critical content is hidden in the panel.\n- [ ] Every task that must be finished or given up first is in a modal. Brief feedback is in a toast.\n- [ ] Every variant and option on the panel is one the knowledge MCP server lists for the theme. No side, width, size, or type variant is set unless the theme has that variant. No variant or option is invented.\n- [ ] A button opens the panel, with no browser history entry. The panel has an address whenever possible.\n- [ ] The header names the panel's purpose and is connected as the panel's accessible name.\n- [ ] No card wraps the panel content, and no form, form section, or form control sits inside a card.\n- [ ] Every form in the panel stacks the labels, uses a single column, and follows the application's one save mode.\n- [ ] Label placement is one decision for the whole form. Every field in the form stacks, with no mix of stacked and side-by-side labels at one breakpoint.\n- [ ] The panel footer has one primary action at the bottom right. The alternative sits directly to the left of the primary action.\n- [ ] The panel is non-modal: the panel traps no focus. The page behind the panel stays usable and reachable by assistive technology.\n- [ ] Focus moves into the panel when the panel opens. Focus returns to the element that opened the panel when the panel closes.\n- [ ] Escape closes the panel without saving, and closing the panel is never pointer-only.\n- [ ] Focus is not trapped, and the page behind the panel is not made inert.\n- [ ] The page behind a non-modal panel stays readable and reachable by assistive technology.\n- [ ] The tab order follows the visual order and does not jump unpredictably between the panel and the page.\n- [ ] The close control has a real accessible name, and the focus ring is intact. No control or content the persona needs appears only on hover.\n- [ ] Changes the panel makes to the page are announced, not only redrawn.\n- [ ] No styling is set or overridden on the panel. No container or spacer is added to change the panel's look.\n- [ ] The panel is non-modal: focus is not trapped, and the page behind the panel stays reachable by keyboard. The behavior was checked in the running application, not assumed from the settings in the code.\n- [ ] No panel is nested inside another panel. Each stacked panel covers the first panel completely and uses the same side as the first panel.\n- [ ] The panel sits flush against the left or right edge and runs full height. Panels are open on only one side.\n- [ ] Nothing scrolls horizontally. Content that made the panel scroll up and down is on a page instead. The page repeats the context the content needed.\n- [ ] The panel closes on a route change, unless the navigation only opens another panel or a modal.\n- [ ] Below the tablet breakpoint, the panel opens as a page. More than two stacked panels, and any top or bottom panel, were confirmed with the user before being built.\n- [ ] Every form in the panel uses stacked label placement for every field. No table is inside the panel, and secondary material is in a separate tab.\n- [ ] Closing a panel with unsaved form data asks first. Closing a panel the persona has not changed does not ask.\n- [ ] Open questions were asked about, not decided: the opening transition, panel width, top or bottom panel design, divider visibility, and a loading 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-panel",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-panel",{"tool":41,"command":42},"bunx","bunx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-panel",{"tool":44,"command":45},"pnpm","pnpm dlx skills add borderux\u002Frecursica-knowledge --skill recursica-skill-panel","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fborderux\u002Frecursica-knowledge\u002Fblob\u002Fmain\u002Fskills\u002Fcomponents\u002Frecursica-skill-panel\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",[],[]]