5.5천건 · 관련도순
Save durable preferences, decisions, project facts, commitments, and lessons cheaply with knowledge_remember, or short notes and page updates with attribution and readback. Use for explicit saves or agent-driven remembering when Knowledge is the selected memory provider.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ingest meeting transcripts from any recorder into Knowledge with attendee enrichment, timeline merge, supported decisions and commitments, and verification of substance and sequence. Summary-only input is not a verified meeting ingestion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug Keel agent command or validation failures under Keel's selected OpenSpec task contract. Use when `/opsx:apply` or a selected task reports failed commands, failing tests, validation errors, stop decisions, or needs an evidence-bound failure report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Align explicit requirements, implicit expectations, non-goals, observable acceptance, evidence, and decision authority before OpenSpec specs and executable tasks finalize. Use when authoring or updating a proposal, design, specs, or tasks, or when a request hides a material product choice. Do not use for routine implementation of an already-authorized task, unrelated conversation, or facts the repository can answer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interviews a request until no essential choice is left to guess, then hands the settled decisions on. Trigger on 'grill me', 'interview me before you build', 'stress-test this idea', 'ask me questions until it's clear', 'what am I missing before we start', or a vague plan, feature, prompt or skill where a wrong build costs more than questions. Or say grillwright (grill, record, resume, questionnaire — for someone else to answer, docs — check against glossary and ADRs). Builds nothing — prompts are promptwright's, skills skillwright's, agents agentwright's, game code slicesmith's, what a running agent may do gatewarden's, even asked as a grill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Combine React's official "You Might Not Need an Effect" guidance with this project's stricter no direct useEffect stance. Use when writing, reviewing, or refactoring React components that might reach for useEffect, derived state, event relays, reset logic, subscriptions, or client fetching.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
PHP Standards Recommendations (PSR) overview knowledge base. Provides comprehensive reference for all accepted PSRs including PSR-1,3,4,6,7,11,12,13,14,15,16,17,18,20. Use for PSR selection decisions and compliance audits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GRASP principles knowledge base for PHP 8.5 projects. Provides quick reference for 9 responsibility assignment patterns (Information Expert, Creator, Controller, Low Coupling, High Cohesion, Polymorphism, Pure Fabrication, Indirection, Protected Variations). Use for architecture audits and design decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze context and decide on continuation via Stop hook. Use when determining if work should continue, analyzing completion status, making continuation decisions, or implementing the Two-Claude pattern.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply 37signals/DHH Rails conventions when writing Ruby on Rails code. Use when building Rails applications, reviewing Rails code, or making architectural decisions. Covers various aspects of Rails application architecture, design and dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[51] EXECUTE. Commitment to maximum quality work with 150% coverage. Use when you need the highest quality output for critical tasks, complex problems, important decisions, or when standard work isn't enough. Triggers on "maximum quality", "150% mode", "full quality", "critical task", or when you explicitly want AI to work at its best.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[31] ANALYZE. Universal deep thinking methodology for any situation requiring quality reasoning. Use when solving problems, debugging, making decisions, analyzing code, planning, reviewing, or anytime you need thorough thinking instead of surface-level responses. Triggers on "think deeply", "analyze thoroughly", "reason carefully", "deep thinking", "understand completely", or any task requiring careful thought.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[32] ANALYZE. Ensure every critical claim has verifiable evidence with confidence levels. Each fact must have source + confidence percentage. If confidence <85%, enter Loop150 to find more sources. Use for critical decisions, factual claims, legal/compliance work, or any situation where unverified claims are dangerous.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply timeless programming wisdom from "97 Things Every Programmer Should Know" when writing, reviewing, or refactoring code. Use for design decisions, code quality checks, professional development guidance, testing strategies, and workflow optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when GitHub may have shipped a GraphQL schema update affecting timeline event unions (PullRequestTimelineItems / IssueTimelineItems), when the gh-timeline dispatcher fallback is hitting more than expected, before a gh-timeline release, or when the user requests phrases like "verify timeline coverage", "audit gh-timeline schema", "check for new timeline events", "GitHub schema changed". Walks through schema diff → patch → test update → live verification → optional fixture refresh, marking each spot where a human decision is required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
実装要求に、要求が答えていない設計判断が残るとき、または誤りが後段で黙って通る変更を扱うときに使う。具体的には、API・設定の与え方・データモデル・新しい型や概念・責務や層境界を決める必要がある、複数の実現方法から選ぶ設計判断がある、変更範囲を事前に局所化できない、認可・公開範囲・データ消失・外部送信のように誤りをテストや型検査で検出しにくい、のどれかに当たるタスクで発火する。原因と修正箇所が特定済みで期待結果と検証方法が明確な修正、既存パターンの適用、機械的な rename、CI/CD・ドキュメント・設定値・依存バージョンだけの変更では使わない。要求を出典付きの決定と質問に分解する解釈ゲート、判断の重さに応じた階層(直接実装 / 軽量 / 標準)の判定、subagent への分担、実物差分での検収、独立レビューをフェーズ順に管理するスキル。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decision framework for choosing between regex and LLM when parsing structured text — start with regex, add LLM only for low-confidence edge cases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate concise (3-4 page), focused medical treatment plans in LaTeX/PDF format for all clinical specialties. Supports general medical treatment, rehabilitation therapy, mental health care, chronic disease management, perioperative care, and pain management. Includes SMART goal frameworks, evidence-based interventions with minimal text citations, regulatory compliance (HIPAA), and professional formatting. Prioritizes brevity and clinical actionability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.