glee-fully-repo-standardizer

原文涵盖的主题

• glee-fully-repo-standardizer
• When to Activate
• Core Concepts
• Step 1 — Confirm Project Root
• Step 2 — Gather Entity Details
• Step 3 — Locate the Script
• Step 4 — Run the Scaffold
• Step 5 — Report Results

Scaffold and standardize any Glee-fully child repository against the canonical structure defined in OKHP3/Glee-fullyTools-FoundRy. -- Use this skill when the user is working inside (or about to set up) a glee-fully-gpt child repository and wants to: Create the canonical folder/file structure from scratch Audit an existing repo for missing folders or files Pre-populate files with Glee-fully brand payload (tone, persona, governance) Prepare a repo to receive content migrated from ChatGPT threads or Notion -- Every Glee-fully child repo belongs to one of three tiers: | Tier | Pattern | Emoji | Role | |------|---------|-------|------| | Toolbox | glee-fully-gpt00- | 🧰 | Trunk — suite concierge, routing only | | Tool | glee-fully-gpt01- through glee-fully-gpt07- | 🪚 | Branch — category hub, routing only | | Tool-ette | glee-fully-gpt01a- through glee-fully-gpt07g- | 🔩 | Twig — specialized task executor | Tier determines the folder structure and default tone overlay. -- Verify you are at the root of the target child repo: -- Before running the scaffold, collect: | Field | Example | Source | |-------|---------|--------| | --tier | toolette | Repo name pattern (01a = toolette, 01 = tool

这里只展示节选，请以完整原文和当前要求为准。