'decision' 검색 결과

Create a new Architecture Decision Record (ADR) for a proposed feature or design change.

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

[BETA] AEM Cloud Service expert skill — migrate javax.inject.@Inject fields in Sling Model (@Model) classes to injector-specific annotations (@ValueMapValue / @OSGiService / @SlingObject). Self-discoverable (scan for @Model classes with field-level @Inject); the replacement is chosen deterministically from each field's declared type. Use for "fix @Inject in HeroModel.java", "modernize my Sling Models", or when scanning an AEM project for @Inject misuse. Detailed decision table, companion-annotation handling, import management, and file-level skip policy are in recipe.md. This skill is in beta. Verify all outputs before applying them to production projects.

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

AEM Cloud Service expert skill for Sling ResourceChangeListener. Covers the lightweight listener + JobConsumer pattern, migration from javax.jcr.observation.EventListener and resource-topic OSGi EventHandler, ResourceChangeListener vs ExternalResourceChangeListener decision, OSGi filter configuration, review checklist, troubleshooting (silent failures, hot-path blocking, missing service-user mapping), and common pitfalls.

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

Survey available blocks from local AEM Edge Delivery Services project and Block Collection to understand the block palette available for authoring. Returns block inventory with purposes to inform content modeling decisions.

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

Create or update source-grounded documentation when the user explicitly asks for docs/ADR/onboarding material, a public contract change requires docs, or an accepted hard-to-reverse decision meets the ADR gate; do not trigger for every feature, architecture discussion, implementation, review, or SHIP request.

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

Create, edit, fix, or explain Mermaid diagrams for relationships, decision branches, interactions, lifecycles, and data models; also use when the parent selects a diagram to materially clarify an explanation. Do not trigger for simple status, one fact, short lists, quantitative charts, or marketing slides.

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

Research one bounded mature-project/prior-art question when the user explicitly asks how established projects handle it or ROSE names a decision-shaping prior-art gap; do not trigger automatically for IDEATE, DEFINE, BUILD, implementation, local review, or every design choice.

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

Structure source-grounded consulting-style analysis for strategy, market, product, operations, or decision memos. Use for MECE problem framing, hypotheses, options, tradeoffs, executive recommendations, or "consulting analysis" requests; do not use for legal/financial advice, implementation, data computation, chart rendering, or unsourced business claims.

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

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

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

Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.

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

Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use `animate`.

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

Use when reviewer comments arrive and each one needs a tracked decision, when a revise and resubmit letter must map every comment to a manuscript change, or when contradictory reviewer demands need evidence-based, editor-facing framing.

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

Use when a high-stakes analysis, citation set, or decision should be checked by a second independent AI agent that verifies rather than decides, or when disagreement between agents must be surfaced for the human to adjudicate.

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

Use when AI contribution metadata must match the actual workflow, when model alias and dated identifiers need auditing, when verified and fabricated citation counts feed a release decision, or when a venue's AI disclosure statement needs evidence behind it.

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

Use when selecting a statistical test with AI consultation, when assumptions need checking against the actual data, when an analysis plan or decision log must be written before running anything, or when results need APA-style reporting with effect sizes.

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

Use when a study's materials, data, code, or preprint need an open-science release: license choice, a persistent DOI (Zenodo/OSF), README and metadata, and an access-and-embargo decision that respects ethics constraints.

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

Finding validation before writing any report — 7-Question Gate (all 7 questions), 4 pre-submission gates, always-rejected list, conditionally valid with chain table, CVSS 3.1 quick reference, severity decision guide, report title formula, 60-second pre-submit checklist. Use BEFORE writing any report. One wrong answer = kill the finding and move on. Saves N/A ratio.

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

Security payloads, bypass tables, wordlists, gf pattern names, always-rejected bug list, and conditionally-valid-with-chain table. Use when you need specific payloads for XSS/SSRF/SQLi/XXE/NoSQLi/command injection/SSTI/IDOR/path-traversal/HTTP smuggling/WebSocket/MFA bypass, or bypass techniques. Submittability and the always-rejected / what-NOT-to-submit decision are owned by triage-validation.

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

Git-Notes-Based knowledge graph memory system. Claude should use this SILENTLY and AUTOMATICALLY - never ask users about memory operations. Branch-aware persistent memory using git notes. Handles context, decisions, tasks, and learnings across sessions.

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

Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.

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

Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.

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

Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns.

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

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

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

Clawdbot documentation expert with decision tree navigation, search scripts, doc fetching, version tracking, and config snippets for all Clawdbot features

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