Skip to content
Live nowSeason 2 · Episode 15 · Agentic Coding Guide
← Back to builds
Screenshot of Redteaming Co Learning Site

Redteaming Co Learning Site

by Sharon

★ 2.9 (9)

Voted by ₥AN$A, Air Planes, Auny 🧡, durdy, Hovhannes Mkhitaryan, kaleb, rookepoole, Smiley “MakeShif”, Wil

I built a red teaming collaboration site for a builder crew to test and work together in real time. When users land on the homepage, they can click LOGIN (DEMO), which uses a fake login flow (no auth backend yet) and routes them to a mission dashboard. The landing page is fully re-themed for red teaming, with sections focused on reporting findings, triage flow, collaboration, and team training. The dashboard gives the crew quick access to Bug Reports, Project Rooms, Training Labs, and Team Activity. This version is intentionally no-backend for speed, so we can test UX and team workflow first, then add real auth + database once the flow is validated.

Models
GPT-5.3-Codex (Factory Droid)
Cost
Estimated ~60k–120k tokens total across design + implementation iterations.
Prompts & issues

Main issues were scope and sequencing, not code complexity. - First pass was too “AI product” branded, so I did a full content/theme rewrite to a red teaming voice (mission control, report flow, triage, validation, resolution). - Needed a login-like flow without backend overhead, so I implemented a fake login button that sets a localStorage flag and routes users to /dashboard. - Build validation initially failed lint because eslint wasn’t installed in this shell setup, so I validated with production build (pnpm build) and confirmed all routes compiled. What worked: fast iteration on copy + UI structure first, then backend later after the team validates the workflow.