The core orchestration loop that processes work items one at a time
Skills（SKILL.md）は、AIエージェント（Claude Code、Cursor、Codexなど）に特定の能力を追加するための設定ファイルです。
詳しく見る →The core orchestration loop that processes work items one at a time
Research topics thoroughly and write comprehensive, well-structured content including articles, documentation, blog posts, and technical writing with proper citations and sources. Use when writing blog posts, creating technical articles, researching topics, gathering sources, writing documentation, creating educational content, or producing research-backed content.
Comprehensive quality audit for CLAUDE.md context files. Use when performing thorough quality checks, preparing for releases, ensuring context efficiency, or verifying token optimization.
Create Architecture Decision Records (ADRs) documenting strategic technical decisions while acknowledging ecosystem E(t) constraints. Use when choosing cloud providers, languages, frameworks, databases, or architectural patterns.
Use this skill when users ask questions about Databricks courses, tutorials, documentation, or learning materials from Databricks Academy (customer-academy.databricks.com). This skill handles login-required access to search and retrieve course content, learning paths, hands-on labs, and technical documentation.
Create user stories and epic design documents. Use when defining new features, writing Given-When-Then criteria, creating story logs, or designing larger features.
Archive outdated design documentation. Use when design docs are no longer relevant, have been superseded, or document deprecated features.
Comprehensive health audit for design documentation. Use when performing thorough quality checks, preparing for releases, or ensuring documentation compliance.
Manage design documentation system configuration. Use when initializing the system, adding modules, or updating quality standards.
Transform approved requirements into comprehensive technical designs. Define system architecture, component interactions, data models, and interfaces to create a blueprint for implementation.
Co-author design docs and propose section-by-section requirement edits
Create architecture documentation and ADRs from PRD requirements
>-
Sync design docs with codebase state. Use when verifying documentation accuracy, after code changes, or when last-synced is stale.
This skill manages the project's design documentation (`.claude/docs/DESIGN.md`). It automatically tracks:
>
Sync user documentation with design doc changes. Use when design docs
Universal methodology for verifying factual correctness in documentation using WebSearch and WebFetch tools. Covers command syntax verification, version checking, code example validation, API correctness, confidence classification system ([Verified], [Error], [Outdated], [Unverified]), source prioritization, and update frequency rules. Essential for maintaining factual accuracy in technical documentation and educational content
Summarize long documents with key points and abstracts. Use when creating executive summaries or condensing content.
PRD、ADR、Design Doc、作業計画書の作成を支援。テンプレートと作成判定マトリクスを提供。
fdd-feature-design
'Autonomous feature research and gap analysis. Use when starting /add-new-feature or analyzing existing architecture documents. Explores codebase patterns, identifies ambiguities, and produces feature-context-{slug}.md for orchestrator RT-ICA phase. Does NOT make technical decisions.'
Apply Forth AI brand guidelines when creating frontends. Use for UI components, pages, applications, and design systems. Enforces radical simplicity, polymorphic interfaces, and the Forth AI visual identity.
Game Design Document creation and structure. Use when no GDD exists in the project, starting a new game project, major feature requires design documentation, GDD needs updating due to changes, or preparing for prototype or production.
**Monitor open GitHub issues, match them to design docs, identify closable issues, and keep the issue tracker synchronized with actual development progress.**
Initialize or update GoReleaser configuration for automated Go releases with multi-architecture Docker builds, binary distribution, and Homebrew publishing
infra-architect
Expert guide for documenting infrastructure including architecture diagrams, runbooks, system documentation, and operational procedures. Use when creating technical documentation for systems and deployments.
Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and decisions, builds resumable architecture documents, and structures work into epics and milestones.
| Condition | Required Documents | Creation Order |
merge-docs
>
>
>
>
Analyzes a feature or sprint for scope creep by comparing current scope against the original plan, flagging additions and recommending cuts. Use when a sprint feels bloated or when the user mentions scope creep, scope check, or feature bloat.
Support agents currently spend a median of 8 minutes composing the first reply to each ticket. Much of that time is spent searching the internal knowledge base (KB) of ~500 Zendesk articles, copying r
Transforms technical documents into rigorous learning journeys with collegiate-level mastery requirements. Uses Bloom's taxonomy progression, 80%+ mastery thresholds, and multi-level verification before advancing. Treats learning as a high school to college graduation progression. Use when user wants deep understanding, not surface familiarity.
Bộ kỹ năng Office (DOCX/PPTX/XLSX/PDF) và Design Toolkit tích hợp từ file người dùng cung cấp.
docs-architect workflow skill. Use this skill when the user needs Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
docs-architect workflow skill. Use this skill when the user needs Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages `packages/skills-catalog/skills/(creation)/create-technical-design-doc` from `https://github.com/tech-leads-club/agent-skills` into the native Omni Skills editorial sh
Game planning and production agent. GDD structuring, game balance math, narrative design, economy design, systems design, player psychology, and production management. Does not write code.
This skill runs a structured dialogue that takes a raw idea and builds it into a complete design document through collaborative, incremental development. Every section gets user approval before moving
Mermaid diagram creation covering flowcharts, sequence diagrams, ERDs, state machines, Gantt charts, and architecture views. Use when creating or updating technical diagrams in documentation.
Maintain system architecture documentation (ARCHITECTURE_MAP.md) showing module structure, data flows, and entry points. Use this skill when architecture changes, modules are added, or system overview needs updating.
Skill for maintaining clear, DRY, and easy-to-navigate design documents for architect agents.
manage-architecture
Create Mermaid diagrams for technical documentation including ERDs, sequence diagrams, flowcharts, and architecture diagrams. Use when: (1) designing database schemas (ERD), (2) documenting API interactions (sequence), (3) illustrating process flows (flowchart), (4) visualizing system architecture.
Manage Linear documents. Use for creating and viewing documentation.