create-issue
Creates GitHub issue with task checklist based on architecture documents (specs.md, frontend.md, backend.md). Run after reviewing the planning documents.
Skills matching the name, description or GitHub author.
Creates GitHub issue with task checklist based on architecture documents (specs.md, frontend.md, backend.md). Run after reviewing the planning documents.
Builds complete features full-stack (backend + frontend + tests). Triggers when user wants to implement a feature, add functionality, or build a specific capability.
Full-stack development context for coordinating changes across contracts and frontend. Use this skill when changes span both backend contracts and frontend code, requiring synchronized updates across the stack.
Code Reviewer Agent. Frontend/Backend 코드 리뷰를 담당합니다. 코드 품질, 테스트 커버리지, 보안, 성능을 검토합니다.
빌드/배포 에이전트. 빌드 설정과 배포 파이프라인을 관리합니다.
Expert guidance for debugging Next.js, React, and Playwright applications with modern tools and best practices.
Audit frontend code for security, UX regressions, performance, and accessibility issues. Use when reviewing React, Next.js, Vue, Svelte, or any frontend code changes. Triggers on "audit frontend", "review UI",...
Ensures frontend code quality by enforcing Design System (9 ESLint rules), Storybook coverage, and 5-step verification pipeline. Use when creating/modifying React components in frontend/src/, especially shared/...
This skill should be used when users need to generate Azure DevOps CI/CD pipelines with Dockerfiles for full-stack applications. Use when creating Azure pipelines, generating Dockerfiles for frontend/backend, s...
Deploy applications to AWS (SageMaker, Amplify, EC2). Use this skill to deploy models, frontends, or manage infrastructure. Invoke with /deploy.
Cloudflare deployment for frontend (Pages) and backend (Workers). Covers secrets, environment variables, custom domains, and production configuration.
Deploys a component (frontend, backend, or landing) using SST. Use when deploying to AWS, pushing to dev or prod environments.
Deploys multiple components to an environment. Use for coordinated deployments of backend, frontend, and landing.
Standard project layout and Spec-Kit usage patterns for AI-driven, spec-driven monorepos that host frontend, backend, and specs in a single repository.
Vercel deployment management for frontend apps: CLI, env vars, config, troubleshooting, rollback.
Vercel deployment management for frontend apps: CLI, env vars, config, troubleshooting, rollback.
Standard project layout and Spec-Kit usage patterns for AI-driven, spec-driven monorepos that host frontend, backend, and specs in a single repository.
Generate production-ready Helm charts for Kubernetes apps. Use when: (1) Deploying applications to Kubernetes, (2) Containerizing apps for Minikube/K8s, (3) Creating reusable deployment packages, (4) Needing pa...
Automate local development environment setup for multi-service applications. Use when developers need to quickly set up or configure local dev environments with frontend (React/TypeScript/Tailwind), backend (No...
Provides guidance and templates for containerizing applications using Docker. Use when a user wants to create Dockerfiles, optimize images, set up multi-container applications with docker-compose, or follow bes...
Builds a complete SaaS frontend wrapper around validated n8n workflows. Use this skill when you want to CREATE A WEBSITE, BUILD A UI, MAKE A SAAS PRODUCT, or WRAP AN N8N WORKFLOW in a user-friendly interface. G...
Use this skill when performing QA reviews of the Planted website (Astro frontend at localhost:4321), Admin Dashboard V2 (localhost:5175), or production sites (planted.com, admin.planted.com). Orchestrates visua...
Orchestrates frontend development with MidsReborn UI analysis, React component planning, visual verification, and quality gates
Expert guidance for deploying, managing, and scaling GabeDA infrastructure on Railway (backend) and Render (frontend). Handles environment configuration, CORS setup, troubleshooting, monitoring, and production...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.