Skip to content

Instantly share code, notes, and snippets.

View stelmakh's full-sized avatar

Volodymyr Stelmakh stelmakh

View GitHub Profile
name description argument-hint
implement
Skip exploration and start coding immediately from a referenced plan (PRD or tech spec).
plan-file-path

You are in implementation mode. Your job is to execute a plan, not explore or ask questions.

Instructions


name: code-reviewer description: "Use this agent when code has been written or modified and needs review before being finalized. This includes after implementing a feature, fixing a bug, refactoring code, or any time the user explicitly asks for a code review. The agent should be used proactively after significant code changes are made.\n\nExamples:\n\n- User: "Please implement a caching layer for the API responses"\n Assistant: implements the caching layer\n Assistant: "Now let me use the code-reviewer agent to review the changes I just made."\n (Since a significant piece of code was written, use the Task tool to launch the code-reviewer agent to review the implementation.)\n\n- User: "Can you review my latest changes?"\n Assistant: "I'll use the code-reviewer agent to perform a thorough review of your recent changes."\n (The user explicitly requested a review, so use the Task tool to launch the code-reviewer agent.)\n\n- User: "Refactor the authentication module to use the n


name: tech-spec-architect description: "Use this agent when the user wants to create a Technical Specification from a Product Requirement Document (PRD), when they need architectural design for a new feature or change, or when they need to translate business requirements into technical plans. This includes scenarios where the user has a PRD ready to share, wants to plan implementation of a feature, or needs a structured technical document for engineering teams.\n\nExamples:\n\n- User: "I have a PRD for a new filtering system in the CMS, can you help me create a tech spec?"\n Assistant: "I'll use the tech-spec-architect agent to analyze your PRD and create a comprehensive Technical Specification."\n [Launches tech-spec-architect agent via Task tool]\n\n- User: "We need to add real-time collaboration to the content editor. Here's the requirements document."\n Assistant: "Let me launch the tech-spec-architect agent to work through this PRD and produce a detailed technical specification."\


name: test-engineer description: "Use this agent when you need to write, review, or improve tests (unit, integration, or e2e), design testable architectures, create stable mocks/stubs/fakes, refactor code for better testability, or establish testing strategies and patterns. This agent should be used proactively after writing significant code to ensure proper test coverage.\n\nExamples:\n\n- User: "Write a service that fetches user profiles from an API and caches them"\n Assistant: "Here is the user profile service with caching logic."\n \n Since significant code was written, use the Task tool to launch the test-engineer agent to write comprehensive tests for the new service, including unit tests with mocked API calls and cache behavior verification.\n Assistant: "Now let me use the test-engineer agent to write tests for this service."\n\n- User: "Can you review the tests in our authentication module?"\n Assistant: "I'll use the test-engineer agent to rev


name: prd-writer description: "Use this agent when the user asks for a Product Requirement Document (PRD), product spec, feature specification, or detailed requirements documentation for a component, model, feature, or system. This includes requests like 'write a PRD for...', 'create requirements for...', 'spec out this feature...', 'document the expected behavior of...', or 'I need a product doc for...'.\n\nExamples:\n\n- user: "Write a PRD for the table-view component"\n assistant: "I'll use the prd-writer agent to create a detailed Product Requirement Document for the table-view component."\n The user is requesting a product requirements document for a specific component. Use the Task tool to launch the prd-writer agent to analyze the component and produce a comprehensive PRD.\n\n- user: "I need to spec out the capabilities system and how lazy loading works"\n assistant: "Let me use the prd-writer agent to create a detailed specification for the capabilities

Frontend Engineer — Wix CMS

Про продукт

Wix CMS — це платформа для керування контентом Wix-сайтів. Складний продукт для просунутих користувачів та агенцій, де критичні стабільність, перфоманс і якість архітектури.

Тут є детальний опис - link

А тут відео, з основним флоу роботи - link.

Шукаємо Frontend Engineer в команду Wix CMS

Привіт. Наш колега перейшов в іншу команду, тож ми шукаємо фронтенд-інженера в нашу.

Команда

Наразі у нас 4 фронт-енд розробники. Всі дуже досвідчені, кожен в чомусь крутий і всі добре доповнюють один одного. Ідеальні умови для професійного зросту :)

No assholes policy, всі адекватні. Працюємо віддалено, іноді збираємось разом, особливо на свята. Вся команда в Києві.

Що ми робимо

@stelmakh
stelmakh / .editorconfig
Last active October 10, 2022 18:03
Dropticket project setup
# EditorConfig
# https://EditorConfig.org
# top-most EditorConfig file
root = true
# Unix-style newlines with a newline ending every file
[*]
charset = utf-8
end_of_line = lf
import React from 'react'
import './index.css'
class Input extends React.Component {
onChange = (evt) => {
const { onChange, disabled } = this.props
const { value } = evt.target
if (!disabled && onChange) {
onChange(value)
.input {
padding: 8px 16px;
font-size: 16px;
border-radius: 4px;
outline: none;
border: 1px solid #e2e2e2;
}
.input.error {
border-color: red;