When is the best time to use Flow Architect?

Activate it during the brainstorming phase when discussing technology stacks, design patterns, system structure, or when you need to define what functionality is in scope for the current version.

How does it update my project?

It primarily updates the PLAN.md file, specifically the Architecture, Scope, and DO/DON'T Guideline sections, ensuring that the design rationale is captured before implementation begins.

Does it help with team consistency?

Yes, by documenting DO/DON'T guidelines with clear rationale and code examples, it creates a living style guide that helps all contributors follow the same architectural patterns.

What is the Flow Architect skill?

Flow Architect is a Claude Code capability that helps developers make and document architectural decisions using the Flow framework's iterative methodology.

What are 'Type B' subjects in this framework?

Type B subjects are documentation-only updates that resolve architectural questions or design decisions in PLAN.md without requiring immediate source code changes.

Flow Architect

Name: Flow Architect
Author: khgs2411

bykhgs2411

•

생산성 및 워크플로

Guides architectural decision-making and documents system design within the Flow framework to maintain long-term project clarity.

소개

Flow Architect is a specialized skill for Claude Code designed to bridge the gap between high-level brainstorming and structured documentation. It helps developers capture architectural rationale, define system boundaries, and establish coding guidelines (DO/DON'T rules) directly within a project's PLAN.md file. By focusing on documentation during the design phase rather than implementation, it ensures that technology choices, design patterns, and scope constraints are preserved as a 'source of truth' for the entire development lifecycle, preventing architectural drift and technical debt.

주요 기능

Formalized technology choice documentation including trade-off analysis and alternatives
Resolution of Type B subjects to finalize architectural decisions during brainstorming
Establishment of DO/DON'T guidelines with technical rationale and code examples
36 GitHub stars
Standardized PLAN.md architecture section updates for system structure and data flow
Clear definition of MVP scope boundaries versus future version enhancements

사용 사례

Creating a shared repository of team-wide coding patterns and anti-patterns for consistent development
Defining system components and module boundaries during the initial project setup
Evaluating and documenting the choice of third-party libraries, APIs, or database schemas

소개

주요 기능

Formalized technology choice documentation including trade-off analysis and alternatives
Resolution of Type B subjects to finalize architectural decisions during brainstorming
Establishment of DO/DON'T guidelines with technical rationale and code examples
36 GitHub stars
Standardized PLAN.md architecture section updates for system structure and data flow
Clear definition of MVP scope boundaries versus future version enhancements

사용 사례

Creating a shared repository of team-wide coding patterns and anti-patterns for consistent development
Defining system components and module boundaries during the initial project setup
Evaluating and documenting the choice of third-party libraries, APIs, or database schemas