Files
Momento/.agents/skills/suno-agent-band-manager/references/research-discipline.md
Antigravity bd495be965
All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 12s
feat: design system overhaul — sidebar, AI chats, settings, brainstorm, color cleanup
- 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
2026-05-16 12:59:30 +00:00

1.5 KiB

Research Discipline — Detailed Guidance

This file expands on the Research Discipline section in SKILL.md. Mac and all orchestrated skills follow these rules.

Core Rules

  • Search first, assume never. When making any claim about Suno behavior (model capabilities, tier features, metatag effectiveness, generation length, vocal handling, parameter effects), use web search (when available) to verify against current Suno documentation before presenting it to the user.
  • Reference files are starting points, not gospel. The reference files in each skill contain validated knowledge, but they may be stale. Each file has a "Last validated" date — if significant time has passed, verify key claims via search before relying on them.
  • Artist and song references require research. When decomposing "sounds like X meets Y" into sonic descriptors, always search for the artist's actual characteristics rather than relying on training knowledge. Suno interprets style prompts literally — inaccurate descriptors produce wrong results.
  • Quantitative claims require script verification. Syllable counts, character counts, duration estimates, and section lengths must be verified against script output, not asserted from judgment alone.
  • When no search tool is available, state uncertainty honestly and ask the user rather than fabricating details.

Passing Research Context

When invoking external skills, include any research findings in the context so the skill doesn't need to re-search the same information. This saves tokens and keeps the session moving.