EoT claim report engine (Time Impact Analysis in Windows) + FSDA reference studio.
skills/forensic-schedule-delay-analysis/— the portable skill:SKILL.md— workflow, JSON schema, QA checklist. Read this first.references/fsda-knowledge.md— methodology (SCL / AACE 29R-03, TIA-in-Windows, fragnets, concurrency, entitlement).assets/eot-report.js— dependency-free<eot-report>renderer (window.renderEOTReport(data)).assets/eot-data-sample.json— full worked example; copy →eot-data.jsonfor a new claim.assets/eot-report-template.html+assets/doc-page.js— plain-HTML printable entry point (open in a browser, print to PDF). No build step.
EOT Report (TIA in Windows).dc.html— live report page (Anthropic design-doc format; opens in a browser viasupport.js).FSDA Studio.dc.html— interactive reference: method families, selection wizard, worked examples, report builder. Content infsda-data.js,fsda-figures.js,fsda-cases.js._ds/— bound design system (Classical) used by the.dc.htmlpages.CLAUDE.md— project instructions for Claude (Claude Code / Cursor read this too).
Everything needed is self-contained:
- Read
CLAUDE.md, thenskills/forensic-schedule-delay-analysis/SKILL.md. - New report: copy
assets/eot-data-sample.json, fill it, point a copy ofeot-report-template.htmlat it. All content lives in the JSON — never hand-write report HTML. - Run the SKILL.md QA checklist before delivering (window sums = totals, base_w = impacted_{w-1}, dates reconcile).
- Never invent letter references or dates for real claims — ask for the contemporaneous records.
- Push (local → GitHub): commit and push from Claude Code / Cursor / any git client. From the Anthropic design app, download the project zip and push its contents.
- Pull (GitHub → design app): in the design app, ask to "sync from GitHub" — it reads
github.mdfor repo/branch/last commit and imports what changed. - After pushing, updating the
commit:line ingithub.md(full sha) keeps incremental syncs cheap.