collisionengineers

Current Box REST API reference for collisionspike archive integration, including server-side CCG authentication, folders, file requests, shared links, webhook signatures, retry behavior, and least-privilege scopes. Use when building or validating services/functions/box-webhook or an archive caller.

EVA Sentry API v1.2 reference for collisionspike, covering authentication, the eight endpoint families, the canonical twelve-field payload, image ordering, idempotency, and server-side submission. Use when changing EVA contracts, services/functions/eva-sentry, or any submission caller.

Distills operator drop-notes and sample emails/documents into new collisionspike tickets under the status-folder system (docs/tickets/backlog|blocked|next|now|verify|done/TKT-NNN folders with frontmatter, evidence/, changes.md, verification.md) and adds them to BOARD.md. Use when creating a ticket from raw operator material, a new work-todo-spike stub, or a small new work item.

Implements and closes collisionspike tickets (TKT-NNN) in the status-folder ticket system — reads the ticket spec/research/plan, verifies live facts against the registry, routes work by area, records changes.md and verification.md, and changes status with scripts/maintenance/ticket-move.mjs. Use when picking up, finishing, verifying, or moving a ticket, or when the user references TKT-NNN or docs/tickets/.

Orchestrates collisionspike ticket work by dispatching agents — routes a ticket's area to the right specialist (azure-integration-engineer, fluent-spa-designer, box-integration-architect, eva-sentry-integration) or the ticket-implementer fallback, enforces the lifecycle transition graph and the verify→done separation of duties via the read-only ticket-verifier, and runs batch modes (verify-sweep, work-batch). Use for delegated or multi-ticket execution; for working one ticket inline yourself use ticket-implement.

Creates and maintains docs/tickets/plans/PLAN-NNN plans that cluster related collisionspike tickets. Use for multi-ticket operator plans, plan lifecycle updates, bidirectional plan/ticket links, and closing plans when all member tickets are done.

UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

Current Box REST API reference for collisionspike archive integration, including server-side CCG authentication, folders, file requests, shared links, webhook signatures, retry behavior, and least-privilege scopes. Use when building or validating services/functions/box-webhook or an archive caller.

Collision Engineers house style and branded document generation. Use whenever a CE output needs the house visual layout, the house writing tone, or a branded document built. Modes: document-builder generates branded DOCX and PDF (letters, reports, fee notes, certificates) from a JSON spec via a self-contained ReportLab/python-docx engine with no external service; visual-layout for logo, typography, page headers/footers, brand red, and templates; writing-tone for the plain independent-engineer register, dispute/TPI wording, and anti-AI phrasing checks. Use this skill whenever you draft, brand, or format any CE client, court, insurer, valuation, repair, rebuttal, roadworthy, fee-note or invoice document, even if "house style" is not mentioned. Consumed by vehicle-valuation, damage-estimating, rebuttal, roadworthy, finance-document, and invoice drafts.

Shared reference for current UK collision-repair charges from the ABP Club rate book (2026 edition). Use whenever a skill needs labour rates, the repair-plan fee, ADAS calibration charges, EV/hybrid handling, alloy/alignment/air-con/recovery/storage specialist charges, paint-protection or mobility charges, or the regional uplift - to build or challenge a repair estimate, total-loss assessment, finance document, or diminution rebuttal. Consumed by damage-estimating, rebuttal, roadworthy, and finance-document. Reference data, not an output-producing skill.

Use for UK collision damage estimating work: standalone repair estimates, EVA/Audatex total-loss damage assessments, AZT paint costing, ABP charge review, and estimate challenge support. Modes: repair-estimate, eva-total-loss, paint-costing, charge-review. Expert modes produce AI-assisted drafts until named-human sign-off; paint and charge-review modes are assistive inputs.

Use to draft Collision Engineers finance documents: fee-note, standard-audatex-invoice, website-invoice, and invoice-email-draft. Produces document drafts only; billing workflow, ledger, payment status, approvals, and chasing remain owned by finance/business. Human review required before send.

Shared reference library of vehicle-manufacturer (OEM) repair position statements - wheel and tyre reconditioning prohibitions, genuine-parts policies, and authoritative repair-procedure sources (erWin, ElsaPro, VIDA). Use whenever a repair estimate, total-loss assessment, or roadworthy certificate must respect an OEM constraint, e.g. confirming a damaged alloy must be replaced (not refurbished) or that only genuine parts are approved. Consumed by roadworthy and damage-estimating. Reference data, not an output-producing skill.

Use when drafting a Collision Engineers rebuttal to a diminution-in-value claim (e.g. an EVA / Exclusive Vehicle Assessors diminution report) for an instructing solicitor. Produces a CPR Part 35-style rebuttal report in CE house style. Triggers on "diminution", "rebuttal", "diminution in value", "EVA diminution".

Use when generating an HS (Hackney Solutions) roadworthy certificate from an engineer's accident-damage report (PDF or docx). Extracts the required fields from the report and fills the roadworthy docx template. Triggers on "roadworthy", "roadworthy certificate", "HS roadworthy", "taxi / private-hire roadworthy".

Determine the ABI salvage category (A / B / S / N) for a damaged vehicle using the ABI Code of Practice, with a reasoned justification and the regulatory notification obligations (MIAFTR, V5C/DVLA, Certificate of Destruction). Use when assessing whether a vehicle is scrap, break, repairable-structural, or repairable-non-structural, including EV high-voltage battery cases and water/fire damage. Expert class - the output is an AI-assisted draft until a named, appropriately qualified person signs off.