By buyoung
Activate 20 specialized AI skills tailored for backend development workflows, converting complex SQL queries to type-safe Kysely TypeScript code for PostgreSQL/MySQL, auditing codebases with OWASP standards, reviewing git changes for risks and breaking changes, generating documentation like contributor guides and style docs, configuring IDEs/releases, and automating Linear issue creation/execution.
npx claudepluginhub buyoung/skills --plugin backend-skillsAnalyze 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, folder structure, patterns, conventions, and working agreements. Update mode refreshes only the standard sections while preserving user-defined custom sections. Use when setting up a new repository, onboarding AI agents to an existing codebase, updating an existing AGENTS.md, or when the user mentions AGENTS.md.
Identify 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.
Performs production-ready code reviews on git changes. Supports commit/range/file-scoped analysis, impact assessment, breaking-change detection, confidence-aware finding classification, and risk-weighted verdict generation.
Performs 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.
Guide users through a structured 3-stage workflow for co-authoring documentation — Context Gathering, Refinement & Structure, and Reader Testing. Use this skill whenever the user wants to write documentation, proposals, technical specs, decision docs, RFCs, PRDs, design docs, or any structured content. Trigger when the user mentions writing docs, drafting a proposal, creating a spec, writing up decisions, or similar documentation tasks, even if they just say "write a doc" or "let's draft something."
Provides JetBrains IDE VM options knowledge for version-specific GC selection and memory/performance tuning (JDK 17/21, IDE 222+). Use this skill whenever the user mentions JetBrains IDE performance, vmoptions, .vmoptions files, IntelliJ/WebStorm/PyCharm/GoLand/Rider/CLion/PhpStorm/RubyMine/DataGrip tuning, IDE freezes or lag, heap size configuration, GC tuning for IDEs, or wants to optimize their JetBrains IDE startup or runtime performance — even if they don't explicitly mention "vmoptions".
Capable of converting raw SQL queries into type-safe Kysely TypeScript code. Knows how to handle various SQL dialects and complex query structures.
Create 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.
Review 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.
Execute 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).
React 19 + Vite SPA development guidelines. Use PROACTIVELY when writing, reviewing, or refactoring any React component — even if the user doesn't explicitly ask for best practices. Covers composition patterns (compound components, boolean prop elimination, state lifting, context providers), performance optimization (React.lazy, Suspense, code splitting, useMemo, useCallback, memo, re-render prevention, bundle size reduction), and web interface best practices (accessibility, ARIA, forms, animation, dark mode). Triggers on any work involving useState, useEffect, useRef, useMemo, useCallback, useTransition, useContext, use(), React.lazy, Suspense, SWR, React Router, Vite config, import.meta.env, manualChunks, rollupOptions, Tailwind CSS, CSS Modules, or barrel file imports. Also triggers on performance debugging, re-render issues, bundle analysis, code splitting decisions, component architecture discussions, state management patterns, or new feature development in React + Vite projects.
release-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, and custom plugin development.
A skill that analyzes user requirements to generate production-ready system prompts. It determines whether a single or multi-prompt architecture is needed and queries for missing information if requirements are insufficient.
Generate a structured work-brief Markdown at `docs/briefs/` from planning notes or a rough task description. Nine sections keyed to Conventional Commits types so downstream coding agents switch behavior (refactor → preserve, fix → reproduce first, perf → measure first). Halts on vague input. Manual trigger only.
Generate Typst source code for documents, reports, papers, and presentations, covering markup, math, scripting, and layout syntax.
Generate, update, and maintain UI style guide documents from actual codebase analysis. Scans project files (Tailwind config, CSS/SCSS, design tokens, component code) to extract real color palettes, typography scales, spacing systems, component patterns, and layout approaches — then produces a structured Markdown style guide for developers. Use PROACTIVELY when: user asks to create a style guide, document UI conventions, audit current styles, update an existing style guide, or wants UI/UX recommendations for their project. Triggers on: 'style guide', 'UI guide', 'UI 가이드', '스타일 가이드', 'document styles', 'UI conventions', 'design documentation', '스타일 문서', 'UI 문서화'. Also triggers on Korean phrases like '스타일 가이드 만들어줘', '업데이트해줘', 'UI 추천해줘'.
Reviews existing UI for UX guideline violations and generates implementation guidance based on 99+ rules across Navigation, Layout, Accessibility, Forms, Performance, Typography, and more. Supports Web, Mobile, and Desktop GUI platforms. Use when the user requests a UX review, UX audit, UI accessibility check, or implementation guidance for user experience best practices.
Generates structured Google Veo 3.1 video prompts by collecting user input for subject, action, style, cinematography, and audio. Guides users through the Universal Prompt Formula to produce camera-ready prompts. Use when creating Veo video prompts or when the user mentions Veo, video generation, or cinematic prompts.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Team-oriented workflow plugin with role agents, 27 specialist agents, ECC-inspired commands, layered rules, and hooks skeleton.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Claude Code skills for Godot 4.x game development - GDScript patterns, interactive MCP workflows, scene design, and shaders
Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,393 supported skills.