recursica-skill-panel

Guides correct usage of the Recursica panel component for non-blocking side surfaces.

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/borderux/recursica-knowledge --skill recursica-skill-panel-borderux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recursica-skill-panel
Source: https://github.com/borderux/recursica-knowledge/tree/main/skills/components/recursica-skill-panel
Command: npx skills add https://github.com/borderux/recursica-knowledge --skill recursica-skill-panel-borderux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designers and developers often misuse side panels by making them modal, hiding critical content, or inventing unsupported variants like sizes and sides. This Skill defines exactly when a Recursica panel is justified versus a modal, page, or toast, and enforces its accessibility and layout rules. ## Core Features & Use Cases - Decision guidance: Distinguishes panels from modals, toasts, pages, and cards with a clear use/when-not-to-use table. - Accessibility rules: Covers focus management, Escape dismissal, focus return, screen-reader naming, and the prohibition on trapping focus in non-modal panels. - Adapter defect workaround: Documents the Mantine Drawer default overrides (withOverlay, closeOnClickOutside, trapFocus, lockScroll) needed to achieve non-modal behavior. - Use Case: When adding a filter panel beside a data table, use this Skill to confirm the panel stays non-modal, stacks form labels, announces filter results to screen readers, and avoids horizontal scrolling. ## Quick Start Ask the agent to review or build a Recursica panel for showing filters beside a page without blocking it.

Frequently Asked Questions about recursica-skill-panel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I use a panel instead of a modal?▼

Use a panel when the user needs the page underneath while working, such as filters, settings, or a details view. Use a modal when the task must be finished or abandoned before continuing, or when confirming an irreversible action.

How do I make a Mantine Drawer behave as a non-modal panel?▼

Pass withOverlay={false}, closeOnClickOutside={false}, trapFocus={false}, and lockScroll={false} explicitly. The Recursica adapter wraps Mantine's Drawer, which defaults to modal behavior with an overlay and focus trap, so all four overrides are required until the adapter defect is fixed.

Can I set the panel width, side, or size in Recursica?▼

No. The panel has no variant axes at all: min-width and max-width are fixed tokens, and there is no side, size, width, or type property. Which edge a panel appears from is designated per panel, not passed as a prop.

Should focus be trapped inside a non-modal panel?▼

No. Focus moves into the panel on open and returns to the trigger on close, but Tab must continue into the page behind. Trap focus only if the panel is genuinely modal, in which case the page behind must be inert and non-scrolling.

Can I put a table or a card inside a panel?▼

No. Tables are forbidden because the narrow panel forces horizontal scrolling or truncation; use stacked field groups instead. Cards are also forbidden because the panel itself is already the boundary, and forms inside must stack their labels.

What happens to a panel on mobile or small screens?▼

Below the tablet breakpoint, the panel opens as a page instead, not as a narrower panel or full-screen overlay. At tablet width and above it remains a panel flush to the left or right viewport edge.