1.4만건 · 관련도순
Query ProteomeXchange through its PROXI API to inspect datasets, libraries, proteins, peptide forms, and spectra. Receive concise summaries focused on a dataset or identifier, and save complete responses when more detail is needed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan and implement features with a workflow that adapts to their complexity. It connects testable requirements to tasks, tests, and small commits, then checks the finished work against the specification through an independent verification pass.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Develop and fix Nexent features by connecting written specifications, acceptance criteria, implementation, and verification evidence. Plan unit tests and appropriate staged checks, maintain their links to requirements, and fill confirmed test gaps after development.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review an OpenSpec implementation against its specifications, tasks, and design decisions. The skill checks for missing work, uncovered scenarios, and inconsistencies, then produces a prioritized report with concrete recommendations and code references where available.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create a structured specification in plain language from a feature description and multi-AI research. Define actors, behaviors, constraints, dependencies, and acceptance conditions, while checking completeness and keeping unresolved user decisions visible for later review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up and inspect periodic prompts that continue a specific Codex thread after idle checks pass. It supports App-native automation and a headless fallback, with controls to inspect status and enable or disable scheduled prompts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create or update a project's governing development principles, covering code quality, testing, and architectural constraints. Maintain the constitution document, record version changes, and align related planning, specification, and task templates with the revised rules.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guides general use of AWS messaging and streaming services. Covers Amazon SQS, Amazon SNS, Amazon EventBridge, Amazon MQ, Amazon Kinesis Data Streams, Amazon Data Firehose, Amazon Managed Service for Apache Flink, and Amazon Managed Streaming for Apache Kafka (MSK). Use when reasoning about messaging and streaming patterns. Also identifies which AWS service owns each customer communication channel: email (Amazon SES), and WhatsApp, SMS, MMS, RCS, voice and mobile push (the AWS End User Messaging family of services). Routes the request to the specialized skill for that channel. Defers to the channel's specialized skill when the user already named a specific channel. In general, use specific skills or documentation searches for detailed service-specific questions. Do NOT use for MSK or Managed Service for Apache Flink questions, prefer specific skills. Does not configure customer communication channels; defers to specific skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when SLCI code inspection has failed due to compatibility issues and you need to diagnose the incompatibilities. Traces inspection failures back to root-cause incompatibility settings or known limitations by matching failed code lines against known incorrect code generation patterns and documented limitation scenarios. Hands off to slci-compatibility-analysis for fixes. Trigger keywords: inspect, inspection failed, trace inspection errors, why did inspection fail, SLCI verification failures, limitation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrates Spec Driven Development by coordinating spec, plan, and task skills. Use when running the full speckit workflow from spec to implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check behavioral consistency between high-level hardware specifications and RTL implementations. Use when asked to check RTL consistency, verify RTL against spec, check hardware specification compliance, validate RTL implementation, find spec violations in RTL, check behavioral consistency, or when working with hardware designs that need verification against protocol specifications, timing requirements, or functional specifications in Verilog, VHDL, or SystemVerilog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keeps specification documents and code in agreement. Audit mode finds every divergence when an implementation is claimed complete; sync mode detects spec drift in staged changes and updates the spec after user approval, so each commit is a reconciled snapshot of spec, tests, and code. Use when an implementation is claimed complete against a spec, before committing changes that may drift from the spec, or after approving decisions that must flow back into it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," or "qualified leads." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Condense any input — an idea, brief, PRD, transcript, or mixed notes — into a short spec: one kernel file plus supporting files that downstream skills build from. Also updates and validates existing specs. Use when the user says "create a spec", "distill this into a spec", "validate this spec", or "update the spec"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or implementation can begin. Triggers on: "resolve the open questions", "close the gaps in this spec", "research the open items", "finalize my spec", "make this spec implementation-ready", "answer the TBDs". Also triggers whenever the user points at a brainstorm-beagle spec and asks for research, proposals, or answers to unresolved items. Orchestrates parallel research subagents when available (falls back to inline sequential research otherwise), proposes answers one at a time for user approval, then rewrites the spec in place so it arrives at planning with no known gaps. Does NOT write code, design implementation, or create plans — it only produces a complete spec.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you have a finalized brainstorm-beagle spec at `.beagle/concepts/<slug>/spec.md` and need a bite-sized, TDD-driven implementation plan before any code is written. Triggers on: "write a plan", "plan this spec", "turn the spec into a plan", "now plan the implementation", "write-plan". Reads the spec, designs the file structure, decomposes work into 2-5 minute TDD steps with exact paths and commands, self-reviews against the spec, gets user approval, then writes to `.beagle/concepts/<slug>/plan.md` and offers to generate an execution handoff prompt via the subagent-prompt skill. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze an existing spec for inconsistencies, missing information, ambiguities, and structure issues. Use when user says "analyze spec", "review spec", "spec quality check", "validate requirements", "audit spec", or "check spec quality".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform Markdown or text specifications into human-readable HTML documents with summaries, reordered structure, visual explanations, diagrams, charts, and traceability to the source. Use when asked to convert a spec, requirements document, API spec, product spec, design doc, or technical document into readable HTML, especially when the user wants summarization, restructuring, diagrams, graphs, images, or visual aids rather than a literal Markdown-to-HTML conversion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check the local environment for Spec Kit by running `specify check` (and `specify version`). USE FOR: verifying required tools are installed, diagnosing a broken spec-kit setup, reporting CLI version/feature capabilities. DO NOT USE FOR: installing or upgrading the CLI itself (use the speckit-self skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage and run Spec Kit automation workflows via `specify workflow`. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use speckit-extension), presets (use speckit-preset), or bundles (use speckit-bundle).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Genera una nueva especificación de cambio ligera copiando el directorio de plantilla de especificación en una carpeta de especificación con nombre. Úsalo cuando la persona quiera iniciar una especificación, planificar un cambio/funcionalidad o crear un documento de diseño antes de implementar (p. ej. "especifica el rediseño del checkout", "crea una especificación para el nuevo flujo de autenticación").
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep spec analysis on a Confluence page. Reads page (+ children) via the confluence-as wrapper, produces a structured Spec Research Report with requirements, acceptance criteria, gaps, ambiguities, and suggested user stories for human review. Read-only — does NOT create Jira tickets. Triggers: 'analyze spec for PAGE-ID', 'extract requirements from confluence page', 'spec research on URL'. NOT for raw page CRUD (mk:confluence-page); NOT for ticket complexity scoring (mk:planning-engine).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.