From rtl-agent-team
Provides reference policy for Phase 6 RTL design reviews: rules, design note requirements, consistency protocols, PDF generation pipeline, escalation rules, checklists.
npx claudepluginhub babyworm/rtl-agent-team --plugin rtl-agent-teamThis skill uses the workspace's default tool permissions.
Phase 4/5 gate reviews focus on spec compliance and functional correctness.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Phase 4/5 gate reviews focus on spec compliance and functional correctness. Phase 6 goes deeper:
Why 2-round consistency checks? Wave 1 and Wave 2 agents run independently — each produces its own scoring, terminology, and severity labels. Without consistency enforcement, the same issue may be rated HIGH in one document and MEDIUM in another, or identical concepts named differently across documents.
Why decision rationale in design notes? A design note that only describes WHAT was built is half the story. Future engineers need:
reviews/phase-5-verify/final-compliance.md must exist AND verdict=PASSmake pdf in reviews/phase-6-review/.rat/state/rat-auto-design-state.json if running within autopilotMandatory content per module (all 10 items):
System-level sections: Architecture overview (D2), data/control flow, clock/reset architecture, mode operations, verification summary
Document Splitting Rules:
| Total Lines | Strategy | File Structure |
|---|---|---|
| <= 300 | Single file | design-note.md |
| 300 - 800 | 2-3 files | design-note-overview.md + design-note-{topic}.md + design-note-appendix.md |
| > 800 | Per-module files | design-note-overview.md + design-note-{module}.md per module + design-note-appendix.md |
| Check Item | What to Compare | Fix Action |
|---|---|---|
| Scoring scale | Both use 1-10 with same anchor points | Normalize to shared scale |
| Severity labels | HIGH/MEDIUM/LOW applied consistently | Re-rate using shared criteria |
| Terminology | Same concepts named identically | Adopt canonical terms |
| Finding overlap | Same issue in both reviews | Add cross-references |
| Module names | Consistent module naming | Standardize to rtl/ directory names |
| Check Item | What to Compare | Fix Action |
|---|---|---|
| Narrative coherence | Story told consistently across docs | Align narrative arc |
| Traceability | Every improvement traces to a finding | Add missing traces |
| Completeness | Design note covers all reviewed modules | Add missing modules |
| Terminology | All docs use same terms | Global terminology pass |
| No contradictions | No conflicting statements | Resolve conflicts |
| Diagram consistency | D2/Mermaid match textual descriptions | Update mismatched diagrams |
CC log format (appended to each corrected document):
## Consistency Check {N} Log
- Date: YYYY-MM-DD
- Items checked: {count}
- Inconsistencies found: {count}
- Corrections applied: {list}
Usage:
cd reviews/phase-6-review
make pdf # Generate design-note.pdf
make clean # Remove generated files
make check-deps # Verify required tools
Required tools:
| Tool | Package | Purpose |
|---|---|---|
| pandoc | sudo apt install pandoc | Markdown to LaTeX |
| xelatex | sudo apt install texlive-xetex texlive-fonts-recommended | LaTeX to PDF |
| d2 | curl -fsSL https://d2lang.com/install.sh | sh -s -- | D2 block diagrams (optional) |
| mmdc | npm install -g @mermaid-js/mermaid-cli | Mermaid diagrams (optional) |
Pipeline: Discover design-note*.md → extract D2/Mermaid → render PNGs → replace blocks → combine → pandoc + xelatex → PDF with TOC
Phase 7 Exploration: For free exploration mode, see rtl-p7-exploration-policy.