Unit Testing

Extract text, fill forms, merge PDFs. Use when working with PDF files, forms, or document extraction. Requires pypdf and pdfplumber packages.

This skill should be used when the user asks to "create lwc component", "lightning web component", "component architecture", "lwc state management", "lwc testing", "jest test", or mentions container/presentational patterns, pub-sub, or LWC best practices.

Research-driven design methodology producing unique, context-appropriate frontends. Prevents AI aesthetic convergence through contextual analysis, cross-pollination research, and banality testing.

Activate when users ask about Claude Code installation, slash commands (/cook, /plan, /fix, /test, /docs, /design, /git), creating/managing Agent Skills, configuring MCP servers, setting up hooks/plugins, IDE integration (VS Code, JetBrains), CI/CD workflows, enterprise deployment (SSO, RBAC, sandboxing), troubleshooting authentication/performance issues, or advanced features (extended thinking, caching, checkpointing).

Beads (bd) issue workflow and repo operations for markdowntown. Use when creating bd tasks, updating status, adding dependencies, running required tests, committing, and pushing to main.

Async testing patterns with pytest-asyncio. Use when writing tests, mocking async code, testing database operations, or debugging test failures.

Right-side-of-V verification/validation orchestration for a change or PR.Produces a single Quality Gate Report with evidence covering: code review,security audit, performance regression risk, requirements traceability,acceptance/UAT scenarios, and (when UI changes) visual regression testing.Use when preparing a PR for merge/release, doing a “ready?” check, orenforcing an engineering quality gate.

Parses legacy requirement documents and generates a traceability matrix linking requirements to tasks, code, and tests. Enforces end-to-end traceability for the migration ensuring every work item maps back to formal documented requirements.

HTML documentation test

This skill should be used when the user asks to "style with Tailwind", "add CSS", "configure theme", "use @theme", "add custom colors", "implement dark mode", "use container queries", "add responsive design", "use OKLCH colors", or discusses styling, theming, or visual design. Always use the latest Tailwind CSS version and modern patterns.

Guide experienced developers through GREEN phase of TDD cycle - writing minimal implementation to pass failing tests

Vercel preview deployment access patterns including automation bypass, protected preview authentication, CI integration, and Playwright/Chrome DevTools configuration. Use when accessing protected Vercel previews, configuring CI for preview testing, or setting up UI validation agents. Triggers on vercel preview, preview deployment, automation bypass, protected preview, preview authentication, UI validation CI.

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Kailash MCP (Model Context Protocol) - production-ready MCP server implementation for AI agent integration. Use when asking about 'MCP', 'Model Context Protocol', 'MCP server', 'MCP client', 'MCP tools', 'MCP resources', 'MCP prompts', 'MCP authentication', 'MCP transports', 'stdio transport', 'SSE transport', 'HTTP transport', 'MCP testing', 'progress reporting', or 'structured tools'.

Master epistemology - the theory of knowledge, justification, and belief. Use for: knowledge, justification, skepticism, sources of knowledge, epistemic virtue. Triggers: 'knowledge', 'epistemology', 'justification', 'belief', 'Gettier', 'skepticism', 'certainty', 'evidence', 'testimony', 'perception', 'reason', 'a priori', 'empirical', 'reliability', 'internalism', 'externalism', 'foundationalism', 'coherentism'.

Unified testing and static analysis suite using uv, pytest, ty, and ruff.

Phase 3 of disciplined development. Executes approved implementation plansstep by step. Each step includes tests, follows the design exactly, andproduces reviewable commits.

Reference the project's defined technology stack including frameworks, languages, databases, testing tools, and deployment infrastructure. Use this skill when making technology decisions or choosing libraries. When working with project configuration files like package.json, requirements.txt, or Gemfile. When setting up new features that need to align with existing technology choices. When onboarding to understand the project's technical foundation. When choosing tools for testing, linting, CI/CD, or third-party services.

Property-based testing with Hypothesis (Python) and fast-check (JS)

Create a C# server-side simulation service following the Plugin/IEventAdapter pattern with configuration, pulse updates, and entity management. Use when creating new simulations, scenario generators, or test data providers for FAAD HMI server.