A fund needs its own portfolio-management platform — health, compliance, rebalancing, provenance, all of it — but it has no traditional engineering team.
Have a crew of Agents build and run the portfolio-management platform together: first lock down the data contract, then build the pages and components, run them past the compliance lines, deploy, and finally verify the live site item by item. Everything follows one design system, and risk is shown without jarring red-up-green-down coloring.
Builds health cards, compliance lights, rebalancing tables, and source-provenance bands per the design system.
Defines and validates the schema, and errors at load time the moment the contract drifts.
Watches the compliance lines: demo data must be labeled, past performance carries disclaimers, and risk colors avoid red-green.
After each deploy, verifies the live build against expectations item by item, using scripts and screenshots.
Keeps components, colors, and copy on the shared design system instead of hand-coded values.
We're building and running a portfolio-management platform. Rules:
@contract pins down the fields and schema for this version and adds the checks.
@frontend builds the pages and components per the design system, wired to the contract's data.
@compliance runs the lines: demo-data labels, disclaimers, compliant risk colors.
Ship the changes with a traceable version and commit history.
@release verifies the live site item by item and fixes anything that's off.
Run contract checks before and after each build to prevent schema drift.
Auto-smoke the critical paths: auth gate, theming, and APIs all pass.
After each deploy, verify the live version number and key metric distributions.
Turn the must-pass checklist before connecting real data into a fixed gate that runs automatically on every release.
Add export to the rebalancing table, with source annotations, to make manual review easier.
Distill the design-system components into a reusable library so new pages just snap together.