724건 · 관련도순
维护每个功能一份给人看的「需求设计文档」（docs/modules 下，一个功能一份）：待拍板置顶，按需写背景、目标、流程、布局、状态、交互细节、业务规则、召回、AI 生成（prompt）、效果、成本、系统，先图后字，只写当前设计，末尾记关键改动，附出图与上线前检查。新建、更新、同步、补充这份文档都用它，别直接手改——它有固定写法和检查。用户说「出设计文档」「PRD 太长看不懂」「把设计文档同步一下」「重拍截图」「上线前看文档跟上没有」时用；用户抱怨看不到功能现在的设计、不知道最近改了什么时也用；forge 各阶段改了规则、文案、交互、布局、阈值、prompt、模型、架构后收尾也用，哪怕用户没明说。不处理写给 AI 的 PRD/DESIGN（forge-prd、forge-design）、骨架上定布局（forge-design-lab）、改 prompt 本身（prompt-craft）、进度（forge-status）。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level abstract algebra knowledge. Use when working with groups, rings, fields, modules, Galois theory, representation theory, or algebraic structures. Also use when the user mentions 'group', 'ring', 'field', 'homomorphism', 'isomorphism', 'normal subgroup', 'quotient group', 'Sylow theorem', 'Galois theory', 'polynomial ring', 'ideal', 'module', 'vector space', or 'representation theory'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to improve architecture, consolidate tightly-coupled modules, or make a codebase more testable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conventions for Ktor Gradle modules
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
當使用者要為新客戶規劃或撰寫全新的 Brand Guideline、品牌手冊、視覺識別規範時使用。互動教練模式：一次只問一題完成 intake，全部問完後產出由知識圖譜推理驅動的 Plan 供確認，使用者確認後才 Build 並寫入 clients/ 下的 blueprint、index.yaml 與 note.md 初稿。Plan 階段以 Design Strategy 推理鏈（產業 → 品牌類型 → 商業問題 → 匹配決策卡 → 架構）運作，並引用 references/research/decision_patterns.yaml、contexts、modules、archetypes、module_graph 與 references/docs/*.profile.yaml 的證據。本 skill 亦涵蓋兩個延伸能力（見 references/）：分析既有 guideline PDF（design-guideline-researcher）、把分析升級成決策卡（design-strategy-extractor）。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing Terraform — AWS modules, resources, variables, outputs, remote state — even when the user just says 'provision this infra' or 'add an S3 bucket' without naming Terraform.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When working within any module under `modules.root_paths` from `.agent-project-settings.yml` — Laravel HMVC, Symfony DDD-lite, Node monorepo, Python src/, Go internal/, or a custom path.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing, debugging, or configuring an omp hook or extension — blocking or rewriting tool calls, redacting tool output, reshaping LLM context, registering tools/commands, or wiring modules through config.yml. Covers ExtensionAPI (current) vs HookAPI (legacy), the event catalog, discovery and load order, and disable controls. Not for Claude Code hooks (~/.claude/settings.json) or the shared harness safety guard (~/.agents/harness/hooks/).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Content] Use when a workflow step or the user asks for course material: Bloom objectives, modules, lessons, exercises and assessments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit a codebase or subsystem for architecture simplification - shallow or pass-through modules, scattered concepts, naming drift, sibling workflows that disagree, weak test seams. Use when the user asks what to simplify or restructure. Not for a narrow fix or for implementing an already chosen design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Roblox and Luau game code standards. Writes, reviews, and fixes Script, LocalScript, and ModuleScript code and game systems such as shops, DataStore saves, RemoteEvents, combat, NPCs, and UI. Use when a request involves Luau code or a Roblox Studio project, even when Roblox is never named, when a game bug is reported with no file named, and when the user asks to keep these standards active. Also covers Rojo, Argon, Azul, Script Sync, Studio MCP, and community libraries such as ProfileStore, Knit, Trove, and Fusion. Applies to requests written in any language. Not for plain Lua outside Roblox (Neovim, LOVE, Defold, other engines) or for game design with no Luau to write or review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when generating a single dense technical architecture, reference poster, or system diagram image for a software project. Produces a source-grounded bitmap diagram with topology, primitives, ingest/process flow, core logic, state scopes, tiers/modules, surfaces, runtime cards, and strict semantic color rules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safely clean regenerable clutter from a project folder by scanning for build artifacts and caches, backing up every removed path into a timestamped archive with a BACKUP.md manifest, zipping the backup to save space, and only deleting originals after explicit confirmation. Use when the user asks to clean a project directory, remove node_modules, clear build output, reclaim disk space, or tidy a repo before archiving.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for Electron desktop application implementation, local packaging, and macOS Electron installer builds in GitHub Actions. Covers secure IPC, preload and multi-process architecture, electron-builder/Forge configuration, native modules, signing/notarization setup, DMG/ZIP packaging, mounted packaged smoke, and macOS qualification evidence. For cloud releases, this Skill owns macOS build and qualification; use github-desktop-release for Windows GitHub Actions qualification and for shared artifact promotion, GitHub Release publication, resume, or authoritative readback. Do not use this Skill to build or qualify Windows installers in GitHub Actions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Act as a Senior Frontend Systems Engineer to architect interactive modules — multi-step forms, pricing calculators, faceted search, dashboards, and auth flows. Defines state machines, data flow, error handling, and React component structure. Use when designing complex UI logic for Figma Make prototypes or React implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Install npm packages in a Docker sandbox environment. Use this skill whenever you need to install, reinstall, or update node_modules inside a container where the workspace is mounted via virtiofs. Native binaries (esbuild, lightningcss, rollup) crash on virtiofs, so packages must be installed on the local ext4 filesystem and symlinked back.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Imports existing Azure resources into Terraform using Azure CLI discovery and Azure Verified Modules (AVM), mapping dependencies between resources. Use when generating IaC from a live Azure subscription or resource group, or replacing hand-written azurerm resources with AVM.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Workflow for building and modifying content management systems across WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, Adobe Experience Manager, and similar platforms. Use when working on CMS themes, plugins, apps, modules, admin panels, media uploads, content models, editors, markdown pipelines, or static export workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style). Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay, subgrid bands, 8px baseline lock, and runtime optical alignment. Triggers: "magazine spread", "grid system", "Swiss design", "editorial layout", "show the grid", "align everything to the grid".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use before writing code on anything non-trivial: a new project or feature, ambiguous or incomplete requirements, a change spanning multiple modules, an architectural decision, or work over ~30 minutes. Runs a gated Specify → Plan → Tasks → Implement workflow with human review at each phase. Skip for single-line fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Updates Azure Verified Module (AVM) references in a Bicep file to their latest versions, applying only non-breaking changes and reporting the result as a table. Use when Bicep templates pin outdated AVM versions or before an infrastructure release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds reusable Convex components with isolated tables and app-facing APIs. Use for new components, reusable backend modules, integrations, or component boundary work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.