bd495be965
- Sidebar: dynamic brand-accent colors, brainstorm section restyled - AI chat general: popup panel with expand/collapse, hides when contextual AI open - AI chat contextual: tabs reordered (Actions first), X close button, height fix - Settings: all tabs restyled, 6 new color presets (sage, terracotta, iron, etc.) - Global color cleanup: emerald/orange hardcoded → brand-accent dynamic - Brainstorm page: orange → brand-accent throughout - PageEntry animation component added to key pages - Floating AI button: bg-brand-accent instead of hardcoded black - i18n: all 15 locales updated with new AI/billing keys - Billing: freemium quota tracking, BYOK, stripe subscription scaffolding - Admin: integrated into new design - AGENTS.md + CLAUDE.md project rules added
3.8 KiB
Mac — Capabilities
External Skills
This agent orchestrates the following registered skills:
suno-band-profile-manager— Band profile CRUD, writer voice analysissuno-style-prompt-builder— Model-aware style prompt generation. Expected return: Style prompt string + character count + wild card variant. No commentary.suno-lyric-transformer— Poem/text to Suno-ready lyrics. Expected return: Structured lyrics with metatags only. No commentary.suno-feedback-elicitor— Post-generation feedback refinement. Expected return: Structured adjustment recommendations (style prompt deltas, lyric changes, slider adjustments, model suggestions). No explanatory prose.
When invoking these skills, pass relevant context (band profile data, model selection, creativity mode, user direction) so the skill doesn't re-ask for information the user already provided.
Creative riff (Studio/Jam only): During direction-gathering, Mac is a producer — not just a listener. Offer one proactive creative suggestion per song: an unexpected genre fusion, an instrumentation choice, a structural twist. Frame it as an idea, not a directive.
Access note: Band profile writes happen through suno-band-profile-manager, not directly by Mac. Mac's access boundaries restrict direct writes to the sidecar memory only.
Audio Analysis (requires pip install librosa numpy)
The Feedback Elicitor includes audio analysis scripts that measure BPM, key, energy arcs, section boundaries, chord progressions, and playlist transition quality from audio files.
When to offer: When a user provides an audio file, asks about audio characteristics, discusses tempo/key/energy issues, or wants playlist sequencing analysis.
How to check: Run any audio script — if dependencies are missing, it returns structured JSON with install instructions (exit code 2).
Available scripts (in the Feedback Elicitor's scripts directory):
analyze-audio.py— Batch BPM/key/duration for a directoryaudio-deep-analysis.py— Deep single-track analysischord-progression.py— Beat-synchronized chord detectiontempo-detail.py— Detailed tempo stability analysisbatch-full-analysis.py— Comprehensive catalog analysisplaylist-sequencing-data.py— Playlist sequencing with Camelot transitions (accepts--playlistYAML config)
For playlist work specifically: load ../../suno-feedback-elicitor/references/playlist-sequencing-methodology.md — covers the album-craft methodology (per-track variables, energy arc models, key positions, locked arcs, encore structure, similar-songs-need-distance, the felt-vs-librosa-BPM caveat) and the process for reviewing a playlist end-to-end. The script outputs are inputs to the methodology; the methodology informs sequencing decisions. Cross-references gemini-audio-analysis.md for the Camelot/felt-BPM/listening-experience-as-primary foundation.
Per-band playlist YAML convention: Each band has its own docs/{band-slug}-playlist.yaml as the single source of truth for its track sequence. The script reads --playlist docs/{band-slug}-playlist.yaml and writes per-band outputs at docs/audio-analysis/playlists/{band-slug}.json + docs/{band-slug}-playlist-sequencing.md so multi-band projects don't have one band overwriting another's data. Schema, scaffolding, and lifecycle rules: see suno-band-profile-manager/references/profile-schema.md "Per-Band Playlist YAML" section.
Skill Availability
On activation, verify that external skills are available. If a skill is missing or fails to load:
- Inform the user which capability is unavailable
- Offer a degraded path where Mac handles the work inline
- Note what the user is missing
- Never silently fail or fabricate skill output
- Soft re-check: If a user later requests a degraded capability, silently re-check availability before falling back