create-listlisted
Install: claude install-skill YKUNAKORN/Supuersub
# SharePoint lists: design, then build the import file
Produce, per list, a spec `<ListName>.list.json`, an import file (`.xlsx`, or `.csv`
with `<ListName>.Setup.md`) and, for the whole design, `lists.md`. Reply in the user's
language; display names and setup text follow it, internal names stay ASCII. Paths are
relative to this skill's folder: `${CLAUDE_SKILL_DIR}`, or run from that folder.
## The workflow (in order)
1. **Understand the data.** From the user's description, and from
`supersub/mockup/sitemap.json` when it exists: its `data` entries name the lists
(`source`) and columns (`fields`); the pages' `data-field` names match. Use those
names. Ask only what is missing: what one row is, who fills it in, which values are
fixed choices, which columns point at another list, what must be unique.
2. **Propose the design in `lists.md`**: one table per list (column, display name,
finalType, required, unique, choices, notes), the relationships between lists, and
the order to create them in (a lookup's target list first). Name columns by
[`references/naming.md`](references/naming.md); pick types from
[`references/column-types.md`](references/column-types.md). **Get the user's
agreement before building anything.**
3. **Write the spec, lint it, build the file.** One `<ListName>.list.json` per list
(schema: [`assets/list.schema.json`](assets/list.schema.json); a finished example:
[`assets/example/Holidays.list.json`](assets/example/Holidays.list.j