597건 · 관련도순
Suite de ferramentas para criar artefatos HTML elaborados e multi-componentes para claude.ai usando tecnologias web frontend modernas (React, Tailwind CSS, shadcn/ui). Use para artefatos complexos que requerem gerenciamento de estado, roteamento ou componentes shadcn/ui - não para artefatos HTML/JSX simples em arquivo único.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Banco de dados de embeddings de código aberto para aplicações de IA. Armazene embeddings e metadados, realize buscas vetoriais e full-text, filtre por metadados. API simples com 4 funções. Escala de notebooks para clusters de produção. Use para busca semântica, aplicações RAG ou recuperação de documentos. Melhor para desenvolvimento local e projetos de código aberto.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Instâncias GPU em nuvem reservadas e sob demanda para treinamento e inferência de ML. Use quando você precisar de instâncias GPU dedicadas com acesso SSH simples, sistemas de arquivos persistentes ou clusters multi-node de alto desempenho para treinamento em larga escala.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement or refactor Laravel controllers, commands, jobs, listeners, and scheduled tasks. Use for endpoints, authentication, request validation, simple reads, or extracting business orchestration into Actions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
At the end of a long working session, produce a counterfactual trace note — a backward walk through the session that identifies the small number of load-bearing moments (observations, failures, accidents, decisions) without which the final outcome would not exist. Use this whenever the user asks to "close the session", "run the butterfly", "trace back", "what actually mattered here", asks for a session retrospective, or asks how the session arrived at its result. Also use it when a session ends with a significant outcome (a fix, a design decision, a shipped artifact) and the user wants a note capturing why it happened, not just what happened. Do NOT use for simple summaries of short sessions — this skill is for causal tracing, and it only earns its cost when the session was long enough to contain real forks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discover ordinary public webpages with LLM-optimized Tavily search results. Use when no specific URL is known and the user needs a quick public-web lookup, articles, recent news, sources, or domain-filtered results. This is the default Tavily leaf for simple public-web discovery. Do not use when the user already supplied the target URL (use tavily-extract), wants URLs under one known site (tavily-map), wants many pages' content (tavily-crawl), needs a full cited synthesis (tavily-research), or needs named platforms, login state, platform-native content, or cross-platform collection (Agent Reach).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce comprehensive synthesis with explicit citations from multiple ordinary public-web sources via the Tavily CLI. Use for detailed reports, comparisons, market or literature research, and questions whose answer requires multi-source web evidence rather than a quick lookup. Do not use for simple discovery (tavily-search), one known URL (tavily-extract), one-site URL discovery or bulk extraction (tavily-map/crawl), or research centered on named social, community, career, code, media, authenticated, or cross-platform sources (Agent Reach). Takes 30-120 seconds.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when managing Alibaba Cloud Simple Application Server (SWAS OpenAPI 2020-06-01) resources end-to-end, including querying instances, starting/stopping/rebooting, executing commands (cloud assistant), managing disks/snapshots/images, firewall rules/templates, key pairs, tags, monitoring, and lightweight database operations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write new English text, or rewrite existing text, in ASD-STE100 Simplified Technical English. Use for STE, simple technical English, ASD-STE100, or 80% STE, for writing or rewriting procedures, manuals, SOPs, runbooks, and release notes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explain a topic like I'm a 5 year old, as a single HTML artifact built from big pictures and very few words. Use this whenever the user asks for a dead-simple explanation of how something works, says "ELI5", "explain like I'm five", "簡単に説明して", "図で説明して", "初心者向けに", "素人にもわかるように", wants to explain a concept to a non-technical manager, customer, or family member, or asks for a visual explainer — even if they don't say "ELI5" explicitly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control and interact with a live browser session on any scraped page — click buttons, fill forms, navigate flows, and extract data using natural language prompts or code. Use when the user needs to interact with a webpage beyond simple scraping: logging into a site, submitting forms, clicking through pagination, handling infinite scroll, navigating multi-step checkout or wizard flows, or when a regular scrape failed because content is behind JavaScript interaction. Also useful for authenticated scraping via profiles. Triggers on "interact", "click", "fill out the form", "log in to", "sign in", "submit", "paginated", "next page", "infinite scroll", "interact with the page", "navigate to", "open a session", or "scrape failed".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI-powered autonomous data extraction that navigates complex sites and returns structured JSON. Use this skill when the user wants structured data from websites, needs to extract pricing tiers, product listings, directory entries, or any data as JSON with a schema. Triggers on "extract structured data", "get all the products", "pull pricing info", "extract as JSON", or when the user provides a JSON schema for website data. More powerful than simple scraping for multi-page structured extraction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Replace OneCLI gateway with the built-in credential proxy. For users who want simple .env-based credential management without installing OneCLI. Reads API key or OAuth token from .env and injects into container API requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Replace OneCLI gateway with the built-in credential proxy. For users who want simple .env-based credential management without installing OneCLI. Reads API key or OAuth token from .env and injects into container API requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate logical consistency of decisions and claims through context forking. Use proactively when judgment validity is unclear, but prefer direct tools (Read, Bash) for simple verifications like file contents or test results.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resolve complex or high-impact problems when the cause, solution path, requirements, or proof boundary is genuinely uncertain. Use when work needs evidence-led diagnosis, consequential design or implementation, or a completion audit; do not trigger merely because work has multiple steps, or for simple facts, fully specified routine changes, or pure creative generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate the root cause of a recurring or systemic defect across a series of incidents, not a single one. Use on the third recurrence, or when someone asks 'why again?', 'five whys', 'fix the root'. Skip for one or two ordinary cases, an already proven simple cause, or a one-off external outage. Triggers: /five-whys, five whys, fix the root.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reconstructed reference notes on US FAA approval guidance for airborne software and airborne electronic hardware, built from four public-domain sources (FAA Order 8110.49A, AC 20-115D, AC 20-152A, AC 00-69; documents dated 2017-07-21 to 2022-10-07, pinned 2026-10-12). Use for how FAA certification staff plan and conduct software reviews (certification liaison, desk versus on-site review, review planning agreements), how the level of FAA involvement (LOI) is picked and scored with the Appendix A worksheets, how software conformity inspection works (software part and installation conformity, ASE and ASI tasks, Form 8120-10), what AC 20-115D recognizes and how DO-178B processes and tool qualification transition to DO-178C/DO-330 (supplements, FLS, UMS, legacy software changes), and what AC 20-152A adds for airborne electronic hardware (simple versus complex custom devices, robustness and HDL code coverage, tool assessment, previously developed hardware, COTS IP, COTS devices, circuit board assemblies), and what AC 00-69 adds as best practices for change impact analysis, data and control coupling, and design-level error handling (best practices, not guidance and not a means of compliance). SCOPE LIMITS: FAA guidance only, and guidance is not regulation (ACs are acceptable means, not the only means); no RTCA DO-178C or DO-254, EUROCAE ED-12C or ED-80, supplement, or SAE ARP text, which are copyrighted and named only (see the avionics-signpost pack); no AC 00-72 (named, not packed); no DO-178C software-level objective tables; no EASA AMC 20-115D or AMC 20-152A content (use easa-rules); reflects the pinned source dates, not later FAA actions; synthesized reference notes, not legal advice and not a substitute for the source documents. LICENCE: Public Domain (US Government work, 17 U.S.C. 105).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.