386건 · 관련도순
SOP for normative specification and behavioral contracts. Trigger when: - Defining invariants, permitted transitions, and forbidden states. - Navigating steps: Identify, Formalize, Verify, Record, Connect. - Prompt contains: /spec, spec workflow, normative constraint, invariant, BCP 14.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review an author's manuscript, its argument and paragraph structure, analyze reviewer comments, draft rebuttals, and verify revisions. Use for self-review, structural edit plans, simulated reviewer objections, author responses, revision closure, and submission-readiness assessment. Formal assigned peer review is outside this skill; manuscript edits and final figures/tables use their owning skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform client hearing sheets and meeting notes into structured requirements documents. Use when converting raw hearing data (Japanese/English) into formal requirements, generating traceability matrices, identifying gaps/ambiguities, and mapping requirements to WBS items. Triggers include "hearing to requirements", "meeting notes to specs", "requirements traceability", "gap analysis for requirements", or requests involving hearing sheet analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Activates a structured decorator framework that modifies how Claude reasons, responds, and formats output. Trigger this skill whenever a prompt contains one or more markers prefixed with +++, such as +++Reasoning, +++StepByStep, +++Tone(style=formal), or any other +++ marker, regardless of what follows in the prompt. Also trigger when the user asks to activate, list, or clear decorators, references the prompt decorator framework, or uses phrases like "use decorator", "apply +++", or "what decorators are available". This skill must be active for any +++ marker to take effect.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remove AI-generated writing patterns from Modern Standard Arabic (MSA/الفصحى) text. Use when editing or reviewing Arabic formal text to make it sound naturally human-written.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remove AI-generated writing patterns from Modern Standard Arabic (MSA/الفصحى) text. Use when editing or reviewing Arabic formal text to make it sound naturally human-written.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds a DRAFT proposal skeleton from a discovery summary (call notes, discovery brief, CRM record, emails) and the organisation's own proposal template: every template section in order, pre-filled only where the discovery material supports it with the source beside each line, and every section still needing a human input marked HUMAN INPUT with the owner role and the question to answer. Use when the user asks to "start the proposal for <prospect>", "build the proposal skeleton from the discovery notes", "pre-fill our proposal template", "what do we already have for the proposal" or "first cut of the proposal". Do not use for answering a formal RFP, RFQ or tender question set, use rfp-response-drafter instead; for turning a priced estimate into a statement of work use estimate-to-sow. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts a nonconformance report from inspection notes, test results and the governing specification or procedure: what was observed, where, the evidence with references, the requirement cited quoted verbatim with the departure from it, and containment proposals for the quality lead to decide. Never classifies severity, dispositions the item, names a root cause or closes the report. Use when the user asks to "write up this nonconformance", "draft an NCR from my inspection notes", "formalise this deviation" or "turn this snag into a defect report". Do not use for tracking the actions an NCR raises, use corrective-action-tracker instead. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepares a DRAFT leadership-meeting briefing pack from the reports, meeting notes, emails and dashboard exports the user provides: one headline, metrics exactly as stated with period and source, decisions the meeting must take, risks as reported, talking points with anticipated questions, a source reference on every line and UNKNOWN where the material is silent. Use when the user asks to "brief the leadership team", "prepare the exec pack", "pull together a briefing for the steering committee", "summarise these reports for the CEO", "what do I tell the board on Monday" or "build the pre-read for the management meeting". Do not use for a formal board or committee paper seeking a resolution, use board-paper-skeleton instead; for a personal one-page prep drawn from the user's own calendar and inbox, use meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinate Codex work across the current task, internal subagents, user-owned tasks, worktrees, handoffs, formal review gates, or recurring automation. Use for delegation, parallel roles, another Codex task, cross-repo work, QA/review handoffs, scheduled follow-up, or task inspection and continuation. Chinese triggers include 子Agent/子进程/子对话, 另一个对话接手, 并行处理, 分给QA, 多仓库收口, 巡检, 持续推进, 定时自动继续, 创建/读取/转交任务.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load when asked to create, update, re-baseline, or continue a repository-grounded implementation/technical/refactor plan and its `dev/active/<task>` plan/context/tasks files; not for a product PRD, informal advice, or reviewing an already-written plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Knowledge base from the NASA Cost Estimating Handbook (CEH) v4.0. Use for NASA's 12-step, three-part cost estimating process (Project Definition, Cost Methodology, Cost Estimate); the WBS, CADRe, and ONCE data backbone; estimating methodologies (analogy, parametric/CER, engineering build-up, EVM, Delphi); ground rules and assumptions, data normalization and inflation (BY/CY/RY); the point-estimate-to-S-curve cost-risk chain and Unallocated Future Expense (UFE) reserves; Joint Cost and Schedule Confidence Level (JCL) analysis via probabilistic cost-loaded schedules; decision-support analyses (sensitivity, trade studies, make/lease-vs-buy, affordability, CAIV); and economic analysis (discounting, NPV, OMB Circular A-94). The cost-estimating complement to NASA's SE and risk packs. Does NOT reproduce the handbook's tool-specific procedures, worked examples, or appendix-depth methods (it names the appendices), nor cover full DoD/GAO cost guides, schedule construction, or formal risk management beyond the cost interface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Knowledge base from the FAA Requirements Engineering Management Handbook (DOT/FAA/AR-08/32). Use for writing requirements for real-time, embedded control systems — the avionics/medical slant — via the Handbook's eleven recommended practices: system overview and boundary (monitored/controlled variables), operational concepts (use cases), environmental assumptions, change-tolerant functional architecture (dependency diagrams), safety-driven architecture revision (FHA/PSSA/fault tree), system modes, detailed behavior and performance requirements (ideal value + tolerance + latency), the four-variable model bridge to software requirements (MON/CON/NAT/REQ, IN'/REQ'/OUT', DO-178B mapping), subsystem allocation, and rationale. Carries the Isolette Thermostat and Flight Control System worked examples. Slanted toward control systems with sensors and actuators; thin on information-system / enterprise / agile requirements, on requirements-management tooling, and on the formal-methods internals of SCR/RSML/SpecTRM (it names them, does not re-teach them). Does not reproduce the IEEE/DO-178B/ARP standards it cites.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dieser Skill sollte genutzt werden, wenn der User private oder halbformale E-Mails schreiben, beantworten, absagen, nachfassen, kürzen, umformulieren oder im eigenen Stil entwerfen lassen will, besonders bei Terminen, offiziellen Absagen, freundlichen Kurzantworten und kontaktabhängigem Ton. Profilanalyse erst bei einem konkreten Mail-Schreibauftrag starten.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
متن اداری assistant for Codex; apply when building Persian/RTL web products, localizing content or integrating the related Iranian workflow. Local independent adaptation inspired by publicly documented VibeFarsi topics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Annotate and map the anatomy of any design. Identify visual hierarchy, spacing systems, color roles, and tension points through clinical analysis. Use when doing formal design audits, teaching design analysis, or building structured observation skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when: investigating a legacy, inherited, third-party-built, or otherwise newly-unfamiliar codebase before scoping a migration or major refactor. Formalizes a repeatable five-step investigation pass — entry-point census, business-rule classification, side-effect/idempotency cataloging, implicit-contract discovery, semantic-duplication detection — plus a canonical per-project Open Questions document. Requires checkable signals: ticket keywords or prior documentation gaps. Not a mandatory gate; reserved for entry-point-heavy work in code areas with no prior investigation record.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a design or idea requires higher confidence, risk reduction, or formal review. This skill orchestrates a structured, sequential multi-agent design review where each agent has a strict, non-overlapping role. It prevents blind spots, false confidence, and premature convergence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for the infrastructure design phase between domain exploration and Lean formalization — deriving non-functional requirements from the Lean model, deciding environments (test/local/prod), identity provider, the relational database's product, version and configuration (the storage kind is fixed to relational), ID representation, and the list of things NOT to build. Produces documents/infra-design with INFRA-D/A/Q entries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use to create, update or verify the Lean 4 executable specification under lean/ from the exploration documents (event-timeline, hotspots, ubiquitous-language, ux-review, model-review) — initial generation, reflecting a session's results, fixing lake build, adding a command or a screen, checking a proposed feature against the model. Formalization questions go to model-review.md as MQ, never to the expert directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
当题面已经干净、但不知道该调用哪条物理定律，或者用了定律却说不清它在这里凭什么成立时使用。把问题拆成已知量、未知量、约束三栏，为每一条给定条件追出它背后的定律，并强制写明该定律在本题的适用条件；每条假设标出它近似掉了哪段物理；用未知数与独立方程的计数判断问题定不定得下来。检出凭空补进来的量和"用了定律但没写条件"的条目。不列出解、不推导、不给数值答案。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.