recursica-skill-filters

Defines house rules for designing filter bars in enterprise web applications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Filter bars in enterprise applications often confuse users through inconsistent labels, mixed neutral-state conventions, and hidden applied states. This Skill provides opinionated house rules so every filter is understandable before use and its applied state is always visible. ## Core Features & Use Cases - Labeling rules: Enforces noun-based filter labels that name the field being filtered and match the corresponding table column, never verbs or placeholder-only identification. - Defaults and date handling: Requires one consistent neutral-state convention across the bar, visible default filters, and relative date-range controls instead of paired empty date fields. - Applied-state visibility: Mandates removable filter chips that stay in sync with their controls, announced result counts, and a distinct zero-results state. - Use Case: When reviewing a new filter bar for a request queue, apply the pre-flight checklist to catch mixed All/empty conventions, verb labels like Search, and bulk actions incorrectly placed inside the filter cluster. ## Quick Start Review this filter bar design against the recursica filters house rules and list every violation.

Frequently Asked Questions about recursica-skill-filters

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

FAQPage Schema
How should I label a filter in an enterprise web app?▼

A filter label should be a noun naming the field being filtered, such as Name, Status, or Department, never a verb like Search. The label must match the column it filters, and the placeholder should only show the shape of an accepted value.

What is the best pattern for date range filters?▼

Prefer a single relative-range control offering options like This month or Last 30 days, with a Custom option opening a modal for explicit ranges. Avoid two bare date fields, which force users to infer the range relationship.

Should a filter bar use 'All' options or empty controls for the neutral state?▼

Either convention works, but every filter in the bar must use the same one. Mixing controls that read All with controls that sit empty, both meaning unfiltered, is the most common filter-bar defect.

When should a filter be multi-select instead of single-select?▼

A filter over a known set of categories should be multi-select, since users commonly want two statuses at once. If no multi-select component exists, raise the gap rather than composing one; independent single-value filters that AND together are the interim substitute.

When should I not use this filters skill?▼

Do not use it for the table itself, its columns, sorting, or pagination, which belong to recursica-skill-tables. It also does not cover which control a form field gets, typed autocomplete lookups, or query construction and performance.