@builder.io/dev-tools 1.22.2-dev.202602021932.a1fb74ebb → 1.22.2-dev.202602022342.768d3c452

package/types/cli/repo-indexing/types.d.ts

@@ -1,44 +1,44 @@
 import type { IndexDocumentV1 } from "$/ai-utils";
 interface BaseTask {
-	name: string;
+    name: string;
 }
 export interface ComponentTask extends BaseTask {
-	type: "component";
-	description: string;
-	relevantFiles: string[];
-	relatedComponents: string[];
-	designSystemPackage?: string;
-	designSystemVersion?: string;
-	hash: string;
+    type: "component";
+    description: string;
+    relevantFiles: string[];
+    relatedComponents: string[];
+    designSystemPackage?: string;
+    designSystemVersion?: string;
+    hash: string;
 }
 export interface TokenTask extends BaseTask {
-	type: "token";
-	relevantFiles: string[];
-	tokens: string[];
-	hash: string;
+    type: "token";
+    relevantFiles: string[];
+    tokens: string[];
+    hash: string;
 }
 export interface IconTask extends BaseTask {
-	type: "icon";
+    type: "icon";
 }
 export interface InstallationTask extends BaseTask {
-	type: "installation";
-	relevantFiles: string[];
-	hash: string;
+    type: "installation";
+    relevantFiles: string[];
+    hash: string;
 }
 export type Task = ComponentTask | TokenTask | IconTask | InstallationTask;
 export interface IndexingResults {
-	componentsToCheck: Task[];
-	storedComponentDocs: IndexDocumentV1[];
-	source: "custom" | "auto";
-	specificComponentNames?: string[];
-	summaryData?: {
-		indexedComponents: ComponentTask[];
-		discoveredComponents: ComponentTask[];
-		failedComponents: string[];
-		failedTokens: string[];
-		numIconsIndexed: number;
-		discoveredTokenGroups: TokenTask[];
-		tokenGroupsToIndex: TokenTask[];
-	};
+    componentsToCheck: Task[];
+    storedComponentDocs: IndexDocumentV1[];
+    source: "custom" | "auto";
+    specificComponentNames?: string[];
+    summaryData?: {
+        indexedComponents: ComponentTask[];
+        discoveredComponents: ComponentTask[];
+        failedComponents: string[];
+        failedTokens: string[];
+        numIconsIndexed: number;
+        discoveredTokenGroups: TokenTask[];
+        tokenGroupsToIndex: TokenTask[];
+    };
 }
 export {};

package/types/cli/repo-metrics-utils.d.ts

@@ -10,16 +10,14 @@ export declare function safeReadFile(filePath: string): string | null;
  * Package manager information
  */
 export interface PackageManagerInfo {
-	manager: "npm" | "yarn" | "pnpm" | "bun";
-	setupCommand: string;
+    manager: "npm" | "yarn" | "pnpm" | "bun";
+    setupCommand: string;
 }
 /**
  * Detect the package manager at the root level based on lock files
  * Returns the specific package manager command for setup
  */
-export declare function detectRootPackageManager(
-	files: string[],
-): PackageManagerInfo | null;
+export declare function detectRootPackageManager(files: string[]): PackageManagerInfo | null;
 /**
  * Check if a file exists at the root level
  */
@@ -27,14 +25,8 @@ export declare function hasRootFile(files: string[], fileName: string): boolean;
 /**
  * Check if any file matches a pattern at the root level
  */
-export declare function hasRootFileMatching(
-	files: string[],
-	predicate: (fileName: string) => boolean,
-): boolean;
+export declare function hasRootFileMatching(files: string[], predicate: (fileName: string) => boolean): boolean;
 /**
  * Check if a directory exists at the root level
  */
-export declare function hasRootDirectory(
-	files: string[],
-	directoryName: string,
-): boolean;
+export declare function hasRootDirectory(files: string[], directoryName: string): boolean;

package/types/cli/repo-metrics.d.ts

@@ -15,7 +15,4 @@ export declare function isExactVersion(version: string | undefined): boolean;
  * @param basePath - Absolute path to the repository root
  * @param rootPath - Relative path within the repository to analyze (default: "/" for entire repo)
  */
-export declare function collectRepoMetrics(
-	sys: DevToolsSys,
-	basePath: string,
-): Promise<RepoMetrics>;
+export declare function collectRepoMetrics(sys: DevToolsSys, basePath: string): Promise<RepoMetrics>;

package/types/cli/report/figma-report.d.ts

@@ -1,81 +1,54 @@
 import type { FigmaComponentInfo } from "$/ai-utils";
 import type { CLIArgs } from "..";
 import type { DevToolsSys } from "../../core";
-import type {
-	PublishedComponent,
-	PublishedComponentSet,
-} from "@figma/rest-api-spec";
+import type { PublishedComponent, PublishedComponentSet } from "@figma/rest-api-spec";
 type Context = {
-	sys: DevToolsSys;
-	args: CLIArgs;
-	debug: (msg: unknown) => void;
-	figmaAuth: {
-		access_token: string;
-		oauth: boolean;
-	};
+    sys: DevToolsSys;
+    args: CLIArgs;
+    debug: (msg: unknown) => void;
+    figmaAuth: {
+        access_token: string;
+        oauth: boolean;
+    };
 };
 /**
  * A component or component set
  */
 type FigmaTeamComponent = {
-	/** The unique identifier for the component. */
-	key: string;
-	/** The unique identifier of the Figma file that contains the component. */
-	file_key: string;
-	/** The unique identifier of the component node within the Figma file. */
-	node_id: string;
-	/** A URL to a thumbnail image of the component. */
-	thumbnail_url?: string;
-	/** The name of the component. */
-	name: string;
-	/** The description of the component as entered by the publisher. */
-	description: string;
-	/** The component data. */
-	componentData?: FigmaComponentInfo;
-	/** Whether the component is published. */
-	isPublished?: boolean;
+    /** The unique identifier for the component. */
+    key: string;
+    /** The unique identifier of the Figma file that contains the component. */
+    file_key: string;
+    /** The unique identifier of the component node within the Figma file. */
+    node_id: string;
+    /** A URL to a thumbnail image of the component. */
+    thumbnail_url?: string;
+    /** The name of the component. */
+    name: string;
+    /** The description of the component as entered by the publisher. */
+    description: string;
+    /** The component data. */
+    componentData?: FigmaComponentInfo;
+    /** Whether the component is published. */
+    isPublished?: boolean;
 };
 export declare function extractFigmaIds(url: string): {
-	teamId?: string;
-	fileKey?: string;
-	nodeId?: string;
+    teamId?: string;
+    fileKey?: string;
+    nodeId?: string;
 };
-export declare function fetchTeamComponents(
-	context: Context,
-	teamId: string,
-	onProgress: () => void,
-): Promise<PublishedComponent[]>;
-export declare function fetchTeamComponentSets(
-	context: Context,
-	teamId: string,
-	onProgress: () => void,
-): Promise<PublishedComponentSet[]>;
+export declare function fetchTeamComponents(context: Context, teamId: string, onProgress: () => void): Promise<PublishedComponent[]>;
+export declare function fetchTeamComponentSets(context: Context, teamId: string, onProgress: () => void): Promise<PublishedComponentSet[]>;
 /**
  * Returns a list of components and component sets that are present in the file or selection as
  * well as a set of remote keys for components that are referenced but not present.
  */
-export declare function processFileOrSelection(
-	context: Context,
-	fileKey: string,
-	nodeId?: string,
-): Promise<{
-	fileComponents: FigmaTeamComponent[];
-	remoteKeys: Set<string>;
+export declare function processFileOrSelection(context: Context, fileKey: string, nodeId?: string): Promise<{
+    fileComponents: FigmaTeamComponent[];
+    remoteKeys: Set<string>;
 }>;
-export declare function fetchRemoteComponentData(
-	context: Context,
-	remoteKeys: Set<string>,
-): Promise<(FigmaTeamComponent | undefined)[]>;
-export declare function resolveComponentData(
-	context: Context,
-	components: FigmaTeamComponent[],
-): Promise<FigmaTeamComponent[]>;
-export declare function generateComponentReport(
-	component: FigmaTeamComponent,
-	baseDir: string,
-): Promise<void>;
-export declare const runFigmaReport: (
-	sys: DevToolsSys,
-	args: CLIArgs,
-) => Promise<void>;
+export declare function fetchRemoteComponentData(context: Context, remoteKeys: Set<string>): Promise<(FigmaTeamComponent | undefined)[]>;
+export declare function resolveComponentData(context: Context, components: FigmaTeamComponent[]): Promise<FigmaTeamComponent[]>;
+export declare function generateComponentReport(component: FigmaTeamComponent, baseDir: string): Promise<void>;
+export declare const runFigmaReport: (sys: DevToolsSys, args: CLIArgs) => Promise<void>;
 export {};

package/types/cli/server-ws.d.ts

@@ -3,56 +3,48 @@ import type { IncomingMessage } from "node:http";
 import type { ServerOptions } from "ws";
 import type { WebSocket } from "ws";
 export interface SocketRequest {
-	id: number;
-	jsonrpc: string;
-	method: string;
-	params: any;
+    id: number;
+    jsonrpc: string;
+    method: string;
+    params: any;
 }
 export interface SocketResponse<T = any> {
-	id?: number | null;
-	jsonrpc: string;
-	result?: T;
-	notification?: string;
-	params?: any;
-	error?: {
-		code: number;
-		message: string;
-		data?: any;
-	};
+    id?: number | null;
+    jsonrpc: string;
+    result?: T;
+    notification?: string;
+    params?: any;
+    error?: {
+        code: number;
+        message: string;
+        data?: any;
+    };
 }
 export interface SocketSendOptions {
-	timeout?: number;
+    timeout?: number;
 }
 export interface SocketQueue {
-	type: "request" | "notification";
-	result?: SocketResponse["result"];
-	error?: SocketResponse["error"];
+    type: "request" | "notification";
+    result?: SocketResponse["result"];
+    error?: SocketResponse["error"];
 }
 type RegisterFn<T = any> = (params: T, socketId: string) => Promise<any> | any;
 interface SocketEvents {
-	listening: () => Promise<void> | void;
-	connection: (socket: WebSocket, socketId: string) => Promise<void> | void;
-	disconnection: (socketId: string) => Promise<void> | void;
-	error: (error: Error) => Promise<void> | void;
-	"socket-error": (socketId: string, error: Error) => Promise<void> | void;
-	close: () => Promise<void> | void;
+    listening: () => Promise<void> | void;
+    connection: (socket: WebSocket, socketId: string) => Promise<void> | void;
+    disconnection: (socketId: string) => Promise<void> | void;
+    error: (error: Error) => Promise<void> | void;
+    "socket-error": (socketId: string, error: Error) => Promise<void> | void;
+    close: () => Promise<void> | void;
 }
 export declare function RPCWebSocketServer(opts: ServerOptions): {
-	on: <EventKey extends keyof SocketEvents>(
-		event: EventKey,
-		cb: SocketEvents[EventKey],
-	) => void;
-	event: (e: string) => void;
-	handleUpgrade: (
-		req: IncomingMessage,
-		socket: Duplex,
-		upgradeHead: Buffer,
-		callback?: (client: WebSocket, request: IncomingMessage) => void,
-	) => Promise<void>;
-	clients: () => Map<string, WebSocket>;
-	register: <T = any>(method: string, fn: RegisterFn<T>) => void;
-	emit: (name: string, ...params: any[]) => void;
-	notify: (name: string, socketId: string, ...params: any[]) => void;
-	close: () => Promise<unknown>;
+    on: <EventKey extends keyof SocketEvents>(event: EventKey, cb: SocketEvents[EventKey]) => void;
+    event: (e: string) => void;
+    handleUpgrade: (req: IncomingMessage, socket: Duplex, upgradeHead: Buffer, callback?: (client: WebSocket, request: IncomingMessage) => void) => Promise<void>;
+    clients: () => Map<string, WebSocket>;
+    register: <T = any>(method: string, fn: RegisterFn<T>) => void;
+    emit: (name: string, ...params: any[]) => void;
+    notify: (name: string, socketId: string, ...params: any[]) => void;
+    close: () => Promise<unknown>;
 };
 export {};

package/types/cli/spinner.d.ts

@@ -1,6 +1,6 @@
 export declare const spinner: () => {
-	start: (msg?: string) => void;
-	stop: (msg?: string, code?: number) => void;
-	message: (msg?: string) => void;
-	extra: (msg?: string) => void;
+    start: (msg?: string) => void;
+    stop: (msg?: string, code?: number) => void;
+    message: (msg?: string) => void;
+    extra: (msg?: string) => void;
 };

package/types/cli/sync-utils.d.ts

@@ -1,55 +1,28 @@
 import type { AddCliOptions, DevToolsSys, FileNode, SyncInfo } from "../types";
 export declare function extractSignatureInfo(content: string): {
-	contentId?: string;
-	sessionKey?: string;
-	snippetId?: string;
+    contentId?: string;
+    sessionKey?: string;
+    snippetId?: string;
 };
 export interface GetAllProjectFilesOptions {
-	sys?: DevToolsSys;
-	basePath: string;
-	globPattern?: string | string[];
-	extraIgnorePatterns?: string[];
-	dot?: boolean;
-	deep?: number;
-	gitignore?: boolean;
-	onlyFiles?: boolean;
+    sys?: DevToolsSys;
+    basePath: string;
+    globPattern?: string | string[];
+    extraIgnorePatterns?: string[];
+    dot?: boolean;
+    deep?: number;
+    gitignore?: boolean;
+    onlyFiles?: boolean;
 }
-export declare function getAllProjectFiles({
-	basePath,
-	globPattern,
-	extraIgnorePatterns,
-	dot,
-	deep,
-	gitignore,
-	sys,
-	onlyFiles,
-}: GetAllProjectFilesOptions): Promise<string[]>;
-export declare function findBuilderFiles(
-	basePath: string,
-	targetContentId: string,
-	targetSessionKey: string,
-): Promise<FileNode[]>;
+export declare function getAllProjectFiles({ basePath, globPattern, extraIgnorePatterns, dot, deep, gitignore, sys, onlyFiles, }: GetAllProjectFilesOptions): Promise<string[]>;
+export declare function findBuilderFiles(basePath: string, targetContentId: string, targetSessionKey: string): Promise<FileNode[]>;
 export declare function filterNonImportantFiles(files: string[]): string[];
-export declare function getIgnorePatterns(
-	basePath: string,
-): (path: string) => boolean;
+export declare function getIgnorePatterns(basePath: string): (path: string) => boolean;
 /**
  * Async version of getIgnorePatterns that works with DevToolsSys
  * Used for testing and when sys is available
  */
-export declare function getIgnorePatternsAsync(
-	basePath: string,
-	sys: DevToolsSys,
-): Promise<(path: string) => boolean>;
-export declare function watchDirectory(
-	basePath: string,
-	syncInfo: SyncInfo,
-	onChange: (updatedSyncInfo: SyncInfo) => void,
-): () => Promise<void>;
-export declare function setupSyncServer(
-	sys: DevToolsSys,
-	initialSyncInfo?: SyncInfo,
-): Promise<void>;
-export declare function syncCommand(
-	opts: AddCliOptions,
-): Promise<SyncInfo | undefined>;
+export declare function getIgnorePatternsAsync(basePath: string, sys: DevToolsSys): Promise<(path: string) => boolean>;
+export declare function watchDirectory(basePath: string, syncInfo: SyncInfo, onChange: (updatedSyncInfo: SyncInfo) => void): () => Promise<void>;
+export declare function setupSyncServer(sys: DevToolsSys, initialSyncInfo?: SyncInfo): Promise<void>;
+export declare function syncCommand(opts: AddCliOptions): Promise<SyncInfo | undefined>;

package/types/cli/track.d.ts

@@ -1,8 +1,5 @@
 import * as Amplitude from "@amplitude/analytics-node";
 import * as Sentry from "@sentry/node";
 export declare function initTracking(verbose: boolean): Promise<typeof Sentry>;
-export declare function track(
-	eventName: string,
-	options: Record<string, any>,
-): Promise<Amplitude.Types.Result>;
+export declare function track(eventName: string, options: Record<string, any>): Promise<Amplitude.Types.Result>;
 export declare function setUserId(id: string): Promise<void>;

package/types/cli/utils/agent-discovery.d.ts

@@ -14,14 +14,9 @@ export type { SubAgent };
  * @param rootDir - Root directory to stop search
  * @returns Array of discovered agents
  */
-export declare function getCustomAgents({
-	sys,
-	projectDir,
-	currentDir,
-	rootDir,
-}: {
-	sys: DevToolsSys;
-	projectDir: string;
-	currentDir: string;
-	rootDir: string;
+export declare function getCustomAgents({ sys, projectDir, currentDir, rootDir, }: {
+    sys: DevToolsSys;
+    projectDir: string;
+    currentDir: string;
+    rootDir: string;
 }): Promise<SubAgent[]>;

package/types/cli/utils/agent-parser.d.ts

@@ -4,26 +4,25 @@
  */
 import type { CodeGenMode } from "$/ai-utils";
 export interface SubAgent {
-	name: string;
-	description?: string;
-	systemPrompt?: string;
-	tools?: string[];
-	model?: string;
-	mode?: CodeGenMode;
-	filePath?: string;
-	includeMemories?: boolean;
-	needDevServer?: boolean;
-	needValidation?: boolean;
-	resetAfterRun?: boolean;
+    name: string;
+    description?: string;
+    systemPrompt?: string;
+    tools?: string[];
+    model?: string;
+    mode?: CodeGenMode;
+    position?: string;
+    filePath?: string;
+    includeMemories?: boolean;
+    needDevServer?: boolean;
+    needValidation?: boolean;
+    resetAfterRun?: boolean;
 }
 /**
  * Resolves model shortcut to full model name
  * @param modelOrShortcut - Model name or shortcut (or "inherit" to use parent model)
  * @returns Resolved model name or undefined (undefined means inherit from parent)
  */
-export declare function resolveModelShortcut(
-	modelOrShortcut?: string,
-): string | undefined;
+export declare function resolveModelShortcut(modelOrShortcut?: string): string | undefined;
 /**
  * Parses an agent definition file (Markdown with YAML frontmatter)
  * Expected format (following Claude Code sub-agents format):
@@ -44,7 +43,4 @@ export declare function resolveModelShortcut(
  * @param filePath - The file path (used for fallback name)
  * @returns Parsed SubAgent or null if parsing fails
  */
-export declare function parseAgentFile(
-	fileContent: string,
-	filePath: string,
-): SubAgent | null;
+export declare function parseAgentFile(fileContent: string, filePath: string): SubAgent | null;

package/types/cli/utils/component-group-mdx-prompt.d.ts

@@ -1,2 +1 @@
-export declare const COMPONENT_GROUP_MDX_PROMPT =
-	"# Component Documentation Generation\n\n## Objective\nGenerate comprehensive MDX documentation for a specific component, analyzing their interfaces, relationships, and usage patterns using the relevant files provided in the input.\n\n## Instructions\n\n### 1. Component Analysis\nFor the given component, analyze each relevant file by:\n- **Interdependency mapping** - Document how components depend on each other\n- **Interface examination** - Extract and document all props, their types, and descriptions\n- **Context analysis** - Identify shared state, contexts, or communication patterns\n- **Compositional patterns** - Document required parent-child relationships\n- **Usage pattern analysis** - Identify how components work together\n- **Example extraction** - Find real usage examples from the codebase\n\n{{COMPONENT_NAME}} has the following related components: {{RELATED_COMPONENTS}}\nThe following files are associated with {{COMPONENT_NAME}}: {{FILE_LIST}}\n\n### 2. Documentation Structure\nCreate comprehensive documentation covering:\n- **Component rationale** - Why these components work together and when to use them\n- **Architectural overview** - How the components form a cohesive system\n- **Component interfaces** - Detailed prop documentation with interdependencies\n- **Composition patterns** - Required and optional usage combinations\n- **Integration examples** - Real-world scenarios showing the component in action\n- **Best practices** - Recommended usage patterns and guidelines\n\n## Required Output Format\n\nGenerate an MDX file with this structure:\n\n```mdx\n---\n# {{COMPONENT_NAME}}\n\n## Overview\n\n### Purpose\n{{COMPONENT_DESCRIPTION}}\n\n### When to Use\n[Expand on the use cases mentioned in the description - be specific about scenarios, user needs, and implementation contexts]\n\n### Architecture\n[Explain the architectural pattern based on coupling strength:]\n- **Critical/Strong Coupling**: Describe the required relationships, shared context, or compositional hierarchy\n- **Moderate Coupling**: Explain how components enhance each other\n- **No Coupling**: Note that this is a standalone component\n\n### Component Interdependencies\n[Map out component relationships - only for components with coupling:]\n- Required parent-child relationships\n- Shared context dependencies  \n- Communication patterns between components\n- Related components\n\n## API\n**Types**: Interfaces related to the component including all props, methods, or children along with descriptions.\n**Dependencies:** Other components that must be used\n**Provides:** Context/state this component provides to children. Only required for coupled components.\n\n## Usage Examples\nInclude examples that show how to fully use the component. At a minimum, you must include the following examples:\n\n- Basic usage including how to import the component if applicable\n- Usage with any dependency components\n- Variations with conditional rendering, different prop combinations, etc\n\n## Component Relationships {Only for coupled components}\n\n### Data Flow\n[Explain how data flows between the component and related components}\n\n### Context Sharing\n[Document shared contexts, providers, or state management]\n\n### Event Handling\n[Describe how events bubble up or propagate between components]\n\n## Best Practices\n\n### Usage Guidelines\n- [Specific recommendation based on component purpose and use cases]\n- [Another recommendation focusing on accessibility or performance]\n- [Usage pattern guidance based on the component's architecture]\n\n### Accessibility {When relevant}\n- [ARIA relationships between components]\n- [Keyboard navigation patterns]\n- [Screen reader considerations]\n\n### Performance {When relevant}\n- [Optimization recommendations]\n- [State management best practices]\n- [Rendering performance considerations]\n\n## Common Patterns {Expand based on component functionality}\n\n### Pattern 1: [Specific Pattern Name]\n```tsx\n// Example showing a specific usage pattern\n// Include comments explaining why this pattern is recommended\n```\n\n### Pattern 2: [Another Pattern Name]\n```tsx\n// Another common pattern with explanation\n```\n\n```\n\n## File Generation Requirements\n\n**File Naming:**\n- Use kebab-case derived from component name: `{{COMPONENT_NAME_KEBAB}}.mdx`\n- Place in `repo-indexing/` folder\n- Example: `repo-indexing/{{COMPONENT_NAME_KEBAB}}.mdx`\n\n**Content Requirements:**\n1. **Use coupling strength context** - Adapt documentation structure based on couplingStrength value\n2. **Extract real interfaces** - Don't create placeholder interfaces, extract actual type interfaces from the codebase\n3. **Leverage component description** - Expand on the provided description with specific use cases and implementation guidance\n4. **Document interdependencies** - For coupled components, clearly explain component relationships and requirements\n5. **Include practical examples** - Use realistic, working code examples that demonstrate proper usage\n6. **Show integration patterns** - For coupled components, demonstrate required composition patterns\n**Coupling-Specific Requirements:**\n- **Critical/Strong Coupling**: Focus on required relationships, composition patterns, and shared context\n- **Moderate Coupling**: Show how components enhance each other and optional usage patterns  \n- **No Coupling**: Document standalone usage, variants, and individual component capabilities\n\n## Output\nReturn only the complete MDX file content, ready to be saved as `repo-indexing/{{COMPONENT_NAME_KEBAB}}.mdx`. You must use the Write tool in your response.";
+export declare const COMPONENT_GROUP_MDX_PROMPT = "# Component Documentation Generation\n\n## Objective\nGenerate comprehensive MDX documentation for a specific component, analyzing their interfaces, relationships, and usage patterns using the relevant files provided in the input.\n\n## Instructions\n\n### 1. Component Analysis\nFor the given component, analyze each relevant file by:\n- **Interdependency mapping** - Document how components depend on each other\n- **Interface examination** - Extract and document all props, their types, and descriptions\n- **Context analysis** - Identify shared state, contexts, or communication patterns\n- **Compositional patterns** - Document required parent-child relationships\n- **Usage pattern analysis** - Identify how components work together\n- **Example extraction** - Find real usage examples from the codebase\n\n{{COMPONENT_NAME}} has the following related components: {{RELATED_COMPONENTS}}\nThe following files are associated with {{COMPONENT_NAME}}: {{FILE_LIST}}\n\n### 2. Documentation Structure\nCreate comprehensive documentation covering:\n- **Component rationale** - Why these components work together and when to use them\n- **Architectural overview** - How the components form a cohesive system\n- **Component interfaces** - Detailed prop documentation with interdependencies\n- **Composition patterns** - Required and optional usage combinations\n- **Integration examples** - Real-world scenarios showing the component in action\n- **Best practices** - Recommended usage patterns and guidelines\n\n## Required Output Format\n\nGenerate an MDX file with this structure:\n\n```mdx\n---\n# {{COMPONENT_NAME}}\n\n## Overview\n\n### Purpose\n{{COMPONENT_DESCRIPTION}}\n\n### When to Use\n[Expand on the use cases mentioned in the description - be specific about scenarios, user needs, and implementation contexts]\n\n### Architecture\n[Explain the architectural pattern based on coupling strength:]\n- **Critical/Strong Coupling**: Describe the required relationships, shared context, or compositional hierarchy\n- **Moderate Coupling**: Explain how components enhance each other\n- **No Coupling**: Note that this is a standalone component\n\n### Component Interdependencies\n[Map out component relationships - only for components with coupling:]\n- Required parent-child relationships\n- Shared context dependencies  \n- Communication patterns between components\n- Related components\n\n## API\n**Types**: Interfaces related to the component including all props, methods, or children along with descriptions.\n**Dependencies:** Other components that must be used\n**Provides:** Context/state this component provides to children. Only required for coupled components.\n\n## Usage Examples\nInclude examples that show how to fully use the component. At a minimum, you must include the following examples:\n\n- Basic usage including how to import the component if applicable\n- Usage with any dependency components\n- Variations with conditional rendering, different prop combinations, etc\n\n## Component Relationships {Only for coupled components}\n\n### Data Flow\n[Explain how data flows between the component and related components}\n\n### Context Sharing\n[Document shared contexts, providers, or state management]\n\n### Event Handling\n[Describe how events bubble up or propagate between components]\n\n## Best Practices\n\n### Usage Guidelines\n- [Specific recommendation based on component purpose and use cases]\n- [Another recommendation focusing on accessibility or performance]\n- [Usage pattern guidance based on the component's architecture]\n\n### Accessibility {When relevant}\n- [ARIA relationships between components]\n- [Keyboard navigation patterns]\n- [Screen reader considerations]\n\n### Performance {When relevant}\n- [Optimization recommendations]\n- [State management best practices]\n- [Rendering performance considerations]\n\n## Common Patterns {Expand based on component functionality}\n\n### Pattern 1: [Specific Pattern Name]\n```tsx\n// Example showing a specific usage pattern\n// Include comments explaining why this pattern is recommended\n```\n\n### Pattern 2: [Another Pattern Name]\n```tsx\n// Another common pattern with explanation\n```\n\n```\n\n## File Generation Requirements\n\n**File Naming:**\n- Use kebab-case derived from component name: `{{COMPONENT_NAME_KEBAB}}.mdx`\n- Place in `repo-indexing/` folder\n- Example: `repo-indexing/{{COMPONENT_NAME_KEBAB}}.mdx`\n\n**Content Requirements:**\n1. **Use coupling strength context** - Adapt documentation structure based on couplingStrength value\n2. **Extract real interfaces** - Don't create placeholder interfaces, extract actual type interfaces from the codebase\n3. **Leverage component description** - Expand on the provided description with specific use cases and implementation guidance\n4. **Document interdependencies** - For coupled components, clearly explain component relationships and requirements\n5. **Include practical examples** - Use realistic, working code examples that demonstrate proper usage\n6. **Show integration patterns** - For coupled components, demonstrate required composition patterns\n**Coupling-Specific Requirements:**\n- **Critical/Strong Coupling**: Focus on required relationships, composition patterns, and shared context\n- **Moderate Coupling**: Show how components enhance each other and optional usage patterns  \n- **No Coupling**: Document standalone usage, variants, and individual component capabilities\n\n## Output\nReturn only the complete MDX file content, ready to be saved as `repo-indexing/{{COMPONENT_NAME_KEBAB}}.mdx`. You must use the Write tool in your response.";

package/types/cli/utils/discovery-test-utils.d.ts

@@ -4,6 +4,4 @@ import type { DevToolsSys } from "../../types";
  * @param files - Object mapping file paths to file contents
  * @returns Mock DevToolsSys instance
  */
-export declare function createMockSys(
-	files: Record<string, string>,
-): DevToolsSys;
+export declare function createMockSys(files: Record<string, string>): DevToolsSys;

package/types/cli/utils/env-capture.d.ts

@@ -2,23 +2,23 @@
  * Options for capturing environment variables from a setup command
  */
 export interface EnvCaptureOptions {
-	/** The command to wrap with env capture */
-	command: string;
+    /** The command to wrap with env capture */
+    command: string;
 }
 /**
  * Result of environment capture
  */
 export interface EnvCaptureResult {
-	/** The modified command that includes env capture */
-	command: string;
-	/** Path to the temporary file where env will be captured */
-	envFilePath: string;
-	/**
-	 * Function to get the captured environment variables.
-	 * This will read, parse, and cleanup the env file in one call.
-	 * Returns undefined if the env file couldn't be read.
-	 */
-	getCapturedEnv: () => Promise<Record<string, string> | undefined>;
+    /** The modified command that includes env capture */
+    command: string;
+    /** Path to the temporary file where env will be captured */
+    envFilePath: string;
+    /**
+     * Function to get the captured environment variables.
+     * This will read, parse, and cleanup the env file in one call.
+     * Returns undefined if the env file couldn't be read.
+     */
+    getCapturedEnv: () => Promise<Record<string, string> | undefined>;
 }
 /**
  * Wraps a command with environment variable capture at the end.
@@ -38,9 +38,7 @@ export interface EnvCaptureResult {
  * const env = await getCapturedEnv();
  * ```
  */
-export declare function wrapCommandWithEnvCapture(
-	options: EnvCaptureOptions,
-): EnvCaptureResult;
+export declare function wrapCommandWithEnvCapture(options: EnvCaptureOptions): EnvCaptureResult;
 /**
  * Parses an environment file into a key-value object.
  * Handles multi-line values and empty lines.
@@ -54,9 +52,7 @@ export declare function wrapCommandWithEnvCapture(
  * console.log(env.PATH); // "/usr/bin:/bin"
  * ```
  */
-export declare function parseEnvFile(
-	filePath: string,
-): Promise<Record<string, string>>;
+export declare function parseEnvFile(filePath: string): Promise<Record<string, string>>;
 /**
  * Parses environment variable content into a key-value object.
  * This is the core parsing logic extracted for easier testing.
@@ -73,9 +69,7 @@ export declare function parseEnvFile(
  * // { PATH: '/usr/bin', HOME: '/home/user' }
  * ```
  */
-export declare function parseEnvContent(
-	content: string,
-): Record<string, string>;
+export declare function parseEnvContent(content: string): Record<string, string>;
 /**
  * Cleans up the environment capture file.
  * Call this after parsing to remove temporary files.

package/types/cli/utils/env-substitution.d.ts

@@ -28,7 +28,4 @@
  * substituteEnvVars("URL: ${API_URL:-https://api.example.com}", { API_URL: "https://custom.com" })
  * // Returns: "URL: https://custom.com"
  */
-export declare function substituteEnvVars(
-	str: string,
-	env: Record<string, string | undefined>,
-): string;
+export declare function substituteEnvVars(str: string, env: Record<string, string | undefined>): string;

package/types/cli/utils/feature-flags.d.ts

@@ -1,4 +1,2 @@
-export declare function setFeatureFlags(
-	featureFlags: Record<string, boolean>,
-): void;
+export declare function setFeatureFlags(featureFlags: Record<string, boolean>): void;
 export declare function getFeatureFlag(featureFlag: string): boolean;