'missing' 검색 결과

Use when wrangler deploys silently fail or produce wrong artifacts, secrets upload as empty strings, custom domain DNS is not resolving, route assignment broke after rename, observability/tail logs are needed, D1/KV/R2 bindings are missing, OAuth scope errors block a command, cookies on a redirect are not attaching, or the worker exceeds CPU time. Triggers: "Tenant or user not found", "Authentication error" on wrangler d1 push, secret length is 0 after upload, route returns origin not worker, "compatibility_date too old", 1101 errors, custom_domain assignment lost on script rename. NOT for AWS Lambda / Vercel Edge / Deno Deploy (different runtimes), Cloudflare Zero Trust, or R2-specific tuning.

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

Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).

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

Troubleshoot Coval OpenTelemetry trace ingestion, missing trace UI, sparse traces, bad simulation or conversation correlation, auth/org errors, oversized payloads, duplicate spans, and production debugging with Trace Search.

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

Audit an existing Coval evaluation setup for coverage, misleading scores, missing evidence, judge validation and execution risk. Read-only; use when inheriting an eval or deciding whether its results support a release decision.

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

Trial protocol for teaching AI Matrx an expert's knowledge until the platform breaks, fixing it. Use when asked to run an expertise trial, distil a person/creator/recent video into a Masterwork, or test the capture product. NOT for a known-missing feature (use build-sub-feature).

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

Lifecycle for AI Matrx agent-aware UI surfaces. Use when creating a surface in features/surfaces/manifests/, or completing or repairing one that is partial, stubbed, unregistered, missing runtime context or context menus, or not agent-wired. NOT for certifying a surface (use surface-check).

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

Run the full on-track check on a conversation, project, or keyword the owner names: find the sessions, extract exactly what he typed, dispatch independent judges who go to the live product as him and report what was missed, plan the remedy, and return one page — what he will see, what is missing, the plan. Use when told to check whether work is on track, to audit a project that has drifted, on 'run the on-track check on X', or when a long campaign is about to freeze, hand off, or claim done.

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

Next.js route metadata, per-route favicons, OpenGraph, and Twitter cards. Use when adding a route or layout, adding a favicon or social share image, auditing missing metadata, naming tab titles, or touching createRouteMetadata, createDynamicRouteMetadata, generateFaviconMetadata, or titlePrefix.

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

The universal v3 right-click menu (EditableContextMenu / NonEditableContextMenu). Use when adding a right-click menu to a surface, fixing a fake menu with no Copy or Export, a missing Download as Markdown, or a bespoke per-surface menu. NOT for an assigned rollout shard (use context-menu-rollout).

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

The quick interview that captures a Domain's or major Feature's minimal (go-live) and final vision verbatim into its VISION.md. Use when a node shows VISION MISSING, a registry domain is ratified without a vision, gap analysis lacks a go-live bar, or on /domain-vision-interview <domain>.

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

Quality review of test files and evidence — goes beyond existence, evaluates assertion coverage. ADEQUATE/INCOMPLETE/MISSING/NOT ASSESSED per story.

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

Audit assets against naming conventions, file size budgets, format standards. Finds orphaned assets, missing references.

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

Generate missing design or architecture docs from existing implementation — works backwards from code and prototypes.

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

Expert knowledge of the melosys-api Oracle database schema. Use when: (1) Writing SQL queries against the melosys database, (2) Understanding table relationships and foreign keys, (3) Debugging data issues by querying the database, (4) Understanding what data is stored where, (5) Creating or modifying Flyway migrations, (6) Mapping domain entities to database tables. Triggers: SQL against melosys DB, table/column lookup, FK relationships, "where is X stored", "what column stores X", "why is data missing", beh_resultat_id, behandlingsresultat_id, saksnummer, schema.

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

Interviews a request until no essential choice is left to guess, then hands the settled decisions on. Trigger on 'grill me', 'interview me before you build', 'stress-test this idea', 'ask me questions until it's clear', 'what am I missing before we start', or a vague plan, feature, prompt or skill where a wrong build costs more than questions. Or say grillwright (grill, record, resume, questionnaire — for someone else to answer, docs — check against glossary and ADRs). Builds nothing — prompts are promptwright's, skills skillwright's, agents agentwright's, game code slicesmith's, what a running agent may do gatewarden's, even asked as a grill.

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

Set up, resume or troubleshoot cmail custom-domain email (domain at any registrar → Cloudflare Email Routing → any inbox; optional GoDaddy automation and Gmail send-as): runs cmail setup itself, asking only for missing input, secrets or risky approvals. Don't use for mail migrations or campaigns.

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

Debug and troubleshoot WorkOS AuthKit authentication issues with Convex. Use when authentication fails, JWT validation errors occur, user identity returns null, email claims are missing, admin access checks fail, or sign in button does not work. Supports Netlify deployment.

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

Audit and harden a Convex app's authorization: identity-from-arg impersonation, missing per-document ownership checks, public queries leaking data by a client-supplied id, and writes into a parent/container the caller doesn't own. Scans for the 4 shapes, applies requireIdentity/requireOwner, verifies with tsc. TRIGGER on 'secure my app', 'audit auth/authz', 'who can access this data'. SKIP when there is no convex/ directory.

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

Decision validation and thinking frameworks for startup founders. Use when you need to pressure-test a decision, validate your next steps, think through strategic options, or sanity-check your approach. Triggers on phrases like "should I", "help me think through", "is this the right move", "validate my thinking", "what am I missing". Covers fundraising, customer development, runway management, prioritization, and crypto/web3 founder challenges.

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

Analyzes contracts and agreements for risks, unusual terms, and missing clauses

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

Run pytest tests with coverage, discover lines missing coverage, and increase coverage to 100%.

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

Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers. Triggers: "help me understand", "explain this code", "I'm stuck", "Im stuck", "I'm confused", "Im confused", "I don't understand", "I dont understand", "can you teach me", "teach me", "mentor me", "guide me", "what does this error mean", "why doesn't this work", "why does not this work", "I'm a beginner", "Im a beginner", "I'm learning", "Im learning", "I'm new to this", "Im new to this", "walk me through", "how does this work", "what's wrong with my code", "what's wrong", "can you break this down", "ELI5", "step by step", "where do I start", "what am I missing", "newbie here", "junior dev", "first time using", "how do I", "what is", "is this right", "not sure", "need help", "struggling", "show me", "help me debug", "best practice", "too complex", "overwhelmed", "lost", "debug this", "/socratic", "/hint", "/concept", "/pseudocode". Progressive clue systems, teaching techniques, and success metrics.

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

This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.

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

Guide for using the Microsoft Fluent UI Blazor component library (Microsoft.FluentUI.AspNetCore.Components NuGet package) in Blazor applications. Use this when the user is building a Blazor app with Fluent UI components, setting up the library, using FluentUI components like FluentButton, FluentDataGrid, FluentDialog, FluentToast, FluentNavMenu, FluentTextField, FluentSelect, FluentAutocomplete, FluentDesignTheme, or any component prefixed with "Fluent". Also use when troubleshooting missing providers, JS interop issues, or theming.

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