Claude Skills by paulasilvatech

Provide verified grep command libraries for React 18.3.1 and React 19 migration audits, including deprecated APIs, removed APIs, unsafe lifecycle methods, batching risks, tests, dependencies, and peer conflicts. Use this skill when writing or running React migration audit scan commands.

Diagnose and fix React 18 automatic batching regressions in class components. Use when multiple setState calls occur after await, inside setTimeout, Promise .then() or .catch(), native addEventListener callbacks, or when tests fail because they assert intermediate state after a React 18 upgrade.

Check React 18.3.1 and React 19 dependency compatibility before npm installs, peer-dependency resolutions, or upgrade plans. Use when reviewing a React upgrade matrix, resolving npm peer conflicts, choosing minimum compatible package versions, deciding on --legacy-peer-deps, or separating a react-router v5 to v6 migration.

Rewrite Enzyme tests for React 18 into React Testing Library behavior tests. Use when a test imports enzyme, uses shallow, mount, wrapper.find(), wrapper.simulate(), wrapper.prop(), wrapper.state(), wrapper.instance(), Enzyme configure/Adapter, or needs React 18-compatible RTL migration patterns.

Migrate React legacy context API usage from contextTypes, childContextTypes, and getChildContext to modern createContext. Use this skill when touching legacy context in class or function components because provider and every consumer must be updated together to avoid React 18 warnings and React 19 runtime failures.

Migrate unsafe React class component lifecycle methods to React 18.3.1-safe patterns. Use when fixing `componentWillMount`, `componentWillReceiveProps`, `componentWillUpdate`, `UNSAFE_` lifecycle warnings, choosing `getDerivedStateFromProps` versus `componentDidUpdate`, or adding `getSnapshotBeforeUpdate`.

Migrate React string refs, ref="name" assignments, and this.refs.name access to React.createRef(), callback refs, or child ref forwarding. Use this skill when migrating React 18.3.1 warnings or React 19 removals involving single refs, multiple refs, list refs, callback refs, or refs passed to child components.

Preserve React 18 concurrent patterns and adopt React 19 APIs including useTransition, useDeferredValue, Suspense, use(), useOptimistic, useActionState, useFormStatus, and Actions. Use when reviewing React 19 migrations, auditing concurrent rendering, cleaning up Suspense data fetching, or adopting post-migration APIs.

Apply React 19 source-file migration patterns for root APIs, hydration, unmounting, findDOMNode, forwardRef, defaultProps, useRef initial values, legacy context, string refs, propTypes comments, and unused React imports. Use this skill when fixing React 19 source migration issues.

Provide before-and-after migration patterns for React 19 test compatibility, including act() imports, react-dom/test-utils removal, Simulate to fireEvent conversion, StrictMode call count changes, async act warnings, and custom render helper checks. Use when updating React test files for React 19.

Use this skill when the user works with RHDH Jira projects RHIDP, RHDHPLAN, RHDHBUGS, or RHDHSUPP using acli, GraphQL, and REST fallback. Trigger for Jira keys, creating features, epics, stories, tasks, bugs, assigning owners, refinement, sprint planning, sprint reports, release status, status updates, duplicate checks, sizing, or sprint ceremony prep.

Use this skill when the user tests Red Hat Developer Hub plugins locally with rhdh-local-setup. Trigger for enabling or disabling plugins, switching customized and pristine modes, running local plugin tests, starting or stopping RHDH, health checks, backup and restore, environment variables, 504 errors, startup failures, and local troubleshooting.

Route and support Red Hat Developer Hub (RHDH) work across plugin development, overlay management, local testing, Jira, repository navigation, version compatibility, CI debugging, and environment setup. Use this skill when the user asks about RHDH, Developer Hub, dynamic plugins, overlays, rhdh-local, RHDH Jira, plugin catalogs, repositories, or CI/CD tasks.

Add educational comments to existing code files while preserving encoding, line endings, indentation, syntax, and build correctness. Use this skill when the user asks to annotate a file for learning, add teaching comments, explain code inline, adjust comment detail or repetitiveness, or use Line Number Referencing.

Transform a Python script into a polished beginner-friendly project by refactoring code, adding instructional comments, and generating a complete README.md tutorial. Use this skill when asked to explain, comment, clean up, teach, or turn a Python script into a tutorial project.

Convert plaintext or generic text documentation into well-structured Markdown while preserving source content and applying explicit instructions, documented options, or a converted guide file. Use when asked to convert a file to Markdown, finalize Markdown formatting, apply header patterns, use a guide document, or target GitHub, StackOverflow, VS Code, GitLab, or CommonMark rendering.

Create a high-quality AGENTS.md file for a repository by inspecting project structure, workflows, commands, tests, and conventions. Use this skill when the user asks to create, update, or improve AGENTS.md, add coding-agent instructions, document repo setup for agents, or follow the agents.md format.

Create a new repository-root llms.txt file from repository structure and documentation according to the llms.txt specification. Use when users ask to create llms.txt, generate LLM navigation, document repository structure for LLMs, or add an llms.txt compliant with https://llmstxt.org/.

Create or improve a concise, appealing, project-specific README.md with a clear overview, setup, usage, and practical examples. Use this skill when the user asks to generate, refresh, polish, rewrite, or make a repository README more useful for GitHub readers.

Create a tldr page from documentation URLs and command examples, requiring both URL and command name. Use this skill when the user asks to generate a concise tldr-pages style command reference from official docs and examples.

Write and review C# XML documentation comments for public and complex internal APIs, including summaries, remarks, examples, cref links, parameters, returns, constructors, properties, and exceptions. Use when asked for C# documentation best practices or XML comments.

Create, review, and structure software documentation with the Diátaxis framework: tutorials, how-to guides, reference, and explanation. Use when the user asks for a Diátaxis documentation expert, a documentation outline, markdown docs, audience-focused docs, or help classifying documentation type.

Translate an MkDocs documentation stack from docs/docs/en and docs/docs/includes/en into a target ISO 639-1 or locale folder, preserving Markdown structure and updating mkdocs.yml i18n locale, nav_translations, and admonition_translations. Use when the user asks for mkdocs ai translator, MkDocs translation, docs localization, or adding a new documentation locale.

Create or update standardized object-oriented component documentation from source code or existing Markdown docs using create-mode and update-mode guidance. Use when the user asks to document a class, component, folder, public API, architecture relationships, design patterns, or refresh existing OO component documentation.

Create tldr-style markdown summaries for GitHub Copilot customization files, MCP server documentation, Copilot documentation URLs, or focused Copilot usage queries. Use when asked to "tldr this prompt", "summarize this agent", "make a tldr for MCP docs", "summarize Copilot instructions", or "show examples for this Copilot file".

Update an existing repository-root llms.txt file to match current documentation, specifications, examples, configuration, and repository structure. Use when users ask to update llms.txt, refresh LLM navigation, fix stale llms links, or keep llms.txt compliant with https://llmstxt.org/.

Update a Markdown file with an index, list, or table of files from a specified folder, preserving existing document structure and relative links. Use when the user asks to index a folder in Markdown, refresh a file table, list docs or scripts in a README, or maintain a contents section from filesystem files.

Write a coding standards document by analyzing existing file or folder style. Use when asked to infer project rules, generate CONTRIBUTING.md or CODING_STANDARDS.md, add standards to README.md, find or fix style inconsistencies, choose a minimal or verbose template, or fetch language style references.

Run conversational onboarding for Roundup status briefings and write the user style configuration. Use this skill when the user asks to set up roundup, calibrate status updates, configure briefings, personalize communication style, or change how this conversation should feel.

Generate personalized status briefings from a configured Roundup profile and available data sources such as GitHub, email, Teams, Slack, and Google Workspace. Use when the user asks for a roundup, leadership briefing, team update, weekly status, audience-specific update, or draft in their communication style.

Generate a complete Ruby Model Context Protocol server project using the official MCP Ruby SDK gem. Use when the user asks to create or scaffold a Ruby MCP server with tools, prompts, resources, schemas, annotations, structured content responses, tests, stdio usage, and HTTP usage examples.

Generate a complete Rust Model Context Protocol server project using the official rmcp SDK, including transports, tools, prompts, resources, state, tests, and client configuration. Use this skill when the user asks to create a Rust MCP server, rmcp project, MCP tool server, stdio/SSE/HTTP transport server, or project requirements for a Rust MCP implementation.

Review or generate Salesforce Apex classes, triggers, handlers, batch jobs, and test classes with quality guardrails for bulk safety, explicit sharing, CRUD/FLS enforcement, SOQL injection prevention, PNB tests, trigger architecture, and modern Apex idioms. Use when asked to catch governor limit risks, security gaps, and Apex deployment quality issues.

Apply Salesforce UI component standards for Lightning Web Components, Aura, Visualforce, SLDS 2, WCAG 2.1 AA, secure Apex access, component communication, XSS, CSRF, FLS/CRUD, view state, and Jest tests. Use when building or reviewing Salesforce LWC, Aura components, Visualforce pages, or Apex controllers used by UI components.

Salesforce Flow architecture decisions, flow type selection, bulk safety validation, fault handling, automation density, Screen Flow UX, and deployment safety. Use this skill when designing or reviewing Record-Triggered, Screen, Autolaunched, Scheduled, or Platform Event flows before activation or deployment.

Review and improve AI prompts for safety, bias, security, privacy, effectiveness, robustness, and testability. Use this skill when the user asks to audit a prompt, harden a system prompt, identify prompt injection risk, reduce bias, improve guardrails, or produce a safer enhanced prompt.

Generate AI images and visual assets through OpenAI gpt-image-2 or Google Gemini image models. Use when the user asks to generate, create, or make images, textures, icons, sprites, artwork, mockups, product visuals, or batch image assets from a text description.

Generate GitHub issue planning and project automation artifacts from feature planning documents, including Epic > Feature > Story/Enabler > Test hierarchy, priorities, dependencies, estimates, Kanban fields, and issue creation checklists. Use this skill when asked to break down a feature into GitHub issues, project plans, sprint planning, or automated project tracking.

Create comprehensive test planning, QA strategy, GitHub issue breakdowns, and quality validation plans from feature artifacts. Use when asked to produce a test strategy, break down test work, plan QA for an epic or feature, apply ISTQB techniques, map ISO 25010 quality characteristics, or create test issues for GitHub project management.

Creates formal, AI-optimized specifications for existing GitHub Actions CI/CD workflows by extracting triggers, jobs, dependencies, contracts, quality gates, error paths, environments, governance, and change rules. Use this skill when asked to document a workflow, create a CI/CD workflow specification, summarize a GitHub Actions file for maintenance, or produce spec/spec-process-cicd-[workflow-name].md.

Create or update one GitHub feature issue from a specification file using a feature_request.yml template when available. Use when the user asks to create a GitHub issue from a specification, turn a spec into a feature request, or file one issue that captures a complete specification.

Create GitHub Issues for unimplemented requirements found in specification files, avoiding duplicates and using the feature_request.yml issue template when available. Use this skill when asked to turn unmet specs, missing requirements, or unimplemented acceptance criteria into GitHub Issues.

Create a new AI-ready specification file in /spec/ that defines solution requirements, constraints, interfaces, dependencies, acceptance criteria, test strategy, and validation criteria. Use this skill when the user asks to create a specification, draft an AI-ready spec, define requirements, or apply best practices for AI-ready specifications.

Run an interactive task-refinement workflow before implementation by asking targeted questions, exploring the project, defining deliverables, and confirming success criteria. Use when the user asks to act informed, clarify before doing, plan with human input, or refine scope before execution. Requires Joyride human input support.

Identify missing features, prioritize implementation gaps, write practical MVP specifications, and create GitHub issues with dependencies and acceptance criteria. Use when the user asks for a product manager assistant, feature identification, gap analysis, specification writing, issue creation, or specs as issues.

Generate production-ready Product Requirements Documents for software systems and AI-powered features. Use when starting a product or feature cycle, translating a vague idea into requirements, defining AI system requirements, planning a feature, or creating a stakeholder source of truth.

Update an existing AI-ready specification file in /spec/ from new requirements or code changes, preserving precise requirements, constraints, interfaces, acceptance criteria, and validation structure. Use this skill when the user asks to update a specification, revise requirements, sync a spec with code, or apply best practices for AI-ready specifications.

Generate implementation.md from a structured autonomy plan.md, including concrete steps, complete code blocks, file paths, verification checklists, and STOP & COMMIT boundaries. Use this skill when the user has plans/{feature-name}/plan.md and asks to produce implementation documentation for a PR plan.

Execute an existing structured autonomy implementation plan exactly as written, updating checked items and stopping at plan-defined handoff points. Use this skill when the user asks to implement a plans/{feature-name}/implementation.md plan, continue the next unchecked implementation step, or carry out structured autonomy implementation work without scope drift.

Research a feature request and produce a structured autonomy plan at plans/{feature-name}/plan.md with commit-sized implementation steps, affected files, branch name, tests, and clarification markers. Use when asked to plan a feature, prepare structured autonomy implementation, or create a PR-sized development plan without writing code.