「ties」の検索結果

Expert-level medicinal chemistry knowledge. Use when working with drug design, structure-activity relationships, ADMET properties, pharmacophores, lead optimization, target identification, drug metabolism, or pharmaceutical development. Also use when the user mentions 'SAR', 'drug design', 'pharmacophore', 'ADMET', 'lead compound', 'hit to lead', 'drug metabolism', 'bioavailability', 'selectivity', 'binding affinity', 'scaffold hopping', or 'bioisostere'.

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

Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives. Its System One models, including Jev, turn natural language and application state into typed judgments and probabilities that code can combine. Use when a feature needs programmable common sense, when brainstorming what AI could make possible in an app, or when an LLM prompt-and-parse step could become a structured decision. Applications include routing, ranking, extraction, verification, and interactive experiences; these are starting points, not the limits. Read live docs and cookbooks to find useful patterns and discover new combinations.

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

Research one agent harness's release (docs, source, runtime) and fill its capability cells in scripts/harness_capabilities.py with cited evidence. Use after a harness version bump, when just harness-probe reports re-research, or when capability cells read unknown.

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

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

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

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

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

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

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

Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.

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

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

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

Design relational database schemas (and choose when to go NoSQL) that stay maintainable and fast. Use this skill whenever the user mentions tables, DDL, entities and relationships, normalization (1NF/2NF/3NF), primary and foreign keys, UUID vs bigint IDs, indexes (B-tree, composite, covering, partial), EXPLAIN, constraints (CHECK, UNIQUE, exclusion), transactions and isolation levels, migrations (Alembic, Prisma, Flyway, expand-contract, backfilling), or SQL vs NoSQL (MongoDB, DynamoDB, Cassandra, graph databases). Also trigger for "design the database", "model this domain", "which database should I use", or writing ORM models and migration files for PostgreSQL, MySQL, SQLite, or SQL Server.

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

Session-start orientation for this team harness. Load first, before any work. Explains the operating contract, when each skill triggers, and how installed companion plugins supply agent-craft capabilities while this harness supplies the team contract. Trigger at the start of every session and whenever unsure which skill applies.

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

Use when working with MCP (Model Context Protocol) servers — their tools, capabilities, and best practices for effective agent workflows.

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

Use when creating Laravel jobs, queued workflows, events, or listeners. Covers clear responsibilities, safe serialization, and retry/failure handling.

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

Agents with competing priorities reach consensus through structured trade-offs.

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

[Utilities] Use when you need to review recent changes and wrap up the work.

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

[Utilities] Use when you need to restore workflow context from checkpoint after session loss.

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

[Documentation] Use when scanning the codebase to (re)generate ONE project-reference doc. Parameterized by `--target=<key>`: project-structure | backend-patterns | frontend-patterns | scss-styling | design-system | code-review-rules | domain-entities | feature-spec | docs-index | e2e-tests | integration-tests | seed-test-data | ui-system. Shared 4-phase scan engine; per-target detail lives in references/targets.md. `ui-system` is an orchestrator meta-target (`kind: orchestrator`) that runs the 3 UI child scans in parallel instead of the 4-phase engine.

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

[Utilities] Use when a project needs to add, change, list, or remove its OWN protocol rules layered on top of a framework skill — a named overlay of extra project rules that applies whenever the targeted skill runs, stored with the project rather than in the portable framework. `/project-skill-protocol list` prints every overlay with its target and description; `add` drafts a new overlay and confirms it before writing; `update` applies a surgical change; `delete` removes it. Overlays are ADDITIVE ONLY — they never replace, override, or waive anything the skill already does. Triggers: skill protocol, project protocol, custom protocol for skill, extend a skill, overlay rules, add rules to a skill, project rules for skills, skill protocol overlay.

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

[Utilities] Use when you need to scan workspace and update docs/project-config JSON to match current project structure.

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

[Utilities] Use when recording an engineering journal entry — capture decisions, blockers, lessons, or progress notes during work.

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

[Utilities] Use when saving or recovering task progress across sessions via file checkpoints — especially before context compaction.

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

[Utilities] Use when applying structured problem-solving frameworks to complex, blocked, recurring, or uncertain decisions.

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

[Utilities] Use when initializing or re-evaluating portable project context: project-config, project-reference docs, CLAUDE.md, AGENTS.md, universal agent rules, hookless setup. Triggers on: project init, init project, missing project-config, missing project docs, missing CLAUDE.md, missing AGENTS.md.

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

[Utilities] Use when you need to teach Claude lessons that persist across sessions.

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

[Utilities] Use when you need to save analysis context to a checkpoint file for recovery (user-facing alias for memory-management Part 1 CHECKPOINT_CREATE).

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