Field log · CC-1
Placeholder story, drafted from the project’s own docs, for Lukas to rewrite in his own words:
I joined the Capital Copilot team to handle the frontend, and got pulled into the agentic workflow. It was the first project that put me in it properly: agents writing code next to people, all day. I own the frontend styling and the frontend logic.
Capital Copilot makes your news into a show. You pick topics, sources, a voice and a length, and every day it writes and voices a Pulse: a short brief, podcast-style, built for exactly you. Around it sit podcast and blog generation, a fact-checked news feed and a market terminal with valuation and dividend dashboards.
Decisions
- One design language, for agents and people alike. My shared-component sweep became the house style: translucent tints over real surfaces, one shared component per pattern. The rule is written down so that agent-built and human-built screens can’t be told apart.
- Tint, never fill. Accent colours sit as thin translucent layers over the surface, never as solid blocks. Blue means safe; purple and orange mean it costs credits.
- The rules are checked, not hoped for. A pre-commit script enforces the spacing grid, the type scale, the radii, no raw colours and no
!important. - The taste gate. Tests passing isn’t done. Every component, and every state of it, goes on a showcase page and gets screenshotted at desktop and at 375px before it ships.
- Coverage only goes up. New code lands with at least 98% line coverage, checked per branch.
- Copy is data. The landing page’s headline lives in a file as two variants, so it can be A/B tested without touching the layout.