GitHub
emp-best-practices
Expert guidance for EMP CLI, Rspack, and module federation. Invoke when developing micro-frontends, configuring builds, or debugging EMP projects.
☆ 2,396View skill
Search results for “Frontend”
Skills matching the name, description or GitHub author.
Categories: research cicd
Browse skills
GitHub
performance-lighthouse-runner
Performance Lighthouse Runner - Auto-activating skill for Frontend Development. Triggers on: performance lighthouse runner, performance lighthouse runner Part of the Frontend Development skill category.
☆ 1,308View skill
GitHub
performance-lighthouse-runner
Manage performance lighthouse runner operations. Auto-activating skill for Frontend Development. Triggers on: performance lighthouse runner, performance lighthouse runner Part of the Frontend Development skill...
☆ 1,305View skill
GitHub
system-integration-validator
Validates system integration before deployment. Use when checking ports, database connections, frontend-backend APIs, or debugging blocked/stuck workflows. Detects dead ends, bottlenecks, circular dependencies.
☆ 124View skill
GitHub
tester
Comprehensive testing skill for GabeDA application - designs test strategies (UAT, integration, smoke, unit), creates tests for frontend (React/Playwright) and backend (Django/pytest), executes tests, analyzes...
☆ 124View skill
GitHub
frontend-orchestrator
Coordinates frontend development tasks (React, TypeScript, UI/UX). Use when implementing user interfaces, components, state management, or visual features. Applies frontend-standard.md for quality gates.
☆ 124View skill
GitHub
create-feature
新機能開発統合スキル - 要件分析からPR作成まで、新機能開発の全工程を自動化します。analyze-requirements、develop-backend、develop-frontend、review-architecture、qa-check、create-prの各専門スキルを適切な順序で呼び...
☆ 124View skill
GitHub
deployment
Deployment architecture, multi-tenancy design, and environment-specific deployment commands. Use when the user asks about how the application is deployed, multi-tenant architecture with Navigator, Fly.io deploy...
☆ 35View skill
GitHub
umbrella-repo-detector
Detects multi-repo architecture from user prompts and guides setup. Activates for: multiple repos, 3 repos, frontend repo, backend repo, shared library repo, monorepo services, microservices, separate repos, FE...
☆ 28View skill
GitHub
specweave-router
ACTIVE router that detects development tasks and spawns specialized agents. Activates for: React, Vue, Next.js, frontend, dashboard, component, UI, UX, GitHub, API, backend, database, SQL, PostgreSQL, MongoDB,...
☆ 28View skill
GitHub
grey-haven-project-structure
Organize Grey Haven projects following standard structures for TanStack Start (frontend) and FastAPI (backend). Use when creating new projects, organizing files, or refactoring project layout.
☆ 19View skill
GitHub
performance-optimization
Use when creating performance optimization plan for backend, API, or general system performance. Enforces BASELINE → PROFILE → OPTIMIZE → VALIDATE sequence. Triggers: "optimize API", "backend slow", "API latenc...
☆ 12View skill
GitHub
generic-feature-developer
Guide feature development with architecture patterns for any tech stack. Covers frontend, backend, full-stack, and automation projects. Use when adding new features, modifying systems, or planning changes.
☆ 9View skill
GitHub
gemini-review
Invoke Gemini for design/code review. PROACTIVE: (1) BEFORE proposing new features/architecture, (2) AFTER >100 lines or >3 files changed (before tests), (3) AFTER security/perf changes, (4) ON SESSION RESUME -...
☆ 8View skill
GitHub
deployment-guide
Complete deployment guide for Dr. Sophia AI on Railway. Covers environment-aware build system, frontend dist/ compilation, backend auto-deploy, Railway configuration, troubleshooting build/deployment issues. Us...
☆ 4View skill
GitHub
vercel
Deploys applications to Vercel including serverless functions, edge functions, environment variables, and CI/CD. Use when deploying Next.js applications, frontend projects, or serverless APIs.
☆ 3View skill
GitHub
ringusing-dev-team
Guide to the dev-team skills - specialist developer agents and 6-gate development cycle. Provides backend engineers (Go/TypeScript), frontend engineers, DevOps, SRE, and QA agents.
☆ 3View skill
GitHub
managing-vercel
Vercel platform CLI for frontend deployments, serverless functions, and edge network management. Use for deploying applications, managing domains, environment variables, and debugging deployments.
☆ 3View skill
GitHub
stack-audit
Comprehensive stack health audit for codebase and infrastructure. Runs 10 health checks covering frontend, backend, migrations, Docker, API integrity, and backup status. Use routinely to prevent "time loops" fr...
☆ 2View skill
GitHub
managing-dev-environment
Use this skill when starting, stopping, or troubleshooting the development environment including managing backend/frontend services, handling port conflicts, setting up Docker vs SQLite modes, configuring Cloud...
☆ 2View skill
GitHub
project-scaffold
Scaffold new software projects with best practices. Use this skill when users want to create a new project, initialize a codebase, scaffold an application, start a new repo, or set up a project from scratch. Su...
☆ 2View skill
GitHub
monorepo-generator
Generate production-ready monorepo structures for full-stack applications including frontends (Next.js, React), APIs (Hono, Express), and data pipelines. Use when creating new monorepo projects, scaffolding mul...
☆ 2View skill
GitHub
vercel-deployment
Vercel deployment patterns and best practices. Use when deploying frontend applications, configuring edge functions, setting up preview deployments, or optimizing Next.js applications.
☆ 2View skill
GitHub
multi-dockerfile-build
This skill should be used when the user asks to "build multiple Dockerfiles", "compile varios dockerfiles", "multi-container build", "multiple Docker images in GitLab", "parallel Docker builds", "monorepo Docke...
☆ 2View skill
Popular categories
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.