| name | description | license |
|---|---|---|
skill-creator |
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. |
Complete terms in LICENSE.txt |
This skill provides guidance for creating effective skills.
At the end of this message, I will ask you to do something. Please follow the "Explore, Plan, Code, Test" workflow when you start.
First, use parallel subagents to find and read all files that may be useful for implementing the ticket, either as examples or as edit targets. The subagents should return relevant file paths, and any other info that may be useful.
Next, think hard and write up a detailed implementation plan. Don't forget to include tests, lookbook components, and documentation. Use your judgement as to what is necessary, given the standards of this repo.
If there are things you are not sure about, use parallel subagents to do some web research. They should only return useful information, no noise.
This guide will walk you through creating a custom MCP (Model Context Protocol) server that integrates with Claude Code, allowing you to extend Claude's capabilities with external tools, APIs, or even other AI models.
MCP (Model Context Protocol) is a protocol that allows Claude to communicate with external servers to access tools and capabilities beyond its built-in features. Think of it as a plugin system for Claude.
| - After making changes, ALWAYS make sure to start up a new server so I can test it. | |
| - Always look for existing code to iterate on instead of creating new code. | |
| - Do not drastically change the patterns before trying to iterate on existing patterns. | |
| - Always kill all existing related servers that may have been created in previous testing before trying to start a new server. | |
| - Always prefer simple solutions | |
| - Avoid duplication of code whenever possible, which means checking for other areas of the codebase that might already have similar code and functionality | |
| - Write code that takes into account the different environments: dev, test, and prod | |
| - You are careful to only make changes that are requested or you are confident are well understood and related to the change being requested | |
| - When fixing an issue or bug, do not introduce a new pattern or technology without first exhausting all options for the existing implementation. And if you finally do this, make sure to remove the old implementation afterwards so we d |