buyoung
- 21 skills
- 0 followers
- 6 hours ago last updated
- ▌ Release It · buyoung bundlerelease-it configuration, setup, and plugin development. Triggers on .release-it.* config files, release-it CLI usage, version bumping, changelog generation, npm publishing, GitHub/GitLab releases, git tagging, hooks lifecycle, pre-release workflows, CI/CD pipelines, monorepo strategies, @inquirer/prompts interactive service-app releases, and custom plugin development.
- ▌ Vite Guide · buyoung bundleUse for explaining, designing, implementing, reviewing, refactoring, migrating, or diagnosing Vite 7/8 applications when runtime, build, plugin, deployment, performance, or compatibility judgment is needed, including CSR SPA/MPA, backend-embedded clients, and Vite's own SSR development and production integration. Excludes framework-specific SSR APIs, RSC/Server Functions implementation, custom server-runtime construction, unsupported Vite majors, unrelated non-client bundling, and UI-framework-only decisions.
- ▌ Code Review · buyoung bundleReview Git changes for concrete defects and evidence-backed maintainability concerns. Use for code review of commits, ranges, staged changes, uncommitted changes, or selected files. With no target, review all staged, unstaged, and untracked changes; ask for a target if none exist. Trace behavior in the selected version, challenge suspected defects, exclude style-only preferences, and provide an approval verdict only when requested.
- ▌ React Guide · buyoung bundleUse for explaining, designing, implementing, reviewing, refactoring, migrating, or diagnosing React 18/19 applications when React-specific judgment is needed for CSR, SSR, streaming, hydration, structure, APIs, Hooks, state/data, async UI, accessibility, performance, compatibility, or Compiler behavior. Covers React's own server-rendering APIs; excludes framework-specific APIs, RSC/Server Functions implementation, custom server-runtime construction, unsupported React majors, build-tool-only work, and styling/copy-only work.
- ▌
- ▌ Typst Creator · buyoung bundleCreate, update, review, migrate, or diagnose Typst (.typ) source for documents, reports, papers, and presentations. Use for Typst markup, styling, scripting, math, layout, bibliography, and compiler/export issues. Resolve the compiler and generate source for stable Typst 0.13.0 through 0.15.1, including source shared across supported releases.
- ▌ Document Writing · buyoung bundleCreate, update, rewrite, review, fact-check, or normalize durable human-readable documents. Use for explanatory overviews, action guides, references or specifications, proposals, analysis reports, policies, troubleshooting runbooks, records or meeting notes, Feature Design Docs (FDDs), and Design System Documents for product UI or any digital storefront's visual assets, including the document portion of mixed document-and-production requests. Route by the requested artifact and load only its references. Do not use for implementation plans, task briefs, tickets, system or architecture design docs, source changes, pure UI or asset production, or short chat-only answers.
- ▌ Kysely Converter · buyoung bundleConvert raw SQL into type-safe Kysely TypeScript, write Kysely queries from requirements without source SQL, modify or refactor existing Kysely code, and diagnose Kysely type errors. Use for SELECT, INSERT, UPDATE, DELETE, joins, CTEs, expressions, and window functions with version-aware SQL dialect handling. Excludes migration operations and work on other query builders.
- ▌ Task Brief Creator · buyoung bundleGenerate an executable implementation work-plan Markdown at `docs/briefs/` from planning notes or a rough task description. Work brief, task brief, handoff brief, implementation ticket, and task spec remain trigger aliases. Nine required sections are keyed to Conventional Commits types so coding agents switch behavior (refactor → preserve, fix → reproduce first, perf → measure first). Briefset mode emits a parent execution-management document plus N child briefs when the input describes multiple execution contexts. Explicit task intent only — use when the user invokes this skill or asks for a work plan, implementation plan, work brief, task brief, handoff brief, implementation ticket, or task spec for a coding agent. Not for prose summaries, status reports, design docs, or meeting notes. For the plain-language caveman variant, use task-brief-creator-caveman instead.
- ▌ Agents Md Generator · buyoung bundleAnalyze repository structure and generate or update standardized AGENTS.md files that serve as contributor guides for AI agents. Supports both single-repo and monorepo structures. Measures LOC to determine character limits and produces structured documents covering overview, optional ownership maps, patterns, conventions, and working agreements. Update mode refreshes only standard sections while preserving user-defined custom sections. Existing unmarked files require a concrete change preview and one-time user confirmation before adoption; heading matches alone never authorize rewriting. Use when the user wants an AGENTS.md generated or refreshed — setting one up for a new repository, onboarding AI agents to an existing codebase, updating an existing AGENTS.md after meaningful project changes, or when the user mentions AGENTS.md. Not for CLAUDE.md, README, or other documentation files.
- ▌ Code Security Audit · buyoung bundlePerforms OWASP-based code security audits on any codebase. Analyzes source code against ASVS 5.0.0 verification requirements, API Security Top 10 2023 risk patterns, OWASP CheatSheet secure coding practices, and WSTG testing methodologies. Input is a codebase to review; output is a detailed Markdown security audit report. Use when the user requests a security audit, security review, vulnerability assessment, or code security analysis.
- ▌ Jetbrains Vmoptions · buyoung bundleDiagnose and tune JetBrains IDE VM options against the IDE's actual boot runtime, including bundled or custom JetBrains Runtime (JBR) 17, 21, and 25. Use whenever a user asks about JetBrains IDE performance, freezes, startup or indexing speed, memory pressure, garbage collection, heap sizing, `.vmoptions`, or IntelliJ IDEA, WebStorm, PyCharm, GoLand, Rider, CLion, PhpStorm, RubyMine, or DataGrip JVM tuning. Distinguish the IDE process from project JDK, Gradle, build, test, and remote-backend processes; propose evidence-based minimal changes, confirm effective flags after restart, and provide rollback and before/after measurement steps.
- ▌ Linear Issue Worker · buyoung bundleExecute code tasks from Linear sub-issues: resolve dependencies, implement changes, validate Done Criteria, and sync status. Use when asked to work on, implement, or start coding a Linear issue (e.g. PRI-42).
- ▌ Linear Issue Creator · buyoung bundleCreate structured Linear issues (main + sub-issues) with project linking, title prefix, and labeling. Supports two workflows: Generic (code tasks) and PRD Pipeline (제품 요구사항 정의서). PRD Pipeline applies content-strategy, content-production, content-humanizer, copy-editing principles to produce high-quality issue descriptions targeting fullstack developers in Korean. Use when asked to create, register, or break down tasks into Linear issues. Not for querying or updating.
- ▌ Biz Opportunity Scout · buyoung bundleIdentify and validate profitable business opportunities by analyzing market size (TAM/SAM/SOM), unit economics, competitive landscape, and PMF indicators. Generates comprehensive HTML reports with opportunity scorecards.
- ▌ Delegated Review Loop · buyoung bundleRun a delegated build-review-improve loop when the user explicitly invokes this skill or explicitly asks to have sub-agents build and iteratively review the work. A worker sub-agent produces the artifact (with an optional scout sub-agent gathering context first), a task-matched panel of independent reviewer sub-agents critiques it in parallel, and the worker improves until the panel passes or the iteration cap is reached. All inter-agent content flows through documents in a per-session directory; the main agent orchestrates by passing file paths only and never writes the artifact itself. Applies to any deliverable: code changes, documents, designs, plans. Do not auto-trigger on ordinary requests; this is an explicit-invocation skill. Distinct from iterative-self-review, where the main agent holds the pen and a single blind verifier checks it.
- ▌
- ▌ Linear Issue Reviewer · buyoung bundleReview completed Linear sub-issues: cross-validate Done Criteria, code changes, and worker comments to approve, request changes, or ask for clarification. Use when asked to review, validate, or QA done Linear issues.
- ▌ System Prompt Creator · buyoung bundleGenerate system prompts from user requirements, with application guidance and request-derived evaluation materials. Use when asked to create, design, or draft a system prompt for an LLM bot, assistant, classifier, router, or explicitly requested multi-step pipeline (e.g. "create a system prompt", "시스템 프롬프트 만들어줘", "분류기 프롬프트 짜줘"). Defaults to a model-neutral single prompt; checks official guidance for a named model/provider. Supports revisions during the current creation task and current-agent simulations only after approval of concrete cases and scope. Not for standalone refinement/review of an existing prompt, one-off user prompts, agent definition files, CLAUDE.md/AGENTS.md, or skill definitions.
- ▌ Task Brief Creator Caveman · buyoung bundleGenerate an executable implementation work-plan Markdown at `docs/briefs/` from planning notes or a rough task description, with the plan body written in caveman **full** mode as a register-only transform that preserves every fact, bullet, execution stage, field, and section depth from the normal-mode equivalent. Work brief, task brief, handoff brief, implementation ticket, and task spec remain trigger aliases. Nine required sections keyed to Conventional Commits types so coding agents switch behavior (refactor → preserve, fix → reproduce first, perf → measure first). Briefset mode emits a parent execution-management document plus N child briefs when the input describes multiple execution contexts. Chat / questions / status reporting stay in normal prose — caveman applies to the saved file only. Use only when the user explicitly asks for the caveman register or invokes this skill by name; for normal-prose briefs use task-brief-creator instead.
- ▌ Jetbrains Plugin Development · buyoung bundleIntelliJ Platform plugin development for JetBrains IDEs. Use when writing, debugging, or migrating a JetBrains plugin — `plugin.xml`, services, actions, PSI/VFS/Document, EDT/BGT threading and Read/Write actions, Kotlin coroutines on the IDE platform, custom languages (Grammar-Kit, JFlex, lexer/parser, syntax highlighting, completion, references), code insight (folding, inspections, intentions, inline completion, inlay hints), Kotlin UI DSL v2, tool windows, settings, run/debug configurations, External System (Gradle/Maven), IntelliJ Platform Gradle Plugin 2.x, dynamic reload, Plugin Verifier, signing, and Marketplace publishing; legacy migrations (`ApplicationComponent`, `getCoroutineScope`, raw `Thread`/`ExecutorService`). Not for end-user IDE configuration or vmoptions tuning.