إعلان[ For iPhone / iPad ] 🔥 خلفيات تفاعلية مذهلة من Nugget. لم ترَ شيئًا كهذا من قبل!

skills.homescapability registry البحث

home/categories/knowledge-base

category focus

Knowledge Base

Wikis and information organization.

2421 مهارةall categories

sorting

stars

current ordering strategy

query

all entries

refine the visible subset

knowledge-base

0

aico-pm-brainstorming

Guide users through structured dialogue to transform vague ideas into clear, actionable product concepts. Uses one-question-at-a-time approach with multiple choice options. Use this skill when: - User says "I have an idea", "I want to build", "let me think about" - User mentions "brainstorm", "explore ideas", "think through" - Requirements are vague, incomplete, or user seems unsure what they want - Need to explore problem space before jumping to solutions - Running /pm.plan but requirements are unclear or missing context - User asks "what should I build?", "how should this work?" Process: Ask ONE question at a time, prefer multiple choice, explore 2-3 approaches before settling.

yellinzero

documentation

knowledge-base

0

spec-interview

Conducts structured requirements interviews for spec documents. Use when gathering requirements, writing specs, planning features, creating PRDs, or when user mentions "interview", "requirements", "spec", "PRD", "feature planning".

SmartOzzehir

documentation

knowledge-base

0

planning

Provides expertise on how to plan for work in this repo

yankeeinlondon

documentation

knowledge-base

0

reporter

Professional report writing and meeting minutes specialist. Use when creating meeting minutes, progress reports, project summaries, retrospectives, issue tracking reports, decision logs, or executive summaries. Use "reporter" or "서기님" or "보고서" to invoke.

hnabyz-bot

documentation

knowledge-base

0

ossissue-discovery

Phase 1 of OSS contribution - Find and evaluate suitable issues matching your skills, time, and learning goals. Filters by labels, assesses project health, and provides structured recommendations. Use when starting OSS contribution, looking for beginner-friendly issues, or evaluating multiple issue options.

devkade

documentation

knowledge-base

0

aico-pm-clarification

Resolve requirement ambiguities through STRUCTURED questioning: one question at a time, with recommended options and reasoning. UNIQUE VALUE: Prevents overwhelming users with multiple questions. Provides expert recommendations for each decision. Use this skill when: - Running /pm.clarify command - User says "unclear", "not sure what this means", "confused about" - User asks "what does X mean?", "how should X work?", "can you clarify?" - Requirements have conflicting or inconsistent details - Stories are missing acceptance criteria or have gaps - Need to fill information gaps BEFORE development can proceed Process: Ask ONE question at a time (max 5 per session), provide recommended option with reasoning. DO NOT ask multiple questions at once - this overwhelms users.

yellinzero

documentation

knowledge-base

0

notes-writing

Write clear development notes that document what was built, decisions made, and verification performed. Use when completing tasks, closing out feature implementations, documenting decisions, recording deviations from plans, capturing verification and testing, noting follow-up work, or building institutional knowledge. Triggers include "write notes", "development notes", "implementation notes", "document decisions", "capture context", or when recording the story of implementation work.

pjordan

documentation

knowledge-base

0

release-management

Use this skill when working on releases, version numbers, or release preparation.

ProteoWizard

documentation

knowledge-base

0

project-charter

This skill should be used when the user asks to "プロジェクト憲章", "charter", "プロジェクト定義", "プロジェクト開始", "project kickoff", "Why/What/How", "目的を整理", "スコープ定義", "ゴール設定". MUST USE this skill for: - Creating project charter documents at project start - Clarifying project purpose (Why), deliverables (What), and approach (How) - Interviewing stakeholders to extract implicit project goals - Any work in _docs/charter/ directory

sunbluesome

documentation

knowledge-base

0

microservice-architect

Guide the planning of microservices architecture. Use when designing, planning, or architecting a system using microservices.

yairbederman

documentation

knowledge-base

0

session-refiner

Automatically bridge long technical sessions to keep context window small and costs low. Extracts key technical decisions, resolved bugs, active tasks, and essential code snippets from conversation history into a compact markdown summary (2,000–5,000 tokens). Use when reaching a project phase milestone, when Claude warns the context window is getting full, or to start a fresh session with minimal token cost while maintaining continuity.

amite

documentation

knowledge-base

0

technical

Comprehensive technical architecture guidance for full-stack applications. Use when discussing system design, component architecture, API design, database schema, state management, deployment strategies, performance optimization, or technical implementation decisions. Covers frontend (React/Next.js), backend (Node.js/serverless), databases (SQL/NoSQL), caching, real-time features, file storage, and technology selection. Ideal for architectural reviews, technical planning, code structure discussions, and scaling strategies. For security architecture, use security skill. For code quality, use code-review skill. For DevOps/CI/CD, use devops skill.

tomas-u

documentation

knowledge-base

0

github-issue-helper

GitHub 이슈 작성 도우미. 사용자가 이슈 초안이나 아이디어를 제시하면 고품질 GitHub 이슈로 개선. Use when user asks to (1) write/create/draft a GitHub issue, (2) improve/refine an issue draft, (3) convert an idea into a proper issue format, (4) review issue quality. Supports bug reports, feature requests, and improvement proposals. Communicates in Korean but produces final issues in English.

moreal

documentation

knowledge-base

0

plan-rfc

Plan and draft RFCs (Request for Comments) for major features or architectural changes. Use when user wants to propose a significant feature, system redesign, or cross-cutting change that requires stakeholder alignment before implementation. Triggers on phrases like "RFC", "proposal", "major feature", "architectural change", "need buy-in", or when user describes a feature too large for a single ticket. Guides through structured questioning to produce a complete RFC draft in Notion.

anton-pt

documentation

knowledge-basemarketplace

0

c4-generator

C4 architecture diagram expert. Activate when: - User asks for architecture documentation - User mentions "C4 model", "system context", "container diagram", "component diagram" - Need to document system architecture at different levels of detail - Creating architecture decision records or technical documentation

pagerguild

documentation

knowledge-base

0

aico-pm-clarification

Resolve requirement ambiguities through STRUCTURED questioning: one question at a time, with recommended options and reasoning. UNIQUE VALUE: Prevents overwhelming users with multiple questions. Provides expert recommendations for each decision. Use this skill when: - Running /pm.clarify command - User says "unclear", "not sure what this means", "confused about" - User asks "what does X mean?", "how should X work?", "can you clarify?" - Requirements have conflicting or inconsistent details - Stories are missing acceptance criteria or have gaps - Need to fill information gaps BEFORE development can proceed Process: Ask ONE question at a time (max 5 per session), provide recommended option with reasoning. DO NOT ask multiple questions at once - this overwhelms users.

yellinzero

documentation

knowledge-base

0

clarify

Start iterative requirement clarification loop. Use this skill when the user has a vague requirement and wants to clarify it through structured questioning. Transforms unclear requirements into precise, actionable specifications.

zettalyst

documentation

knowledge-base

0

security-checklist

Security best practices, OWASP guidelines, and vulnerability prevention checklist. (project)

hydershah

documentation

knowledge-base

0

accessibility-complaint-narrative

Parse WCAG accessibility scan reports and combine with personal accessibility testing experiences to generate compelling, evidence-based violation narratives that cite both user impact and technical violations. Generates plain-text complaint narratives suitable for demand letters, legal notices, and accessibility audit reports.

jefdiesel

documentation

knowledge-base

0

product-manager

Organizing features and complex work into manageable/logical tasks

aamini-stack

documentation

knowledge-base

0

clarification-phase

Executes the /clarify phase using AskUserQuestion tool to resolve ambiguities through structured questions (≤3), prioritization, and answer integration. Use when spec.md contains [NEEDS CLARIFICATION] markers, when requirements need disambiguation, or when running /clarify command to resolve critical scope/security/UX ambiguities before planning. (project)

Sjdjdiejdrirhdkjej

documentation

knowledge-base

0

project-architecture

This skill should be used when the user asks about "namespaces", "singleton", "TileManager", "GameManager", "TokenManager", "InputManager", "data flow", "class responsibilities", "layers", "folder structure", "code organization", "design patterns", "ScriptableObject", "databases", or discusses Zero-Day Attack codebase architecture and patterns.

jwmyers

documentation

knowledge-base

0

task-writing

Write high-quality, actionable tasks that are clear, well-scoped, and contain all the information needed for successful execution. Use when breaking down implementation plans, creating issues for bug fixes or features, writing tickets for sprints, defining work items from spec requirements, converting user feedback into tasks, or creating technical debt items. Triggers include "write task", "create issue", "write ticket", "define task", "bug report", "feature request", or when creating trackable units of work.

pjordan

documentation

knowledge-base

0

role-software-engineer

Role definition for software engineer agents. Defines responsibilities, principles, required skills, and success criteria. Use to understand what it means to operate as a software engineer in this codebase.

Anveio

documentation

Page 82 / 101