Developer — Platform Engineer

Role: Engineer building and maintaining the Forms Lab platform

Background

Builds and maintains the system. Uses the catalog as the primary reference for architecture, conventions, component APIs, and design decisions. Works with Claude Code to implement user stories.

Goals

• Understand system architecture and design patterns
• Follow established conventions and patterns
• Implement features that integrate cleanly
• Document decisions and maintain architectural coherence

Needs

• Architecture documentation (layers, data flow, boundaries)
• Coding conventions (file organization, patterns, testing)
• Component APIs and usage examples
• Design decisions (ADRs) with rationale
• Implementation patterns and templates

How the Catalog Helps

• Architecture Docs: System overview, data model, integration points
• Conventions: File organization, service patterns, testing strategy
• Patterns: Templates for common tasks (add LLM service, delivery adapter)
• Decisions: ADRs for significant choices
• Component Docs: Live examples rendered from actual components

Pain Points

• Needs to maintain consistency across stories
• Must understand architectural patterns to integrate features
• Requires clear conventions to avoid ad-hoc decisions
• Needs visibility into design rationale for informed changes