reuse-index

Generate or refresh a .claude/reuse-index.md inventory of shared primitives.

17|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/alexiolan/craft-skills --skill reuse-index
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reuse-index
Source: https://github.com/alexiolan/craft-skills/tree/main/skills/reuse-index
Command: npx skills add https://github.com/alexiolan/craft-skills --skill reuse-index

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate or refresh a project-wide inventory file listing shared utilities, enums, hooks, components, and primitives that downstream agents must consult before adding new code.

Core Features & Use Cases

  • Generates or refreshes a central .claude/reuse-index.md that inventories shared primitives and their purposes
  • Categorizes items into UI primitives, hooks, utilities, enums, services, and models for quick reference
  • Triggers regeneration when the shared surface changes meaningfully to keep plans aligned

Quick Start

Invoke this skill to generate or refresh the project's reuse index.

Frequently Asked Questions about reuse-index

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

FAQPage Schema
How do I generate an inventory of shared codebase primitives for engineering teams?

To generate a shared codebase primitive inventory, invoke this skill to parse project exports and signatures, automatically creating a single-file .claude/reuse-index.md that catalogs utilities, enums, hooks, and components for team reference.

Why do I need a reuse index for shared utilities and components?

A reuse index for shared utilities prevents duplicate code by providing downstream agents and engineers with a central inventory of existing primitives to consult before adding new code to the project.

Can I automatically refresh a codebase index when shared service primitives change?

You can automatically refresh a codebase index by triggering this skill's regeneration process, which updates the shared primitive inventory only when the project's shared surface meaningfully changes.

How to categorize UI primitives, hooks, and enums in a project documentation index?

To categorize UI primitives, hooks, and enums in a documentation index, this skill parses code exports and automatically groups items into distinct categories like UI primitives, hooks, utilities, enums, services, and models for quick reference.

Does the reuse index parse code implementations or just function signatures?

The reuse index parses only function signatures and exports rather than code implementations, ensuring project-agnostic generation that focuses on the shared surface interface.

When should I regenerate a shared primitive inventory for a software engineering project?

You should regenerate a shared primitive inventory only when the shared surface meaningfully changes, keeping engineering plans aligned without unnecessarily refreshing the index during routine code modifications.