Browse Skills

scanning-for-accessibility-issues.md

2

1 export scanning-for-accessibility-issues

2 from "jeremylongshore/claude-code-plugins-nixtla"

3 This skill enables Claude to perform comprehensive accessibility audits. It uses the accessibility-test-scanner plugin to identify WCAG 2.1/2.2 compliance issues, validate ARIA attributes, check keyboard navigation, and assess screen reader compatibility. Use this skill when the user requests an accessibility scan, audit, or compliance check, or when terms like "WCAG", "ARIA", "screen reader", "accessibility testing", or "a11y" are mentioned. It provides actionable insights for improving web application accessibility.

2026-01-05

swagger-ui.md

2

1 export swagger-ui

2 from "daishiman/AIWorkflowOrchestrator"

3 Swagger UI を用いた OpenAPI ドキュメントの公開・統合を支援するスキル。静的HTML/React/Next.js/サーバー埋め込みの構成を整理し、安全なAPI Explorerを構築する。Anchors:• OpenAPI Specification / 適用: API仕様互換 / 目的: 定義の一貫性確保• Swagger UI Documentation / 適用: UI構成 / 目的: 設定項目の正確な適用• OWASP ASVS / 適用: 公開・認証設計 / 目的: セキュリティ要件の確認Trigger:Use when embedding or publishing Swagger UI, configuring OpenAPI docs, or securing API explorer access.swagger ui, openapi docs, api explorer, swagger config, authentication

2026-01-05

responding-to-security-incidents.md

2

1 export responding-to-security-incidents

2 from "jeremylongshore/claude-code-plugins-nixtla"

3 Assists with security incident response, investigation, and remediation. This skill is triggered when the user requests help with incident response, mentions specific incident types (e.g., data breach, ransomware, DDoS), or uses terms like "incident response plan", "containment", "eradication", or "post-incident activity". It guides the user through the incident response lifecycle, from preparation to post-incident analysis. It is useful for classifying incidents, creating response playbooks, collecting evidence, constructing timelines, and generating remediation steps. Use this skill when needing to respond to a "security incident".

2026-01-05

acceptance-criteria-writing.md

2

1 export acceptance-criteria-writing

2 from "daishiman/AIWorkflowOrchestrator"

3 Given-When-Then 形式の受け入れ基準を整理し、テスト可能な完了条件の定義を支援するスキル。要件の明確化、シナリオ設計、検証手順を一貫して整理する。Anchors:• Software Requirements (Karl Wiegers) / 適用: 要件分析・仕様化 / 目的: テスト可能な要件定義の手法• BDD in Action (John Ferguson Smart) / 適用: Given-When-Thenパターン / 目的: 振る舞い駆動開発の基盤Trigger:Use when defining acceptance criteria, user story specifications, or testable requirements.acceptance criteria, user story, GWT, Given-When-Then, testable requirements, definition of done

2026-01-05

test-coverage.md

2

1 export test-coverage

2 from "daishiman/AIWorkflowOrchestrator"

3 テストカバレッジの計測、ギャップ分析、改善計画の策定を行うスキル。リスクベースで優先順位を決め、実行可能な改善ステップに落とし込む。Anchors:• Working Effectively with Legacy Code / 適用: リスク評価 / 目的: 重点領域の特定• xUnit Test Patterns / 適用: テスト設計 / 目的: 有効なテスト追加• Test-Driven Development: By Example / 適用: テスト追加 / 目的: 品質改善Trigger:Use when analyzing test coverage, prioritizing coverage gaps, or planning coverage improvements.test coverage, coverage report, coverage gap, risk-based testing, improvement plan

2026-01-05

python-api-development.md

2

1 export python-api-development

2 from "nekorush14/dotfiles"

3 Implement REST APIs with FastAPI including endpoints, Pydantic models, validation, dependency injection, and error handling. Use when building API endpoints, request validation, or authentication.

2026-01-05

systematic-debugging.md

2

1 export systematic-debugging

2 from "HTRamsey/claude-config"

3 Use when encountering any bug, test failure, or unexpected behavior (including race conditions, deadlocks, concurrency issues) - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) with specialized techniques for deep call stack tracing and concurrency debugging

2026-01-05

electron-ipc-patterns.md

2

1 export electron-ipc-patterns

2 from "daishiman/AIWorkflowOrchestrator"

3 Electronプロセス間通信（IPC）パターンの設計と実装専門知識。安全で効率的なMain-Rendererプロセス通信、contextBridge、型安全なAPI設計を提供。Anchors:• Electron Security / 適用: contextBridge/preload設計 / 目的: セキュアなIPC実装• Clean Architecture / 適用: Main/Renderer境界設計 / 目的: 責務分離と保守性• Type Safety / 適用: TypeScript型契約 / 目的: IPC通信の型安全性確保Trigger:Use when implementing IPC communication patterns, setting up contextBridge, designing typed IPC handlers, securing renderer-main communication, or structuring bidirectional messaging flows.ipcMain, ipcRenderer, contextBridge, invoke, handle, preload, typed IPC

2026-01-05

angular-implementation-specialist.md

2

1 export angular-implementation-specialist

2 from "nekorush14/dotfiles"

3 Implement Angular v21 applications with standalone components, signals-based state management, new control flow syntax (@if, @for, @switch), OnPush change detection, inject() DI, Tailwind CSS, and Vitest testing. Use when creating Angular components/services, implementing signals state, writing Vitest tests, applying Tailwind styling, or working with Angular v21 best practices.

2026-01-05

code-reviewer.md

2

1 export code-reviewer

2 from "9tykeshav/mern-ninja-cc"

3 Use when asked to review MERN stack code - comprehensive code reviewer that checks project health, security, maintainability, performance, testing, and architecture. Combines general code quality analysis with MERN-specific expertise.

2026-01-05

input-validation-security.md

2

1 export input-validation-security

2 from "daishiman/AIWorkflowOrchestrator"

3 Webアプリケーションにおける包括的な入力検証とサニタイズ。型安全な検証、許可リストフィルタリング、コンテキスト対応エンコーディングを通じて、XSS、SQLインジェクション、コマンドインジェクション、パストラバーサルなどの入力ベースの攻撃を防止。Anchors:• OWASP Top 10 / 適用: 全ての入力検証判断 / 目的: 業界標準のセキュリティベースライン• CWE-20 (不適切な入力検証) / 適用: 検証戦略設計 / 目的: 一般的な脆弱性パターン防止• OWASP ASVS 5.1 / 適用: 検証要件仕様 / 目的: セキュリティ検証標準Trigger:Use when implementing user input handling, form validation, API request validation, file upload processing,database query construction, command execution with user input, URL parameter processing, or any data from untrusted sources.

2026-01-05

documentation.md

2

1 export documentation

2 from "duc01226/EasyPlatform"

3 Use for PLANNING documentation with phased analysis (4 phases), gap identification, and structured knowledge modeling. Best for documentation audits, completeness analysis, and documentation strategy planning. NOT for writing actual docs (use tasks-documentation instead).

2026-01-05

test-driven-development-tdd.md

2

1 export test-driven-development-tdd

2 from "robertpelloni/workspace"

3 Write the test first, watch it fail, write minimal code to pass

2026-01-05

security-configuration-review.md

2

1 export security-configuration-review

2 from "daishiman/AIWorkflowOrchestrator"

3 セキュリティ関連設定のレビュー、構成監査、セキュリティベースライン確認を統一的に実施するスキル。脅威モデリングに基づいた設定評価とベストプラクティスの適用を通じて、アプリケーションのセキュリティ態勢を向上させます。Anchors:• 『Web Application Security』（Andrew Hoffman） / 適用: セキュリティ設定監査 / 目的: セキュリティ態勢の向上Trigger:セキュリティ設定レビュー、構成監査、セキュリティベースライン確認時に使用。セキュリティヘッダー設定、CORS設定、認証・認可の監査などの場面で自動選択対象。

2026-01-05

docusaurus-documentation.md

2

1 export docusaurus-documentation

2 from "mcclowes/docusaurus-plugin-cookie-consent"

3 Use when looking up information from the latest Docusaurus documentation at https://docusaurus.io/docs

2026-01-05

generating-security-audit-reports.md

2

1 export generating-security-audit-reports

2 from "jeremylongshore/claude-code-plugins-nixtla"

3 This skill enables Claude to generate comprehensive security audit reports. It is designed to provide insights into an application or system's security posture, compliance status, and recommended remediation steps. Use this skill when the user requests a "security audit report", wants to "audit security", or needs a "vulnerability assessment report". The skill analyzes security data and produces a detailed report in various formats. It is best used to identify vulnerabilities, track compliance, and create remediation roadmaps. The skill can be activated via the command `/audit-report` or its shortcut `/auditreport`.

2026-01-05

validating-pci-dss-compliance.md

2

1 export validating-pci-dss-compliance

2 from "jeremylongshore/claude-code-plugins-nixtla"

3 This skill uses the pci-dss-validator plugin to assess codebases and infrastructure configurations for compliance with the Payment Card Industry Data Security Standard (PCI DSS). It identifies potential vulnerabilities and deviations from PCI DSS requirements. Use this skill when the user requests to "validate PCI compliance", "check PCI DSS", "assess PCI security", or "review PCI standards" for a given project or configuration. It helps ensure that systems handling cardholder data meet the necessary security controls.

2026-01-05

building-cicd-pipelines.md

2

1 export building-cicd-pipelines

2 from "jeremylongshore/claude-code-plugins-nixtla"

3 This skill enables Claude to generate CI/CD pipeline configurations for various platforms, including GitHub Actions, GitLab CI, and Jenkins. It is used when a user requests the creation of a CI/CD pipeline, specifies a platform (e.g., "GitHub Actions"), or mentions specific pipeline stages like "test," "build," "security," or "deploy." This skill is also useful when the user needs to automate software delivery, integrate security scanning, or set up multi-environment deployments. The skill is triggered by terms such as "CI/CD pipeline," "GitHub Actions pipeline," "GitLab CI configuration," or "Jenkins pipeline."

2026-01-05

multi-tenant-safety-checker.md

2

1 export multi-tenant-safety-checker

2 from "patricio0312rev/skillset"

3 Ensures tenant isolation at query and policy level using Row Level Security, automated testing, and security audits. Prevents data leakage between tenants. Use for "multi-tenancy", "tenant isolation", "RLS", or "data security".

2026-01-05

swap-execution.md

2

1 export swap-execution

2 from "Euda1mon1a/Autonomous-Assignment-Program-Manager"

3 Execute resident-requested swaps with safety checks, audit trails, rollback capabilities, and escalation procedures. Use when processing swap requests, validating against constraints, or managing swap lifecycle including rollbacks.

2026-01-05

writing-tests.md

2

1 export writing-tests

2 from "third774/dotfiles"

3 Write behavior-focused tests following Testing Trophy model with real dependencies, avoiding common anti-patterns like testing mocks and polluting production code

2026-01-05

security-gate.md

2

1 export security-gate

2 from "avivsinai/telclaude"

3 Classifies inbound Telegram messages for telclaude as ALLOW/WARN/BLOCK with brief rationale.

2026-01-05

conventional-commits.md

2

1 export conventional-commits

2 from "jedipunkz/dotfiles"

3 Enforces conventional commit message and branch naming conventions with specific prefixes (feat, fix, docs, style, refactor, perf, test, chore). Use when creating git commits, suggesting branch names, reviewing commit messages, or when the user asks about git workflow.

2026-01-05

responding-to-security-incidents.md

2

1 export responding-to-security-incidents

2 from "jeremylongshore/claude-code-plugins-nixtla"

3 Assists with security incident response, investigation, and remediation. This skill is triggered when the user requests help with incident response, mentions specific incident types (e.g., data breach, ransomware, DDoS), or uses terms like "incident response plan", "containment", "eradication", or "post-incident activity". It guides the user through the incident response lifecycle, from preparation to post-incident analysis. It is useful for classifying incidents, creating response playbooks, collecting evidence, constructing timelines, and generating remediation steps. Use this skill when needing to respond to a "security incident".

2026-01-05