Menu
Produce a new album entry for the app. Use when asked to add, analyse, or create an album entry.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Router for 67 bundled design themes. Use whenever building or restyling UI and a visual direction is needed — it maps the desired vibe (minimal, playful, retro, enterprise, glassmorphism, etc.) to the right theme file to load. Trigger on "design style", "make it look...", "UI theme", "visual direction", or any request to build a page/app with a specific aesthetic.
Remove AI slop from every file in the repo — code, docs, config, and data.
Extremely strict maintainability review hunting code-judo restructurings — abstraction quality, the 1k-line rule, and spaghetti growth.
Quality-gate execution for repository hygiene and release readiness. Use when the user asks to run a quality gate, clean all Problems panel issues, fix lint/test/coverage failures, or verify the branch meets strict 80%+ coverage thresholds without suppression.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Surface architectural friction in a codebase and apply deepening improvements.
| name | album-analysis |
| description | Produce a new album entry for the app. Use when asked to add, analyse, or create an album entry. |
Produces a complete new album entry for the current app, not a standalone HTML file.
Leading word: entry — every run produces one finished data/<id>.json entry, validated end-to-end.
When the user asks for multiple albums in one request, fan the work out in parallel using multiple sub-agents. Give each album to its own sub-agent whenever feasible, then merge the results in the main agent and run one shared validation pass after all album files are in place.
Use REFERENCE.md for the repo output model, schema fields, energy mapping guide, timeline guidance, index refresh rules, scaffolder preference, and the quality checklist.
Use:
Extract and record:
Completion criterion: all metadata fields listed above are populated with verifiable sources.
When populating listening links for the album detail page, include platform URLs according to business rules.
Rules:
Completion criterion: at least one audio and one video listening link is resolved and recorded.
Search Wikipedia for the album page and prefer the page summary thumbnail or equivalent Wikimedia-hosted image.
Rules:
upload.wikimedia.org thumbnail URL when availablecoverUrl field in data/<id>.jsoncoverUrl rather than inventing oneCompletion criterion: coverUrl is populated with a verified Wikimedia URL,
or explicitly omitted.
Populate data/<id>.json using the schema and energy mapping in REFERENCE.md.
For each track, derive energy, tags, role, and events per the reference guidance.
Completion criterion: every track has all derived fields populated, every
timestamp uses M:SS or MM:SS format, and the JSON validates against
src/shared/schema.ts.
Regenerate data/index.json after writing data/<id>.json, using the scaffolder or npm run build. See REFERENCE.md for the derived summary shape and scaffolder invocation.
Completion criterion: the new entry appears correctly on index.html after
regeneration.
Run:
npm run build
npm test
Then verify locally:
http://127.0.0.1:3000/index.htmlhttp://127.0.0.1:3000/album.html?id=<id>Completion criterion: npm run build and npm test both pass, and the
entry renders correctly on both pages. Every item on the quality checklist in
REFERENCE.md is satisfied.
After the new album entry is committed, check docs/future-research.md and
remove the matching row if it is still listed. Match by artist and album title
against the table rows — do not rely on the row number. If the entry is not
found in the file, skip this step.
Completion criterion: the album no longer appears in
docs/future-research.md.