skills.rest
linuxfoundation
linuxfoundationOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lfx-product-architect

Analyze LFX repository architecture to guide code placement and data flow.

8|1|Updated Mar 16, 2026
Search Tags:#architecture#data-flow#design-decisions#placement#repo-detection#lfx#read-only-guide
One-click install
npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-product-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lfx-product-architect
Source: https://github.com/linuxfoundation/lfx-skills/tree/main/lfx-product-architect
Command: npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-product-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help engineers decide where code should live in the LFX platform, trace data flows across services, and articulate design decisions. It provides a read-only analysis that guides architecture placements without generating code.

Core Features & Use Cases

  • Determine optimal module and repository ownership for new features spanning frontend and backend.
  • Map data flows across services (proxy, platform, resource services) to identify integration points and data ownership.
  • Provide rationale for architectural decisions to support onboarding, reviews, and maintenance.

Quick Start

Analyze a proposed feature and ask for the best placement within the LFX architecture.

Frequently Asked Questions about lfx-product-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide where new code should go in a microservices architecture?▼

Mapping data flows across proxy, platform, and resource services reveals integration points and data ownership boundaries, guiding architectural placement without modifying source code.

What is the best way to trace data paths across frontend and backend services?▼

Mapping data flows across proxy, platform, and resource services reveals integration points and data ownership boundaries, guiding architectural placement without modifying source code.

How do I document design rationales for repository placement decisions?▼

Yes, this read-only analysis supports onboarding, code reviews, and maintenance by articulating architectural design decisions and tracing data paths across services without generating or modifying source code.

Can I get architectural guidance for lfx-v2 without modifying existing source code?▼

Yes, this read-only analysis supports onboarding, code reviews, and maintenance by articulating architectural design decisions and tracing data paths across services without generating or modifying source code.

When do I need to analyze module ownership for platform integration points?▼

Analyze module ownership when determining optimal repository boundaries for new features, ensuring correct data ownership and interaction across proxy, platform, and resource services.

Related Skills

Explore More Software Engineering Skills→
linuxfoundationlinuxfoundation
8

lfx-research

Explore LFX repositories to validate API contracts and read architecture documents.

Official
Advanced
nicholasgriffintnnicholasgriffintn
2

performance-optimisation

Identify and fix performance bottlenecks across frontend, backend, and database layers.

Community
Basic
lightseekorglightseekorg
11

map

Map SMG crate ownership and inter-crate dependencies into a graph.

Official
Intermediate
daudaudinangdaudaudinang

gitnexus-exploring

Trace execution flows and outline architecture from GitNexus repository context.

Community
Intermediate