component-inventory
From the author
Inspect an existing project to discover pages, components, inline UI, real content, and conditional consumers, then create or refresh its component system document. Use before component governance or when asked which pages use which components.
Install
npx skills add kostja94/bricks --skill component-inventory -a claude-code
Installs to .claude/skills/component-inventory/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 84
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- component-auditorkostja94/bricksAnalyze existing components and inline sections for semantic duplication, style drift, and justified variants. Use for audit-only analysis, component-by-component alignment, or authorized reconstruction; preserve project-specific design and content decisions.Design★ 192
- design-systemanthropics/knowledge-work-pluginsAudit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.OfficialDesign★ 34.8K
- component-builderkostja94/bricksBuild new interface components and bounded composition patterns inside an existing project. Use for named components, interface blocks, and workspaces. Preserve the target project's design system and stack; for a complete new page with page-level structure and multiple sections, use Pagina page-builder instead. Do not use to audit or reconstruct an existing component, plan a whole product or website, or handle purely editorial copy requests.Design★ 192
- component-docsarla6ka/design.howUse to write one component's documentation entry from its code, stories and real call sites, such as "document the button", "write docs for Select", "what states does Toast have", or usage rules for a new or changed component. Not for foundations or pages that span components, which no skill here writes, nor for changing the component, which is build-design-system.Design★ 244
- component-cleanupkostja94/bricksClean unused components, abandoned generated UI, and code or assets left behind by component migration. Inspect unimported component candidates and remove verified unused implementations and their exclusive support files; excludes general codebase, dependency-upgrade, or production-data cleanup.Design★ 192
- design-systemsMindrally/skillsComprehensive design system guidelines for building consistent, accessible, and scalable component libraries. Use when creating design tokens, building component libraries, implementing design systems, setting up theming architecture, or establishing UI governance processes.Design★ 297
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in