agentleFS
kunalsurikunalsuri/ai-fication-kit/.claude/skills/create-feature-catalog/SKILL.md

create-feature-catalog

Skill3 starsChanged 4 months agoApache-2.0View on GitHub

Deep-mine the source code to discover implemented features; writes ai/analysis/FEATURE_CATALOG.md.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start from user-visible surfaces: routes, UI entry points, CLI commands, public APIs.

    line 12
  2. Very specific:

    Every entry [inferred]. Where a layer can't be confirmed, write "UNSURE".

    line 25
  3. Very specific:

    Do not modify source. Update ai/guide/FEATURE_MAP.md candidate list to reference the catalog, nothing more.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Copyright (c) 2026 Kunal Suri (CEA LIST). All rights reserved. -->

Build the feature catalog — the highest-value artifact for agents. Budget significant exploration; use repo-explorer for the heavy reading.

Method

  1. Start from user-visible surfaces: routes, UI entry points, CLI commands, public APIs. Each surface is a candidate feature.
  2. For each feature, trace the touch list across layers: UI, backend/services, persistence (tables/collections/files), and tests that exercise it.
  3. Cluster and name features the way a USER would name them, not by module names.

Output — ai/analysis/FEATURE_CATALOG.md

For every feature: name · business goal (one line) · touch list per layer · verifying tests · related features. End with two sections agents use most:

  • "Where new code lives" — a decision tree from feature-type to target directories.
  • The 3-file rule — for each feature, the 3 files to read first to understand it.

Rules

  • Every entry [inferred]. Where a layer can't be confirmed, write "UNSURE".
  • Do not modify source. Update ai/guide/FEATURE_MAP.md candidate list to reference the catalog, nothing more.
  • Print a sampling guide at the end: the 5 entries a human should spot-check first (pick the ones you are least sure of).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.