Feature Inventory

The feature inventory pipeline auto-generates a structured catalog of every capability in the project. It produces two committed artifacts (FEATURES.json and FEATURES.md) and exposes them via GET /api/features.

When to Load This Skill

• •Before adding new IPC channels, HTTP endpoints, renderer panels, skills, workflows, or scripts
• •Before modifying extractor logic or the renderer registry
• •When debugging why a capability is missing from the inventory
• •During REVIEW/AUDIT of changes to scripts/lib/extractors/

Commands

# Generate inventory (writes FEATURES.json + FEATURES.md)
npm run features:generate

# Generate with mobile companion views included
CC_MOBILE_ROOT=../command-center-mobile npm run features:generate

# CI drift check — exits 1 if committed artifacts are stale
npm run features:check

# Query capabilities via HTTP
curl "http://127.0.0.1:3050/api/features" | jq
curl "http://127.0.0.1:3050/api/features?kind=ipc&q=deploy" | jq
curl "http://127.0.0.1:3050/api/features?surface=gui" | jq

How Capabilities Are Discovered

Canonical Source Rules

• •Only .ts files in electron/ are scanned for IPC/HTTP — generated .js mirrors are ignored
• •.test.ts and .d.ts files are excluded
• •Mobile views are opt-in — only included when --mobile-root or CC_MOBILE_ROOT is set
• •The generator does not inventory itself (.ts scripts in scripts/ are not scanned for IPC/HTTP)

Adding a New Capability

New IPC channel or HTTP endpoint

No action needed — the AST extractors pick these up automatically. Run npm run features:generate after committing.

New renderer panel

Add an entry to the UI_PANELS array in electron/renderer-registry.ts:

{
    name: 'My Panel',
    view: 'composer',
    entryFn: 'renderMyPanel',
    sourcePath: 'electron/renderer-my-panel.ts',
    description: 'What this panel does.'
}

New skill or workflow

Include YAML frontmatter at the top of the .md file:

---
name: my-skill
description: What this skill teaches agents
---

New script

Add a comment header in the first few lines:

#!/bin/bash
# What this script does

Adding a New Extractor

If you need to inventory a new capability kind (e.g., MCP tools, cron jobs):

1. •Create scripts/lib/extractors/my-extractor.ts
2. •Import shared helpers from scripts/lib/extractors/shared.ts:
   • •toPosixPath — normalize paths to forward slashes
   • •listTypeScriptFiles — recursive .ts file listing (excludes .test.ts, .d.ts)
   • •readLeadingDescription — extract JSDoc/comment above an AST node
   • •readStringLiteral — safely read string literal from AST expression
   • •parseFrontmatter — parse YAML frontmatter from markdown files
3. •Export a function matching the signature: (rootDir: string) => Capability[]
4. •Add the new kind to CapabilityKind in scripts/lib/types.ts
5. •Add the kind label to KIND_ORDER and KIND_LABELS in scripts/lib/render-markdown.ts
6. •Wire it into buildInventory() in scripts/generate-features.ts
7. •Add tests in scripts/generate-features.test.ts
8. •Run npm run features:generate and commit the updated artifacts

Schema

FEATURES.json follows this structure:

interface FeatureInventory {
    schemaVersion: 1;
    generatedAt: string;          // ISO 8601 timestamp
    generatedBy: 'scripts/generate-features.ts';
    commitSha: string;            // git HEAD at generation time
    capabilities: Capability[];   // sorted by id → sourcePath → sourceLine
}

interface Capability {
    id: string;           // e.g. "endpoint:http:GET:/api/health", "ipc:main:send-prompt"
    kind: CapabilityKind; // 'endpoint' | 'ipc' | 'skill' | 'workflow' | 'script' | 'panel' | 'view'
    surface: CapabilitySurface; // 'http' | 'main' | 'agent' | 'cli' | 'gui' | 'mobile-*'
    name: string;
    method?: string;      // HTTP method (endpoints only)
    sourcePath: string;   // relative posix path from project root
    sourceLine?: number;  // 1-indexed line number
    description: string;
}

ID Format

• •Endpoints: endpoint:http:{METHOD}:{path} (4 segments — prevents collisions when same path has GET + POST)
• •All other kinds: {kind}:{surface}:{name} (3 segments)

--check Mode (CI)

npm run features:check regenerates the inventory in memory and compares against committed files. It never mutates the working tree. Metadata fields (generatedAt, commitSha) are read from the committed FEATURES.json to prevent false drift from timestamp/SHA changes.

Exit codes:

• •0 — inventory is up to date
• •1 — drift detected, run npm run features:generate

API Endpoint

GET /api/features serves the committed FEATURES.json with optional query filters:

Returns 404 if FEATURES.json doesn't exist yet.

File Reference