Identify backend DB entities lacking frontend listings and emit TABLE metadata JSON blocks.
npx skills add https://github.com/tonehq/tone --skill backend-tables
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
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.
Point me to the backend and frontend roots, then run the scan to emit only TABLE metadata for missing listings.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
tonehqDetect schema entities lacking frontend forms and emit FORM metadata blocks.
slingr-stackAnalyze Drumr frontend-hooks for React and TanStack headless controller patterns.
jhlee0409Adds a new field to the Project entity across schema, validation, and UI.
wade56754Verify ad-code integration for cross-module boundary and API violations.
