Theoretical review and centralization of music concepts
Theory / Refactoring / Copywriting
Task metadata
Original request
"Fazer um levantamento e revisão das explicações textuais do app. Elas foram criadas pelo agente e não estão 100% corretas. Aqui vamos identificar onde é que estamos definindo coisas como: Men. Harmônica, Men. Melódica... b3, Exótico, oriental, tenso, Consequências harmônicas. O ideal é que isso tudo esteja centralizado em algum local do repo, assim como temos libs de teoria, pra que possamos editar, traduzir, etc, sem precisar sair procurando por esses termos no meio do código"
Structured task
Problem
The music theory copywriting inside the app contains confusing, inaccurate, or vaguely generalized fragments ('Exotic, tense, hybrid sound') introduced by previous LLMs. This text is physically coupled and scattered across multiple visual codebase components.
Context
Taxonomic precision and clarity inside a portal focused on mode and scale education afford no margin for error. Every pedagogical explanation must be unified within a 'Dictionary' residing in a global state or constants scope, which ensures the decoupling of business logic and abstract theory from the UI structural layer.
Expected
Identify all hardcoded descriptive definitions throughout the repository (Modal analyses, tonic characteristics, qualitative formulas). Migrate all references sequentially towards a dedicated library/data table framed in TypeScript (like a musicDictionary.ts or local JSON files). Following portability, review and conceptually rewrite the vocabulary surrounding scales and degrees to ensure utmost accuracy.
Notes
- Pay specific detail when defining b3, b6, and V7 (Dominant) characteristics to ensure immaculate harmonic definitions.
- This portability directly paves the way for feature roadmap milestones like language internationalization, so make sure to use simple, cohesive locale keys.