356건 · 관련도순
Use when the user says 'figma to bricks', 'build this figma design in bricks', or hands over a Figma frame to rebuild on a Bricks Builder site. Maps the Figma node tree to native Bricks elements with BEM global classes, imports the frame's palette into the Bricks design system, and writes to a draft, so nothing live is touched.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cultivate edible and medicinal mushrooms from spawn through fruiting. Covers substrate preparation, inoculation methods, incubation conditions, fruiting chamber management, harvest timing, and successive flushes for oyster, shiitake, lion's mane, and other commonly cultivated species. Use when growing edible mushrooms without the risks of wild foraging, when a reliable supply of fresh culinary or medicinal mushrooms is needed, or when exploring mycelial ecology through hands-on cultivation practice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run Kimi's autonomous goal mode for an explicitly requested hands-off multi-turn objective. This is write-capable and budget-bounded; use only when the user explicitly asks Kimi to pursue an objective autonomously.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert a semantic core into crawlable SEO and LLM-friendly information architecture. Use this skill when the user asks for URL structure, page taxonomy, canonical rules, hreflang groups, page roles, pillar/topic/news/article/blog/project separation, multilingual route strategy, or a durable content model such as one short brief plus one longform article. It prevents duplicate public content bodies and hands link-graph work to internal-link-graph-architect.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit recent tool use across local Senpai OpenHands root and recursively delegated conversations without exposing tool arguments. Use for provider comparisons, tool-loop diagnosis, status-poll analysis, error rates, and latency reports.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user says "找 bug" / "看一下有没有 bug" / "smart-qa" / "/smart-qa" / "帮我测一下这个项目" / "智能 QA" / "推断业务流程测一下"，or asks for an autonomous bug-hunt where they DON'T already know what to test. Distinct from `qa` (blind exploration) and `devtest` (verifies a specific change). smart-qa READS the project source — prefers PRD/requirements docs, falls back to code (activities, routes, click handlers, API calls) — then proposes a focused test plan for confirmation before driving the app. v1 stops after the user confirms the plan and hands off to the existing `qa` skill for execution. v2 (planned) adds per-step assertions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resolve relevant context from the active gc-branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launch a guided durable update for the active gc-branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clear an existing gc-branch so it can be onboarded again.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launch guided onboarding for the active gc-branch through the configured provider.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Switch or create a gctree gc-branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a NowStack Mobile app idea into a build-ready plan. Orchestrates PRD, architecture, and tasks; optionally applies the site-config brief and hands off to implementation. Use for `ns create-app`, "create app", "plan a new app", "I have an app idea", or starting a product from scratch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
First-run conversational setup wizard for marketing-cli. Use when /cmo detects no populated brand files and no cmo-preferences.md, when the user just installed marketing-cli for the first time, or when they say things like "set up marketing", "start marketing", "marketing wizard", "I just installed marketing-cli", "onboard me", "first time", "initial setup". Asks 3 sharp questions (identity, posture, distribution preferences), records the answers to brand/cmo-preferences.md, then hands off to /cmo's foundation flow which spawns 3 research agents in parallel. The user never has to type /mktg-setup directly — /cmo auto-routes here on first run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
DiviOps harness primer — error envelope, capability handshake, dry-run plan shape, idempotency contract. Used as a shared primer by DiviOps target-coverage skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The Arbor executor workflow: clone the repo from the git bundle your brief hands you, implement and evaluate exactly ONE hypothesis with the file tools, then report structured results via worker_complete. Preloaded automatically on arbor-executor task workers. Never touch the held-out test split.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when evidence needs grading before anyone reasons from it — the user asks "how reliable is this?", "grade this source", "check this report", "can I trust this article?", "is this corroborated?", or hands over a URL, a pasted report or a Liberty91 event ahead of an ACH or assessment. The Quality of Information Check from the CIA Tradecraft Primer, adapted for vendor and press CTI reporting. Resolves each document to its originating source, splits it into claims, and grades every claim on two written elements, access level (how the source knows) and claim support (what backs the statement), with a stated rationale, using a fixed rubric with hard caps. The grade is not an Admiralty rating. Five outlets citing one vendor report count as one source; anything that cannot be traced to a primary is capped, not guessed. Returns a graded claim table, gaps, a deception screen and JSON. /ach, /threat-assessment and /writing-assessments run it first by default.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a targeted resume and cover letter for a role folder that already has a job description and role analysis. Runs iterative adversarial review rounds until the materials stabilize, then hands off for human review before submission.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for hands-on repository work when a quiet, risk-scaled engineering method can improve design, execution strategy, implementation, material incorporation, debugging, review, delegation, workspace lifecycle, or verification. Keep clear local changes direct, preserve the complete requested outcome, and add method only where risk or uncertainty justifies it. Do not use for general technical explanations, simple file lookup, casual discussion, or non-engineering writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, read, edit, and open draw.io (.drawio) files. Supports architecture diagrams, ER diagrams, flowcharts, domain model diagrams, and more. Use when requests include "create a diagram", "make a flowchart", "draw an architecture diagram", "create an ER diagram", "open a .drawio file", "what's in this diagram?", etc. Do NOT use for Mermaid or PlantUML generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage, fix, and pre-flight a PR before merge. Checks mergeability, CI, reviews, and bot comments — fixes issues, runs /pre-commit before pushing, then hands off to /pr-merge.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate bugs with unknown root cause. Spawns fresh-context investigation subagent + parallel /review solve companion, persists hypotheses across iterations, hands off to /fix when root cause found.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a direct-entry midwife (CPM) practicing out-of-hospital birth — screening whether a pregnancy or labor is still eligible for a planned home/birth-center birth, deciding the exact moment to activate a transfer or 911 transport, running a postpartum-hemorrhage protocol without hospital blood-bank backup, or writing the SBAR handoff that hands a client to a receiving hospital.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of an audiovisual equipment installer/repairer — diagnosing an EDID or HDCP handshake failure between a source and a display, sizing a display's screen size and brightness for a room's viewing distance and ambient light, specifying an HDMI/HDBaseT/AVoIP signal run against its rated distance ceiling, designing conference-room speaker placement and acoustics, or drawing the install-vs-programming boundary with a control-system (Crestron/Extron/AMX) integrator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Specify a FlexCard before a developer opens Card Designer: the card-state set and the condition that selects each state, the data source type behind each card (DataRaptor, Integration Procedure, Apex remote, SOQL), the action menu users get (navigate, launch OmniScript, Apex, DataRaptor), and every embedded child FlexCard or custom LWC. Produces the artifacts a BA hands to the builder. Trigger keywords: FlexCard requirements, FlexCard BA, FlexCard layout design, FlexCard data sources, FlexCard actions, FlexCard card states, OmniStudio FlexCard scoping. NOT for building the card in Card Designer, NOT for OmniScript step and branching requirements (use admin/omniscript-flow-design-requirements), NOT for standard Lightning record-page component requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.