Loading...
Loading...
Found 51 Skills
Transform approved requirements into comprehensive technical designs. Define system architecture, component interactions, data models, and interfaces to create a blueprint for implementation.
Analyze and create a testing strategy for native Android apps - install testing libraries, set up test infrastructure, create harnesses for unit tests, UI tests, screenshot tests, and end-to-end tests.
Create a detailed refactor plan with tiny commits through user interviews, then file it as a GitHub issue. Use this when the user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
Patrons et stratégies de test complets pour les projets JavaScript/TypeScript. Couvre les tests unitaires, d'intégration et E2E, les stratégies de mocking, l'organisation des tests et les anti-patrons courants. À utiliser quand l'utilisateur veut écrire des tests, améliorer la couverture de tests, établir une stratégie de test ou corriger des tests instables.
Complete React + Vite expertise for building optimized, scalable applications. Covers project architecture, folder structure, component patterns, performance optimization, TypeScript best practices, testing, and build configuration. Use when building React apps with Vite, organizing projects, optimizing performance, or implementing best practices. Includes code generators, bundle analyzer, and production-ready templates.
Core code quality principles for writing maintainable code. Use when reviewing code for design violations, assessing code quality, or applying architectural patterns like composition, immutability, and fail-fast.
Decide how much proof a piece of work needs — from just looking at it, to walking the flow, to writing a test, to writing the test first. Use right after a feature works, before changing code that already works, and every time something that used to work breaks. Also use when the builder asks whether they need tests, or when a change touches money, auth, permissions, data they can't get back, or logic with rules and edge cases.
Use when the user asks to analyze code for test coverage, list what test cases are needed, or review testing strategy — WITHOUT generating actual test code.
End-to-end ***plain spec authoring workflow: runs a structured QA interview (product, tech stack, behavior) then produces complete .plain specification files with automated review. Use when the user wants to build something new from scratch or asks to start a new project.
Construct a business cycle model using leading and coincident indicators, and interpret two business cycle phases: Expansion (Risk-On) and Contraction (Risk-Off), and generate "Iceberg" and "Sinking" event signals based on the theory.
Write a technical spec document (architecture diagrams, request lifecycle, module breakdown, data models, implementation steps, testing plan, risks) that follows a stakeholder-facing feature plan. Use when user has a plan and wants to deepen it into a developer-ready spec, or asks to "write a spec", "create technical design", "design doc for this feature".
Highest-priority for all NestJS-related tasks involving API engineering. Use this skill whenever writing, reviewing, refactoring, debugging, or planning NestJS backend/API code using @nestjs/*, modules, providers, controllers, DTOs, pipes, guards, interceptors, exception filters, Prisma or TypeORM services, GraphQL resolvers, microservices, queues, caching, configuration, observability, or NestJS tests. Prefer this skill over generic Node.js or backend advice for NestJS code.