How to decide the name and description of your template

🔹 Name (short handle / title)

• Purpose: fast lookup, unique identifier.
• Length: 2–5 words (max ~40 chars).
• Format: describe what it is in plain English—like you're telling a friend.
• Rule: lead with the most important noun (what someone would search for).

Examples

• Name: House Builds
  • Description: Prefab house build with walls, roof, doors, and windows. Optimized for placement and resizing in game worlds. Includes collision, lighting hooks, and customizable materials.
• Name: Currency System
  • Description: Handles player currency with earn, spend, and save functions. Supports leaderstats display, DataStore persistence, and customizable currency types.
• Name: Quest GUI
  • Description: Interface for tracking player quests with progress bars, objectives list, and reward previews. Supports client-side updates and integrates with QuestService for syncing.

🔹 Description (retrieval context)

• Purpose: richer semantic signal for embeddings + keyword search.
• Length: 1–3 sentences (100–250 chars).
• Structure:
  1. What it is (short definition).
  2. Key capabilities (main verbs/keywords).
  3. Scope/limits if relevant. (Optional)
• Style: plain, keyword‑dense, no fluff.

Examples

• Admin Commands → Provides role-based admin commands (kick, ban, fly, announce). Configurable ranks and group linking.

• Cooking System → Implements time-based recipes at stove/oven stations. Supports burn states, inventory IO, and recipe table extension.

🔹 Why this works for Marketplace Search

• Name = fast disambiguation: short, unique.
• Description = dense semantic vector: enough keywords for recall, but not bloated.