backend_tables

Name: backend_tables
Availability: InStock
Author: tonehq

Identify backend DB entities lacking frontend listings and emit TABLE metadata JSON blocks.

11|3|Updated Aug 31, 2025

Search Tags:#frontend #codebase #backend #analysis #metadata #table

Ready to run

npx skills add https://github.com/tonehq/tone --skill backend-tables

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend_tables
Source: https://github.com/tonehq/tone/tree/main/.claude/skills/backend_tables
Command: npx skills add https://github.com/tonehq/tone --skill backend-tables

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discrepancies between backend DB definitions and frontend listings cause missing UIs and orphaned data views. This skill automatically identifies entities defined in the backend schema that do not yet have a corresponding frontend listing and emits dedicated TABLE metadata blocks for each gap, enabling a focused UI generation workflow.

Core Features & Use Cases

Discovers DB entities with a defined schema but no frontend listings.
Emits TABLE metadata JSON blocks per gap, ready for integration with the frontend tooling.
Pairs with [[backend_form]] and operates in a project-agnostic manner by asking the user for the backend and frontend roots before scanning.

Quick Start

Point me to the backend and frontend roots, then run the scan to emit only TABLE metadata for missing listings.

Frequently Asked Questions about backend_tables

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

FAQPage Schema

How do I find backend DB tables that are missing a frontend listing?▼

To find backend DB tables missing a frontend listing, you scan the codebase by specifying your backend and frontend root directories. The analysis identifies entities defined in the backend schema with no corresponding frontend listing and emits metadata for each gap.

What is TABLE metadata JSON and when do I need to generate it?▼

TABLE metadata JSON is a structured block containing display names, keys, endpoints, and column metadata derived from your codebase. You need to generate it when backend DB entities exist but lack frontend listings, enabling focused UI generation workflows.

How do I generate frontend table metadata from an existing backend schema?▼

To generate frontend table metadata from a backend schema, provide the backend and frontend root directories for scanning. The process derives display names, keys, endpoints, and column metadata strictly from the discovered codebase and emits TABLE metadata JSON blocks for missing listings.

Does this approach generate database migrations or endpoint code?▼

No, this approach does not generate database migrations, endpoint code, or models. It emits only TABLE metadata JSON blocks derived from the existing codebase to identify schema gaps and enable UI generation.

Can I use this to analyze any project structure for missing DB entity listings?▼

Yes, you can analyze any project structure for missing DB entity listings. The process operates in a project-agnostic manner by asking you to specify the backend and frontend roots before scanning, without hardcoding paths or names.

Why do discrepancies between backend schemas and frontend listings cause orphaned data views?▼

Discrepancies between backend schemas and frontend listings cause orphaned data views when DB entities are defined but lack corresponding UI components. Emitting TABLE metadata for these gaps bridges the backend-to-frontend divide and enables focused UI generation.