fba-compliance

Detect Feature-Based Architecture violations in Capo repository imports and exports.

2|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/mfuentesg/capo-app --skill fba-compliance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fba-compliance
Source: https://github.com/mfuentesg/capo-app/tree/main/.copilot/skills/fba-compliance
Command: npx skills add https://github.com/mfuentesg/capo-app --skill fba-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capo's FBA compliance checker helps teams identify and fix violations of the Feature-Based Architecture guidelines across the codebase.

Core Features & Use Cases

  • Enforces imports via public API roots to prevent tight coupling between features
  • Prevents subpath imports inside a feature
  • Ensures public APIs are re-exported from the feature root index.ts
  • Provides guided fixes and validation commands to maintain architectural integrity in the capo-app repository

Quick Start

Run the FBA compliance checker on your repository to identify violations and suggested fixes.

Frequently Asked Questions about fba-compliance

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

FAQPage Schema
How do I enforce Feature-Based Architecture compliance in a TypeScript repository?

Feature-Based Architecture compliance is enforced by statically analyzing the TypeScript project structure under features/ to validate imports, exports, and barrel patterns, then reporting violations and guided fixes.

How do I prevent subpath imports between features in TypeScript?

Preventing subpath imports requires checking that all feature dependencies route through public API roots instead of reaching into internal files, validating barrel patterns to ensure correct architecture and prevent tight coupling.

What is the best way to validate public API re-exports from feature root index.ts files?

Validating public API re-exports involves analyzing the feature root index.ts barrel file to ensure all public interfaces are correctly re-exported, identifying missing exports that violate FBA guidelines and suggesting fixes.

Does the FBA compliance checker work without external dependencies?

Yes, the FBA compliance checker operates without external dependencies, performing static analysis directly on the repository structure to identify architectural violations and propose guided fixes.

How do I fix tight coupling between features in a Capo repository?

Fixing tight coupling between features involves analyzing import patterns to ensure dependencies only use public API roots, preventing subpath imports and providing guided fixes to maintain architectural integrity.

When should I run an FBA compliance check on my codebase?

Running an FBA compliance check is needed when maintaining architectural integrity in a Capo repository, ensuring that imports via public API roots and barrel patterns correctly enforce Feature-Based Architecture guidelines.