116건 · 관련도순
Cascade the same edit pattern across N files safely. Use when applying the same refactor to multiple files (e.g. swap import paths across 11 scripts, rename a symbol, migrate a call signature). Detects the common-shape-across-files situation and turns an N-file cascade into a planned audit → apply → verify workflow instead of N sequential manual edits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Framework-agnostic SQLAlchemy 2.0 core shared by fastapi-plugin and flask-plugin: declarative mapped classes with Mapped/mapped_column, column type selection, relationships with explicit lazy loading and cascades, 2.0-style select() querying, transaction/flush discipline, and Alembic-agnostic migration metadata rules. Framework plugins layer their delta skills (async sessions for FastAPI, Flask-SQLAlchemy integration for Flask) on top of this skill. Use this skill to: - Write SQLAlchemy 2.0 declarative models with Mapped[T] annotations and mapped_column(). - Pick correct column types (String(N), Numeric, DateTime(timezone=True), Uuid, Enum). - Define relationships with explicit lazy loading strategy and cascade settings. - Query with 2.0-style select() statements and manage flush vs commit boundaries. - Keep model metadata visible to Alembic autogenerate. Do NOT use this skill for: - FastAPI async engine/session lifecycle — see fastapi-plugin:sqlalchemy-patterns. - Flask-SQLAlchemy extension setup and Flask-Migrate — see flask-plugin:sqlalchemy-patterns. - Python idioms — see python-foundation:python-conventions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cascade approved evolution changes through downstream layers, assess impact, run consistency checks, and write evolution audit record
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
claude-org-runtime のリリース (release-* タスク / vX.Y.Z タグ発行) を、 同 PyPI 発行を受ける claude-org-ja 側の expectation 同期と ペアで設計・委譲・完了させるためのワークフロー。 DEFAULT_NOTIFY 値・classifier vocabulary・role_configs_schema (ja 側ミラー: org_extension_schema)・attention.example.json テンプレ等が 変わるリリースで発動する。 CI cascade を予測・予防し、ja-side の red を回避することを目的とする。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find background music, sound effects, images, and icons from existing assets, shared caches, or HeyGen. Save selected files locally and register them in an inventory, giving the agent a usable file path.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and review company procedures and operational guides, then audit internal wikis for outdated pages, missing owners, broken connections, and inconsistent terminology. Produce structured drafts, step checks, and a prioritized list of documents to improve.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare employee communications for organizational changes, tool rollouts, and policy updates. Create announcements, audience-specific FAQs, manager talking points, and a communication calendar, while checking tone, channel choices, and sequencing against the change's impact.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Extract text from local or downloaded PDFs using a sequence of tools. Try file reading, then pdftotext before a Python fallback, check readability, and document failures while clearly separating extracted content from knowledge-based additions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Keep document creation moving when web searches and page retrieval repeatedly fail. The skill preserves the original task, uses the model’s existing knowledge, and clearly identifies information that could not be checked against external sources.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check whether a single tool outage, invalid input, or repeated retry can disrupt an entire agent workflow. Use dialogue tests to identify spreading errors, missing fallbacks, and uncontrolled retries, then document confirmed findings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Share shopping carts, themes, and other state across Blazor components that are not directly connected. Choose cascading values or shared services, notify components when data changes, and account for rendering boundaries and service lifetimes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create complete specs (requirements, design, tasks) for all features in roadmap.md sequentially by dependency wave in Cascade.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement approved tasks in Cascade using TDD and inline review. Runs all pending tasks or selected tasks in the main context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, refine, or fix NVIDIA voice agents (Cascaded or Omni) with Pipecat or LiveKit. Use when building, scaffolding, or iterating on a real-time voice-agent pipeline, including speech (ASR/TTS) customization and cloud or local deployment. Not for offline/batch speech-to-text, text-only chat or RAG, or generic Docker or CUDA work unrelated to a voice agent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Web scraping with anti-bot bypass, content extraction, undocumented APIs and poison pill detection. Use when extracting content from websites, handling paywalls, implementing scraping cascades or processing social media. Covers requests, trafilatura, Playwright with stealth mode, yt-dlp and instaloader patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
KQL language expertise for writing correct, efficient Kusto Query Language queries. Covers syntax gotchas, join patterns, dynamic types, datetime pitfalls, regex patterns, serialization, memory management, result-size discipline, and advanced functions (geo, vector, graph). USE THIS SKILL whenever writing, debugging, or reviewing KQL queries — even simple ones — because the gotchas section prevents the most common errors that waste tool calls and cause expensive retry cascades. Trigger on: KQL, Kusto, ADX, Azure Data Explorer, Fabric Real-Time Intelligence, EventHouse, Log Analytics, log analysis, data exploration, time series, anomaly detection, summarize, where clause, join, extend, project, let statement, parse operator, extract function, any mention of pipe-forward query syntax.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "check if our surfaces have drifted from the canon", "watch for competitor repositioning", or "define when we should reposition"; produces a drift report — self-drift per flagship surface vs the narrative-registry canon over time (via wayback.py, change history Measured with as-of dates), competitor-repositioning alerts, an explicit repositioning-trigger condition set, and a D1/W1/M1 message-shift retro (intended vs actual pull-through, evidence-labeled) — feeding the TALE L drift-audit sub-items and the narrative-whiplash guardrail fact base. Not for the first-time consistency check before a surface ships — use narrative-cascade-planner; not for computing the TALE profile result or running the vetoes — use narrative-quality-auditor; not for echo-rate / AI-answer resonance measurement — use narrative-resonance-monitor. 自漂移监测/竞品重定位告警/重定位触发/叙事漂移复盘
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline's creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
PM2 process management, backend/frontend cascade execution, parallel worktree builds, and cross-service integration testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a puzzle game: grid/board state, move input, rule-based resolution (match-3 cascades, sokoban pushes, tile logic), scoring, and undo. Use for a match-3, sokoban, or grid-logic puzzle.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research <topic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.