910건 · 관련도순
Crystallize shared understanding into a reviewable spec, or update an existing one. Use when the problem needs a written specification, when assumptions or decisions have changed, or when the user says 'write a spec'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Knowledge base from MIL-HDBK-338B (Electronic Reliability Design Handbook). Use for electronic reliability engineering: R/M/A theory, reliability specification/allocation/prediction, parts management and derating, reliable circuit and fault-tolerant design, environmental and human performance reliability, FMEA/FMECA/FTA/sneak circuit analysis, design reviews and testability, FRACAS, reliability demonstration and growth testing, and systems-level R&M parameters. Covers selected Part 2 design-guidance topics only; skips large annex/part-stress tables. Guidance handbook — not a contractual requirement text. Does not replace MIL-HDBK-217 prediction libraries, service-specific reliability regs, or safety standards (see mil-std-882).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Knowledge base from IS-GPS-200 Rev N (NAVSTAR GPS Space Segment / Navigation User Segment Interfaces). Use as a worked ICD/IS exemplar: what an interface specification is, DIST-A and IRN/CCB change control, interface definition vs identification, composite-signal criteria patterns, NAV data as payload families, and time/definition hygiene. Covers Rev N synthesized notes only; does not transcribe Apps II–IV bit fields or PRN/Gold-code tables, and does not replace faa-std-025 preparation rules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proposes the piping content a P&ID adds to an accepted PFD process model: line inventory with off-page continuity and required ancillary lines, line identification elements per the project line numbering procedure, connection items at nozzles matched to a quoted schedule, per quoted standards, specification break questions and observations. Every proposal cites its source and revision; no source, no proposal; never sizes a line or selects a class. Use when the user asks to "run the piping enrichment", "start the discipline enrichment", "list the lines the P&ID adds to this PFD" or "fill the line identifiers from the numbering procedure" after gate G2. Do not use for instruments, loops or instrument tags, use instrumentation-and-control-enrichment instead; do not use before gate G2, use process-model-check. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates complete, production-ready REST API endpoint specifications for any system or domain the user describes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Translates user intent into a precise, unambiguous specification and requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate Claude Code skills against the agentskills specification. Catches structural, semantic, and naming issues before users do.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create and improve agent skills following the Agent Skills specification. Use when asked to create, write, or update skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate generic React component test skeletons (RTL) from specifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate Vue.js component test skeletons (Vue Test Utils) from specifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensure requirement docs define scope, terminology, acceptance criteria, edge cases, and non-functional requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate React/Next.js component test skeletons (RTL) from specifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate Python/pytest unit test skeletons from specifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate TypeScript unit test skeletons (Jest/Vitest) from specifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate PHP/Laravel (PHPUnit) test skeletons from specifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reads an OpenAPI 3.0 specification and manually implements a type-safe Dart API layer using Dio for HTTP, Freezed or Equatable for models, and json_serializable for serialisation. Use when given an OpenAPI/Swagger file (JSON or YAML) and asked to implement the API in Flutter/Dart, create Dart models from an API schema, build a Dio API client, implement endpoints from a spec, convert openapi to dart, or set up a data/network layer from an API contract. Handles $ref resolution, oneOf union types, enums, query params, request bodies, and DioException error mapping.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Methodology for writing complete, unambiguous IA, BE, and FE specification documents in the CFSA pipeline. Covers completeness testing, progressive section writing, cross-reference checking, and ambiguity gate application.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when building applications with Gemini API hosted models, including Gemini and Gemma 4, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or needing current model specifications. Covers SDK usage (google-genai for Python, @google/genai for JavaScript/TypeScript, com.google.genai:google-genai for Java, google.golang.org/genai for Go), model selection, and API capabilities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.