「source」の検索結果

Use when creating a new Laravel API endpoint — Controller, FormRequest, Resource, route, Policy, OpenAPI annotations — versioned route layout, single-action `__invoke` controllers.

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

Turn a confirmed brand identity into a DTCG .tokens.json source of truth — emit CSS vars + Tailwind via design-tokens, export locked brand deck templates.

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

Use when working with AWS resources — ECS Fargate, ECR, EFS, Secrets Manager, gomplate templates, multi-env deployments — even when the user says 'deploy to staging' without naming AWS.

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

Check any artifact against an explicit specification and report adherence using the add-comments workspace format. Use when validating plans, scripts, docs, or code changes against a source-of-truth spec.

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

Banco de dados de embeddings de código aberto para aplicações de IA. Armazene embeddings e metadados, realize buscas vetoriais e full-text, filtre por metadados. API simples com 4 funções. Escala de notebooks para clusters de produção. Use para busca semântica, aplicações RAG ou recuperação de documentos. Melhor para desenvolvimento local e projetos de código aberto.

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

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

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

Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"

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

Load this skill whenever the project contains tooltip components, hover- triggered informational popups, title attribute tooltips, or any content revealed on hover or focus. Under no circumstances create tooltips that are only triggered by hover without keyboard equivalent access. Absolutely always ensure tooltips are dismissible, persistent enough to read, and not the sole source of essential information.

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

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

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

[Workflow] Use when activating the Research & Synthesis workflow — research a topic via web sources, then synthesize per --output={synthesis|business-eval|marketing|course} (knowledge report, business evaluation, marketing strategy, or course material).

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

[Workflow] Use when activating the E2E testing workflow to generate, update, or maintain Playwright/E2E tests. Pick mode with --source={changes|recording|update-ui}.

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

[Research] Use when starting a web research task — discover, gather, and triage candidate sources on a topic to feed deeper investigation.

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

[Testing] Use when you need to drive an integration-test suite to fully green — each round runs /integration-test-verify (whole system by default, or the target named in the prompt), and on ANY failure combines /debug-investigate + /integration-test-review (report-only) to adjudicate the fault (test wrong · test not optimal · source wrong), then /fix to resolve it at the owning layer, then /changes-review on that round's fix diff, then re-runs a FRESH full verify — looping until the whole suite passes its 2-consecutive-green-runs gate with zero failures.

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

[Research] Use when deeply researching top sources from web-research.

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

Use when planning the migration of a legacy system or monolith — analyzes the source codebase (current repo, or a repo URL cloned to a temp dir) and produces an evidence-based Strangler Fig migration plan with per-domain SPECs. Default target is .NET (Blazor WebAssembly, .NET MAUI, ASP.NET Core); other stacks allowed by user decision. Do NOT use to implement code or when approved SPECs already cover the migration.

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

Creates a repeatable process for researching and comparing companies. Use when the user wants a structured, reusable company-research workflow with objectives, sources, fields, and validation.

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

Turns an ICP or research goal into a plan for finding and scraping suitable directories. Use when the user has a target audience but is unsure where to find them, and wants source categories, queries, and an extraction workflow.

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

Designs an end-to-end process for finding, extracting, enriching, qualifying, and exporting leads. Use when the user wants a repeatable lead workflow plan rather than a single source plan.

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

Identifies missing information required to complete qualification, segmentation, or outreach preparation. Use when the user provides records and a goal and wants prioritized research gaps with sources.

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

Converts a job description into a structured candidate-sourcing workflow. Use when the user provides a role and wants candidate criteria, search terms, source recommendations, and a screening process. Must avoid sourcing on sensitive personal attributes.

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

Use when creating or editing raster images, visual concepts, product graphics, launch assets, diagrams, posters, thumbnails, reference sheets, UI mock images, or image prompts that need source-grounded claims, readable text, brand direction, and post-generation verification.

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

Use when generating a single dense technical architecture, reference poster, or system diagram image for a software project. Produces a source-grounded bitmap diagram with topology, primitives, ingest/process flow, core logic, state scopes, tiers/modules, surfaces, runtime cards, and strict semantic color rules.

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

Create or repair a project-local Inspector profile after INSPECTOR_PROFILE_REQUIRED, INSPECTOR_PROFILE_INCOMPLETE, INSPECTOR_PROFILE_INVALID, or PROFILE_AUTHORING_REQUIRED, using Unity component source, custom Inspector evidence, serialized surfaces, and validation diagnostics.

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

Project-level WeChat article drafting workflow for turning source materials, repo intakes, product notes, screenshots, or existing markdown into a publishable Chinese公众号 draft. Use for writing, rewriting, evidence-gating, title options, platform adaptation, and image planning before optional publishing.

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