4,645 件 ・ 関連度順
概要と使いどころ
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
日本語の概要は準備中です。原文の説明を表示しています。
Complete knowledge domain for Firecrawl v2 API - web scraping and crawling that converts websites into LLM-ready markdown or structured data. Use when: scraping websites, crawling entire sites, extracting web content, converting HTML to markdown, building web scrapers, handling dynamic JavaScript content, bypassing anti-bot protection, extracting structured data from web pages, or when encountering "content not loading", "JavaScript rendering issues", or "blocked by bot detection". Keywords: firecrawl, firecrawl api, web scraping, web crawler, scrape website, crawl website, extract content, html to markdown, site crawler, content extraction, web automation, firecrawl-py, firecrawl-js, llm ready data, structured data extraction, bot bypass, javascript rendering, scraping api, crawling api, map urls, batch scraping
日本語の概要は準備中です。原文の説明を表示しています。
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...
日本語の概要は準備中です。原文の説明を表示しています。
Google-grade software engineering culture encompassing Code Readability, Design Doc Review, Blameless Postmortem, Testing Philosophy, Code Review standards, and engineering excellence practices distilled from Google's internal engineering culture documented in "Software Engineering at Google" and real Google/Brain/DeepMind experience. USE WHEN: establishing engineering standards, reviewing code quality, designing development workflows, onboarding engineers, setting code review guidelines, adopting Google-level engineering excellence, or building an engineering culture that promotes maintainability, readability, and quality.
日本語の概要は準備中です。原文の説明を表示しています。
Captures clause risks, compliance gaps, precedent shifts, contract deviations, regulatory changes, and litigation exposure to enable continuous legal operations improvement. Use when: (1) An unfavorable clause is accepted or slips through review, (2) A compliance deadline is missed or approaching, (3) A new regulation impacts the organization, (4) A contract remains unsigned past SLA, (5) An IP infringement notice is received, (6) New case law changes interpretation in a relevant jurisdiction, (7) A data subject access request reveals process gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture Decision Records (ADR) — a lightweight method for capturing important architectural decisions with context, trade-offs, and rationale. Based on Michael Nygard's ADR pattern and Google/Meta/ByteDance's design documentation culture. USE WHEN: deciding between technology choices, designing new architecture, changing existing architecture, documenting why a decision was made, onboarding new team members, or preserving design context for future maintainers. Triggered by terms like "tech choice", "architecture decision", "why did we choose", "design rationale", "ADR", or "architectural decision record".
日本語の概要は準備中です。原文の説明を表示しています。
A Vedic astrology (Jyotish) analyzer based on the Indian Jyotish tradition, using the Sidereal zodiac to read birth charts. Covers 27 Nakshatras (Lunar Mansions), the Vimshottari Dasha (Major Period) system, and the Navagraha (Nine Planets). Triggered when users mention "Vedic astrology," "Jyotish," "Vedic," "Nakshatra," "Dasha," or "Indian astrology." Pure LLM reasoning for interpretation (precise charts require an astronomical engine). No external API required. Not applicable for: Western astrology horoscopes, BaZi, tarot, Zi Wei Dou Shu, or other domains → use the fortune-hub router instead.
日本語の概要は準備中です。原文の説明を表示しています。
Mechanism conflict detection and coordination for AI assistant systems. Automatically detects crontab conflicts, systemd service conflicts, script overlaps, and log path inconsistencies. Use for maintaining system harmony and preventing internal conflicts.
日本語の概要は準備中です。原文の説明を表示しています。
Manus-style file-based planning for complex tasks. Creates and maintains task_plan.md, findings.md, and progress.md under .kiro/plan/. Use when planning, breaking down work, resuming a multi-step task, tracking phases, or restoring context after compaction. Trigger phrases include start planning, continue task, resume work, current phase, restore context.
日本語の概要は準備中です。原文の説明を表示しています。
Build and ship software — code, implement, develop, API, backend, frontend, deploy, infrastructure, CI/CD, databases, cloud, mobile, AI/ML. The CTO office's broadest execution domain, applied with TDD discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Agency and studio operations — operations, analytics, finance, infrastructure, support, reporting, dashboards, KPIs, budget. Multi-office domain where CTO, CEO and CSO agents converge.
日本語の概要は準備中です。原文の説明を表示しています。
Growth marketing and go-to-market — campaign, GTM, brand awareness, conversion, growth hacking, user acquisition, funnel, social media strategy. The CMO office's full-funnel growth domain.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and track delivery — plan, sprint, project, timeline, milestone, task breakdown, backlog, Kanban, RACI, changelog governance. The COO office's workflow coordination domain.
日本語の概要は準備中です。原文の説明を表示しています。
UX and interaction design — UI, interface, wireframe, mockup, prototype, user experience, user journey, usability, accessibility audit, onboarding flow. The "how users think and move through it" domain.
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (GLOSSARY.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive MCP tool reference for Proxmox Virtual Environment management - 92 tools across 14 domains including QEMU VMs, LXC containers, cluster operations, storage, networking, Ceph, certificates, ACME, and notifications
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive Power BI DAX formula optimization prompt for improving performance, readability, and maintainability of DAX calculations.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patterns, and extension templates for maintaining consistent code organization across diverse technology stacks.
日本語の概要は準備中です。原文の説明を表示しています。
Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades.
日本語の概要は準備中です。原文の説明を表示しています。
Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI consumption and workflow maintenance.
日本語の概要は準備中です。原文の説明を表示しています。
Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.
日本語の概要は準備中です。原文の説明を表示しています。
Patterns for designing well-structured, maintainable Ansible playbooks with state-based (present/absent) design, play organization, and proper variable scoping.
日本語の概要は準備中です。原文の説明を表示しています。
Adopt a virtual Persian cat at animalhouse.ai. High maintenance. Rewards grooming. Hates being rushed. Feeding every 5 hours. Uncommon tier cat.
日本語の概要は準備中です。原文の説明を表示しています。