Architect durable, event-driven workflows using step functions, retry strategies, idempotency, fan-out patterns, and the critical differences between orchestration approaches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
844건 · 관련도순
Architect durable, event-driven workflows using step functions, retry strategies, idempotency, fan-out patterns, and the critical differences between orchestration approaches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scaffold project/workspaces, apply base structure and configs, and verify dev server startup gate
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scoring rubrics for all 5 pipeline layers (Vision, Architecture, IA, BE, FE). Use when auditing specs, running self-checks, or remediating ambiguity gaps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Universal AI design correction rules — SUPERSEDED. The `impeccable` skill now provides 27 deterministic anti-pattern rules plus a 12-rule LLM critique pass, which are more comprehensive and runtime-enforced via the `impeccable` CLI. This file is kept for backward compatibility — the `impeccable` skill's design laws and anti-patterns take precedence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic methodology for verifying that IA, BE, and FE specification layers are mutually consistent. Covers coverage matrices, field mapping checks, error code propagation, access control consistency, and data contract drift detection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage API versioning and evolution with URL/header/query strategies, deprecation workflows, breaking change classification, sunset headers, and consumer-driven contract testing. Use when designing versioning strategy, deprecating endpoints, or evolving API contracts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate implementation prerequisites, load slice/spec context, detect execution mode, and write contract schemas before TDD execution
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Leverage concurrent terminal background processes to debug multiple independent failures simultaneously using ACH methodology. Use when you have 2+ failures across different subsystems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate concurrent analysis or implementation across independent domains. Use when a task can be decomposed into independent workstreams (e.g., via simultaneous tool calls or background processes) — spec writing, code review, security audit, feature implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute RED→GREEN→REFACTOR with validation, deep checks, and mandatory progress updates
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Exhaustive idea extraction through recursive breadth-before-depth exploration with Deep Think protocol and fractal structure. Use during /ideate to transform raw ideas into comprehensive, structured ideation output. Writes to a fractal folder hierarchy — every node has an index, CX file, and children.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate single-slice implementation via setup and strict TDD passes with mandatory progress tracking updates
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement structured logging with JSON formats, log levels (DEBUG, INFO, WARN, ERROR), contextual logging, PII handling, and centralized logging. Use for logging, observability, log levels, structured logs, or debugging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage database migrations and schema versioning. Use when planning migrations, version control, rollback strategies, or data transformations for any database paradigm.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive advanced Git patterns guide covering interactive rebase, cherry-pick, bisect for bug hunting, worktrees, reflog for recovery, stash management, submodules vs subtrees, hooks (pre-commit, commit-msg, pre-push), conventional commits, merge strategies, branch naming, git attributes (LFS, diff drivers), blame/log archaeology, patch workflow, sparse checkout, filter-repo, signing commits, and performance optimizations. Use when performing complex Git operations beyond basic add/commit/push.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes codebase structure, data flow, module relationships, and key patterns to generate and maintain a living architecture document (ARCHITECTURE.md).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture and classify new scope, write entry-point updates, and determine downstream cascade scope
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute recursive breadth-before-depth ideation discovery with Deep Think, CX gate enforcement, and feature deepening
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design database schemas with normalization, relationships, and constraints. Use when creating new database schemas, designing tables, or planning data models for any database paradigm.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when editing an existing codebase and the goal is minimal, standard, and non-invasive changes — prioritizes simplest solution, standard libraries first, and surgical modification without unsolicited refactors
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Introduce genuinely new scope into the pipeline by classifying change type and cascading updates through downstream layers
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.