Total 31,632 skills
Showing 12 of 31632 skills
Parse PRD, determine horizontal splitting strategy, and generate mini-PRD with acceptance criteria. Used when the main coordinator receives the initial PRD or needs to re-split work.
Comprehensive content review and quality assurance for CTR documents - validates contract completeness, dual-file consistency, OpenAPI compliance, and identifies issues requiring manual attention
Use this for exploratory data analysis (EDA), generating visualizations, finding trends, and deriving insights from datasets using Python (Pandas/Seaborn/Plotly) or SQL.
Three-layer Vitest-BDD Skill for DashPlayer. Use this when developers want business-readable BDD scenarios without coupling scenario writing to code implementation details. Trigger keywords: "Three-layer BDD", "Behavioral Testing Layering", "Given-When-Then", "Vitest BDD", "Avoid writing implementations in scenarios".
Chapter 1 (개발대상 및 필요성) 작성 가이드 - 템플릿, 요구사항, 웹검색 전략 통합
Update PRD based on design decisions and strategic changes made during conversations
Use when building accessible Vue.js interfaces with Reka UI (Radix Vue).
Draft or refine introduction sections for academic manuscripts using an interview-driven workflow. Use when the user needs to write or refine an introduction for research papers. Produces clear, flowing prose that establishes context, identifies gaps, frames research questions, previews methods, and articulates contributions. Follows a structured approach from phenomenon to theory to empirical contribution.
Deploys a Next.js or Vite project to Vercel, pushes all environment variables from .env.local to production, adds a SPA rewrite rule for Vite, and updates the Supabase site_url to the live domain. Called by the vibe-ship orchestrator.
Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".
Systematic codebase investigation to extract architectural patterns and implementation details from an existing project, with findings persisted for long-term reuse. Use when the user wants to explore an open-source or existing codebase to understand how it works and inform the development of a new project. Triggers include: "explore this codebase", "investigate this repo", "how does X implement Y", "I want to build X, study how Y does it", "deep dive into this project", "understand how this works".
Use when writing any code - enforces clean architecture with descriptive names, real implementations, no backward compatibility concerns, and no lint suppressions