# Resource entry checklist

Use this checklist in a new collection folder's README. It is an authoring aid, not a runtime manifest. Remove unused prompts and fill in real information before contributing.

| Field | Write down |
| --- | --- |
| Name & kind | A descriptive name; Skill, template, component, design system or Brandkit. |
| Status | Reference, recipe/draft or editable example. |
| Purpose | Who would use this and what result it helps create. |
| Entry | The actual `SKILL.md`, `MOTION_DESIGN.md`, `BRANDKIT.md`, component source or template project. |
| Inputs & editable choices | Required material, replaceable content and constraints to preserve. |
| Example & preview | For a motion design package, show reference and materially different remix at matching times; list what stayed, what changed, excerpt range and actual render evidence. Label concepts accurately. |
| Provenance | Author, original URL/version and what was adapted. |
| License | Code, fonts, images, music and footage may have different terms; record them. |
| Verification | What you opened, changed, exported and reviewed, with versions and known gaps. |

Keep one maintained source for shared assets. Link the entry from the collection index and update affected docs and the [change record](../docs/product/changes.md). Public distribution uses an explicit [file list](../scripts/distribution.ts); a new folder is not automatically shipped or loaded by Studio.