frontend▌

Use this skill when the user wants to reverse-engineer a public website's design primitives into project-local starter token files.

Transform threat analysis into actionable security requirements. \n \n Converts STRIDE threat categories into functional, non-functional, and constraint requirements with automatic priority calculation based on impact and likelihood \n Generates security user stories, acceptance criteria, and test cases directly from threats; includes traceability matrices linking threats to requirements \n Maps requirements to compliance frameworks (PCI-DSS, HIPAA, GDPR, SOC2, NIST, ISO 27001, OWASP) and identi

Standard Vue 3 workflow with Composition API, <script setup> , and TypeScript as the default approach. \n \n Requires confirming project architecture upfront and reading core references on reactivity, SFCs, component data flow, and composables before implementation \n Enforces minimal source state with ref / reactive , deriving everything possible with computed , and keeping templates declarative \n Mandates component splitting when responsibilities exceed one clear purpose, with entry/root

Translates Figma designs into production-ready code with pixel-perfect visual fidelity. \n \n Requires Figma MCP server connection and a Figma URL with file key and node ID to extract design context, screenshots, and assets \n Seven-step structured workflow: parse URL, fetch design context, capture visual reference, download assets, translate to project conventions, achieve 1:1 parity, and validate against Figma \n Prioritizes design system reuse over duplication; maps Figma tokens to project de

Multi-stage CI/CD pipelines with approval gates and deployment orchestration. \n \n Covers four deployment strategies: rolling updates, blue-green, canary, and feature flags, each with trade-offs for downtime, rollback speed, and infrastructure cost \n Includes approval gate patterns for manual review, time-based delays, and multi-approver workflows across GitHub Actions, GitLab CI, and Azure Pipelines \n Provides automated rollback mechanisms triggered by health checks and failure detection, pl

Advanced Next.js patterns for authentication, middleware, Server Actions, and user-scoped caching with Clerk. \n \n Distinguishes server-side await auth() from client-side useAuth() hook; mixing them is a common breaking mistake \n Covers middleware strategies (public-first vs protected-first), API route protection, and proper HTTP status codes (401 vs 403) \n Includes user-scoped caching patterns with unstable_cache and protecting Server Actions from unauthorized mutations \n Provides Core 2 co

Convert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators. \n \n Supports multiple conversion tools: marked.js for Node.js/CLI workflows, pandoc for cross-format conversion, gomarkdown for Go projects, and Jekyll/Hugo for static site generation \n Handles all standard Markdown flavors including CommonMark, GitHub Flavored Markdown, and extended syntax for tables, code blocks, math expressions, and collapsed sections \n Provides CLI and programmatic workflo

Vue Pinia state management patterns, store setup guidance, and reactivity best practices. \n \n Covers store initialization, DevTools integration, and SSR considerations for setup stores \n Addresses common reactivity pitfalls including destructuring breaks and method binding issues in templates \n Provides patterns for ephemeral state like filters, URL synchronization, and production app conventions \n References specific error scenarios with linked solutions for quick troubleshooting \n

Automatically create GitHub issues for specification requirements not yet implemented in code. \n \n Analyzes specification files to extract all requirements, then checks codebase implementation status for each one \n Searches existing issues to prevent duplicates before creating new feature request issues \n Generates issues with requirement IDs, detailed descriptions, implementation guidance, and acceptance criteria \n Scans related specification files and code patterns to verify whether requi

Complete Power Platform custom connector generator with MCP integration, schema validation, and Copilot Studio compliance. \n \n Generates four core files (apiDefinition.swagger.json, apiProperties.json, script.csx, readme.md) with built-in MCP protocol support and JSON-RPC 2.0 handling for Copilot Studio agents \n Validates schemas against Copilot Studio constraints: no reference types, single type values only, primitive types, and resources as tool outputs \n Supports six generation modes: com