Toolset Types keeps the definitions for every custom post type, taxonomy, and field group inside wp_options with keys such as wpcf-custom-types, wpcf-custom-taxonomies, and wpcf-fields. Each registered post then writes its field values into wp_postmeta on the target post. The default admin gives you a wizard-style editor and a per-type field manager, but no public-facing way to see which types your team actually relies on, which fields are misconfigured, or which the dev team has already reviewed.

SleekView reads those records directly and renders one feedback card per Toolset post type or field group. Pick a numeric column like populated value count or registered field count as the vote weight, attach a tts_review_status meta for the status badge, and pull the parent post type as the chip. Developers and editors can upvote a card to flag broken or unused types, and the increment writes back to the meta key you choose so reporting stays consistent.

Because SleekView is read-only against the Toolset records, the Types admin keeps managing definitions and field values exactly as before. SleekView only adds a parallel review surface that ranks types and field groups by votes, shows location chips, and exposes status pills so anyone on the team can spot Stale, Needs refactor, and Reviewed records at a glance.

Toolset Types is fantastic at registering custom data structures and slowly turns into a museum if nobody ever reviews them. A theme migration leaves behind two unused types, a microsite leaves another, a campaign leaves a one-off taxonomy, and within a year the Types admin looks like an unsorted spreadsheet. The default admin has no way to surface which types are still wired to live content, which are duplicates of a forgotten earlier attempt, or which have drifted out of sync with the template they were built for.

The result is that quality signal stays in the heads of two senior developers and gets reinvented every quarter. SleekView gives the same records a public, vote-driven home. Devs get a saved Refactor board sorted by usage count and review status pill.

Editors get a feedback wall where they can flag a misbehaving type without filing a support ticket. Agency teams get per-client scoping so each engagement has its own ranked queue. Nothing about Toolset changes underneath, the Types admin stays the source of truth, and the review loop now lives where the team already works.