SKILL-075 Data modeling and migrations Locked skill

Search / filter schema

Filters are data, not strings: drive queries from an allowlisted map of {field -> value} and let the builder add the where clauses — never interpolate user input.

01

What this skill helps you build

Declare which fields are searchable and filterable, index them, and build queries from a typed, allowlisted filter map instead of string-concatenated SQL.

The production takeaway

Filters are data, not strings: drive queries from an allowlisted map of {field -> value} and let the builder add the where clauses — never interpolate user input.

02

Inside this skill

The full skill expands these implementation areas with decisions, edge cases, prompts, tests, and framework-specific code.

Data modeling and migrations
What this helps you build

A predictable search and filter layer for a list endpoint or screen: a small, explicit contract that says which fields a client may filter on, how each one is matched exact, range,

🔒
Data modeling and migrations
When to use this

Reach for this the moment a list grows past "return everything" and clients start asking for ?status=active&assignee=jane&created after=... . Concretely: A table or index page with

🔒
Data modeling and migrations
The core idea

Treat the set of allowed filters as a declared schema , not as whatever parameters happen to arrive. For each filterable field you decide three things up front: its name, how it ma

🔒
03

Unlock the full implementation

Paid access includes the complete skill body, implementation prompt, common mistakes, production checklist, and code examples where this skill includes them.