808건 · 관련도순
One command from "plugin installed" to "running brief on your idea." Combines /mycelium:setup (project-state initialization) and /mycelium:interview (10-minute discovery brief) into a single flow. Run this immediately after installing the Mycelium plugin — it's the recommended entry point for first-time users.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Record findings from completed offline human tasks (interviews, observations, outreach) back into the canvas. The re-entry point after /mycelium:handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate structured handoff materials for offline human tasks (interviews, observations, outreach). Creates actionable briefs with phone-friendly capture templates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structures customer diligence with interview guides, NPS analysis, switching cost assessment, and usage pattern evaluation. Use when conducting customer references, validating product-market fit, or assessing customer satisfaction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides through creating a new OpenCode-compatible agent with interactive interview, permission configuration, and validation. Use when user says "create opencode agent", "new opencode agent", "build agent for opencode", or wants to create an OpenCode agent markdown file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a new specification through an adaptive interview process with proactive recommendations and optional research. Use when user says "create spec", "new spec", "generate spec", or wants to start a specification document.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reference for advanced data structure patterns used in competitive programming and technical interviews. Covers heaps, monotonic stacks, tries, segment trees, Fenwick trees, stack-based parsing, and ordered sets with Python templates, recognition signals, and edge case guidance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides through creating a new OpenCode command with interactive interview, $VARIABLE configuration, and validation. Use when user says "create opencode command", "new opencode command", "build command for opencode", or wants to create an OpenCode command markdown file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides through creating a new OpenCode-compatible skill with interactive interview, best-practice enforcement, and validation. Use when user says "create opencode skill", "new opencode skill", "build skill for opencode", or wants to create an OpenCode SKILL.md file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when someone wants to contribute, submit or publish a GRC skill to the grcskills library (github.com/better-isms/grcskills, grcskills.com), or update a skill or author profile they already published there. Interviews the contributor for practitioner judgment, drafts the files in the library format, runs the validator and opens one pull request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a company needs its record of processing activities for the first time, or has one that is really a list of tools, and asks "build our RoPA", "records of processing", "data map for GDPR", "Article 30 record", "what personal data do we process and why", "data inventory for privacy" or "our DPO needs a processing register". Drafts the record by processing activity from systems, vendors and team interviews, with purposes, data and subject categories, proposed legal bases, recipients, transfers and concrete retention, plus a separate processor record when the company processes data for customers, and a notes file of open questions per owner.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA-<N>-<slug>.md) that /execute-qa runs. The agent drives browser and shell; the human steps in only at named handoff points. Use only when the user asks to plan manual QA — never trigger automatically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan the UX and UI for a feature before writing code. Run a structured discovery interview, then produce a design brief (.design-context.md) that guides implementation. Establishes design direction, constraints, and strategy before any code is written. Triggers on plan the design, design brief, shape the UX, before we build, design discovery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conversational profile builder. Produces validated JSON config files for any rootnode Skill that consumes profile-shaped configuration (handoff trigger check, mode router, critic gate, future Skills). Reads a target JSON Schema (draft-07), conducts a progressive-depth interview using plain-language questions, validates answers, and writes the resulting JSON to a destination path. Schema-agnostic — works with any profile schema conforming to draft-07. Use when a user needs to create, clone, or revise a profile and you do not want them hand-editing JSON. Trigger on: "build me a profile," "create a profile," "I need a profile for X," "set up my profile," "edit my profile," "clone the X profile," "walk me through making a profile." Do NOT use when the user already has a working profile and only wants to invoke the consuming Skill, when the schema cannot be located, or for non-profile JSON config work. Always validate before writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coach the user through a rigorous, repository-grounded interview to create or improve program.md. Use when a target repository lacks program.md, its goals, metrics, data, or guardrails are unclear, or the user asks to be grilled about an autoresearch setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a complete "constitution + documentation system" for a new autonomous, agent-run project — a content channel, an ebook press, an SEO tool-site, a web product, a casual game, or anything that should run itself with minimal human babysitting. Use when starting a brand-new self-running project and you want a CEO-orchestrated architecture (main agent → sub-agents → skills → CLI/MCP) with a named document system, a session lifecycle (start → work → finalize), and a growing identity/soul — scaffolded from a short structured interview. Triggers - "start a new autonomous project", "scaffold a project constitution", "set up an agent-run project", "generate a CLAUDE.md / AGENTS.md for a new project", "design the workflow for X", "bootstrap a self-running pipeline".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a repository decision needs an interview plus durable terminology and decision records. Not for remote, credential, publish, deploy, or irreversible changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create interview preparation from a job analysis, tailored resume, and master resume. Use when the user wants likely questions, truthful STAR answers, and ways to discuss gaps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a persistent visual brand identity for image generation. Defines how the brand looks visually — aesthetic, lighting, composition, mood — and writes it to brand/creative-kit.md so /image-gen and other creative skills produce consistent on-brand visuals. Three modes: Extract (from website/URL), Build (interview), Reference (mood board/examples). Use when starting any project that needs images, when the user says "visual style", "brand aesthetic", "image style", "visual identity", "how should our images look", "build visual brand", "define our look", or when /image-gen outputs feel generic because no visual style exists yet.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define or extract a consistent brand voice that other skills can use. Three modes: Extract (analyze existing content), Build (interview-based), Auto-Scrape (from URL). Use when copy sounds generic, when starting any new project, when voice feels inconsistent across channels, when onboarding a new brand, or when any skill needs voice-profile.md but it doesn't exist yet. This is always the first skill to run for a new project. Make sure to use this skill whenever the user mentions tone of voice, brand personality, 'my copy all sounds the same', 'how should I sound', 'analyze my website voice', 'define my tone', or anything about making content sound more human or distinctive. Even if the user just says 'my marketing sounds generic' — that's a voice problem.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me". Run BEFORE /claude-setup:build when a feature idea is fuzzy and a PRD doesn't yet exist.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me". Run BEFORE /build when a feature idea is fuzzy and a PRD doesn't yet exist.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.