ilya-valasiuk
- 16 skills
- 0 followers
- 17 hours ago last updated
- ▌ Issue To Pr · ilya-valasiuk bundleCoordinate a GitHub issue from rough intake through planning, implementation, verification, pull request, and manual merge by reconstructing state and delegating to existing skills. Use when a user provides a GitHub issue and asks to start, implement, continue, deliver, or move it toward a PR; when they ask what comes next in an issue workflow; or when work is split across a parent issue and subissues with integration branches. Also trigger on explicit `$issue-to-pr` requests.
- ▌ Prepare Svg · ilya-valasiuk bundlePrepare and normalize SVG files for reusable UI icon usage. Use this whenever the user wants to import an SVG from Figma or another design source, clean up an SVG icon, make an SVG reusable across different sizes or colors, replace hardcoded SVG dimensions or colors, or standardize SVG assets before developers decide how to render them in code.
- ▌ Init Ghp Labels · ilya-valasiuk bundlePreview and safely install a standardized set of area, workflow, and outcome labels in a GitHub repository. Use when a user asks to initialize, standardize, add, merge, replace, reset, or clean up GitHub labels, including when they provide a GitHub repository or Projects URL. Inspect existing labels first, distinguish existing labels from preset labels, ask whether to add alongside existing labels or replace all other labels, show the exact repository and final changes, require explicit approval, and only then mutate labels.
- ▌ Refine Issue Plan · ilya-valasiuk bundleAnalyze an issue, task, conversation, design, or repository context; decide whether the work should remain in one issue or be split into independently deliverable subissues; and, when it should remain whole, draft or append a clear PRD-style implementation brief. Use when a user asks to refine, flesh out, plan, scope, assess, or rewrite an issue before implementation, or asks whether an issue is ready to implement or should be decomposed.
- ▌ Building Components · ilya-valasiuk bundleBuilds, restructures, and standardizes React components according to project conventions (placement, folder/file naming, exports, props patterns). Use when adding components or when reorganizing existing components during refactors, migrations, or component moves.
- ▌ Organizing Classnames · ilya-valasiukEnforces classNames package usage patterns and Tailwind CSS class ordering conventions in React components. Use this skill whenever writing or reviewing component className props, applying Tailwind classes, using the classnames package, organizing breakpoint-specific styles, writing conditional class expressions, or when the user asks about CSS class ordering, mobile-first responsive patterns, or how to handle className props in components.
- ▌ Recaptcha Integration · ilya-valasiuk bundleAdd, migrate, or review score-based Google Cloud reCAPTCHA Enterprise in TypeScript Next.js applications. Use this skill when protecting forms, API routes, route handlers, or server actions; configuring reCAPTCHA actions, score thresholds, environment variables, browser token generation, or server assessments; or reusing the bundled project-standard scaffold. Do not use it for unrelated checkbox or image CAPTCHA implementations.
- ▌ Report Implementation · ilya-valasiuk bundleVerify every acceptance criterion for completed repository work, review the complete implementation against its intended base, and report the outcomes and verification results to the relevant GitHub issue. Use whenever the user asks to update an issue after implementation, summarize completed work in an issue, add implementation or verification notes, or report finished work before opening a PR. Run once after the current issue or subissue is fully implemented, never at per-commit checkpoints. Add an issue comment by default; only edit the issue body when explicitly requested.
- ▌ Review Implementation · ilya-valasiuk bundleDiscover and run a project's verification checks, then review the complete implementation branch against its intended base, including committed and local changes. Use when Codex needs to verify an implementation before a GitHub issue update, PR, commit, handoff, or release note; when the user asks to review code; or when the user asks to run lint, typecheck, tests, build checks, or all project checks.
- ▌ Creating Pull Requests · ilya-valasiuk bundlePrepare, preview, and open pull requests using the team's Features/Fixes template, correct base-branch routing, linked GitHub issues, and an approval checkpoint before any push or PR creation. Use when the user asks to create, draft, preview, or open a pull request, including child-issue PRs into a parent integration branch, normal PRs into the discovered default branch, and explicitly requested release PRs.
- ▌ Design Tokens Tailwind · ilya-valasiuk bundleGenerate or update Tailwind CSS v4 CSS-first theme variables from design token JSON files. Use this skill whenever the user asks to sync, convert, regenerate, import, or update styles, Tailwind config, @theme CSS, colors, typography, spacing, breakpoints, shadows, radii, or other design tokens from design-tokens.json or another token JSON file, especially in Tailwind 4 projects that use CSS-first configuration instead of tailwind.config.js. This skill is reusable across projects and should be used even when the user only says "update styles from tokens" or provides a token export path.
- ▌ Managing Release Issue · ilya-valasiukMaintain a phased production release checklist in a GitHub issue. Use when a user finishes configuring a service, environment, or integration outside production and wants to record its production counterpart, asks to update a release issue or checklist, or prepares production steps for a release.
- ▌ Split Issue Into Subissues · ilya-valasiuk bundleAnalyze a parent issue or task, decompose it into smaller independently implementable subissues, visualize dependencies, draft complete issue bodies, and create and link the approved subissues while preserving the parent body. Use when a user asks to split, break down, decompose, parallelize, or create child issues from an existing issue, epic, feature, bug, or implementation task.
- ▌ Generating Payload Migration · ilya-valasiuk bundleExplains how to create and review Payload CMS migrations. Use this skill whenever the user changes Payload collections, globals, fields, indexes, relationships, database adapter-backed schema, or wants to generate, rename, review, or decide whether to create a Payload migration.
- ▌ Generating Typeorm Migration · ilya-valasiuk bundleExplains how to create and review TypeORM migrations. Use this skill whenever the user wants to change an entity, add or update schema-related database objects, generate a migration, or decide whether a database change should be handled through TypeORM metadata or a custom migration.
- ▌ Structuring Nextjs App Router · ilya-valasiuk bundleStandardize and preserve Next.js App Router project structure across `src/`, including route files, page composition, API modules, server actions, hooks, providers, helpers, and shared utilities. Use this skill whenever the user asks to add, move, rename, refactor, or review files in a Next.js App Router codebase, especially if the task affects file placement, page architecture, or folder naming.