Feature Request: Split into separate skills #43
Description
A monolithic skill is a waste of tokens and is not a best practice when it comes to context engineering. Instead, it would be better to split the current solana-dev-skill into separate skills to reduce context drift and improve output. Separating into dedicated skills also allows for a more thoughtful procedure outline in the SKILL.md.
I would suggest splitting some of the following:
- Program Security Analysis - reviews and identifies issues. This could generate a TODO list md file or annotate code directly where issues are found.
- Anchor Program Development - writes solana program's using anchor framework
- Pinocchio Program Development - writes solana programs using Pinocchio
- Client Development - writes TS code for clients interacting with Solana and smart contracts
- IDL Generation - context for generating IDLs
- Testing - writes testing code
- This could be split by testing framework as well
- Payments - context for payments