25건 · 관련도순
Turn a founder’s business vision into linked Markdown files through a phased interview covering strategy, finance, sales, operations, and governance. Build a company knowledge bundle that people and AI agents can read, with progress tracking and decision history.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create production-ready Grafana dashboards with reusable panels, template variables, annotations, and provisioning for version-controlled dashboard deployment. Use when creating visual representations of Prometheus, Loki, or other data source metrics, building operational dashboards for SRE teams, migrating from manual dashboard creation to version-controlled provisioning, or establishing executive-level SLO compliance reporting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Delegate a feature, bug fix, or substantial code change and carry it through implementation, review, and verification. Start from a task description or issue link, with options for the workflow route and review depth.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Comprehensive markdown and Mermaid diagram writing skill that establishes text-based diagrams as the DEFAULT documentation standard. Use this skill when creating ANY scientific document, report, analysis, or visualization — it ensures all outputs are in version-controlled, token-efficient markdown with embedded Mermaid diagrams as the source of truth, with clear pathways to downstream Python or AI-generated images. Includes full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates ready to use.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use `design-system-governance` (design-systems).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define how the system evolves — contribution model, versioning, deprecation, and change management. Use when multiple teams contribute. For driving uptake use `design-system-adoption` (designer-toolkit); for design file history use `version-control-strategy` (design-ops).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Author SVG figures for Grida docs — diff-able, version-controlled vector diagrams embedded in doc pages instead of screenshots. Provides reusable primitives (selection chrome, size badges, anchor pins, resize cursors, click ripples), color/typography tokens, a starter template, and finished examples to crib from. Canvas user docs (docs/editor/) are the first consumer; the kit is meant to generalize to any product's docs. Use when drawing diagrams that explain UI behaviour — gestures, alignment, before/after states — that a screenshot alone can't capture. Trigger phrases: "svg diagram", "draw a figure", "visual for docs", "explain this gesture visually", "before/after diagram".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establishes ongoing RoPA maintenance processes including update triggers, change management integration, version control, stakeholder review cycles, and completeness verification procedures. Activate for RoPA updates, record maintenance, change management, version history, review scheduling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides the periodic DPIA review lifecycle including trigger identification for regulatory changes, new data categories, technology changes, and breach incidents. Covers version control, stakeholder sign-off procedures, and DPIA register management per Art. 35(11). Keywords: DPIA review, PIA update, review cadence, version control, Art. 35(11), periodic review, trigger events, stakeholder sign-off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage Git repositories and collaborative workflows — branching strategies, commit hygiene, conflict resolution, pull requests, hooks, and .gitignore management. Use when the user requests version control or provides relevant inputs for this workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Git is deceptively simple to learn and incredibly hard to master. The difference between a team that ships and a team that fights merge conflicts all day comes down to workflow discipline. Your git history is documentation - make it tell a story future you can understand. This skill covers branching strategies (trunk-based, gitflow, GitHub flow), commit hygiene, merge vs rebase, conflict resolution, and the commands you actually need. Key insight: most git disasters come from not understanding what you're about to do. 2025 lesson: Trunk-based development with short-lived branches has won. Long-lived feature branches are a code smell. If a branch lives more than a few days, something is wrong with your architecture or process. Use when "git workflow, branching strategy, git merge, git rebase, merge conflict, git commit, trunk-based, gitflow, git history, git revert, git reset, git, version-control, workflow, branching, commits, merge, rebase, collaboration" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define version control strategies for design files, components, and libraries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns implementation work into working code, reviewed and verified. Use when the user delegates a feature, story, bug fix, or meaningful change; a bare story or issue link counts. Skip obvious, low-risk mechanical maintenance such as small ignore-file, typo-only, formatting-only, or configuration-hygiene edits. Explicit BMAD requests always qualify. Do not volunteer for user-directed interactive edits or version-control operations that only record existing work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resolve merge and rebase conflicts with safe recovery strategies. Covers identifying conflict sources, reading conflict markers, choosing resolution strategies, and continuing or aborting operations safely. Use when a git merge, rebase, cherry-pick, or stash pop reports conflicts, when a git pull results in conflicting changes, or when you need to safely abort and restart a failed merge or rebase operation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement secure secrets management in Kubernetes using SealedSecrets for GitOps, External Secrets Operator for cloud secret managers, and rotation strategies. Handle TLS certificates, API keys, and credentials with encryption at rest and RBAC controls. Use when storing sensitive configuration for Kubernetes applications, implementing GitOps where secrets must be version-controlled, integrating with AWS Secrets Manager or Azure Key Vault, rotating credentials without downtime, or migrating from plaintext Secrets to encrypted solutions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stage, commit, and amend changes with conventional commit messages. Covers reviewing changes, selective staging, writing descriptive commit messages using HEREDOC format, and verifying commit history. Use when saving a logical unit of work to version control, creating a commit with a conventional message, amending the most recent commit, or reviewing staged changes before committing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure a Git repository with proper .gitignore, branch strategy, commit conventions, hooks, and remote setup. Covers initial setup and common patterns for R, Node.js, and Python projects. Use when initializing version control for a new project, adding a .gitignore for a specific language or framework, setting up branch protection and conventions, or configuring commit hooks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a Document Management Specialist — designing or auditing a records retention schedule, planning a content migration between DMS platforms (SharePoint, OpenText, Documentum, M-Files), reconciling migrated vs. source document counts, resolving a version-control or legal-hold conflict, or scoping a defensible-disposal (ROT) cleanup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Git branching strategies, conflict resolution, rebase workflows, monorepo patterns, and advanced operations like cherry-pick, bisect, and reflog recovery. Activate on "git", "branching strategy", "merge conflict", "rebase", "cherry-pick", "monorepo git", "git bisect", "git reflog", "squash commits". NOT for GitHub Actions CI/CD (use github-actions-pipeline-builder), GitHub API/webhooks, or PR review processes (use code-review-checklist).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, edit, review, preview, and export polished Marp Markdown slide decks in Canvas Notebook. Use when the user wants Markdown-native presentations, `.marp.md` or `.slides.md` files, version-controlled decks, Marp PDF/image/PPTX/HTML export, speaker notes, dashboard-style slides, data cards, or better looking decks that should remain close to plain text.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Company Architect: builds a business from scratch as an OKF (Open Knowledge Format) bundle — a tree of version-controllable .md files with frontmatter type, links forming a graph, and reserved index.md/log.md, readable by humans and agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Git workflows, branching strategies, collaboration, and code management
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Essential Git patterns for effective version control, eliminating redundant Git guidance per agent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When creating, updating, and merging code in a collaborative version control environment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.