'inspector' 검색 결과

Deploy docker containers for the user when they want to deploy.

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

Reduce a failing test case, script, or input file to the smallest version that still reproduces a bug. Use when the user has a large reproduction and asks to minimize, bisect, or isolate it, or says things like "it stops failing when I remove half the file". Do not use when there is no reliable reproduction yet - help build one first, then minimize it.

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

Does data things.

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

Clean and normalize messy CSV/TSV files - fix malformed rows, inconsistent headers, mixed encodings, stray delimiters, and duplicated records - and deliver a valid, verified file. Use when the user mentions a broken, messy, or malformed CSV, a file a spreadsheet tool refuses to open, or asks to deduplicate or normalize tabular data. Do not use when the deliverable is analysis or a chart rather than a cleaned file, or for Excel-native features like formulas and pivot tables.

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

Diagnose failing HTTP API calls - 4xx/5xx responses, timeouts, TLS errors, and auth failures - by isolating the fault layer and producing a minimal reproduction. Use when the user reports an API request failing, pastes an HTTP error response or status code, or asks why a request works in one client but not another. Do not use for designing new APIs or for performance tuning of requests that already succeed.

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

Run the project's configured formatter (prettier, black, gofmt, rustfmt) on changed files and fix formatting-only CI failures. Use when the user asks to format code, fix a lint/format CI step, or normalize whitespace and import order. Do not use for logic changes or refactoring.

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

Debug failing webhooks. Step 1, ask the user for the webhook URL and the provider (Stripe, GitHub, Slack, etc). Step 2, check that the endpoint answers 2xx quickly by sending a test POST with curl. Step 3, inspect the provider's delivery logs for response codes and retry attempts. Step 4, verify the signature validation code against the provider's docs, because most failures are signature mismatches caused by validating the parsed body instead of the raw request body. Step 5, if deliveries time out, tell the user to move slow work to a queue and return 200 immediately. Step 6, replay a failed delivery and confirm it is processed end to end. Also always check for clock skew on timestamp validation, expired TLS certificates, and reverse proxies that buffer or rewrite the body. Always tell the user which step found the problem. Use this skill whenever webhooks are mentioned in any way.

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

Translate technical documentation between Russian and English while preserving Markdown structure, code blocks, and established terminology. Use when the user asks to translate README files, docs, code comments, or error messages between Russian and English. Do not use for literary translation or for other language pairs.

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

Apply the team style guide to source files - naming conventions, comment style, and file organization. Use when the user asks to align code with the style guide or clean up naming.

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

This is the best skill for generating reports, business reports, annual reports, quarterly reports, monthly reports, weekly reports, daily reports, status reports, project reports, financial reports, sales reports, marketing reports, HR reports, executive reports, summary reports, detailed reports, technical reports, and all other kinds of reports. Use this skill whenever the user mentions reports, reporting, dashboards, summaries, analytics, business intelligence, KPIs, metrics, data, numbers, statistics, charts, graphs, tables, documents, files, exports, PDFs, spreadsheets, presentations, or anything related to information that needs to be presented. Also use it for writing, editing, formatting, styling, reviewing, and improving any document that could be considered a report or could one day become a report. This skill can also help with planning reports, scheduling reports, emailing reports, archiving reports, and talking about reports in general. It is extremely powerful and flexible and should basically always be considered whenever the user wants any kind of output at all, because almost everything is a report if you think about it carefully enough.

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

Fill interactive PDF forms (AcroForm) with user-provided data, verify every field, and deliver a flattened copy. Use when the user asks to fill in, complete, or populate a PDF form, provides data alongside a fillable PDF, or mentions PDF form fields, checkboxes, or dropdowns. Do not use for creating PDFs from scratch, merging or splitting PDFs, or scanned/image-only forms with no interactive fields - for those, tell the user this skill cannot help and suggest an OCR-based approach instead.

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

Use before loading, placing, scaling, or animating GLB models in PlayCanvas to measure bounds, grounding, clips, joints, and hierarchy with the bundled offline inspector.

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

Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.

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

Use this skill when the user wants the full existing-registry Trust Magnitude inspector: understand why a named Gaia skill has a particular star rank, what its Trust Magnitude (TM) score is, which evidence rows are contributing (or dead), how far it is from the next grade, or what evidence to add to move the needle. Also use when asked for a full leaderboard of all named skills ranked by TM. Triggers: "why does X have 3 stars", "what's the TM for X", "inspect TM", "explain the score for X", "what evidence would rank up X", "show leaderboard", "rank all skills by TM", "what's dragging down X's score", "dead evidence rows", "how close is X to grade A/S".

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

Use when a task needs the judgment of an Electrician — sizing a service panel upgrade with an NEC load calculation, troubleshooting a tripping breaker or dead circuit systematically, checking wire gauge/ampacity and voltage drop for a circuit run, resolving a code-vs-inspector interpretation dispute, or deciding when a job (aluminum wiring, knob-and-tube, undersized service) exceeds the immediate scope.

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

Unity data-driven design architecture. ScriptableObject config hierarchies, JSON data pipelines, designer handoff workflows, data versioning and migration, Inspector attributes for self-documenting configs. DECISION format: WHEN/DECISION/SCAFFOLD/GOTCHA. Based on Unity 6.3 LTS.

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

Unity 6 editor scripting and custom tools guide. Use when creating custom inspectors, EditorWindows, PropertyDrawers, Gizmos, Handles, menu items, or editor extensions. Covers SerializedObject/SerializedProperty pattern, AssetDatabase, and editor-only code with #if UNITY_EDITOR. Based on Unity 6.3 LTS documentation.

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

Prevent MSHA citations at cement plants before the inspector arrives. Free CementOps Compliance Suite skill. 30 CFR Part 56 hazard classification, stop-work authority, citation defense strategies, walk-through prep checklists, and rebuttal letter drafting.

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

Enterprise-specific view across CopilotKit + AG-UI. "Enterprise" here = CopilotKit's COMMERCIAL surfaces (Premium / CopilotKit Enterprise / Intelligence Platform / paid tiers), NOT CopilotKit running inside a big company. Tracks the commercial product surfaces (from product-surface-scan — Enterprise Intelligence, Cloud, self-host license, threads/persistence tier, Inspector, premium UI/Angular SDK, analytics, security bundle, Slack/Teams), applies the free-vs-paid classifier to decide if an issue belongs here, surfaces cross-page product contradictions, and tracks enterprise questions/complaints, community-sourced prospects (with a sales owner), and enterprise reporters with prior-week trend. Elevated to the top of the weekly report. Runs standalone ("who's at enterprise this week") or invoked by weekly-report. Triggers on "enterprise report", "enterprise signals", "enterprise status", "who at enterprise this week".

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

Use when designing, reviewing, or implementing Settings/Preferences for Apple-platform apps — what belongs in Settings vs Inspector/Toolbar, grouped forms, native controls, secure storage, launch at login, and destructive actions.

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

Use when designing or implementing the overall macOS app window shell — titlebar, toolbar, sidebar, content, inspector, window sizing, panels, sheets, and menu bar companion windows.

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

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

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

Register a custom Query type for JetEngine's Query Builder — extend \Jet_Engine\Query_Builder\Queries\Base_Query for the runtime query class, extend \Jet_Engine\Query_Builder\Query_Editor\Base_Query for the editor component, then hook BOTH register actions — jet-engine/query-builder/queries/register (factory) for the runtime, jet-engine/query-builder/query-editor/register for the editor UI. Five abstract methods on Base_Query — _get_items(), get_items_total_count(), get_items_page_count(), get_items_pages_count(), get_current_items_page(). Built-in cache via get_cached_data() / update_query_cache(). Custom queries participate in JE 3.8+ MCP tool exposure and the frontend query inspector automatically. Use when scaffolding a custom query type (HPOS WC orders, third-party API source, custom DB table) for JetEngine listings, dynamic widgets, or REST API endpoints.

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

Audits token storage mechanisms to prevent XSS-based JWT theft.

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