Menu
SkillsMP a collecté 21 skills depuis kwkraus/edgefront-builder. Ouvrez un skill pour examiner sa source et ses détails.
Affichage de 21 skills collectés sur 21.
Design EF Core schema changes, constraints, and migrations for the backend data model. Use for entity updates, indexes, uniqueness rules, cascade behavior, and migration planning.
Langue du texte source : anglais
Design ASP.NET Core minimal API request and response contracts. Use for DTO shapes, route and verb decisions, OpenAPI metadata, and compatibility planning before implementation.
Langue du texte source : anglais
Define focused tests for ASP.NET Core minimal APIs. Use for endpoint branch coverage, contract assertions, regression planning, and choosing the narrowest useful verification command.
Langue du texte source : anglais
Define deployment safeguards, environment protections, and rollback readiness for CI/CD releases. Use when adding or reviewing release jobs, promotion controls, or recovery plans.
Langue du texte source : anglais
Apply email and domain normalization plus session and series metric rules, including W1/W2 warm-account logic and internal-domain exclusion. Use for domain logic changes, recompute behavior, and mandatory unit-test coverage.
Langue du texte source : anglais
Review Next.js interfaces for accessibility and UX acceptance. Use for semantic markup, keyboard flow, responsive behavior, async states, and final user-flow validation before merge.
Langue du texte source : anglais
Define focused frontend tests for Next.js user-visible behavior. Use for rendering, interaction, loading and error states, regression coverage, and choosing narrow verification scope.
Langue du texte source : anglais
Design GitHub Actions workflows with clear triggers, deterministic job boundaries, safe caching, and diagnosable failure output. Use for new workflows or structural CI/CD refactors.
Langue du texte source : anglais
Triage reliability incidents by isolating likely fault domains and defining safe mitigation and recovery checks. Use during outages, regressions, failed deployments, or recurring degradation.
Langue du texte source : anglais
Align frontend consumers with backend API contracts. Use for route or DTO changes, compatibility windows, rollout sequencing, and cross-stack acceptance criteria.
Langue du texte source : anglais
Validate frontend-backend environment wiring without hardcoded service endpoints. Use for local, dev, and prod config mapping, runtime key alignment, and configuration gap analysis.
Langue du texte source : anglais
Compose Next.js App Router features with thin routes, reusable components, and intentional server/client boundaries. Use for route refactors, shared UI extraction, or rendering-boundary decisions.
Langue du texte source : anglais
Inventory existing CI/CD workflows and map required quality gates by component and environment. Use before changing GitHub Actions so pipeline gaps and blockers are explicit.
Langue du texte source : anglais
Run targeted CI/CD validation and report pass/fail outcomes with clear blockers and rerun scope. Use after workflow changes or when diagnosing failed pipeline runs.
Langue du texte source : anglais
Choose HTTP status codes and response payload behavior for ASP.NET Core minimal APIs. Use for success and error branch semantics, problem details, conflicts, and compatibility exceptions.
Langue du texte source : anglais
Define production-safe structured logging for ASP.NET Core API flows. Use for event naming, stable log fields, correlation context, severity policy, and secret-safe diagnostics.
Langue du texte source : anglais
Execute a minimal-scope red-green-refactor workflow. Use for test-first features, regression-first bug fixes, and refactors that must preserve externally observable behavior.
Langue du texte source : anglais
Design logs, metrics, and traces for critical frontend and backend flows with clear operator actionability and low noise. Use when adding or revising end-to-end observability.
Langue du texte source : anglais
Guide iterative authoring of functional specifications as Azure DevOps work item hierarchies (Epic → Feature → User Story). Use for business requirement capture, scope definition, acceptance criteria, and approval readiness.
Langue du texte source : anglais
Manage the lifecycle of functional and technical specifications tracked as Azure DevOps work items. Use for state transitions, review readiness, staleness detection, change management, and process enforcement.
Langue du texte source : anglais
Generate technical specifications from approved functional specs (Azure DevOps Epic hierarchies) and publish as wiki pages. Use after functional approval to create implementation-ready technical documentation.
Langue du texte source : anglais