vinvcn

Find the right skill and sequence for your current development task, from shaping an idea to implementation, debugging, and review. The guide also explains when to prototype, prepare specifications, or move work into a fresh session.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose a workflow for turning an idea into working software
• Find the starting point for a difficult bug investigation
• Plan specifications and tickets for work across multiple sessions

Review issues and external pull requests, classify them, verify their claims, and assign a handling state. The skill checks existing implementations and past rejections, requests missing details, and prepares briefs that agents or human maintainers can act on.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find issues and external PRs needing attention
• Reproduce reported bugs and verify PR changes
• Prepare work briefs for agents

Turn existing Markdown material into an article by choosing among suggested next passages. Establish what readers already know, introduce concepts before relying on them, and build the article one selected passage at a time.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build an article from collected Markdown material
• Choose among different openings
• Introduce unfamiliar concepts in a readable order

Create short HTML lessons and interactive practice tailored to learning goals and prior progress. Keep learning records, trusted resources, and quick reference materials so study can continue across sessions with exercises designed for long-term retention.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Learn a new topic through short, focused lessons
• Continue studying from previous learning records
• Review with printable reference sheets

Review a coding session to identify improvements to the agent’s working environment. Get prioritized suggestions for finding files, strengthening automated checks, clarifying guidance, reducing costly tool calls, and accessing missing information.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing why a coding agent struggled
• Finding gaps in automated checks
• Simplifying agent instructions

Refine a plan or design through an ongoing interview while creating documentation. The skill combines grilling and domain-modeling to produce architectural decision records, which capture design decisions, and a glossary of relevant terms.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Refine a plan through follow-up questions
• Explore a design through an interview
• Record design decisions during discussion

Write and revise documents that guide AI agents, including skills and AGENTS.md files. Organize steps, define checkable completion criteria, and clarify when to load references so agents can follow a consistent process across different tasks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write or revise instructions for a skill
• Review AGENTS.md or CLAUDE.md guidance
• Move detailed references out of an overloaded main document

Shape Markdown notes, fragments, or transcripts into a separate article through a collaborative drafting session. Choose an opening, establish what readers already know, and develop each paragraph or block in an order that introduces concepts before relying on them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning scattered notes into an article
• Developing an article from a transcript
• Comparing openings to choose an angle

Implement work described in a specification or set of tickets, using test-first development where agreed. Run type checks and tests throughout, review the completed changes, and commit the work to the current branch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing work from a specification
• Completing a set of development tickets
• Checking changes with types and tests

Turn an existing conversation and codebase context into a feature specification. Organize user needs, implementation decisions, testing plans, and scope, then publish the specification to the project’s issue tracker with a label marking it ready for agent work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a feature discussion into a specification
• Recording implementation and testing decisions
• Publishing an issue ready for agent work

Migrate TypeScript test data from type assertions to @total-typescript/shoehorn helpers. Use partial objects for focused tests and deliberately invalid data for error cases, then check that the migrated tests pass type checking.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Replace type assertions in test files
• Create test objects with only the properties needed
• Supply deliberately invalid data for error tests

Turn a course plan into numbered exercise folders with starter readmes for problems, solutions, and explanations. Check the structure with the specified lint command, fix errors, and handle exercise moves or renaming while preserving Git history.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating exercise folders from a course plan
• Preparing problem, solution, and explanation stubs
• Checking exercise structure and readme links

Ask an agent to restate an unclear message with more background, using the conversation's language and the project's glossary. It applies simplified technical writing guidance to help explain how the discussion reached its current point.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Asking for a clearer explanation of the previous message
• Adding background to understand the reasoning
• Aligning explanations with project glossary terms

Examine a plan, decision, or idea through rounds of questions with recommended answers. Each response reveals the next decisions to discuss, helping clarify assumptions and build a shared understanding before taking action.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Stress-testing a plan before acting
• Clarifying the assumptions behind an idea
• Working through decisions in dependency order

Create a Markdown questionnaire for someone who has information you need. Clarify the recipient and required decisions, then produce prioritized questions with context and answer spaces for asynchronous replies or a meeting.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Requesting information from a subject expert
• Gathering answers without scheduling a meeting
• Preparing questions for a discovery meeting

Explore a writing topic through ongoing questions and collect sentences, experiences, metaphors, and unfinished thoughts in one Markdown file. Build a pool of usable material without committing to an outline or article structure.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explore a writing topic before choosing a structure
• Collect striking sentences, experiences, and metaphors
• Find a name for a recurring idea

Set up dependency-cruiser in a TypeScript repository to enforce package boundaries: outside code uses public entry files while implementation stays in subfolders. Add checks, a starter package, and documentation, then verify that forbidden imports fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preventing imports into package internals
• Adding boundary checks to existing validation commands
• Creating a starter package with public entry files

Build a disposable prototype to answer a specific design question. Use a shareable HTML demo to explore logic and state changes, or compare distinct UI variations on one route, then record the decision and retain the prototype separately.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trying state transitions through an interactive demo
• Sharing a logic prototype with non-developers
• Comparing distinct UI designs on one route

Set up the repository settings that engineering skills read: where work is tracked, which triage labels to use, and where domain documents belong. Review existing files and confirm drafts before writing configuration documents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a repository before using engineering skills
• Configure GitHub, GitLab, or local Markdown issue tracking
• Match triage labels to an existing workflow

Summarize the current conversation into a handoff document so another agent can continue the work. Reference existing artifacts, suggest skills for the next session, remove sensitive information, and save the document in the operating system’s temporary directory.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Continuing work with a fresh agent
• Preparing context for the next session
• Focusing a handoff on the next task

Set up checks that run before each commit using Husky, lint-staged, and Prettier. Format staged files, run existing type-check and test scripts, then verify and commit the configuration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding automated checks before commits
• Formatting staged files with Prettier
• Running type checks and tests before committing

Turn a specification and its linked tickets into code. Multiple agents work on available tasks in separate worktrees, combine changes on one integration branch, and complete a code review before preparing the result for review or closing tickets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a specification and its linked tickets
• Working through tasks with blocking dependencies
• Coordinating parallel implementation in separate worktrees

Build features or fix bugs by writing one failing test, then the minimum code needed to pass it. Test agreed public interfaces, the boundaries callers use, to check behavior without depending on internal implementation details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a feature through test-first development
• Fixing a bug with a failing test first
• Writing behavior-focused integration tests

Draft or revise pull request descriptions that show the change, evidence of its behavior, and merge risks. Use concise diagrams, trees, or diffs alongside before-and-after results to help reviewers assess impact and how easily changes can be reversed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft a description for a pull request
• Explain a refactor with a tree or diff
• Present before-and-after evidence for a fix