Content & Writing

by Chachamaru127

Diagnosis and repair guide for errors and failures including CI. Use when user mentions something broken, errors, it doesn't work, CI failures, CIが落ちた, build errors, test failures, or pipeline issues. Do NOT load for: successful builds, new feature implementation, or reviews.

by Chachamaru127

UIコンポーネントとフィードバックフォームを生成。Use when user mentions components, UI, hero sections, forms, feedback, or contact requests. Do NOT load for: authentication features, backend implementation, database operations, or business logic.

by glozow

Automatically generate minor release notes based on the PRs merged into this branch since the last version.

by hackmdio

HackMD command-line interface for managing notes and team notes. Use this skill when users want to create, read, update, delete, or export HackMD notes via CLI, manage team notes, list teams, view browsing history, or automate HackMD workflows. Triggers on mentions of hackmd-cli, HackMD CLI, or requests to interact with HackMD notes programmatically.

by proffesor-for-testing

WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.

by proffesor-for-testing

Unvarnished technical criticism combining Linus Torvalds' precision, Gordon Ramsay's standards, and James Bach's BS-detection. Use when code/tests need harsh reality checks, certification schemes smell fishy, or technical decisions lack rigor. No sugar-coating, just surgical truth about what's broken and why.

by proffesor-for-testing

Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.

by proffesor-for-testing

Conduct context-driven code reviews focusing on quality, testability, and maintainability. Use when reviewing code, providing feedback, or establishing review practices.

by proffesor-for-testing

Regulatory compliance testing for GDPR, CCPA, HIPAA, SOC2, PCI-DSS and industry-specific regulations. Use when ensuring legal compliance, preparing for audits, or handling sensitive data.

by proffesor-for-testing

Apply effective software quality consultancy practices. Use when consulting, advising clients, or establishing consultancy workflows.

by proffesor-for-testing

Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Use when making testing decisions, questioning dogma, or adapting approaches to specific project needs.

by axone-protocol

Guide for writing conventional commit messages. Use when committing changes, writing commit messages, or reviewing commit history.

by axone-protocol

Guide for developing CosmWasm smart contracts using the Abstract SDK. Use when creating new contracts, implementing handlers, or working with contract structure.

by axone-protocol

Guide for generating and maintaining contract documentation from JSON schemas. Use when creating schemas, generating docs, or documenting contract APIs.

by proffesor-for-testing

Advanced exploratory testing techniques with Session-Based Test Management (SBTM), RST heuristics, and test tours. Use when planning exploration sessions, investigating bugs, or discovering unknown quality risks.

by proffesor-for-testing

Apply the Holistic Testing Model evolved with PACT (Proactive, Autonomous, Collaborative, Targeted) principles. Use when designing comprehensive test strategies for Classical, AI-assisted, Agent based, or Agentic Systems building quality into the team, or implementing whole-team quality practices.

by proffesor-for-testing

Internationalization (i18n) and localization (l10n) testing for global products including translations, locale formats, RTL languages, and cultural appropriateness. Use when launching in new markets or building multi-language products.

by proffesor-for-testing

Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate. Use when evaluating test quality, identifying weak tests, or proving tests actually catch bugs.

by proffesor-for-testing

API contract testing, authentication flows, rate limit handling, and error scenario coverage for n8n integrations with external services. Use when testing n8n node integrations.

by proffesor-for-testing

Credential exposure detection, OAuth flow validation, API key management testing, and data sanitization verification for n8n workflows. Use when validating n8n workflow security.

by proffesor-for-testing

Webhook testing, schedule validation, event-driven triggers, and polling mechanism testing for n8n workflows. Use when testing how workflows are triggered.

by proffesor-for-testing

Comprehensive n8n workflow testing including execution lifecycle, node connection patterns, data flow validation, and error handling strategies. Use when testing n8n workflow automation applications.

by proffesor-for-testing

Apply safe refactoring patterns to improve code structure without changing behavior. Use when cleaning up code, reducing technical debt, or improving maintainability.

by proffesor-for-testing

Evidence-based investigative code review using deductive reasoning to determine what actually happened versus what was claimed. Use when verifying implementation claims, investigating bugs, validating fixes, or conducting root cause analysis. Elementary approach to finding truth through systematic observation.

by proffesor-for-testing

Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix. Use when implementing TDD, CI/CD, or early quality practices.

by proffesor-for-testing

Testing in production with feature flags, canary deployments, synthetic monitoring, and chaos engineering. Use when implementing production observability or progressive delivery.

by proffesor-for-testing

Apply Edward de Bono's Six Thinking Hats methodology to software testing for comprehensive quality analysis. Use when designing test strategies, conducting test retrospectives, analyzing test failures, evaluating testing approaches, or facilitating testing discussions. Each hat provides a distinct testing perspective: facts (White), risks (Black), benefits (Yellow), creativity (Green), emotions (Red), and process (Blue).

by proffesor-for-testing

Apply London (mock-based) and Chicago (state-based) TDD schools. Use when practicing test-driven development or choosing testing style for your context.

by proffesor-for-testing

Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.

by proffesor-for-testing

Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency.

by proffesor-for-testing

Strategic test data generation, management, and privacy compliance. Use when creating test data, handling PII, ensuring GDPR/CCPA compliance, or scaling data generation for realistic testing scenarios.

by proffesor-for-testing

Systematic test design with boundary value analysis, equivalence partitioning, decision tables, state transition testing, and combinatorial testing. Use when designing comprehensive test cases, reducing redundant tests, or ensuring systematic coverage.

by proffesor-for-testing

Advanced test reporting, quality dashboards, predictive analytics, trend analysis, and executive reporting for QE metrics. Use when communicating quality status, tracking trends, or making data-driven decisions.

by proffesor-for-testing

AI-powered testability assessment using 10 principles of intrinsic testability with Playwright and optional Vibium integration. Evaluates web applications against Observability, Controllability, Algorithmic Simplicity, Transparency, Stability, Explainability, Unbugginess, Smallness, Decomposability, and Similarity. Use when assessing software testability, evaluating test readiness, identifying testability improvements, or generating testability reports.

by axone-protocol

Guide for writing tests and achieving high code coverage for CosmWasm contracts. Use when creating unit tests, integration tests, or analyzing coverage reports.

by proffesor-for-testing

Advanced visual regression testing with pixel-perfect comparison, AI-powered diff analysis, responsive design validation, and cross-browser visual consistency. Use when detecting UI regressions, validating designs, or ensuring visual consistency.

by proffesor-for-testing

Apply XP practices including pair programming, ensemble programming, continuous integration, and sustainable pace. Use when implementing agile development practices, improving team collaboration, or adopting technical excellence practices.

by athola

Interactive selector and router for architecture paradigms. Use when

by athola

Detect codebase bloat through progressive analysis: dead code, duplication,

by athola

Provides KISS, YAGNI, and SOLID code quality principles for clean code,

by athola

Guidance on when to ask clarifying questions vs proceed with standard

by athola

detailed development workflow with modular patterns for git, code review, testing, documentation, and deployment

by athola

Triggers: architecture review, FPF, functional programming framework, systems architectureArchitecture review using FPF (Functional Programming Framework) methodology.Evaluates codebases through functional, practical, and foundation perspectives.Use when: conducting architecture reviews, evaluating system designDO NOT use when: simple code reviews, bug fixes, documentation updates

by athola

Generate language-specific Makefiles with testing, linting, and automation targets. Use for project initialization and workflow standardization. Skip if Makefile exists.

by athola

Surfaces expert frameworks and proven methodologies before creating OR

by athola

Systematic methodology to reduce skill file size through externalization,consolidation, and progressive loading patterns.Triggers: large skill, skill optimization, skill size, 300 lines, inline code,skill refactoring, skill context reduction, skill modularizationUse when: skills exceed 300 lines, multiple code blocks (10+) with similarfunctionality, heavy Python inline with markdown, functions >20 lines embeddedDO NOT use when: skill is under 300 lines and well-organized.DO NOT use when: creating new skills - use modular-skills instead.Consult this skill when skills-eval shows "Large skill file" warnings.

by athola

Configure three-layer pre-commit system with linting, type checking, and testing hooks. Use for quality gate setup and code standards. Skip if pre-commit is optimally configured.

by athola

Guide project ideation through Socratic questioning and constraint analysis for actionable project briefs. Use for starting projects, exploring problems, comparing approaches, feasibility. Skip if requirements are clear.

by athola

Execute implementation plans with checkpoint validation, progress tracking, and quality gates. Use for task implementation, plan execution, progress tracking. Skip if no plan exists.

by athola

Transform specifications into implementation plans with architecture design and dependency-ordered tasks. Use for spec-to-plan conversion, task breakdown, effort estimation. Skip if no spec exists.

by athola

Transform project briefs into testable specifications with acceptance criteria. Use for requirements translation, spec creation, pre-implementation. Skip if spec exists or still exploring.

by athola

hype, and unnecessary framing. Includes termination and directness guidelines.

by athola

Capture and retrieve PR review knowledge in project memory palaces.

by athola

Prevents sycophantic reasoning through checklist-based analysis, categorical

by athola

Manage Claude Code sessions with naming, checkpointing, and resume strategies.

by athola

Audit shell scripts for correctness, portability, and common pitfalls.

by athola

TDD-style testing methodology for skills using fresh subagent instances

by athola

automatically create GitHub issues for workflow improvements via /fix-workflow.

by athola

Configure GitHub Actions CI/CD workflows for automated testing, linting, and deployment. Use for CI/CD setup and quality automation. Skip if CI/CD configured or using different platform.

by GGPrompts

Patterns for building and debugging TabzChrome itself. Use when working on Terminal.tsx, xterm.js integration, WebSocket I/O, resize handling, or any TabzChrome extension/backend code.

by GGPrompts

Integrate projects with TabzChrome terminals via HTML attributes, WebSocket, JS API, or Spawn API

by GGPrompts

Spawn and manage terminal tabs via TabzChrome REST API. Use when spawning workers, creating terminals programmatically, setting up worktrees for parallel work, or crafting prompts for Claude workers.

by doccker

当用户操作 .sh、Dockerfile、Makefile、.yml、.yaml 文件，或在 Markdown 中编写 bash 代码块时触发。提供 Bash 编写规范。

by paiml

Generates comprehensive, LLM-optimized codebase context using PMAT(Pragmatic AI Labs MCP Agent Toolkit). Use this skill when:- Starting work on unfamiliar codebases- Onboarding to new projects or repositories- Need quick understanding of project architecture- Preparing for refactoring or feature implementation- Creating documentation or technical specificationsOutputs highly compressed markdown (60-80% reduction) optimized for LLM consumption.Supports 25+ languages with architecture visualization, complexity heatmaps, and dependency graphs.

by doccker

Go 开发规范，包含命名约定、错误处理、并发编程、测试规范等

by doccker

Java 开发规范，包含命名约定、异常处理、Spring Boot 最佳实践等

by hikanner

Translate JSON i18n files to multiple languages with AI-powered quality optimization. Use when user mentions translating JSON, i18n files, internationalization, locale files, or needs to convert language files to other languages.

by doccker

Python 开发规范，包含 PEP 8 风格、类型注解、异常处理、测试规范等

by flashinfer-ai

Add pytest tests to validate reference implementations in flashinfer_trace against FlashInfer or SGLang ground truth. Use when validating kernel definitions, adding tests for new op_types, or verifying reference implementations are correct.

by hiromaily

Bitcoin Cash (BCH) API implementation rules. Critical pattern for embedding Bitcoin struct and overriding BCH-specific methods. Use when working on BCH-related code in internal/infrastructure/api/btc/bch/.

by hiromaily

Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type). Use when working on BTC-related code, config files, or shell scripts.

by flashinfer-ai

Clone SGLang, FlashInfer, sgl-cookbook repositories from GitHub to tmp/. Use when setting up the project, preparing for kernel extraction, or when the user needs the source repositories.