메뉴
SkillsMP는 HirogaKatageri/hirokata에서 31개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
수집된 skill 31개 중 31개를 표시합니다.
This skill should be used when the user says "check in", "clock in", "standup", "guild check in", "what's the status", "let's get to work", "start working", "daily standup", "guild standup", "I'm here", "reporting in", or any phrase indicating they want to…
원문 언어: 영어
This skill should be used when the user asks for "guild status", "board status", "show the board", "what's on the board", "project status", "show guild", "guild board", or "what's happening". Shows a quick read-only view of the guild board without starting…
원문 언어: 영어
This skill should be used when the user asks to "add a requirement", "new requirement", "I need a feature", "add to the guild", "create requirement", "queue a feature", "I want to build", or wants to add a new work item to the guild board. Runs a live 3-way…
원문 언어: 영어
This skill should be used when the user asks to "cut a release", "release the guild", "ship it", "create a release", "tag a version", "publish a release", "guild release", or wants to finalize completed requirements into a versioned release. Renames CHANGELOG…
원문 언어: 영어
Pre-loaded QA discipline for the qa-strategist and qa-tester agents. Covers the five QA pillars (validation over verification, disconfirmation, empiricism, the oracle problem, risk-based triage), the hybrid oracle rule for testing existing products, the…
원문 언어: 영어
Use this skill to structure a message as ABT — And, But, Therefore: setup, tension, resolution in three beats. Best for elevator pitches, one-liners, hooks, openers, and landing a point in under 30 seconds. Triggers on "abt", "and but therefore", "elevator…
원문 언어: 영어
Use this skill to structure a message with Simon Sinek's Golden Circle — Why → How → What. Best for rallying a team, framing a brand or mission, launching a company or product with meaning, or any "why we exist" moment. Triggers on "golden circle", "start…
원문 언어: 영어
Use this skill to structure a message with the Pixar story spine — "Once upon a time... Every day... Until finally." Best for transformation and journey narratives: before/after, old world → new world, the arc of a change, product origin stories, case…
원문 언어: 영어
Use this skill to structure a message with Barbara Minto's Pyramid Principle — answer first, then grouped evidence. Best for boards, executives, investors, and decision memos where the reader wants the bottom line now. Triggers on "pyramid principle",…
원문 언어: 영어
Use this skill to structure a message with Donald Miller's StoryBrand (SB7) framework — make the customer the hero and position yourself as the guide. Best for marketing, sales, landing pages, value propositions, cold outreach, and product messaging. Triggers…
원문 언어: 영어
Use this skill when the user has something to communicate — an idea, a pitch, a product, a strategy, an update, a decision, a launch, an ask — and wants it to actually land. Triggers on things like "help me tell the story of <X>", "how should I pitch <X>",…
원문 언어: 영어
Use this skill to structure a message as What / So What / Now What — state the fact, explain the impact, recommend the action. Best for post-mortems, retros, incident reviews, status updates, debriefs, and any "here's what happened and what we should do"…
원문 언어: 영어
Use this skill when the user wants to review code changes, verify implementation quality, or check readiness before a PR or deployment. Trigger on phrases like "review my changes", "run comprehensive review", "check all my code", "am I ready for PR", "before…
원문 언어: 영어
This skill should be used when the user wants quality assurance on the product itself — "QA the product", "QA the checkout flow", "run a QA pass", "build comprehensive e2e tests", "write regression tests", "test the running app", "what-if testing", or any…
원문 언어: 영어
This skill should be used when the user asks to "clear the board", "reset the guild", "start fresh", "wipe the board", "clear all tasks", "reset the board", or wants to remove all current work from the guild board and start over.
원문 언어: 영어
This skill should be used when the user says "discuss", "let's discuss", "discuss [topic]", "talk about", "let's talk about", "summarize the context", "what are we working on", "break down the topics", "what subjects do we have", "let's review the context",…
원문 언어: 영어
Pre-loaded QA artifact formats for the qa-strategist and qa-tester agents. Defines the evergreen `.guild/qa/` files — charter (quality definition, risk map, coverage matrix, oracle ledger), missions (scope, what-if input matrix, oracle sources), the bug…
원문 언어: 영어
Use this skill when the user wants deep, PhD-level, multi-perspective research on a topic and says things like "storm research <topic>", "run STORM on <topic>", "deep research <topic>", "research <topic> from every angle", "multi-perspective deep dive", "give…
원문 언어: 영어
Use this skill when the user wants to find where sources, viewpoints, or perspectives disagree — phrases like "contradiction map", "where do these disagree", "map the conflicts", "find the disagreements", "where do the experts clash", "compare these…
원문 언어: 영어
Use this skill when the user wants a fast multi-angle read of a topic without the full STORM pipeline — phrases like "multi-perspective scan", "give me 5 perspectives on <topic>", "analyze <topic> from multiple angles", "what would different experts say about…
원문 언어: 영어
Use this skill when the user wants to rigorously audit a piece of research, a briefing, a report, or an argument before relying on it — phrases like "peer review this", "self-critique this", "audit my research", "red team this report", "fact-check this",…
원문 언어: 영어
This skill should be used when the user reports an error, bug, or unexpected behavior and wants it diagnosed and fixed. Trigger on phrases like "check this error", "check this bug", "here's an error", "here's a bug", "I have an error", "I have a bug", "found…
원문 언어: 영어
This skill should be used when the user says "check svelte env vars", "check environment variables", "validate env vars", "check env var patterns", "audit environment variables", "audit env vars", "check SvelteKit env", "svelte env check", or any phrase…
원문 언어: 영어
This skill should be used when the user asks to "create a workflow", "generate a workflow", "add a GitHub Actions workflow", "create a CI/CD pipeline", "write a script workflow", "automate a task", "set up automation", or wants to build any kind of automated…
원문 언어: 영어
Pre-loaded advanced Svelte 5 / SvelteKit techniques for the developer-svelte agent. Covers attachments ({@attach}), actions (use:), transitions and animations, the motion module, custom elements, packaging libraries, server hooks, remote functions, service…
원문 언어: 영어
Pre-loaded Svelte 5 / SvelteKit best practices for the developer-svelte agent. Covers state management strategies, performance optimization, accessibility, SEO, TypeScript usage, testing (vitest + playwright), and error handling. Load alongside the other…
원문 언어: 영어
Pre-loaded SvelteKit knowledge for the developer-svelte agent. Covers project structure, file-based routing (+page, +layout, +server, +error), load functions (universal vs server), form actions, page options (prerender / ssr / csr), building for production,…
원문 언어: 영어
Pre-loaded Svelte 5 core knowledge for the developer-svelte agent. Covers the component model, runes ($state, $derived, $effect, $props, $bindable), basic markup, control flow, snippets, bindings, scoped styles, lifecycle, and context. Load this skill before…
원문 언어: 영어
This skill should be used when the user asks to "create a conventional commit", "generate conventional commits", "generate commit", "commit with conventional format", "group my changes for commits", "make a conventional commit message", or mentions "semantic…
원문 언어: 영어
Reference guide for classifying development tasks into the 8-phase clean architecture structure (Foundational → Models → Services → Data → Rules → State Management → UI → Tests). Use when you need to determine which architectural phase a task belongs to.
원문 언어: 영어
Analyze a master plan file and split it into 8 phase-specific implementation plans organized by feature tracks. Automatically identifies tracks, classifies tasks by phase, scores complexity, and generates detailed phase plan files following clean architecture…
원문 언어: 영어