「without」の検索結果

Place reusable auth components in the shared layer without breaking ASP.NET Core consumers or tests.

日本語の概要は準備中です。原文の説明を表示しています。

Verify ASP.NET Web services build the right IDownstreamApi route and payload without standing up HTTP

日本語の概要は準備中です。原文の説明を表示しています。

Register shared claims transformation and hierarchical role policies in the API without breaking existing scope enforcement.

日本語の概要は準備中です。原文の説明を表示しています。

Safely push recovered issue-scoped fixes onto an existing PR branch without disturbing a dirty local workspace.

日本語の概要は準備中です。原文の説明を表示しています。

Implement a common social media publisher contract without breaking existing platform managers

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user is working with an Aspire distributed application and needs to operate the AppHost or its resources through the Aspire CLI: start, restart, stop, or wait on the app; inspect resources, logs, traces, docs, or health; add integrations; manage secrets or config; publish, deploy, or rerun a named pipeline step; initialize Aspire in an existing app; recover missing `.modules` files in a TypeScript AppHost; discover the right frontend URL for Playwright from Aspire state; expose custom dashboard/resource commands; or understand unfamiliar Aspire AppHost APIs in C# or TypeScript. Use it even if they describe the task in terms of an AppHost, resources, dashboard, existing app bootstrap, missing generated modules, Playwright URL discovery, C# API understanding, or local distributed app workflow without explicitly naming Aspire. Do not use it for non-Aspire .NET apps, container-only repos with no AppHost, or ordinary build and test tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Designer-turned-developer who crafts stunning UI/UX even without design mockups

日本語の概要は準備中です。原文の説明を表示しています。

Use when code changes should be scanned and reflected back into living specs, docs, or architecture notes without changing product intent.

日本語の概要は準備中です。原文の説明を表示しています。

Fix a specific bug or problem in a {{engine_name}} project. Supports two modes — immediate fix or plan-first. Without arguments executes existing .unikit/code/FIX_PLAN.md. Checks {{engine_name}} compilation, suggests test coverage, and creates self-improvement patches. Use when user says "fix bug", "debug this", "something is broken", "fix the tests", "fix the errors in the tests", "read the errors in the {{engine_name}} console logs and fix the problems", or pastes an error message or {{engine_name}} console log. Also trigger when user shares a NullReferenceException, MissingReferenceException, compilation error, or any {{engine_name}}-specific error.

日本語の概要は準備中です。原文の説明を表示しています。

Enter explore mode for technical work — a thinking partner for {{engine_name}} code, architecture, and implementation decisions before you write any code. Use it to investigate a technical solution, design the architecture of a feature, choose between frameworks or libraries, compare implementation approaches, analyze how existing code or a system works, or deeply root-cause a complex bug without fixing it yet. The ultra mode adds adaptive artifacts (a C4 view, ADRs, a dependency graph) to the research folder — run it on "ultra research", "ultra explore" or "ultraresearch"; otherwise run the default. Trigger on "let's explore this technical solution", "how should we architect this feature", "which framework should we use", "run an ultra research on the save system", "investigate this error deeply". Research and analysis only — it never writes code. This is the CODE / engineering explorer — for GAME-DESIGN, GDD, mechanics, or balance research (no code) use /unikit-gd-explore.

日本語の概要は準備中です。原文の説明を表示しています。

Exploratory workflow for understanding problem spaces and drafting feature proposals, refactorings, or complex bug-fixes. Creates detailed tickets in your issue tracker without doing implementation work.

日本語の概要は準備中です。原文の説明を表示しています。

Replace OneCLI gateway with the built-in credential proxy. For users who want simple .env-based credential management without installing OneCLI. Reads API key or OAuth token from .env and injects into container API requests.

日本語の概要は準備中です。原文の説明を表示しています。

Install the claw CLI tool — run NanoClaw agent containers from the command line without opening a chat app.

日本語の概要は準備中です。原文の説明を表示しています。

Run the same scrape or task across many accounts at once - each in its own browser profile with its own fingerprint, cookies and exit IP - and read data from sites that need a session or that answer a plain HTTP scraper with a captcha while answering a real browser. One command per site returns JSON, so there are no selectors to write or repair: Amazon and Walmart search, Google and DuckDuckGo results, Reddit posts and comments, X timeline, Medium, Yelp, Indeed job listings, Hacker News, GitHub, PyPI, npm, plus exit-IP and fingerprint checks. Use for multi-account operations you are authorized to run, price and listing monitoring per region, SERP collection, logged-in data, and scrapers that keep breaking. Also for 'scrape amazon', 'google search results', 'reddit data', 'scrape logged in site', 'run task on many accounts', 'site blocks my scraper', 'scraping without selectors'. Node or Python.

日本語の概要は準備中です。原文の説明を表示しています。

Create reproducible, cross-platform development environments with Flox — a declarative environment manager built on Nix. ALWAYS use this skill when the user needs to: set up a project with system-level dependencies (compilers, databases, native libraries like openssl, libvips, BLAS, LAPACK); configure reproducible toolchains for Python, Node.js, Rust, Go, C/C++, Java, Ruby, Elixir, PHP, or any language; manage environments that must work identically across macOS and Linux; pin exact package versions for a team; run local services (PostgreSQL, Redis, Kafka) alongside development tools; onboard new developers with a single command; or solve 'works on my machine' problems. Especially valuable for AI-assisted and vibe coding — Flox lets agents install tools into a project-scoped environment without sudo, system pollution, or sandbox restrictions, and the resulting environment is committed to the repo so anyone can reproduce it instantly. Use this skill even if the user doesn't mention Flox — if they describe needing reproducible, declarative, cross-platform dev environments with system packages, this is the right tool. Also use when the user mentions .flox/, manifest.toml, flox activate, or FloxHub.

日本語の概要は準備中です。原文の説明を表示しています。

Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.

日本語の概要は準備中です。原文の説明を表示しています。

Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.

日本語の概要は準備中です。原文の説明を表示しています。

Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.

日本語の概要は準備中です。原文の説明を表示しています。

Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.

日本語の概要は準備中です。原文の説明を表示しています。

Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.

日本語の概要は準備中です。原文の説明を表示しています。

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases.

日本語の概要は準備中です。原文の説明を表示しています。

Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

日本語の概要は準備中です。原文の説明を表示しています。

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

日本語の概要は準備中です。原文の説明を表示しています。

Index for Corey Haines marketing skills — use product-marketing first, then pull other skills from the reference clone without duplicating all 44 into the harness.

日本語の概要は準備中です。原文の説明を表示しています。