Skill: design-table

Purpose

Create a complete, usable TeamDesk table, not just its basic schema.

Unless the user explicitly requests schema only, follow the full process below and proactively configure the table, columns, form, views, and table properties.

Process

  1. Inspect current tables

    • Review the existing database structure.
    • Reuse existing tables and relations where appropriate.
    • Avoid creating duplicate tables or data.
  2. Create the table

    • Use a clear singular table name.
  3. Plan the columns

    • Determine which physical, reference, lookup, summary, and formula columns are needed.
    • Prefer references to duplicating data stored in another table.
  4. Create physical columns

    • Create all required physical columns except reference columns.

    • During column creation, set only:

      • column name;
      • column type;
      • default visibility.
    • If additional properties are needed, edit the corresponding column after creation.

  5. Create reference columns

    • Add references to existing tables where relationships are needed.
  6. Create Lookup and Summary columns

    • Use the existing relations to create necessary Lookup and Summary columns.
  7. Create Formula columns

    • Add Formula columns for calculated or derived values when needed.
  8. Review all created columns

    • Inspect the complete table structure.

    • Fine-tune column properties where appropriate, such as:

      • Required;
      • Unique;
      • Allow Find;
      • Default/Calculate;
      • formatting;
      • choices;
      • visibility;
      • other type-specific properties.
  9. Review the table form

    • Check column order and form name.
    • Arrange fields logically.
    • Add sections when useful.
    • Modify the form layout to make data entry clear and convenient.
    • Avoid exposing unnecessary technical or helper fields.
  10. Review the Default View

    • Make sure meaningful columns are displayed by default.
    • Remove unnecessary columns.
    • Arrange columns in a useful order.
    • Set sensible sorting when appropriate.
  11. Create additional views if needed

    • Add views only when they provide clear value for common workflows or ways of browsing the data.
  12. Review table properties

    • Configure the table so records are easy to identify, search, and select.

    • Review and adjust:

      • Singular and Plural Name;
      • Name Column;
      • Default Record Picker;
      • search options;
      • other relevant table properties.

Completion Rule

Do not consider table creation complete immediately after creating the table and columns.

Complete all applicable steps above and review the result from an end-user perspective so the table is ready to use without requiring obvious additional setup.