kb-layers

Manage project layer vocabulary by listing, adding, or removing allowed layers via shelf-index.

41|6|Updated Jul 12, 2025
One-click install
npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill kb-layers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-layers
Source: https://github.com/SteveGJones/ai-first-sdlc-practices/tree/main/plugins/sdlc-knowledge-base/skills/kb-layers
Command: npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill kb-layers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage the project's layer vocabulary used in library files and enforce safe, auditable changes based on shelf-index data.

Core Features & Use Cases

  • List allowed layers with file counts from shelf-index.
  • Add a new layer to the allowed set.
  • Safely remove unused layers (with a forced removal option) and ensure no files reference them.

Quick Start

Run kb-layers to list, add, or remove layers according to the shelf-index.

Frequently Asked Questions about kb-layers

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

FAQPage Schema
How do I manage allowed knowledge-base layers in a project?

To manage allowed knowledge-base layers, you can list, add, or remove project layers by consulting the shelf-index and updating CLAUDE.md atomically to maintain a stable layer vocabulary across library files.

How do I safely remove unused knowledge-base layers without breaking file references?

To safely remove unused knowledge-base layers, the system consults the shelf-index to ensure no files reference them before removal, preventing destructive changes and preserving library file consistency.

Can I force remove a knowledge-base layer that is currently in use?

Yes, you can use the forced removal option to remove a knowledge-base layer even when files reference it, though standard removal prevents deletion to avoid breaking active library file references.

What is a shelf-index and how does it validate knowledge-base layers?

A shelf-index tracks allowed knowledge-base layers and their file counts, enforcing validation of layer names and reading CLAUDE.md configuration to ensure non-destructive, auditable changes to the project layer vocabulary.

How do I add a new layer to my project's knowledge-base vocabulary?

To add a new knowledge-base layer, the system validates the layer name against the shelf-index and updates the CLAUDE.md configuration atomically to expand the allowed set of project layers.

Why should I use shelf-index for knowledge-base layer management instead of manual editing?

Using shelf-index for knowledge-base layer management enforces validation, ensures non-destructive atomic updates to CLAUDE.md, and prevents removing layers still referenced by library files, avoiding consistency errors.