Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
日本語の概要は準備中です。原文の説明を表示しています。
Word・Excel・PowerPoint・PDF、議事録、マニュアル(3,583 件)
Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
日本語の概要は準備中です。原文の説明を表示しています。
Expert C4 Container-level documentation specialist.
日本語の概要は準備中です。原文の説明を表示しています。
Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships.
日本語の概要は準備中です。原文の説明を表示しています。
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...
日本語の概要は準備中です。原文の説明を表示しています。
API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
日本語の概要は準備中です。原文の説明を表示しています。
Control FriendlyBet operating cost, free-tier viability, provider/API cost, GitHub Actions/Supabase/Vercel usage, documentation hygiene, company memory updates, playbook maintenance, and skill validation. Use when evaluating cost, operational burden, tooling, internal docs, company memory, or whether agent profiles should become full skills.
日本語の概要は準備中です。原文の説明を表示しています。
Govern FriendlyBet agent values, professional standards, anti-hallucination behavior, truthfulness, risk reporting, AI resource discipline, feedback loops, skill improvement, performance reviews, decision-rights hygiene, and team quality. Use when creating, reviewing, promoting, correcting, or retiring agents; reducing hallucinations or mistakes; reviewing AI/tool usage; handling agent incidents; or aligning work with Eyal's philanthropic user-first approach.
日本語の概要は準備中です。原文の説明を表示しています。
Create clear, comprehensive technical documentation for any audience
日本語の概要は準備中です。原文の説明を表示しています。
Use when building, updating, or styling any monday Builders presentation, slide deck, internal pitch, kickoff doc, or HTML deliverable that should match the official Builders brand. Provides the canonical color palette, typography, gradient stroke, cover decorations, card patterns, and layout primitives sourced from the 2026 Builders Kickoff master deck. Invoke when user mentions "Builders deck", "Builders style", "match the deck", "make it on-brand", "kickoff style", or asks to design a slide/page that should look like internal monday Builders material.
日本語の概要は準備中です。原文の説明を表示しています。
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill any time a spreadsheet file is the primary input or output. Covers reading, editing, cleaning, modeling, formula repair, workbook generation, and converting tabular data into validated spreadsheet deliverables.
日本語の概要は準備中です。原文の説明を表示しています。
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
日本語の概要は準備中です。原文の説明を表示しています。
Word (.docx) manipulation via MCP server. Use for reading, creating, editing, formatting Word documents including tables, footnotes, comments, images, headers, styles, and PDF conversion.
日本語の概要は準備中です。原文の説明を表示しています。
Crawl and extract a bounded set of pages from one website through Tavily. Use for documentation downloads, site-section collection, or semantic multi-page extraction when map plus individual extract calls are insufficient.
日本語の概要は準備中です。原文の説明を表示しています。
Write and debug spreadsheet formulas (Excel/Google Sheets), pivot tables, and array formulas; translate between dialects; use when users need working formulas with examples and edge-case checks.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill any time a `.pptx` file is involved as input, output, or both. Covers reading decks, editing existing presentations, creating slides from scratch, visual QA, notes, layouts, and presentation-safe file transforms.
日本語の概要は準備中です。原文の説明を表示しています。
PowerPoint (.pptx) manipulation via MCP server. Use for creating slides, formatting presentations, managing placeholders, adding images, applying templates, or extracting text from .pptx files.
日本語の概要は準備中です。原文の説明を表示しています。
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.
日本語の概要は準備中です。原文の説明を表示しています。
Excel (.xlsx) manipulation via MCP server. Use for creating workbooks, formatting cells, writing formulas, building charts, pivot tables, data analysis, or any task involving Excel spreadsheets.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect PDFs, DOCX, PPTX, and XLSX files for share-readiness, metadata, links, comments, and hidden content.
日本語の概要は準備中です。原文の説明を表示しています。
Templates and structural patterns for API docs, feature docs, config guides, and REST endpoint documentation. Use when structuring docs, applying Markdown templates, or standardizing doc formats.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
日本語の概要は準備中です。原文の説明を表示しています。
Create structured docs from scratch — PRDs, technical specs, design docs, decision records, knowledge bases. Use when drafting documentation, writing proposals, defining requirements, or planning features.
日本語の概要は準備中です。原文の説明を表示しています。