Tech Leads Club Agent Skills

Install

npx @tech-leads-club/agent-skills

This is third-party code. Review the repository files before installing.

What it does

The repository combines a skill catalog, an install CLI and an MCP server. The catalog covers architecture and decomposition, cloud deploys, ADRs, RFCs and design docs, spec-driven development, frontend and accessibility, performance, security, go-to-market, and working with Nx, Playwright, Figma, Sentry and Jira. The interactive CLI lets you pick skills, agents, install method and scope, and handles updates, removal and an audit log. Skills go through static analysis and Snyk Agent Scan before publishing. The MCP server lets the agent search skills by intent and load only the files it needs.

Who it is for. For engineering teams that want a shared, vetted skill set across different agents.

Example request

Plan the report export feature with tlc-spec-driven: specification, design, tasks

Limitations

The CLI and MCP server download skills from the project's CDN and need Node.js 22+. Third-party skills keep their own licenses; the project's own skills are CC-BY-4.0. All content is in English.

How to disable. Remove skills with agent-skills remove -s <name>, delete the agent-skills MCP server from your config, and clear the cache with agent-skills cache --clear if needed.

Security check

• The CLI downloads and writes files into agent configs
• Some skills run deploys, Playwright and CI tasks

README in short

The README explains what skills are, how the registry is secured and which agents are supported. It shows featured skills, the install wizard and full CLI reference: install, update, remove, cache, audit. It describes the MCP server with four tools and a config snippet. Code is MIT, the project's own skills are CC-BY-4.0.

SKILL.md

---
name: component-common-domain-detection
description: Finds duplicate business logic spread across multiple components and suggests consolidation. Use when asking "where is this logic duplicated?", "find common code between services", "what can be consolidated?", "detect shared domain logic", or analyzing component overlap before refactoring. Do NOT use for code-level duplication detection (use linters) or dependency analysis (use coupling-analysis).
---

# Common Domain Component Detection

This skill identifies common domain functionality that is duplicated across multiple components and suggests consolidation opportunities to reduce duplication and improve maintainability.

## How to Use

### Quick Start

Request analysis of your codebase:

- **"Find common domain functionality across components"**
- **"Identify duplicate domain logic that should be consolidated"**
- **"Detect shared classes used across multiple components"**
- **"Analyze consolidation opportunities for common components"**

### Usage Examples

**Example 1: Find Common Functionality**

```
User: "Find common domain functionality across components"

The skill will:
1. Scan component namespaces for common patterns
2. Detect shared classes used across components
3. Identify duplicate domain logic
4. Analyze coupling impact of consolidation
5. Suggest consolidation opportunities
```

Related