backend_form

Detect schema entities lacking frontend forms and emit FORM metadata blocks.

11|3|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/tonehq/tone --skill backend-form
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend_form
Source: https://github.com/tonehq/tone/tree/main/.claude/skills/backend_form
Command: npx skills add https://github.com/tonehq/tone --skill backend-form

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a codebase to identify DB entities that exist in the schema but lack frontend create/edit UIs and emits FORM metadata blocks to bridge the gap. It pairs with [[backend_tables]] and derives layout decisions from the actual schema and entity complexity.

Core Features & Use Cases

  • Detects entities defined in the backend schema that have no corresponding frontend forms.
  • Generates FORM metadata blocks for each gap, coordinating with the shared entities.json to keep UI scaffolding aligned.
  • Fully project-agnostic: inspects the actual codebase and asks for the backend and frontend locations before scanning.

Quick Start

Locate the backend and frontend roots, then emit FORM metadata for entities missing frontend create/edit UIs.

Frequently Asked Questions about backend_form

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

FAQPage Schema
How do I generate frontend forms from an existing database schema?

The tool scans your specified backend and frontend project roots to detect DB entities lacking create/edit UIs, then emits FORM metadata blocks to bridge the schema and frontend interface.

What is form metadata generation and how does it bridge backend and frontend code?

Form metadata generation analyzes backend schema complexity to produce FORM metadata blocks. This metadata bridges the gap by providing the structural layout needed to scaffold missing frontend create and edit UIs.

Do I need to provide backend and frontend locations before scanning my codebase?

Yes, you must provide the backend and frontend directory locations before scanning. The analysis runs project-agnostically by inspecting the actual codebase paths you specify to find schema gaps.

Does this form metadata tool generate database models or migrations?

No, this tool produces ONLY metadata blocks and does not generate database models, migrations, or API endpoints. It strictly derives layout decisions from the actual schema and entity complexity.

Can I use this tool to detect DB entities missing a frontend create or edit UI?

Yes, you can use this tool to detect DB entities defined in your backend schema that have no corresponding frontend create or edit UI. It coordinates with shared entities.json to keep UI scaffolding aligned.