eitelcj

18 mods in 2 plugins, 1 repository, 2 stars between them.

blog-draft

01

eitelcj/Claude-Weekend

Skill Claude Code

Draft a blog post from ideas and resources. Use when users want to write a blog post, create content from research, or draft articles. Guides through research, brainstorming, outlining, and iterative drafting with version control.

not rated 2 6mo ago A 47 tokens copy · 91% MIT

eitelcj/Claude-Weekend

Skill Claude CodeCodex

Ensure all communication matches brand voice and tone guidelines. Use when creating marketing copy, customer communications, public-facing content, or when users mention brand voice, tone, or writing style.

not rated 2 6mo ago A 42 tokens copy · 83% MIT

claude-md

03

eitelcj/Claude-Weekend

Skill Claude Code

Create or update CLAUDE.md files following best practices for optimal AI agent onboarding.

not rated 2 6mo ago A 20 tokens original MIT

eitelcj/Claude-Weekend

Skill Claude CodeCodex

Comprehensive code review with security, performance, and quality analysis. Use when users ask to review code, analyze code quality, evaluate pull requests, or mention code review, security analysis, or performance optimization.

not rated 2 6mo ago A 46 tokens copy · 88% MIT

eitelcj/Claude-Weekend

Skill Claude CodeCodex

Generate comprehensive, accurate API documentation from source code. Use when creating or updating API documentation, generating OpenAPI specs, or when users mention API docs, endpoints, or documentation.

not rated 2 6mo ago A 40 tokens original MIT

code-refactor

06

eitelcj/Claude-Weekend

Skill Claude CodeCodex

Systematic code refactoring based on Martin Fowler's methodology. Use when users ask to refactor code, improve code structure, reduce technical debt, clean up legacy code, eliminate code smells, or improve code maintainability. This skill guides through a phased approach with research, planning, and safe incremental…

not rated 2 6mo ago A 65 tokens copy · 95% MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: