Capability Map

Map reusable capabilities from capabilities.json across frontend, harness, engine, and platform layers.

2|3|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/genesis-agents/GenesisPod --skill capability-map-genesis-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Capability Map
Source: https://github.com/genesis-agents/GenesisPod/tree/main/.claude/skills/capability-map
Command: npx skills add https://github.com/genesis-agents/GenesisPod --skill capability-map-genesis-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a centralized, machine-readable index of reusable capabilities across frontend, harness, engine, and platform layers to reduce duplication and accelerate development.

Core Features & Use Cases

  • Single source of truth: Exposes capabilities.json listing {name, layer, domain, source, import} to guide reuse decisions.
  • Cross-layer reuse: Enables engineers to discover existing capabilities before implementing new ones, ensuring architectural discipline.
  • Use Case: When starting a new feature, consult the Capability Map to find an existing capability to reuse instead of building from scratch.

Quick Start

Refer to the machine-readable capabilities.json at docs/architecture/capabilities.json to locate canonical capabilities and usage patterns.

Frequently Asked Questions about Capability Map

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

FAQPage Schema
How do I find reusable capabilities across frontend and engine layers?

To find reusable capabilities across frontend and engine layers, consult the centralized capabilities.json index, which maps each capability's name, layer, domain, source, and import for precise reuse decisions. This prevents building duplicate features from scratch.

What is a machine-readable capability map for software architecture?

A machine-readable capability map is a centralized index, specifically a capabilities.json file, that lists reusable full-stack capabilities across frontend, harness, engine, and platform layers to reduce duplication and accelerate development.

How do I discover existing platform capabilities before implementing a new feature?

You can discover existing platform capabilities before implementing a new feature by referencing the canonical capabilities.json source at docs/architecture/capabilities.json to locate existing capabilities and their usage patterns for architectural discipline.

Can I directly edit the capabilities.json file to register a new architecture capability?

No, you should not directly edit the capabilities.json file to register a new architecture capability. This machine-readable truth source is generated from code via scripts and serves as a read-only index for mapping capabilities.

What's the best way to ensure cross-layer reuse in full-stack development?

The best way to ensure cross-layer reuse in full-stack development is to apply a canonical capabilities source map, enabling engineers to discover existing capabilities across frontend, harness, engine, and platform layers before implementing new ones.