manoel freitas
fd3a4eb5f1
## Summary - CTA orientação (banda “Ainda não sabe?”) na home e em `/servicos` abre WhatsApp com mensagem distinta; sem número oficial, cai em `/briefing`. - Glossário canônico em `SPEC.md` §8.0 (Vertente, Modalidade, Briefing, Contato parceiro, CTA contextual, CTA orientação). Sem `CONTEXT.md` paralelo. - Linear: https://linear.app/maneco-workspace/issue/MAN-127/ajustar-ctas-consultivos-no-whatsapp-e-briefing-comercial ## Test plan - [x] Feature: `HomePageContentTest` + `ServicesPageCtaTest` (17 passed) - [ ] CI Gitea (static, unit, feature, browser, container) - [ ] Conferir banda de modalidades com e sem `whatsapp_number` no Filament Reviewed-on: #7 Co-authored-by: manoel freitas <manoel.josefneto@gmail.com> Co-committed-by: manoel freitas <manoel.josefneto@gmail.com>
1.4 KiB
Domain Docs
How engineering skills should consume this repo's domain documentation.
Single source of truth
SPEC.md §8 (especially §8.0 Linguagem ubíqua) is the glossary and domain model for Amare. There is no root CONTEXT.md on purpose — do not create one. Prefer SPEC.md over Linear copy or OpenSpec prose when terms conflict.
Also useful:
PRODUCT.md— positioning and audience (not the glossary)openspec/specs/— current capability contractsdocs/adr/README.md— index only; ADR-001–010 live inSPEC.md§21
Before exploring
- Read
SPEC.md§8.0 for vocabulary; skim §5.1 for public routes and §8.2+ for persistence shape when relevant. - If a skill expects
CONTEXT.md/CONTEXT-MAP.mdand finds neither, proceed usingSPEC.md§8 — do not invent a parallel glossary file.
Use the glossary's vocabulary
When output names a domain concept (issue title, refactor, hypothesis, test name), use the term as defined in SPEC.md §8.0. Don't drift to synonyms the glossary explicitly avoids (_Avoid_).
If the concept isn't in §8.0 yet, either you're inventing language the project doesn't use (reconsider) or there's a real gap — resolve it by updating SPEC.md §8.0 via /grill-with-docs / domain-modeling, not by adding CONTEXT.md.
Flag ADR conflicts
If output contradicts an ADR in SPEC.md §21, surface it explicitly rather than silently overriding.