Add squad: professional-web-squad#21
Open
ldalda wants to merge 1 commit into
Open
Conversation
Version: 1.0.0 Author: Lucas Description: Squad especializado em criação de sites e landing pages profissionais de alta conversão Agents: 5 (discovery, copywriter, web-designer, seo-specialist, ui-ux-expert) Tasks: 20 Submitted via *publish-squad from AIOS-FullStack
📝 WalkthroughWalkthroughThis pull request introduces the "Professional Web Squad," a complete squad configuration for AI-assisted high-conversion professional website and landing page creation. The PR adds a squad manifest, five agent specifications, comprehensive configuration documentation, and sixteen task specifications that define workflows and output templates across discovery, copywriting, SEO, UI/UX, and web design domains. ChangesProfessional Web Squad
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 17
🧹 Nitpick comments (1)
squads/professional-web-squad/tasks/seo-audit.md (1)
45-45: ⚡ Quick winEvite meta fixa de densidade de keyword (1–2%).
Essa regra está desatualizada e pode incentivar keyword stuffing. Prefira cobertura semântica + alinhamento de intenção de busca.
♻️ Proposta de ajuste
-- [ ] Densidade de keyword 1-2% +- [ ] Cobertura semântica do tópico (sinônimos, variações e entidades relacionadas)🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@squads/professional-web-squad/tasks/seo-audit.md` at line 45, Replace the checklist item "Densidade de keyword 1-2%" with a modern guideline: remove the fixed numeric density rule and instead state that audits should verify semantic coverage and alignment with search intent (e.g., "Priorize cobertura semântica e alinhamento com a intenção de busca; evite regras fixas de densidade de keywords que incentivem keyword stuffing"). Update any related checklist logic or documentation that references "Densidade de keyword 1-2%" to reference the new guidance.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@squads/professional-web-squad/agents/copywriter.md`:
- Around line 18-20: The Commands `*write-about` and `*review-copy` declared in
the "## Commands" / "## Workflow" sections are not mapped to any task entries in
"Dependencies", causing unresolved command paths at runtime; either add matching
task definitions for these commands in the Dependencies block (create tasks
named write-about and review-copy or whatever the squad uses as task IDs and
include their metadata) or remove both commands from the Commands and Workflow
sections if they are intentionally unsupported; update any references to these
symbols (e.g., `*write-about`, `*review-copy`, Commands/Workflow, Dependencies)
so every declared command has a corresponding dependency task.
- Around line 23-25: Add a language identifier "text" to the fenced code block
containing the workflow line so the markdown linter MD040 is satisfied; locate
the fenced block that contains the sequence "*write-headline → *write-copy →
*write-cta → *review-copy" and change its opening fence from ``` to ```text
(leave the content and closing fence unchanged).
In `@squads/professional-web-squad/agents/discovery.md`:
- Line 18: The Commands list contains `*project-scope` (and similar entries
around the 28-31 area) but there is no corresponding task declared under `##
Dependencies`; remove `*project-scope` from the `## Commands` section or add a
matching dependency/task entry under `## Dependencies` so every command has a
backing task (look for the `*project-scope` token and the `## Commands` / `##
Dependencies` headers to locate and fix).
- Around line 22-24: Wrap the workflow line "*briefing → *define-persona →
*define-value-proposition → *competitor-analysis" in a fenced code block with
the language label text (use ```text ... ```), replacing the inline/backtick
rendering so the markdown linter (MD040) is satisfied and the content remains
unchanged; ensure you include both opening and closing triple backticks and
preserve the exact arrowed sequence.
In `@squads/professional-web-squad/agents/seo-specialist.md`:
- Around line 17-19: The Commands list includes `*optimize-performance` and
`*generate-schema-markup` but there are no corresponding task entries under the
Dependencies section, breaking the task-first command mapping; either add
Dependency task entries named/identified for optimize-performance and
generate-schema-markup (with the expected task details and identifiers) so each
command maps to its task, or remove these two commands from the "## Commands"
section if they are not intended for v1; update any references in Dependencies
and Commands to keep names consistent (look for the `*optimize-performance`,
`*generate-schema-markup`, `## Commands`, and `Dependencies` identifiers).
- Around line 23-25: Add a language tag to the fenced code block that contains
the workflow arrow sequence "*keyword-research → *write-meta → *audit-seo →
*check-core-web-vitals" (e.g., change ``` to ```text) so the Markdown linter
rule MD040 (`fenced-code-language`) is satisfied; edit the code fence around
that exact sequence in the SEO specialist workflow to include the language tag.
In `@squads/professional-web-squad/agents/ui-ux-expert.md`:
- Around line 24-26: The fenced code block containing "*create-moodboard →
*color-palette → *typography-scale → *design-system → *ui-review" needs a
neutral language tag to satisfy markdownlint MD040; update the fence from ``` to
```text so the block becomes a labeled text code fence (i.e., change the opening
triple backticks to ```text) in the UI/UX expert doc where that snippet appears.
In `@squads/professional-web-squad/agents/web-designer.md`:
- Around line 23-25: Add the missing fenced-block language to the Markdown code
fence that contains the workflow sequence "*plan-sections → *create-wireframe →
*define-style-guide → *optimize-above-fold" (the code block surrounding that
sequence); specify "text" after the opening triple backticks so the fence
becomes ```text to satisfy MD040 and make the block language explicit.
In `@squads/professional-web-squad/config/coding-standards.md`:
- Around line 19-30: The fenced code block that shows the directory tree (the
block beginning with ``` and the line "projeto/") is missing a language
specifier; update the opening fence to ```text so the directory tree is treated
as plain text (resolving MD040) while keeping the block contents unchanged.
In `@squads/professional-web-squad/config/source-tree.md`:
- Around line 5-31: The fenced code block in
squads/professional-web-squad/config/source-tree.md is missing a language
specifier (violates MD040); update the opening fence from ``` to ```text so the
ASCII tree is treated as plain text (preserve the existing tree content and
comments), then commit the change referencing the fenced block
(triple-backticks) and MD040 in your commit message.
In `@squads/professional-web-squad/README.md`:
- Around line 17-26: The fenced workflow block beginning with "1. `@discovery` →
*briefing → *define-persona → *define-value-proposition" is missing a language
identifier which triggers MD040; update that fenced code block in README.md by
adding a language tag (e.g., ```text or ```md) immediately after the opening
backticks so the block becomes ```text and the rest of the workflow lines remain
unchanged, ensuring the linter no longer flags the fenced-code-language issue.
In `@squads/professional-web-squad/tasks/copywriter-create-story.md`:
- Around line 30-39: The fenced code block containing the three-act framework
(the triple-backtick block with "Ato 1 — CONTEXTO" / "Ato 2 — CONFLITO" / "Ato 3
— RESOLUÇÃO") is unlabeled and triggers markdownlint MD040; fix it by adding a
language label (e.g., change ``` to ```text) so the block is explicitly typed,
ensuring the block remains otherwise unchanged and the linter warning is
resolved.
In `@squads/professional-web-squad/tasks/discovery-define-value-proposition.md`:
- Around line 30-34: The fenced code block containing the value-proposition
template (the block starting with "Para [persona] que [dor/necessidade],") is
missing a language tag which triggers markdownlint MD040; update the opening
triple-backtick to include a language tag (e.g., ```text) so the block becomes a
labeled fenced code block and run the linter again to confirm the MD040 warning
is resolved.
In `@squads/professional-web-squad/tasks/seo-check-core-web-vitals.md`:
- Line 12: O campo de saída identificado como scores_cwv contém o texto
"FID/INP" e deve ser padronizado para "INP" para refletir a métrica atual;
localize onde scores_cwv é definido/emitido (procure a chave scores_cwv no
arquivo) e substitua qualquer ocorrência de "FID/INP" por "INP" garantindo que a
alteração seja consistente com o restante do checklist e tabelas do documento.
In `@squads/professional-web-squad/tasks/ui-ux-create-moodboard.md`:
- Around line 31-35: O bloco de código fenced não especifica linguagem e ativa a
regra MD040; atualize o fence de ``` para ```text (por exemplo, alterar ``` ...
``` para ```text ... ```) no trecho que contém as linhas "Moderno | Elegante |
Bold..." para suprimir o lint e preservar o conteúdo; mantenha o conteúdo
interno idêntico e apenas acrescente o identificador de linguagem após os três
acentos graves de abertura.
In `@squads/professional-web-squad/tasks/web-designer-create-wireframe.md`:
- Around line 29-42: The fenced ASCII wireframe block (the triple-backtick fence
enclosing the diagram) is missing a language token and triggers MD040; add a
language identifier (e.g., use "text") immediately after the opening ``` so the
block becomes ```text to satisfy the linter and preserve formatting for the
ASCII wireframe.
In `@squads/professional-web-squad/tasks/web-designer-plan-sections.md`:
- Around line 30-41: The fenced code block that lists the section numbers is
missing a language identifier (the opening ``` fence), which triggers MD040;
update the opening fence by adding a language token such as text (i.e., replace
the plain ``` with ```text) so the block becomes a labeled code block and
satisfies markdownlint. Locate the code fence that wraps the list (the ``` block
that begins before "1. Hero" and ends after "10. Rodapé") and add the language
identifier to the opening fence.
---
Nitpick comments:
In `@squads/professional-web-squad/tasks/seo-audit.md`:
- Line 45: Replace the checklist item "Densidade de keyword 1-2%" with a modern
guideline: remove the fixed numeric density rule and instead state that audits
should verify semantic coverage and alignment with search intent (e.g.,
"Priorize cobertura semântica e alinhamento com a intenção de busca; evite
regras fixas de densidade de keywords que incentivem keyword stuffing"). Update
any related checklist logic or documentation that references "Densidade de
keyword 1-2%" to reference the new guidance.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 1f7f0733-4f64-406a-a719-380a1a113cd7
📒 Files selected for processing (36)
squads/professional-web-squad/README.mdsquads/professional-web-squad/agents/copywriter.mdsquads/professional-web-squad/agents/discovery.mdsquads/professional-web-squad/agents/seo-specialist.mdsquads/professional-web-squad/agents/ui-ux-expert.mdsquads/professional-web-squad/agents/web-designer.mdsquads/professional-web-squad/checklists/.gitkeepsquads/professional-web-squad/config/coding-standards.mdsquads/professional-web-squad/config/source-tree.mdsquads/professional-web-squad/config/tech-stack.mdsquads/professional-web-squad/data/.gitkeepsquads/professional-web-squad/scripts/.gitkeepsquads/professional-web-squad/squad.yamlsquads/professional-web-squad/tasks/copywriter-create-story.mdsquads/professional-web-squad/tasks/copywriter-write-copy.mdsquads/professional-web-squad/tasks/copywriter-write-cta.mdsquads/professional-web-squad/tasks/copywriter-write-headline.mdsquads/professional-web-squad/tasks/discovery-briefing.mdsquads/professional-web-squad/tasks/discovery-competitor-analysis.mdsquads/professional-web-squad/tasks/discovery-define-persona.mdsquads/professional-web-squad/tasks/discovery-define-value-proposition.mdsquads/professional-web-squad/tasks/seo-audit.mdsquads/professional-web-squad/tasks/seo-check-core-web-vitals.mdsquads/professional-web-squad/tasks/seo-keyword-research.mdsquads/professional-web-squad/tasks/seo-write-meta.mdsquads/professional-web-squad/tasks/ui-ux-color-palette.mdsquads/professional-web-squad/tasks/ui-ux-create-moodboard.mdsquads/professional-web-squad/tasks/ui-ux-review.mdsquads/professional-web-squad/tasks/ui-ux-typography-scale.mdsquads/professional-web-squad/tasks/web-designer-create-wireframe.mdsquads/professional-web-squad/tasks/web-designer-define-style-guide.mdsquads/professional-web-squad/tasks/web-designer-optimize-above-fold.mdsquads/professional-web-squad/tasks/web-designer-plan-sections.mdsquads/professional-web-squad/templates/.gitkeepsquads/professional-web-squad/tools/.gitkeepsquads/professional-web-squad/workflows/.gitkeep
Comment on lines
+18
to
+20
| - `*write-about` — Escrever seção Sobre / Quem Somos | ||
| - `*review-copy` — Revisar e otimizar copy existente | ||
|
|
There was a problem hiding this comment.
Map every declared command to a task dependency (or remove unsupported commands).
*write-about and *review-copy are exposed in Commands/Workflow, but no corresponding task files are declared in Dependencies. In a task-first squad, this creates unresolved command paths at runtime.
Suggested direction
## Dependencies
- tasks/copywriter-write-headline.md
- tasks/copywriter-write-copy.md
- tasks/copywriter-create-story.md
- tasks/copywriter-write-cta.md
+ - tasks/copywriter-write-about.md
+ - tasks/copywriter-review-copy.mdIf those tasks are intentionally out of scope, remove the two commands from ## Commands and ## Workflow instead.
Also applies to: 24-24, 29-32
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@squads/professional-web-squad/agents/copywriter.md` around lines 18 - 20, The
Commands `*write-about` and `*review-copy` declared in the "## Commands" / "##
Workflow" sections are not mapped to any task entries in "Dependencies", causing
unresolved command paths at runtime; either add matching task definitions for
these commands in the Dependencies block (create tasks named write-about and
review-copy or whatever the squad uses as task IDs and include their metadata)
or remove both commands from the Commands and Workflow sections if they are
intentionally unsupported; update any references to these symbols (e.g.,
`*write-about`, `*review-copy`, Commands/Workflow, Dependencies) so every
declared command has a corresponding dependency task.
Comment on lines
+23
to
+25
| ``` | ||
| *write-headline → *write-copy → *write-cta → *review-copy | ||
| ``` |
There was a problem hiding this comment.
Add a language identifier to the workflow fenced block.
This triggers MD040; use text.
Suggested diff
-```
+```text
*write-headline → *write-copy → *write-cta → *review-copy</details>
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 markdownlint-cli2 (0.22.1)</summary>
[warning] 23-23: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
</details>
</details>
<details>
<summary>🤖 Prompt for AI Agents</summary>
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @squads/professional-web-squad/agents/copywriter.md around lines 23 - 25, Add
a language identifier "text" to the fenced code block containing the workflow
line so the markdown linter MD040 is satisfied; locate the fenced block that
contains the sequence "*write-headline → *write-copy → *write-cta →
*review-copy" and change its opening fence from totext (leave the
content and closing fence unchanged).
</details>
<!-- fingerprinting:phantom:triton:hawk -->
<!-- This is an auto-generated comment by CodeRabbit -->
| - `*define-persona` — Definir persona e público-alvo | ||
| - `*define-value-proposition` — Definir proposta de valor e diferenciais | ||
| - `*competitor-analysis` — Analisar concorrentes do segmento | ||
| - `*project-scope` — Definir escopo e objetivos do projeto |
There was a problem hiding this comment.
*project-scope is declared without a backing task dependency.
This breaks task-first consistency: the agent advertises a command that has no mapped task file in ## Dependencies.
Suggested diff
## Dependencies
- tasks/discovery-briefing.md
- tasks/discovery-define-persona.md
- tasks/discovery-define-value-proposition.md
- tasks/discovery-competitor-analysis.md
+ - tasks/discovery-project-scope.mdIf not intended, remove *project-scope from ## Commands.
Also applies to: 28-31
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@squads/professional-web-squad/agents/discovery.md` at line 18, The Commands
list contains `*project-scope` (and similar entries around the 28-31 area) but
there is no corresponding task declared under `## Dependencies`; remove
`*project-scope` from the `## Commands` section or add a matching
dependency/task entry under `## Dependencies` so every command has a backing
task (look for the `*project-scope` token and the `## Commands` / `##
Dependencies` headers to locate and fix).
Comment on lines
+22
to
+24
| ``` | ||
| *briefing → *define-persona → *define-value-proposition → *competitor-analysis | ||
| ``` |
There was a problem hiding this comment.
Add fenced-block language for workflow.
MD040 warning applies; use text.
Suggested diff
-```
+```text
*briefing → *define-persona → *define-value-proposition → *competitor-analysis</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 22-22: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@squads/professional-web-squad/agents/discovery.md` around lines 22 - 24, Wrap
the workflow line "*briefing → *define-persona → *define-value-proposition →
*competitor-analysis" in a fenced code block with the language label text (use
```text ... ```), replacing the inline/backtick rendering so the markdown linter
(MD040) is satisfied and the content remains unchanged; ensure you include both
opening and closing triple backticks and preserve the exact arrowed sequence.
Comment on lines
+17
to
+19
| - `*optimize-performance` — Otimizar performance e velocidade | ||
| - `*check-core-web-vitals` — Verificar métricas Core Web Vitals (LCP, FID, CLS) | ||
| - `*generate-schema-markup` — Gerar marcação Schema.org estruturada |
There was a problem hiding this comment.
Two public commands are missing task dependencies.
*optimize-performance and *generate-schema-markup are documented commands but have no corresponding task entries in Dependencies, which violates task-first command mapping.
Suggested direction
## Dependencies
- tasks/seo-keyword-research.md
- tasks/seo-write-meta.md
- tasks/seo-audit.md
- tasks/seo-check-core-web-vitals.md
+ - tasks/seo-optimize-performance.md
+ - tasks/seo-generate-schema-markup.mdIf those tasks are not intended for v1, remove both commands from ## Commands.
Also applies to: 29-32
🧰 Tools
🪛 LanguageTool
[locale-violation] ~17-~17: “performance” é um estrangeirismo. É preferível dizer “desempenho”, “atuação”, “apresentação”, “espetáculo” ou “interpretação”.
Context: ...na - *optimize-performance — Otimizar performance e velocidade - *check-core-web-vitals...
(PT_BARBARISMS_REPLACE_PERFORMANCE)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@squads/professional-web-squad/agents/seo-specialist.md` around lines 17 - 19,
The Commands list includes `*optimize-performance` and `*generate-schema-markup`
but there are no corresponding task entries under the Dependencies section,
breaking the task-first command mapping; either add Dependency task entries
named/identified for optimize-performance and generate-schema-markup (with the
expected task details and identifiers) so each command maps to its task, or
remove these two commands from the "## Commands" section if they are not
intended for v1; update any references in Dependencies and Commands to keep
names consistent (look for the `*optimize-performance`,
`*generate-schema-markup`, `## Commands`, and `Dependencies` identifiers).
Comment on lines
+30
to
+34
| ``` | ||
| Para [persona] que [dor/necessidade], | ||
| [produto/serviço] oferece [benefício principal] | ||
| diferente de [alternativa], porque [diferencial único]. | ||
| ``` |
There was a problem hiding this comment.
Add a language tag to the fenced framework block.
Line 30 opens a code fence without language, which triggers markdownlint MD040.
Suggested fix
-```
+```text
Para [persona] que [dor/necessidade],
[produto/serviço] oferece [benefício principal]
diferente de [alternativa], porque [diferencial único].</details>
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 markdownlint-cli2 (0.22.1)</summary>
[warning] 30-30: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
</details>
</details>
<details>
<summary>🤖 Prompt for AI Agents</summary>
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @squads/professional-web-squad/tasks/discovery-define-value-proposition.md
around lines 30 - 34, The fenced code block containing the value-proposition
template (the block starting with "Para [persona] que [dor/necessidade],") is
missing a language tag which triggers markdownlint MD040; update the opening
triple-backtick to include a language tag (e.g., ```text) so the block becomes a
labeled fenced code block and run the linter again to confirm the MD040 warning
is resolved.
</details>
<!-- fingerprinting:phantom:triton:hawk -->
<!-- This is an auto-generated comment by CodeRabbit -->
| Entrada: | | ||
| - url_pagina: URL da página publicada | ||
| Saida: | | ||
| - scores_cwv: Scores de LCP, FID/INP e CLS |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Core Web Vitals currently use which interaction metric in ranking/reporting: FID or INP?
💡 Result:
Core Web Vitals currently use INP (Interaction to Next Paint), not FID (First Input Delay). Evidence: web.dev states that INP “officially become[s] a Core Web Vital and replace[s] FID” (with FID deprecated/removed from the program) as of March 12, 2024 [1], and Google’s Search Central docs say INP is the Core Web Vitals interactivity metric used for Search [2]. Google Search Console’s Core Web Vitals report also lists INP as the interactivity metric in its reporting (along with LCP and CLS) [3].
Citations:
- 1: https://web.dev/blog/inp-cwv-march-12
- 2: https://developers.google.com/search/docs/appearance/core-web-vitals
- 3: https://support.google.com/webmasters/answer/9205520?hl=en
🏁 Script executed:
#!/bin/bash
set -euo pipefail
file="squads/professional-web-squad/tasks/seo-check-core-web-vitals.md"
echo "== File: $file =="
nl -ba "$file" | sed -n '1,80p'
echo
echo "== Occurrences of FID/FID/INP/INP in file =="
rg -n "FID/INP|FID|INP" "$file" || trueRepository: SynkraAI/aiox-squads
Length of output: 202
🏁 Script executed:
#!/bin/bash
set -euo pipefail
file="squads/professional-web-squad/tasks/seo-check-core-web-vitals.md"
echo "== Preview: $file =="
if [ -f "$file" ]; then
sed -n '1,80p' "$file"
else
echo "File not found: $file"
fi
echo
echo "== Grep for FID/FID/INP/INP in file =="
if command -v rg >/dev/null 2>&1; then
rg -n "FID/INP|\\bFID\\b|INP" "$file" || true
else
grep -nE "FID/INP|\\bFID\\b|INP" "$file" || true
fiRepository: SynkraAI/aiox-squads
Length of output: 1912
Padronizar “scores_cwv” para INP (remover “FID/INP”)
O campo de saída usa “FID/INP”, enquanto o restante do arquivo (checklist e tabelas) já padroniza para INP; além disso, o FID foi substituído pelo INP como métrica de interatividade do Core Web Vitals.
♻️ Proposta de ajuste
- - scores_cwv: Scores de LCP, FID/INP e CLS
+ - scores_cwv: Scores de LCP, INP e CLS📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - scores_cwv: Scores de LCP, FID/INP e CLS | |
| - scores_cwv: Scores de LCP, INP e CLS |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@squads/professional-web-squad/tasks/seo-check-core-web-vitals.md` at line 12,
O campo de saída identificado como scores_cwv contém o texto "FID/INP" e deve
ser padronizado para "INP" para refletir a métrica atual; localize onde
scores_cwv é definido/emitido (procure a chave scores_cwv no arquivo) e
substitua qualquer ocorrência de "FID/INP" por "INP" garantindo que a alteração
seja consistente com o restante do checklist e tabelas do documento.
Comment on lines
+31
to
+35
| ``` | ||
| Moderno | Elegante | Bold | Minimalista | Vibrante | ||
| Profissional | Amigável | Premium | Jovem | Confiável | ||
| Tecnológico | Natural | Orgânico | Limpo | Dinâmico | ||
| ``` |
There was a problem hiding this comment.
Adicione linguagem no fenced code block.
O bloco sem linguagem aciona lint (MD040).
🛠️ Proposta de ajuste
-```
+```text
Moderno | Elegante | Bold | Minimalista | Vibrante
Profissional | Amigável | Premium | Jovem | Confiável
Tecnológico | Natural | Orgânico | Limpo | Dinâmico</details>
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 markdownlint-cli2 (0.22.1)</summary>
[warning] 31-31: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
</details>
</details>
<details>
<summary>🤖 Prompt for AI Agents</summary>
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @squads/professional-web-squad/tasks/ui-ux-create-moodboard.md around lines
31 - 35, O bloco de código fenced não especifica linguagem e ativa a regra
MD040; atualize o fence de paratext (por exemplo, alterar ...
para text ... ) no trecho que contém as linhas "Moderno | Elegante |
Bold..." para suprimir o lint e preservar o conteúdo; mantenha o conteúdo
interno idêntico e apenas acrescente o identificador de linguagem após os três
acentos graves de abertura.
</details>
<!-- fingerprinting:phantom:triton:hawk -->
<!-- This is an auto-generated comment by CodeRabbit -->
Comment on lines
+29
to
+42
| ``` | ||
| ┌─────────────────────────────────────┐ | ||
| │ [LOGO] [MENU] [CTA] │ ← Nav: sticky, CTA destaque | ||
| ├─────────────────────────────────────┤ | ||
| │ │ | ||
| │ [HEADLINE PRINCIPAL] │ ← H1: acima da dobra | ||
| │ [Subheadline de apoio] │ | ||
| │ │ | ||
| │ [CTA PRIMÁRIO] [CTA SECUNDÁRIO] │ ← CTAs: 40px height mín. | ||
| │ │ | ||
| │ [Imagem Hero / Vídeo] │ ← Visual: direita no desktop | ||
| │ │ | ||
| └─────────────────────────────────────┘ | ||
| ``` |
There was a problem hiding this comment.
Specify the fenced code language for the ASCII wireframe block.
Line 29 is missing a language token, causing MD040 lint warnings.
Suggested fix
-```
+```text
┌─────────────────────────────────────┐
│ [LOGO] [MENU] [CTA] │ ← Nav: sticky, CTA destaque
├─────────────────────────────────────┤
│ │
│ [HEADLINE PRINCIPAL] │ ← H1: acima da dobra
│ [Subheadline de apoio] │
│ │
│ [CTA PRIMÁRIO] [CTA SECUNDÁRIO] │ ← CTAs: 40px height mín.
│ │
│ [Imagem Hero / Vídeo] │ ← Visual: direita no desktop
│ │
└─────────────────────────────────────┘</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 29-29: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@squads/professional-web-squad/tasks/web-designer-create-wireframe.md` around
lines 29 - 42, The fenced ASCII wireframe block (the triple-backtick fence
enclosing the diagram) is missing a language token and triggers MD040; add a
language identifier (e.g., use "text") immediately after the opening ``` so the
block becomes ```text to satisfy the linter and preserve formatting for the
ASCII wireframe.
Comment on lines
+30
to
+41
| ``` | ||
| 1. Hero → Capturar atenção (acima da dobra) | ||
| 2. Problema → Identificar a dor do visitante | ||
| 3. Solução → Apresentar o produto/serviço | ||
| 4. Benefícios → Detalhar o valor entregue | ||
| 5. Como funciona → Reduzir fricção e incerteza | ||
| 6. Prova social → Depoimentos e resultados | ||
| 7. Oferta/Preço → Apresentar a proposta comercial | ||
| 8. FAQ → Quebrar objeções finais | ||
| 9. CTA Final → Provocar a conversão | ||
| 10. Rodapé → Confiança e informações legais | ||
| ``` |
There was a problem hiding this comment.
Add language identifier to fenced code block.
Line 30 opens a fenced block without a language, which triggers MD040 and can break markdownlint quality gates.
Suggested fix
-```
+```text
1. Hero → Capturar atenção (acima da dobra)
2. Problema → Identificar a dor do visitante
3. Solução → Apresentar o produto/serviço
4. Benefícios → Detalhar o valor entregue
5. Como funciona → Reduzir fricção e incerteza
6. Prova social → Depoimentos e resultados
7. Oferta/Preço → Apresentar a proposta comercial
8. FAQ → Quebrar objeções finais
9. CTA Final → Provocar a conversão
10. Rodapé → Confiança e informações legais</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 30-30: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@squads/professional-web-squad/tasks/web-designer-plan-sections.md` around
lines 30 - 41, The fenced code block that lists the section numbers is missing a
language identifier (the opening ``` fence), which triggers MD040; update the
opening fence by adding a language token such as text (i.e., replace the plain
``` with ```text) so the block becomes a labeled code block and satisfies
markdownlint. Locate the code fence that wraps the list (the ``` block that
begins before "1. Hero" and ends after "10. Rodapé") and add the language
identifier to the opening fence.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New Squad: professional-web-squad
Version: 1.0.0
Author: Lucas
Category: community
Description: Squad especializado em criação de sites e landing pages profissionais de alta conversão
Agents (5)
Components
Pre-submission Checklist
*validate-squad(0 errors, 0 warnings)Submitted via
*publish-squadfrom AIOS-FullStackSummary by CodeRabbit