Comprehensive serverless security guide covering threat models, attack techniques, and defense patterns across AWS, Azure, and Google Cloud. Covers IAM credential abuse, storage misconfiguration, code injection, privilege escalation, and supply chain attacks with practical attack/defense examples. Use when developing or securing serverless applications (Lambda, Cloud Run, Azure Functions). For code-level security (OWASP, CodeGuard), use securing-code instead. For AWS development patterns, use developing-aws instead. For GCP development, use developing-google-cloud instead.
Generates security guidance for serverless applications covering threat models, attacks, and defense patterns across AWS, Azure, and GCP.
npx claudepluginhub sumik5/sumik-claude-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
INSTRUCTIONS.mdreferences/AWS-IAM.mdreferences/AWS-LAMBDA.mdreferences/AZURE-FUNCTIONS.mdreferences/CODE-ANALYSIS.mdreferences/GCP-COMPUTE.mdreferences/GCP-STORAGE.mdreferences/THREATS.md詳細な手順・ガイドラインは INSTRUCTIONS.md を参照してください。
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.