6,621 件 ・ 関連度順
Bedrock is a WordPress boilerplate with Composer-based dependency management, environment-specific configuration via .env files, and an improved folder structure. It separates WordPress core from application code for cleaner version control and deployment.
日本語の概要は準備中です。原文の説明を表示しています。
BackstopJS gives agents a repeatable way to capture reference screenshots, compare UI states, and flag visual regressions before changes ship. This skill centers on the real BackstopJS project and turns browser-based layout comparison into a structured QA workflow for web teams.
日本語の概要は準備中です。原文の説明を表示しています。
Benchmark clean and incremental Xcode builds, surface compile and configuration hotspots, and produce an approval-first optimization plan before changing project files.
日本語の概要は準備中です。原文の説明を表示しています。
Use AB Method when a Claude Code task is too large for one pass and needs to be broken into focused tasks and missions that are completed incrementally instead of trying to solve the whole project in one conversation.
日本語の概要は準備中です。原文の説明を表示しています。
Use Deptry when an agent needs to verify that a Python project's declared dependencies still match the imports the code actually uses. The agent scans the codebase, flags unused direct dependencies, missing declarations, and transitive imports that only work by accident, then turns the findings into cleanup commits or release blockers.
日本語の概要は準備中です。原文の説明を表示しています。
mcp-atlassian is a Model Context Protocol server that connects AI assistants to Atlassian Jira and Confluence. It enables searching and managing Jira issues, reading and editing Confluence pages, and performing project management tasks through natural language via any MCP-compatible client.
日本語の概要は準備中です。原文の説明を表示しています。
Run CodeBurn locally or as an MCP server so agents can inspect token usage, cost, model mix, project spend, and budget waste across coding tools.
日本語の概要は準備中です。原文の説明を表示しています。
Use Cognee to ingest project knowledge into graph and vector memory so agents can retrieve durable context across sessions and workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Generate pre-populated NFR table for a system's HLD based on tier and project type
日本語の概要は準備中です。原文の説明を表示しています。
Use the gda CLI to build, inspect, validate, and export Godot projects without opening the editor, or to inspect and control a running game through gda-daemon. Use when an agent builds or modifies a Godot game, or the user asks for gda or Godot automation.
日本語の概要は準備中です。原文の説明を表示しています。
Create a product brief document for a feature or project.
日本語の概要は準備中です。原文の説明を表示しています。
Bridges asset requirements from motion design specs to production-ready assets. Parses specs for required assets, recommends free/paid sources, provides format conversion guidance, generates validated import code, and offers asset preparation checklists. Use when preparing assets for Remotion projects or when asked "where to get assets", "how to prepare assets", "asset formats for Remotion".
日本語の概要は準備中です。原文の説明を表示しています。
Master orchestrator that chains all Remotion video creation skills together in a single automated pipeline. Takes a creative brief and produces a complete, production-ready Remotion video project. Use when starting a new video from scratch, when asked to "create a video", "make a video", "build a complete video", or "video from idea to code".
日本語の概要は準備中です。原文の説明を表示しています。
The Mileva Method (CRISP) — Phase 1: Clarify. Problem definition, eliciting, painkiller test, buy vs build, AI justification gate, Go/No-Go. Use at the start of any AI implementation project. Triggers on "clarify", "phase 1", "start discovery", "define the problem", "what problem are we solving", or at the beginning of a new client engagement.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a beautiful single-file HTML report from the project's docs/ folder. Works after any CRISP phase, after Archaeology, or at sprint close in Execute. Triggers on "generate report", "export docs", "create HTML report", "share docs", or automatically at sprint close in CRISP Execute.
日本語の概要は準備中です。原文の説明を表示しています。
The Mileva Method (CRISP) — Phase 3: Investigate. Process mapping for existing or greenfield processes, user journey mapping, UX discovery, project goals, system architecture (integration map + data flow). Use after outcome alignment. Triggers on "investigate", "phase 3", "map the process", "process mapping", "user journey", "as-is process", or after Phase R exit checklist is complete.
日本語の概要は準備中です。原文の説明を表示しています。
The Mileva Method (CRISP) — Phase 4: Spec. Full implementation readiness package including solution design, UX direction, tech stack, backlog, MVP prioritization, risk assessment, and AI architecture for Claude Code projects — CLAUDE.md, skill mapping, AI specs, sprint planning, quality gates. Triggers on "spec", "phase 4", "build ready", "implementation plan", "CLAUDE.md", "sprint planning", "backlog", "AI spec", or after Phase I exit checklist is complete.
日本語の概要は準備中です。原文の説明を表示しています。
Generates AI-authored code reading guides from a project or module. Invoke when user asks to read code, summarize architecture, and write a guide document.
日本語の概要は準備中です。原文の説明を表示しています。
Build and refine TouchDesigner projects with tdmcp using context-first, visible, reversible workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Apply fail-closed consent, scope, undo, and verification rules to TouchDesigner mutations made with tdmcp.
日本語の概要は準備中です。原文の説明を表示しています。
Study a merged or shipped tdmcp implementation and extract reusable learnings: code improvements, runtime/UX lessons, test gaps, docs updates, roadmap items, and harness changes. Use when the user asks to learn from a completed feature/project/PR/build, analyze what can be improved from an implementation, or turn a real installation experience into actionable tdmcp improvements. This is a post-implementation learning harness; it does not replace tdmcp-pipeline for building or tdmcp-quality-audit for broad repo audits.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates the dedicated Kinect wall harp implementation team. Use whenever the user asks to build, implement, continue, fix, QA, document, or ship the Kinect wall harp, Kinect v2 wall-depth harp, FreenectTD depth-blob hand tracking, projected wall strings, pluck synth harp, or this feature's Layer 1 tool/recipe/docs. Use this before the generic tdmcp-pipeline for this feature.
日本語の概要は準備中です。原文の説明を表示しています。
Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging a release.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold, build, and run MCP servers from a predictable Python project layout with tools, prompts, resources, auth, and OpenTelemetry hooks.
日本語の概要は準備中です。原文の説明を表示しています。