code-documentation

Description

Use when writing or improving code documentation. Covers docstrings (Google style), README files, API documentation, architecture decision records, and inline comments. Triggers on documentation requests, docstring generation, README creation, or when code needs explanation.

Install

Add the repository(one-time)

/plugin marketplace add btimothy-har/mycc-config

Install the plugin

/plugin install btimothy-har-my-skills-my-skills@btimothy-har/mycc-config

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Links

GitHub Stats

0 forks

Similar Skills

claude-opus-4-5-migration

2 files

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

claude-opus-4-5-migration

47.1k

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

frontend-design

47.1k

Writing Hookify Rules

This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.

hookify

47.1k