writing-claude-prompts
Best practices for writing Claude Code skills, CLAUDE.md files, and prompts optimized for Opus 4.5. Use when creating or reviewing skills, writing agent instructions, or optimizing prompts for Claude 4.x models...
Browse published AI skills maintained by stephendolan. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
14Repository stars across indexed skills
28Repository forks
0Average repository stars per indexed skill
2Repository stars may repeat across skills from the same repository.
Best practices for writing Claude Code skills, CLAUDE.md files, and prompts optimized for Opus 4.5. Use when creating or reviewing skills, writing agent instructions, or optimizing prompts for Claude 4.x models...
Manage personal tasks using OmniFocus via the `of` CLI. Use when discussing tasks, projects, inbox processing, GTD workflow, or adding/organizing to-dos.
Manage school lunch ordering for preschool with catered meals. Analyzes menus based on preferences (avoid rice, prefer BBQ and mac & cheese), helps select meals, processes orders from any source (PDF/screenshot...
Guide revenue analysis using ChartMogul reports. Use when discussing MRR, ARR, churn, retention, cohorts, or subscription metrics. Helps select the right report and interpret results.
Personal culinary advisor for meal planning, recipes, and cooking. Use when discussing food, recipes, meal prep, or cooking questions.
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 avoid...
Create effective Agent Skills following the agentskills.io specification. Use when creating new skills, reviewing existing skills, or improving skill descriptions.
Best practices for project documentation including README, CONTRIBUTING, CHANGELOG, and Markdown files. Use when updating documentation, writing README sections, or maintaining project docs.
Create PR, open pull request, submit for review, push branch. Use when code is ready for review, need to create PR, or "make a PR". Creates concise descriptions focused on the problem being solved.
Audit codebase, assess technical debt, analyze architecture, find structural problems. Use when evaluating code health, planning refactors, or need architectural review. Covers brittleness, coupling, complexity...
Review my code, check for issues, clean up implementation, refine before commit. Use when implementation is done and you want fresh-eyes review, code quality check, or to catch issues before committing.
Handle PR feedback, address review comments, fix PR issues, respond to reviewer. Use when PR has comments to address, need to resolve feedback, or reviewer requested changes.
Commit changes, save work, create git commit. Use when done coding, ready to commit, need to save progress, or "commit this". Creates conventional commit messages focused on why, not what.
Question my plan, probe assumptions, find gaps, challenge design. Use when you have a plan that needs scrutiny, want to surface edge cases, or need help finding what you missed.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.