What are Claude Code Skills?

Claude Code Skills are reusable prompt templates stored as markdown files in your project's .claude/skills/ directory. They let you codify best practices and common workflows into slash commands that Claude follows consistently.

How do I create a Claude Code Skill?

Create a markdown file in .claude/skills/ with instructions for Claude. The filename becomes the command name — for example, .claude/skills/code-review.md can be invoked with /code-review during a Claude Code session.

Can I share skills with my team?

Yes. Skills stored in .claude/skills/ can be committed to version control so every team member has access to the same standardized workflows. You can also organize skills into subdirectories by category.

What is the difference between project and global skills?

Project skills (.claude/skills/) are specific to the current project and are committed to git. Global skills (~/.claude/skills/) are personal skills available across all your projects.

readme-writer

New

2Community RegistryGeneralby Szymon Paluch · MIT

Generate and audit perfect READMEs using the PRD-README v1 standard

Community PluginView Source

Overview

Claude Code plugins that enforce code quality practices: TDD workflows, performance analysis, and documentation standards.

![License: MIT](LICENSE) !Status: Active

What's Included

Plugin	Version	Purpose
tdd-dev	0.2.1	Enforce Red→Green→Refactor TDD cycles
n1-optimizer	0.1.3	Detect N+1 queries and performance issues
readme-writer	0.1.0	Generate/audit READMEs with PRD-README v1
doc-master	0.2.1	9 specialized documentation agents

Quick Start

Prerequisites: Claude Code CLI installed

Step 1: Add the marketplace

bash

/plugin marketplace add hculap/better-code

Output:

code

Successfully added marketplace: better-code

Step 2: Install a plugin

bash

/plugin install tdd-dev

Output:

code

Installed plugin: tdd-dev

Step 3: Use the plugin

bash

/tdd-dev:start

Output:

code

TDD Dev Mode: ACTIVE

Configuration:
  Strictness: strict
  Test Command: npm test

That's it! You're now coding with TDD enforcement.

Usage

tdd-dev: Test-Driven Development

Enforces writing tests before implementation code.

bash

/tdd-dev:start              # Enable TDD mode
/tdd-dev:feature "add auth" # Implement feature with TDD
/tdd-dev:bug "fix #123"     # Fix bug with regression test first
/tdd-dev:refactor           # Safe refactoring verified by tests
/tdd-dev:stop               # Disable TDD mode

Strictness levels: strict (tests required), standard (tests encouraged), relaxed (minimal enforcement)

n1-optimizer: Performance Analysis

Runs 4 parallel agents to analyze your codebase for performance issues.

bash

/n1-optimizer:analyze

Output:

code

Analysis Complete

Database Layer: 3 issues found
  HIGH: N+1 query in UserService.getOrders() - src/services/user.ts:45

Backend Layer: 1 issue found
  MEDIUM: Sequential awaits could be parallelized - src/api/reports.ts:23

Frontend Layer: 2 issues found
  HIGH: Missing React.memo on ExpensiveList - src/components/List.tsx:12

API Layer: 1 issue found
  MEDIUM: Missing pagination on /api/products - src/routes/products.ts:8

Agent	Detects
Database	N+1 queries, missing indexes, unbatched writes
Backend	O(n²) algorithms, blocking I/O, memory issues
Frontend	Re-render loops, large bundles, missing memoization
API	Over-fetching, missing pagination, chatty endpoints

readme-writer: README Generation

Generate or audit READMEs following the PRD-README v1 standard.

bash

/readme-writer:generate      # Generate README from codebase analysis
/readme-writer:audit         # Score existing README (0-10)

Audit output:

code

README Audit Score: 7/10

✓ Test 1: What is it? - PASS
✓ Test 2: Is it maintained? - PASS
✗ Test 3: Quickstart works - FAIL (missing expected output)
...

doc-master: Documentation Toolkit

9 specialized agents for comprehensive documentation.

bash

/doc-master:setup            # Choose framework (Diátaxis/Traditional/Custom)
/doc-master:generate "API"   # Generate API documentation
/doc-master:audit            # Audit existing docs
/doc-master:plan             # Create documentation plan

Agent	Focus
api-docs	REST/GraphQL endpoints, schemas
backend-docs	Services, data flows, deployment
frontend-docs	Components, state management
database-docs	Schema, migrations, ER diagrams
architecture-docs	System design, ADRs
test-docs	Test strategy, coverage
user-guide-docs	Tutorials, help articles
compliance-docs	Security, audit, regulatory
mobile-docs	iOS/Android, app stores

Documentation

Full documentation available in docs/:

Contributing

Contributions welcome! Please open an issue first to discuss proposed changes.

Quick steps:

Fork the repository
Create a feature branch
Make your changes
Open a pull request

See individual plugin READMEs for plugin-specific guidance.

Support

•Questions: Open a discussion
•Bugs: File an issue
•Feature requests: File an issue

When reporting bugs, include:

•Plugin name and version
•Claude Code version
•Steps to reproduce
•Expected vs actual behavior

Security

To report security vulnerabilities, please email the maintainer directly rather than opening a public issue.

License

MIT License - see LICENSE for details.

Install & Usage

Create the skills directory

mkdir -p .claude/skills

Download the skill file

mkdir -p .claude/skills && curl -o .claude/skills/readme-writer.md https://raw.githubusercontent.com/hculap/better-code/main/SKILL.md

Invoke in Claude Code

/readme-writer

View source on GitHub

readmedocumentationprd-readmedeveloper-experience

Frequently Asked Questions

What is readme-writer?

Generate and audit perfect READMEs using the PRD-README v1 standard

How to install readme-writer?

To install readme-writer, create the .claude/skills directory in your project, then run the curl command to download the skill file. Once installed, invoke it in Claude Code with /readme-writer.

What is readme-writer best for?

readme-writer is a community categorized under General. It is designed for: readme, documentation, prd-readme, developer-experience. Created by Szymon Paluch.