SuperAPI AI Directory

Skills

Find an Agent Skill for your task. Read the guide and copy the install command.

Updated 11-21 00:15

All skills

258,650 results

structure-codebase

Design, audit, and evolve physical source and package structures that expose real architectural boundaries while keeping related behavior together. Use when creating or reviewing repository trees, deciding where files or packages belong, reducing flat folders, organizing by feature, route, screen, use case, bounded context, workflow or endpoint, structuring frontend state/data/UI ownership and design systems, making hexagonal inside/outside boundaries visible, locating ports, adapters and composition roots, structuring BFF routes, planning folder migrations, or enforcing package and import direction. For one module's logical responsibility, deepening, splitting, or caller contract use codebase-design; for repository-wide architecture investment discovery use improve-codebase-architecture. A physical flattening alone is not a reduce-system-complexity result.

General & other99 installs

necessary-code-audit

Audit whether "code that still has consumers" really needs to continue to exist, focusing on wrappers/facades, compatibility layers, stale public APIs, defensive branches, fallbacks, default values, configuration, duplicate sources, and hypothetical extension points. Use for code that is already used but whose necessity is insufficient, legacy compatibility cleanup, meaningless wrappers, defensive code removal, cleanup with no compatibility requirements, in-depth necessity checks, and "is this still needed?"-type requests; do not use it as...

Coding & development99 installs