'data write' 검색 결과

Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide resource audits. Produces curl commands or scripts. Triggers: 'cloudflare api', 'bulk dns', 'custom hostname', 'email routing', 'cache purge', 'waf rule', 'd1 query', 'r2 bucket', 'kv bulk', 'vectorize query', 'audit resources', 'fleet operation'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate project documentation from codebase analysis — ARCHITECTURE.md, API_ENDPOINTS.md, DATABASE_SCHEMA.md. Reads source code, schema files, routes, and config to produce accurate, structured docs. Use when starting a project, onboarding contributors, or when docs are missing or stale. Triggers: 'generate docs', 'document architecture', 'create api docs', 'document schema', 'project documentation', 'write architecture doc'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Python visual creation and matplotlib/seaborn patterns for PBIR reports. Automatically invoke when the user mentions "Python visual", "matplotlib in Power BI", "seaborn in Power BI", "pythonVisual", or asks to "create a Python visual", "add a matplotlib chart", "write a Python visual script".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

R visual creation and ggplot2 patterns for PBIR reports. Automatically invoke when the user mentions "R visual", "ggplot2", "ggplot in Power BI", or asks to "create an R visual", "add an R chart", "write an R visual script", "inject an R script into Power BI".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host is bound to the source env, provisions a new **Platform Host** (recommended, idempotent) or a **Custom Host** via the BAP env-create API with the `D365_ProjectHost` template, or guides the user through PPAC install / `New custom host` (manual fallbacks). Polls lifecycle operations, verifies the host responds to Pipelines API calls, writes a host-check artifact other ALM skills consume. Use when asked to: "set up pipelines host", "ensure pipelines host", "no pipelines host", "install pipelines", "create pipelines host", "provision platform host", "provision custom host". Also invoked transparently by /power-pages:setup-pipeline when its host discovery step finds nothing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement Terraform provider ephemeral resources with the Plugin Framework: the Open/Renew/Close lifecycle, ephemeral schema design, registration via EphemeralResources, renewal for expiring credentials, and how ephemeral values flow into write-only attributes and provider configuration. Use when adding an ephemeral resource, exposing secrets/tokens/certificates that must never persist in state or plan, deciding between an ephemeral resource and a data source, or wiring short-lived credentials from one provider into another.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a white-labeled report for one client from tracked data. All clients → agency-dashboard. "prepare the monthly client report"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Panel health assessment, firm exit management, coverage gap analysis, and panel refresh brief for in-house legal ops teams. Produce an annual Panel Health Report synthesising scorecard data, billing compliance, and step-out patterns into per-firm recommendations — Retain, Watch, Improvement Plan, or Exit Review. Produce a firm exit pack: formal exit notice with active matter transition plan, plus an internal exit record. Identify practice area, geographic, or tier gaps and produce a structured Coverage Gap Report with remediation options. Produce a Panel Refresh Brief as a scoped input to the RFP process. Trigger on: 'review our panel', 'annual panel review', 'is our panel working', 'which firms should we exit', 'write the exit notice', 'coverage gap', 'we don't have anyone for restructuring', 'refresh the panel', 'panel rationalisation', 'too many firms', 'step-out problem', 'do we have the right firms'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bevy 0.20 dialogue data: line tables in a resource, the current line index on a component, and choice flags filtered before the write. Use when lines or choices advance. Keywords: Bevy, dialogue, line index, choices, ECS.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evidence-first development — surround the implementation with an executable spec and a gauntlet of constraints (tests, types, coverage, mutation) so line-by-line review becomes optional. Use when the user explicitly asks for high-assurance or evidence-first work ("reliable", "TDD", "prove it works", "I won't read the code"), or when the change touches high-stakes domains (money, auth, data loss, concurrency, public API). For routine changes where the user just wants normal tests, write good tests directly instead of invoking this loop.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Monthly, and on its first run it is the whole setup, launched by hand. It discovers what the member actually runs by walking their code roots and reading the registrar, the host, and the hosted database, then writes the inventory, the domains file, the starting budgets, and the opening safe fix rules, seeds the board, builds the dashboard, and registers one scheduled job per routine. It creates no account, buys nothing, and provisions nothing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Weekdays, browser only when a source refuses to be fetched. Works the single card the standup marked next: reads the shared publishing standard and the card's specification, pulls the live result set for the primary keyword, reads the pages currently ranking, writes the body, the metadata, the internal links and the outbound authority links, generates and compresses a hero, and leaves a complete draft folder with one ready line. It never opens a publishing surface, never touches a live property, and never touches a credential.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a leader evaluates a marketing TEAM MEMBER using data — a KPI scorecard by role, strengths with real examples, areas to improve stated as observable behavior, a 30 and 90 day development plan, and a 1-5 rating rubric. Trigger on 'performance review for my marketer', 'evaluate a team member', 'monthly 1:1 review', 'feedback for my content writer', 'development plan for an employee', 'is this person underperforming'. Also use when the user is unhappy with someone and cannot articulate why. Not for — evaluating a campaign rather than a person, see `63-campaign-retrospective-global`; reviewing one piece of output, see `62-marketing-review-global`; scoring an external vendor, see `67-agency-vendor-brief-global`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user needs to WRITE a marketing report someone else will read — a one-page weekly for a CEO, a full monthly, or a quarterly strategy report with TL;DR, results versus target, insight, decisions needed, and next actions with owners. Trigger on 'marketing report', 'monthly report', 'weekly update for my boss', 'report for the client', 'quarterly summary', 'turn these numbers into a report'. Also use when the user says a stakeholder is asking how marketing is doing. Not for — diagnosing why the numbers are bad, see `03-performance-eval-global`; turning a raw export into insight, see `13-data-analysis-global`; a closed campaign retrospective, see `63-campaign-retrospective-global`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write maintainable Python with small functions, explicit boundaries, guard clauses, and readable state flow. Use when refactoring Python services, helpers, modules, or async logic for clarity—not generic test writing, tooling setup, or database transaction implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write Unit and E2E tests with Jest, mocking strategies, and database isolation in NestJS. Use when writing NestJS unit tests, E2E tests with supertest, or mock providers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write performant Eloquent queries with eager loading, reusable scopes, and strict lazy-loading prevention in Laravel. Use when defining model relationships, creating query scopes, or processing large datasets with chunk/cursor.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build dual-write notification services with database persistence and FCM push delivery in NestJS. Use when creating notification entities, sending push via FCM, or implementing in-app notification feeds.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write Android unit, Compose UI, and Hilt-integrated tests. Use when designing test behavior with MockK or coroutine test utilities; defer database/WorkManager-specific recipes to the owning feature skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Meta-skill for designing orchestrator+phases structured workflow skills. Creates SKILL.md coordinator with progressive phase loading, TodoWrite patterns, and data flow. Triggers on "design workflow skill", "create workflow skill", "workflow skill designer".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Rewrite and audit SEO page titles, title tags, MDX frontmatter titles, H1 alignment, and bulk title improvements. Use when the user mentions titles, title tags, SERP titles, metadata titles, SEO titles, CTR, truncation, or asks to improve titles across pages.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.