596 件 ・ 関連度順
概要と使いどころ
Use for strategic thinking, or when the user must choose a direction under constraints: "where should we focus?", "how do we win?", "roadmap for next year", "what should we not do?". Ends in explicit bets and risks. Skip for step-by-step implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Generate project ideas via creative constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Learn from consequences, not instructions — generate and enforce constraints from experience.
日本語の概要は準備中です。原文の説明を表示しています。
Plan multi-waypoint journeys with route optimization, feasibility analysis, and time budget constraints.
日本語の概要は準備中です。原文の説明を表示しています。
A comprehensive toolkit for AI agents operating under budget constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Keep your constraints healthy — lifecycle management with automatic staleness detection.
日本語の概要は準備中です。原文の説明を表示しています。
Explains the ~/.worktrees/<path-key>/<branch> worktree convention, the dotfiles-repo opt-in, and what a dotfiles worktree cannot validate. Use to understand or explain worktree layout and its constraints; use the git-worktree skill to actually create, switch to, or delete one.
日本語の概要は準備中です。原文の説明を表示しています。
Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
Opinionated constraints for building better web interfaces with coding agents. Use this skill whenever the user asks you to build, review, or fix a UI — landing pages, dashboards, components, or any frontend code — and whenever you write Tailwind CSS, motion/react animations, accessible component primitives (Base UI, React Aria, Radix), or review agent-generated interface code for quality, accessibility, and performance. Also trigger for "make the UI better", "review my interface", "clean up this component", or any frontend work in React, Next.js, or plain HTML/CSS.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or changing public C#/.NET APIs with compatibility and versioning constraints. Keywords: breaking change, API design, backward compatibility, binary compatibility, deprecation strategy, versioning.
日本語の概要は準備中です。原文の説明を表示しています。
Force plan, HLD, ADRs, and constraints to exist BEFORE any code is generated. Trigger when starting a new feature, epic, or significant change.
日本語の概要は準備中です。原文の説明を表示しています。
Shared corpus-grounding engine — BM25 + structured filters + decision rules over CSV corpora via a domain manifest. Use when a skill needs grounded pre-action option-space constraints.
日本語の概要は準備中です。原文の説明を表示しています。
Projete um schema específico para PostgreSQL. Abrange práticas recomendadas, tipos de dados, indexação, constraints, padrões de desempenho e recursos avançados
日本語の概要は準備中です。原文の説明を表示しています。
Translate motion, interaction, and visual experience into implementable constraints while preserving accessibility and performance. Apply when working on animations, transitions, scroll effects, or micro-UX.
日本語の概要は準備中です。原文の説明を表示しています。
Writing quality guidelines, formatting conventions, and styling constraints for documentation. Trigger when: - Writing, editing, or auditing documentation files, READMEs, markdown files, or guides. - Modifying files with suffixes like: *.md, *.qmd, *.txt, *.rst. - Prompt contains keywords: doc, documentation, spelling, grammar, headers, links, table alignment, Divio, tone, voice, clarity.
日本語の概要は準備中です。原文の説明を表示しています。
Rules, conventions, and constraints for formatting git commit messages and committing at logical boundaries. Trigger when: - Drafting, revising, or validating git commit messages. - Pausing at commit boundaries under the CORE or CONTINUE workflows. - Evaluating whether a changeset should be split into multiple commits. - Prompt contains keywords: commit message, git commit, conventional commits, commit hygiene, commit guidelines, logical boundary, spaghetti diff, atomic commit, commit boundary.
日本語の概要は準備中です。原文の説明を表示しています。
Before building new infrastructure or a non-trivial capability, check whether the Nuxt ecosystem, UnJS, Vite, or other OSS already solves it — within our constraints (Nuxt, OSS, self-hostable, no mandatory SaaS). Use when weighing build-vs-adopt or starting new infra/tooling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, editing, debugging, or reviewing dealer language code in btn, dlr, or script files. Provides the complete dealer DSL syntax reference for bridge hand generation constraints.
日本語の概要は準備中です。原文の説明を表示しています。
First-principles strategy — strip away conventional assumptions and find the theoretical maximum for your business. Three modes. Diagnostic mode runs a full session (45+ min) to define your theoretical maximum, map the gap honestly, classify constraints, invert for failure modes, set strategic intent, and work backwards to your first intervention. Review mode (15-20 min) checks whether your theoretical maximum has shifted, whether the gap has changed, and whether you're still climbing the right peak. Alert mode defines constraint-shift, peak-shift, and local-peak triggers that tell you when to reassess. Use when someone is stuck optimising incrementally, when conventional wisdom is driving strategy, when a new technology or regulation changes what's physically possible, or when you suspect the business is climbing a local peak. Integrates with company-context.md. Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
Use before build, fix, debug, review, or docs implementation; converts prompts into structured intent JSON with goal, constraints, and routing.
日本語の概要は準備中です。原文の説明を表示しています。
Recommend Azure VM sizes, VM Scale Sets (VMSS), and configurations based on workload requirements, performance needs, and budget constraints. No Azure account required — uses public documentation and the Azure Retail Prices API. WHEN: recommend VM size, which VM should I use, choose Azure VM, VM ...
日本語の概要は準備中です。原文の説明を表示しています。
Create or update project governing principles and development guidelines. Use at project start to establish code quality, testing standards, and architectural constraints that guide all development.
日本語の概要は準備中です。原文の説明を表示しています。
Dependency-conflict resolution when a `fix` version bump fails — diagnose the peer-dep tree, find a compatible safe version set, propose package-manager overrides (`overrides`/`resolutions`/`replace`/`[patch]`), fall back to safe-harbour inline patching. Use when an upgrade is blocked by transitive constraints, a peer-dep conflict surfaces, or you need to override a vulnerable transitive without bumping the parent.
日本語の概要は準備中です。原文の説明を表示しています。