Agent A5 - Paradigm & Worldview Advisor - Philosophical foundations for research design. Covers ontology, epistemology, axiology, and methodology alignment. Use when: establishing philosophical foundations, justifying methodological choices, writing positionality statements Triggers: paradigm, 패러다임, ontology, epistemology, worldview, 세계관, philosophical foundations, 철학적 기초
日本語の概要は準備中です。原文の説明を表示しています。
brycewang-stanford/Auto-Empirical-Research-Skills☆ 4,6272026年10月12日 更新
Agent C3 - Mixed Methods Design Consultant Comprehensive mixed methods research design specialist covering sequential, concurrent, embedded, and multiphase designs with Morse notation. Core Capabilities: - Sequential Explanatory (QUAN → qual): Explain quantitative results - Sequential Exploratory (QUAL → quan): Develop instruments - Convergent Parallel (QUAN + QUAL): Comprehensive understanding - Embedded (QUAN(qual)): Secondary strand addresses different question - Multiphase: Long-term projects with iterative phases - Morse notation interpretation and recommendation
日本語の概要は準備中です。原文の説明を表示しています。
brycewang-stanford/Auto-Empirical-Research-Skills☆ 4,6272026年10月12日 更新
VS-Enhanced Qualitative Design Consultant with Ethnography & Action Research Enhanced VS 3-Phase process: Avoids overused phenomenology, proposes context-optimal qualitative strategies Absorbed H1 (Ethnographic Research Advisor) and H2 (Action Research Facilitator) capabilities Use when: selecting qualitative research design, planning phenomenology/grounded theory/case study/ethnography/action research Triggers: phenomenology, 현상학, grounded theory, 근거이론, case study, 사례연구, narrative inquiry, ethnography, 민족지, action research, 실행연구, qualitative design
日本語の概要は準備中です。原文の説明を表示しています。
brycewang-stanford/Auto-Empirical-Research-Skills☆ 4,6272026年10月12日 更新
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
日本語の概要は準備中です。原文の説明を表示しています。
brycewang-stanford/Auto-Empirical-Research-Skills☆ 4,6272026年10月12日 更新
VS-Enhanced Quantitative Design Consultant with Materials & Sampling Enhanced VS 3-Phase process: Avoids obvious experimental designs, proposes context-optimal quantitative strategies Absorbed C4 (Experimental Materials Developer) and D1 (Sampling Strategy Advisor) capabilities Use when: selecting quantitative research design, planning experimental/survey methodology, power analysis, developing materials, sampling Triggers: RCT, quasi-experimental, experimental design, survey design, power analysis, sample size, factorial design, materials, stimuli, sampling strategy
日本語の概要は準備中です。原文の説明を表示しています。
brycewang-stanford/Auto-Empirical-Research-Skills☆ 4,6272026年10月12日 更新
Use only when creating new registrable ML components that require Factory or Registry patterns.
日本語の概要は準備中です。原文の説明を表示しています。
brycewang-stanford/Auto-Empirical-Research-Skills☆ 4,6272026年10月12日 更新
Publication Specialist - Writing, Review, Pre-registration & Quality Assurance Light VS applied: Avoids template-based writing + audience-specific message design Absorbed G3 (Peer Review Strategist), G4 (Pre-registration Composer), F1-F3 (Quality functions) capabilities Use when: writing abstracts, creating summaries, peer review response, pre-registration, reporting checklists, reproducibility Triggers: abstract, plain language, press release, summary, communication, peer review, revision, pre-registration, OSF, PRISMA, CONSORT, reproducibility
日本語の概要は準備中です。原文の説明を表示しています。
brycewang-stanford/Auto-Empirical-Research-Skills☆ 4,6272026年10月12日 更新
This skill covers applied microeconomic empirical methods and research design. Use when the user is selecting an identification strategy, comparing estimators, running diagnostics, designing a research study, or evaluating an empirical strategy. Triggers on "which method", "what estimator", "how to choose", "method comparison", "empirical strategy", "research design", "applied micro", "identification strategy", "power analysis", "design-based", "model-based", "minimum detectable effect", "specification".
日本語の概要は準備中です。原文の説明を表示しています。
brycewang-stanford/Auto-Empirical-Research-Skills☆ 4,6272026年10月12日 更新
Generate testable hypotheses. Formulate from observations, design experiments, explore competing explanations, develop predictions, propose mechanisms, for scientific inquiry across domains.
日本語の概要は準備中です。原文の説明を表示しています。
brycewang-stanford/Auto-Empirical-Research-Skills☆ 4,6272026年10月12日 更新
Open a user-provided URL in the host's built-in browser and use the page's MCP or WebMCP tools before browser UI automation for app communication or edits.
日本語の概要は準備中です。原文の説明を表示しています。
BuilderIO/skills☆ 4,5832026年10月9日 更新
Open and collaboratively edit a running local app in Design, with shared fallback previews and source handoff. Use when the user asks to inspect, share, or edit a real local app in Design.
日本語の概要は準備中です。原文の説明を表示しています。
BuilderIO/skills☆ 4,5832026年10月9日 更新
Turns a thread, skill, spreadsheet, or Claude/ChatGPT project into a polished, visual Agent-Native app: populated domain screens with the in-app agent working behind contextual controls. Use when a user invokes `/turn-into-app`, or asks to turn a workflow, skill, spreadsheet, or project into an app, UI, workbench, or dashboard, including from Claude or ChatGPT on the web.
日本語の概要は準備中です。原文の説明を表示しています。
BuilderIO/skills☆ 4,5832026年10月9日 更新
Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.
日本語の概要は準備中です。原文の説明を表示しています。
BuilderIO/skills☆ 4,5832026年10月9日 更新
How to work in a Software Lifecycle project (the `software-lifecycle` starter pack): proposals → decisions → specs → postmortems, plus guides. Read when the project has these folders, or when asked how this project is organized. Carries the doc lifecycle, status flows, and per-folder agent behaviors so that guidance does not live inside template bodies or folder descriptions. The five workflows — frame a proposal, write a spec, record a decision, write a postmortem, review a design — each ship as their own sibling skill in this pack. Complements the platform `open-knowledge` skill; does not replace it.
日本語の概要は準備中です。原文の説明を表示しています。
inkeep/open-knowledge☆ 4,5782026年10月15日 更新
Records an architecture decision as a Nygard/MADR-shaped ADR under decisions/ — capturing the context that forced the choice, the options weighed, the decision itself, and its consequences in both directions, plus the supersedes chain that keeps a decision log honest. Read when asked to record an architecture decision, write an ADR, log the decision we made, document why we chose X over Y, capture this decision for the record, or supersede an old decision with a new one. Do NOT read to frame a proposal or explore an idea not yet decided (frame-a-proposal), to write a spec or implementation plan (write-a-spec), to write an incident postmortem (write-a-postmortem), or to judge whether a design is sound (review-a-design). This skill records a decision already made; it does not make one.
日本語の概要は準備中です。原文の説明を表示しています。
inkeep/open-knowledge☆ 4,5782026年10月15日 更新
Write a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident and wants it documented. Do NOT read to frame a proposal (use frame-a-proposal), write a spec (use write-a-spec), record a decision (use record-a-decision), or review a design (use review-a-design) — a postmortem documents an incident that already happened, it does not propose, specify, decide, or critique future work.
日本語の概要は準備中です。原文の説明を表示しています。
inkeep/open-knowledge☆ 4,5782026年10月15日 更新
Reviews whether a design is SOUND — solving the right problem, derived from its stated goals and constraints — and emits ranked, evidence-backed findings, not edits. Read when asked to 'review this design', 'is this design sound', 'pressure-test this proposal', 'do a design review', 'does this solve the right problem', 'poke holes in this spec', 'should we build this', or to critique a proposal / spec / ADR / architecture or product decision. Do NOT read when the user wants to AUTHOR one of these — routing a new proposal is frame-a-proposal, a spec is write-a-spec, a decision record is record-a-decision, a postmortem is write-a-postmortem. Do NOT read for code review of a diff, or to fact-check individual claims (that is a correctness pass, a different job).
日本語の概要は準備中です。原文の説明を表示しています。
inkeep/open-knowledge☆ 4,5782026年10月15日 更新
Domain-Driven Design architecture for claude-flow v3. Implements modular, bounded context architecture with clean separation of concerns and microkernel pattern.
日本語の概要は準備中です。原文の説明を表示しています。
ruvnet/RuVector☆ 4,5662026年10月14日 更新
Add descriptions for new models from the HuggingFace router to chat-ui configuration. Use when new models are released on the router and need descriptions added to prod.yaml and dev.yaml. Triggers on requests like "add new model descriptions", "update models from router", "sync models", or when explicitly invoking /add-model-descriptions.
日本語の概要は準備中です。原文の説明を表示しています。
ruvnet/RuVector☆ 4,5662026年10月14日 更新
为 CC GUI 桌面客户端创建、修改、迭代插件(Tier-0 声明式 CSS/JSON,或 Tier-1 单文件 ESM)。当用户要"做一个插件 / 给 CC GUI 加个功能 / 改输入框或界面样式 / 加设置页、侧边栏或状态栏入口 / 加面板页签或命令面板命令 / 把某套工作流包装成插件 / 改一下我做过的那个插件",或提到 ccgui 插件、插件目录、从本地目录安装插件时使用。
日本語の概要は準備中です。原文の説明を表示しています。
zhukunpenglinyutong/desktop-cc-gui☆ 4,4792026年10月14日 更新
Parallel divergent ideation for coding agents. Spawns N isolated branches under different cognitive frames (regulator, biology, speedrunner, 10-year-old, $0 budget), scores, clusters, prunes traps, and deepens top survivors. Use on /adhd, "ADHD mode", brainstorm/ideate intents, or open-ended design, architecture, naming, API/SDK surface, and fuzzy-debugging decisions. Skip for syntax, lookups, bugs with known root cause, or closed phrasing ("quick", "standard", "canonical", "textbook"). Full pre-flight gate is in the skill body.
日本語の概要は準備中です。原文の説明を表示しています。
UditAkhourii/adhd☆ 4,4182026年10月6日 更新
Create polished design artifacts as self-contained HTML: UI mockups, interactive prototypes, wireframes, landing pages, dashboards, app screens, mobile apps, slide decks (a.k.a. PPT / PowerPoint presentations), documents and résumés, animations, 3D objects, research reports, HTML email, diagrams, fliers, and visual explorations. Use whenever the user asks to design, mock up, prototype, wireframe, visualize, explore, or make a PPT/deck for an interface, product screen, user flow, content layout, visual artifact, or pitch/deck concept, even if they do not say "design". Also use to export a deck built with this skill to PowerPoint (PPT/PPTX) — but only decks authored here (deck-stage / this skill's slide-structured HTML), NOT arbitrary HTML, so confirm the target is such a deck first. Also use for setting up, importing, or authoring reusable design systems, UI kits, brand tokens, or component libraries. Harness-agnostic for Claude Code, Cursor, Codex Agent, and similar file-capable agents.
日本語の概要は準備中です。原文の説明を表示しています。
JimLiu/baoyu-design☆ 4,3802026年9月23日 更新
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
日本語の概要は準備中です。原文の説明を表示しています。
get-bb/bb☆ 4,3032026年10月14日 更新
Create or change BB plugins and Plugin SDK extensions, including CLI commands, agent tools, providers, and UI surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
get-bb/bb☆ 4,3032026年10月14日 更新