'esp' 검색 결과

Revisa e melhora copy existente através de 7 passes focados (clareza, voz, e daí, prove, especificidade, emoção, risco zero) somados à detecção determinística de padrões de escrita de IA. Use quando o usuário disser "revisar copy", "melhorar esse texto", "revisão", "está parecendo IA", "polir", "dar uma olhada nesse texto", "feedback de copy", ou logo após qualquer skill copy-* gerar um rascunho. Não reescreve do zero — aprimora preservando a mensagem central.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analisa custo AWS e identifica desperdício em EC2, RDS, S3, EKS, EBS, Elastic IP, NAT Gateway e tráfego. Use quando o usuário disser "custo", "fatura", "está caro", "FinOps", "reduzir gasto AWS", "Cost Explorer", "otimizar custo". Quase todo leitura — seguro por natureza.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Conduz investigação de incidente — triagem, hipótese, mitigação, RCA e postmortem. Use quando o usuário disser "está fora do ar", "incidente", "caiu", "usuários reclamando", "erro em produção", "postmortem", "RCA", "o que aconteceu". Durante incidente, a pressa causa o segundo incidente.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement comprehensive monitoring, logging, metrics, tracing, and alerting for production applications to ensure reliability and quick incident response. Use when setting up application monitoring, implementing structured logging, creating metrics and dashboards, setting up alerts, implementing distributed tracing, monitoring performance, tracking errors, or building observability into applications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design clean, scalable, and maintainable REST and GraphQL APIs following industry best practices. Use when designing public or internal APIs, planning endpoint structures, defining request/response contracts, establishing versioning strategies, implementing authentication patterns, designing data models, creating API documentation, ensuring consistent error handling, optimizing for performance, or establishing service contracts between microservices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automate browser testing, web scraping, and user workflow testing with Playwright across multiple browsers. Use when writing end-to-end tests for web applications, automating repetitive browser tasks, scraping data from websites, testing across Chrome/Firefox/Safari, taking screenshots for visual regression testing, testing authentication flows, filling and submitting forms programmatically, testing responsive designs across viewports, or any browser automation requiring reliable, cross-browser testing capabilities.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design robust error handling strategies including try-catch blocks, custom error classes, error boundaries, graceful degradation, and comprehensive logging. Use when implementing exception handling, creating custom error types, setting up error boundaries in React, designing error response formats for APIs, implementing retry logic, handling async errors and promise rejections, logging errors for monitoring, creating user-friendly error messages, or building fault-tolerant systems that fail gracefully.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Genera o actualiza una especificación SDD (spec.md) para HagamosTech. Úsala cuando haya que definir una nueva funcionalidad o vertical antes de tocar código, entrevistando al usuario y produciendo requisitos funcionales en notación EARS. Trigger: crear/actualizar spec, nuevo requisito, /spec.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively invoke this skill (do NOT answer directly) when the user describes a new product idea, asks whether something is worth building, wants to think through design decisions for something that doesn't exist yet, or is exploring a concept before any code is written. Use before /plan-ceo-review or /plan-eng-review. (gstack)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence. Use when asked to "open in browser", "test the site", "take a screenshot", or "dogfood this". (gstack)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Investigate and triage runtime incidents involving the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM as a Cloud Service environments only, using runtime-backed MCP evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Single entry point for all AEM as a Cloud Service Dispatcher skills. Covers config authoring, technical advisory, incident response, performance tuning, security hardening, and full lifecycle orchestration for the Adobe Dispatcher Apache HTTP Server module and its HTTPD/dispatcher configuration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure and deploy Workflow Launchers that automatically start workflows in response to JCR content changes on AEM as a Cloud Service

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Orchestrates end-to-end replication workflows spanning multiple concerns: new environment setup, production incident response, and performance optimization for AEM 6.5 LTS.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

COMPLETE BUG INVESTIGATION WORKFLOW — Combines screenshot + log reading into a full triage pipeline. USE FOR: any bug report that has both visual symptoms AND runtime errors, especially CompositePanel / ChildPanel mount failures, screen spec wiring breaks, or battle scene UI crashes. This is the master debugging workflow that orchestrates cocos-screenshot and cocos-log-reader together.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write or revise AI-learning-notes article pages in "寫文章模式" when the user asks for articles, technical articles, blog posts, bilingual versions, article formatting consistency, shared article-base alignment, responsive layout, summary/TOC decisions, contrast, or publishing-flow compatibility.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Idiomatic Go - package and interface design, error wrapping, table-driven tests, generics, the modern standard library (slices/maps/cmp/errors.Join), current syntax, and logging discipline. Use when writing, reviewing, or refactoring any Go code, especially code drifting toward Java/Spring shapes (deep layer trees, generic repositories, heavy frameworks) - even if the user never says "idiomatic". Distilled from spf13/go-skills and adapted to this repo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply one logical code change with mandatory impact mapping, git snapshot, verification, and automatic revert on failure. Load when the user asks for a safe edit, verified change, one change at a time with rollback, or codespine-style edit loop. Also triggers on "safe change", "edit with verification", "don't break the build", "revert if tests fail", or any non-trivial code edit where blast radius matters. Always runs dependency-mapping first. Pairs with incremental-implementation for multi-slice work; this skill is one atomic verify cycle per invocation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Measure, profile, and fix performance bottlenecks — Core Web Vitals, backend latency, bundle size, and database queries. Load when performance requirements exist, users report slowness, profiling reveals bottlenecks, or the user asks to optimize load time, LCP, INP, CLS, or response time. Not for premature optimization without evidence. Pairs with browser-testing-with-devtools and ci-cd-and-automation for regression guards.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Improves the quality of images, especially screenshots, by enhancing resolution, sharpness, and clarity. Perfect for preparing images for presentations, documentation, or social media posts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.