「factory」の検索結果

Search and analyze products on the Chinese 1688 wholesale platform (Alibaba domestic B2B market) for sourcing, supplier discovery, and product selection. Trigger when the user mentions 1688 product search, finding suppliers on 1688, wholesale product queries, factory sourcing, dropshipping supplier search, 1688 keyword product selection, wholesale price comparison, filtering by sales volume, any product research on the 1688 platform, 1688 search, 1688 product selection, find suppliers, factory lookup, wholesale pricing, supplier search, domestic sourcing, 1688 products. Even if the user does not explicitly say "1688", if their need involves searching for wholesale products, finding domestic suppliers, or sourcing from the domestic Chinese market, this skill should also be triggered.

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

Self-learning SEO content pipeline: dashboard, multi-agent queue, token budgets, research → write → audit → publish. StoryBrand/Cialdini/JTBD-style frameworks; config-driven. Use for content factory, batch articles, or scaled publishing.

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

Flask web framework conventions: app factory pattern with create_app(), Blueprint registration with url_prefix, MethodView for class-based API views, Marshmallow schema validation, WTForms for HTML forms, Flask-Login for session auth, flask-jwt-extended for stateless API auth, Jinja2 template conventions, error handlers, and extension initialization. Activated automatically by flask-plugin/stack.md. Use this skill to: - Structure Flask applications with the app factory and per-feature Blueprints. - Validate JSON request data with Marshmallow and HTML forms with WTForms. - Implement session-based auth with Flask-Login or token auth with flask-jwt-extended. - Render Jinja2 templates safely or return JSON responses for API mode. - Register global error handlers for consistent error responses. Do NOT use this skill for: - SQLAlchemy ORM model patterns and Flask-Migrate — see flask-plugin:sqlalchemy-patterns. - Python language idioms — see python-foundation:python-conventions. - Testing patterns — see python-foundation:pytest-testing.

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

xUnit, Moq/NSubstitute, FluentAssertions, and coverlet patterns for any .NET project. Covers test structure ([Fact]/[Theory]/[InlineData]), mocking discipline, fluent assertions, integration test setup with WebApplicationFactory, and coverage measurement. Stack-agnostic — referenced by every .NET plugin in the marketplace. Use this skill to: - Write clear, maintainable unit tests with xUnit [Fact] and [Theory]. - Mock dependencies with Moq or NSubstitute without overusing mocks. - Write expressive assertions with FluentAssertions. - Measure coverage with coverlet and enforce a minimum threshold. Do NOT use this skill for: - ASP.NET Core-specific integration tests (WebApplicationFactory, HttpClient — those are in aspnet-core-plugin:aspnet-conventions). - EF Core in-memory or SQL Server LocalDB test patterns (aspnet-core-plugin:efcore-patterns). - C# language idioms — see csharp-foundation:csharp-conventions.

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

Use this skill when designing the human-executable UAT test cases that prove a Salesforce feature works for a specific persona — the per-persona scripts with preconditions, data setup, permission setup, ordered steps, and pass/fail evidence that close out an RTM row. Trigger keywords: UAT test case salesforce, user acceptance test script salesforce, manual test salesforce feature, UAT script per persona, UAT precondition data setup, UAT permission set assignment for testing, negative path UAT case. NOT for high-level UAT planning, defect classification, regression strategy, or sign-off (use admin/uat-and-acceptance-criteria). NOT for the Given/When/Then technique used to write the AC the case is derived from (use admin/acceptance-criteria-given-when-then). NOT for Apex test method generation (use agents/test-class-generator). NOT for test data factory patterns (use templates/apex/tests/TestDataFactory.cls). NOT for performance or load testing.

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

Produce a researched long-form article from a topic prompt via an orchestrated pipeline - research agent (first-person sources, working-definition gate), narrative-architecture outline, writer/cold-reviewer loop with an explicit ACCEPT/REVISE verdict contract, then a catalog-deslop pass with a regression gate. The orchestrator dispatches subagents only; the writer never judges its own draft. Use when the user says "article factory", "write an article about X", "run the article pipeline", or asks for a researched long-form piece produced end-to-end. For essays and micro posts in the user's own voice without a research stage, use the prose skill instead.

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

Use when reviewing active Loop Factory specs against the working tree, checking verification evidence, deciding ACCEPTED or CHANGES_REQUESTED, and archiving accepted specs.

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

Produce a UGC-style talking-head video ad end to end on the MaxFusion MCP — research the product with user-supplied competitor leads, tear down 5 competitor Meta ads and 5 organic TikToks, write a pain-driven script that sounds like a person talking (never like an ad), reverse-prompt a rights-clean photoreal actor from a user-supplied reference photo, generate two chained 10-second Gemini Omni clips that play as one continuous take, and ship a single seamless 9:16 MP4. Use whenever the user wants a UGC ad, a talking-head ad, an ad for an app or product, mentions Omni or Gemini Omni Flash, drops an actor photo and asks for a video ad, or says anything like "make me some UGC", "let's make ads for X", or "another variation". Built for Claude Code (local ffmpeg); degrades to Claude app with documented fallbacks.

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

Produce variants of an existing Style by shifting tone (light/dark), density (compact/relaxed), or accent (palette rotation) while preserving the brand identity. Use when the user wants alternate themes derived from one brand.

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

Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.

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

Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or drafting proposed host automations for report-only review.

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

Apply Gang of Four design patterns to solve architectural problems in TypeScript. Use when refactoring code architecture, implementing extensible systems, decoupling components, or following SOLID principles. Covers all 22 GoF patterns: Creational (Factory Method, Abstract Factory, Builder, Prototype, Singleton), Structural (Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy), and Behavioral (Chain of Responsibility, Command, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, Visitor).

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

Claim one live GitHub queue item, implement it end to end, run fail-closed gates and independent verification, then open a draft PR. Use for one ready-to-implement issue or the implementation routine.

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

Claim and implement one ready GitHub issue, run fail-closed gates, obtain independent verification, and open a draft pull request.

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

Turn a ready-to-spec queue item into an approved plan through explicit human gates. Use when an item needs scope decided before code exists, when planning a feature, or before starting a migration. Runs interactively - not for unattended routines.

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

Imports an FBX vehicle into a CARLA source build as a spawnable vehicle.<make>.<model> — checks the FBX carries CARLA's 4-wheel bone rig, imports the mesh, then assembles the vehicle through CarlaTools' VehicleAuthoringLibrary (physics asset with kinematic wheel bodies, retargeted anim blueprint, four configured wheel blueprints, the vehicle blueprint), registers it in VehicleFactory through CARLA's own add_vehicle_to_vehicle_factory.py, and verifies it spawns, drives and steers. Use when the user asks to "add a car/truck/van to CARLA", "import a vehicle FBX", or needs a custom drivable vehicle spawnable from the Python API.

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

Imports an FBX pedestrian into a CARLA source build as a spawnable walker.pedestrian.NNNN — checks the FBX is skinned to CARLA's GEN3 rig, imports the mesh, physics asset and materials, builds the walker blueprint from a GEN3 donor, registers it in WalkerFactory through CARLA's own add_walker_to_walker_factory.py, and verifies it spawns, stands on the ground and walks. Use when the user asks to "add a pedestrian to CARLA", "import a walker/character FBX", or needs a custom human spawnable from the Python API.

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

Hono (軽量・マルチランタイム対応 Web フレームワーク) リファレンス。 Hono App, Context (c.req / c.json / c.text / c.html), HonoRequest, Routing, HTTPException、 Built-in Middleware (JWT, CORS, CSRF, Cache, Logger, Compress, Basic / Bearer Auth)、 Helpers (Cookie, Streaming, WebSocket, Factory, RPC)、 Cloudflare Workers / Deno / Bun / Node.js / AWS Lambda 対応。

Use this skill when the user asks about DOT audits, FMCSA compliance reviews, new entrant safety audits (NESA), focused investigations, what auditors actually ask for, audit document checklists, common audit failures, the audit ratings (Satisfactory / Conditional / Unsatisfactory), or how to prepare for an upcoming audit. Cite 49 CFR 385.

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

pytest-djangoによるDjangoテスト戦略、TDD方法論、factory_boy、モック、カバレッジ、Django REST Framework APIのテスト。

Generates DDD Factory for PHP 8.5. Creates factories for complex domain object instantiation with validation and encapsulated creation logic. Includes unit tests.

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

Specialized skill for ASP.NET Core integration testing. Use when testing Web API endpoints, HTTP request/response, middleware, and dependency injection. Covers WebApplicationFactory, TestServer, HttpClient testing, in-memory database configuration. Keywords: integration testing, web api testing, WebApplicationFactory, TestServer, HttpClient testing, controller testing, endpoint testing, RESTful API testing, Microsoft.AspNetCore.Mvc.Testing, CreateClient, ConfigureWebHost, AwesomeAssertions.Web, Be200Ok, Be404NotFound, middleware testing, dependency injection testing

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

Complete guide for ASP.NET Core Web API integration testing. Use when performing integration testing on Web API endpoints or validating ProblemDetails error format. Covers WebApplicationFactory, IExceptionHandler, Testcontainers multi-container orchestration, Flurl URL construction, and AwesomeAssertions HTTP validation. Keywords: webapi integration testing, WebApplicationFactory, asp.net core integration test, webapi integration test, IExceptionHandler, ProblemDetails, ValidationProblemDetails, AwesomeAssertions, Flurl, Respawn, Be201Created, Be400BadRequest, multi-container testing, Collection Fixture, global exception handling

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

Complete guide for TUnit advanced applications. Use when using TUnit for data-driven testing, dependency injection, or integration testing. Covers MethodDataSource, ClassDataSource, Matrix Tests, Properties filtering. Includes Retry/Timeout control, WebApplicationFactory integration, Testcontainers multi-service orchestration. Keywords: TUnit advanced, TUnit advanced, MethodDataSource, ClassDataSource, Matrix Tests, MatrixDataSource, MicrosoftDependencyInjectionDataSource, Property, Retry, Timeout, data-driven testing, test filtering, WebApplicationFactory TUnit, multi-container orchestration

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