agentrc: Skill for Claude Code

You are debugging consistency between two readiness report outputs for the AgentRC project:

1. CLI visual report — generated by npm run dev -- readiness --visual from the repo root (produces an HTML file)
2. Webapp report — rendered by the local dev server at http://localhost:3000/{owner}/{repo}

Both should produce identical results for the same repository because they share the same core engine (packages/core/src/services/readiness.ts). In practice they can diverge due to rendering differences or scoring logic bugs.

Architecture Reference

Shared Core (source of truth for checks)

• packages/core/src/services/readiness.ts — All criteria definitions, countStatus(), buildCriteria(), buildExtras(), pillar/level aggregation
• Criteria scopes: repo (always), app (per-application), area (only with --per-area)
• countStatus() excludes skipped checks from the denominator when computing pillar pass/total
• Extras (bonus checks) are not scored — they don't affect levels or totals

CLI Rendering

• packages/core/src/services/visualReport.ts — Generates the standalone HTML report
• calculateAiToolingData() — Aggregates AI criteria across repos (counts all including skipped in the hero display)
• Total checks: report.pillars.reduce((s, p) => s + p.total, 0)
• Does not render bonus/extras section in HTML output

Webapp Backend

• webapp/backend/src/services/scanner.js — Clones repo, calls runReadinessReport() from @agentrc/core
• webapp/backend/src/routes/scan.js — POST /api/scan endpoint
• Returns the raw ReadinessReport JSON (same shape as CLI)
• Uses @agentrc/core as a file:../../packages/core dependency — always uses local source code

Webapp Frontend

• webapp/frontend/src/report.js — Independent rendering implementation (NOT shared with CLI)
• buildHero() — Total from report.pillars.reduce((s, p) => s + p.total, 0)
• buildAiToolingHero() — Renders all AI criteria (including skipped) with pass/total count
• buildPillarDetails() — Shows per-pillar expandable cards
• Does render bonus checks section (unlike CLI)
• Has Service Information section (policy chain, engine signals) — CLI doesn't