Time Saved: 30 minutes - 1 hour debugging
원문 언어: 영어
메뉴
이 저장소의 skills
SkillsMP는 fabioc-aloha/Alex_Skill_Mall에서 379개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
fabioc-aloha/Alex_Skill_Mall수집된 skill 379개 중 40개를 표시합니다.
Time Saved: 30 minutes - 1 hour debugging
원문 언어: 영어
Time saved: 2-4 hours per issue
원문 언어: 영어
Azure Verified Modules (AVM), Bicep best practices, and MCP-powered infrastructure as code for Azure
원문 언어: 영어
Design well-architected Azure cloud systems — 10 design principles, 6 architecture styles, 44 design patterns, technology choices, WAF pillars
원문 언어: 영어
Containerize an ASP.NET Core project by creating Dockerfile and .dockerfile files customized for the project.
원문 언어: 영어
Patterns for Microsoft Graph, Microsoft Entra ID, and enterprise feature integration in VS Code extensions
원문 언어: 영어
Microsoft Entra Agent ID (preview) — create OAuth2-capable AI agent identities via Microsoft Graph beta API
원문 언어: 영어
Import existing Azure resources into Terraform using Azure CLI discovery and Azure Verified Modules (AVM). Use when asked to reverse-engineer live Azure infrastructure, generate Infrastructure as Code from existing subscriptions/resource groups/resource IDs,…
원문 언어: 영어
Domain: DevOps & Cloud Engineering
원문 언어: 영어
Microsoft Fabric workspace management, governance, REST API patterns, and medallion architecture implementation
원문 언어: 영어
Comprehensive Microsoft Graph API reference for M365 service integration
원문 언어: 영어
Microsoft Authentication Library (MSAL) patterns for React/SPA applications with Entra ID
원문 언어: 영어
Time Saved: 1+ hour debugging silent auth failures
원문 언어: 영어
Create optimized multi-stage Dockerfiles for any language or framework
원문 언어: 영어
Full Teams app development patterns.
원문 언어: 영어
Update Azure Verified Modules (AVM) to latest versions in Bicep files.
원문 언어: 영어
Shared audit integrity framework for all AppSec agents — enforces output quality, intellectual honesty, and continuous improvement through anti-rationalization guards, self-critique loops, retry protocols, non-negotiable behaviors, self-reflection quality…
원문 언어: 영어
Use when a user asks to generate or improve unit tests with measurable coverage gains using a strict staged workflow (build -> baseline -> plan -> generate -> verify -> coverage delta). Trigger phrases: generate unit tests, improve coverage, write tests for…
원문 언어: 영어
Code-scanning regex that looks for literal strings misses real usage:
원문 언어: 영어
Systematic code review for correctness, security, and growth — not just style enforcement
원문 언어: 영어
Date comparisons at thresholds fail due to fractional days:
원문 언어: 영어
Adversarial code review with three parallel perspectives — Advocate, Skeptic, Architect — that create productive tension. Use for high-stakes PRs, architectural changes, or when single-pass review would miss issues. Surfaces findings through disagreement, not…
원문 언어: 영어
Systematic 5-dimension audit framework for VS Code extensions — debug hygiene, dead code, performance, menu validation, dependency cleanup
원문 언어: 영어
Plans without measurable success criteria drift into wishful thinking:
원문 언어: 영어
One-time audits don't track improvement:
원문 언어: 영어
When checking that all callers of a contract implement it correctly, you get false positives from wrapper delegators:
원문 언어: 영어
CPU, memory, network bottleneck analysis — systematic performance investigation
원문 언어: 영어
Python mock.patch must target the import location, not the definition location
원문 언어: 영어
Systematic code refactoring to improve maintainability without changing behavior. Use when asked to "refactor this", "clean up this code", "improve code quality", "simplify this", "reduce complexity", or "eliminate code smells". Always preserves existing…
원문 언어: 영어
Safe transformations — same behavior, better structure.
원문 언어: 영어
Evaluate a repository's readiness for AI-assisted development across 4 axes: code understanding, dependency restore, build success, and test execution. Use when onboarding to a new repo, assessing CI readiness, or validating that an AI agent can work…
원문 언어: 영어
Pattern-aware code scaffolding that detects existing conventions and generates new components matching the codebase style. Use when asked to "scaffold a component", "generate boilerplate", "create a new module", "bootstrap a service", "add a new endpoint",…
원문 언어: 영어
Deep structural analysis of a codebase—dependency mapping, architecture boundary detection, coupling/cohesion scoring, and dead code discovery. Use when asked to "analyze codebase structure", "map dependencies", "find dead code", "architecture analysis",…
원문 언어: 영어
Systematic technical debt inventory and prioritization. Use when asked to "find tech debt", "show me the TODOs", "how healthy is this codebase", "what should we fix first", "find code smells", "audit code quality", or "identify hotspots". Scans code markers,…
원문 언어: 영어
Safe terminal command patterns — backtick escaping, output capture, and hang prevention
원문 언어: 영어
Analyze test code quality to detect coverage-only tests, test smells, and low-value assertions. Use when asked to "analyze test quality", "find coverage-only tests", "audit our tests", "are these tests valuable", "find test smells", or "which tests should we…
원문 언어: 영어
When renaming a function, test files have references that survive find-and-replace:
원문 언어: 영어
Systematic testing for confidence without over-testing — the right test at the right level
원문 언어: 영어
Systematic project audit pattern — version consistency, terminology, fact inventory, cross-references
원문 언어: 영어
Visual output that passes static checks can still fail to render:
원문 언어: 영어