2,201 件 ・ 関連度順
概要と使いどころ
Maxim cinematic brand film — engineered for commitment and emotional brand alignment. Uses Hero's Journey + Peak-End Rule + Emotional Arc Theory to convert viewers into brand advocates. Use for brand films, anthem ads, founder stories, long-form brand content. Triggers on cinematic, film, brand film, anthem, dramatic, epic, Hollywood-style.
日本語の概要は準備中です。原文の説明を表示しています。
Block writes through filesystem junctions and symlinks — file write through .mxm-system or .claude junction, git commit through a junction, delete through a junction. Enforces the junction read-only rule so the real repo stays the source of truth.
日本語の概要は準備中です。原文の説明を表示しています。
Build a throwaway HTML or in-app prototype that answers one design question. Use when the user wants to try a state model or UI idea before committing, or says "mock it up", "prototype", "what should this look like".
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI. Covers all four build backends (setuptools+setuptools_scm, hatchling, flit, poetry), PEP 440 versioning, semantic versioning, dynamic git-tag versioning, OOP/SOLID design, type hints (PEP 484/526/544/561), Trusted Publishing (OIDC), and the full PyPA packaging flow. Use for: creating Python packages, pip-installable SDKs, CLI tools, framework plugins, pyproject.toml setup, py.typed, setuptools_scm, semver, mypy, pre-commit, GitHub Actions CI/CD, or PyPI publishing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive skill for working with Azure DevOps REST API across all services including Boards (work items, queries, backlogs), Repos (Git, pull requests, commits), Pipelines (builds, releases, deployments), Test Plans, Artifacts, organizations, projects, security, extensions, and more. Use when implementing Azure DevOps integrations, automating DevOps workflows, or building applications that interact with Azure DevOps services.
日本語の概要は準備中です。原文の説明を表示しています。
GitHub PR lifecycle: branch, commit, open, CI, merge.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 3 of the Forge pipeline. Execute the plan's Beads tasks with red-green-refactor TDD, committing per checkpoint and pausing at each natural stopping point so the user can run a live demo or test and see the work themselves. Use when starting /forge-implement or the implement step of /forgemaster.
日本語の概要は準備中です。原文の説明を表示しています。
Run quality gates, commit, push, and open a PR with the canonical template. Use when the user runs /ship or wants to ship the current changes.
日本語の概要は準備中です。原文の説明を表示しています。
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern git best practices including Conventional Commits, automated testing, and structured PR creation.
日本語の概要は準備中です。原文の説明を表示しています。
GitHub MCP Server integration for repository operations, pull requests, issues, and GitHub Actions. Triggers on: github mcp, github operations, pull request, issue, repository, github actions, commit, branch, merge.
日本語の概要は準備中です。原文の説明を表示しています。
Code implementation, refactoring, and bugfixes. USE FOR: implementing features; refactoring code; fixing bugs; modifying existing code. DO NOT USE FOR: writing tests (separate skill); documentation (separate skill); commit conventions (separate skill).
日本語の概要は準備中です。原文の説明を表示しています。
Use when standing up a fresh deployment of this codebase (or the public vigyan-site-os template) — populates company identity, branding and starting content without committing any of it, and decides for each value whether it belongs in platform env, encrypted DB secrets, DB config, or an admin screen.
日本語の概要は準備中です。原文の説明を表示しています。
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents
日本語の概要は準備中です。原文の説明を表示しています。
Safe git revert. Roll back phase or plan commits using the phase manifest with dependency checks.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
日本語の概要は準備中です。原文の説明を表示しています。
Create a clean PR branch by filtering out .planning/ commits — ready for code review
日本語の概要は準備中です。原文の説明を表示しています。
Socratic ideation and idea routing — think through ideas before committing to plans
日本語の概要は準備中です。原文の説明を表示しています。
Create or update product-update / release-notes content for a given OpenMetadata/Collate patch version across getcollate, openmetadata-site, and docs-om. Sources getcollate's changelog from openmetadata-collate + OpenMetadata + ai-platform; openmetadata-site's from OpenMetadata only; docs-om reuses openmetadata-site's already-written content, reformatted into its Mintlify snippet structure. Filters to customer-facing changes only, runs each target's own doc-review checklist, verifies every link live, and requires explicit approval before any commit.
日本語の概要は準備中です。原文の説明を表示しています。
AEM Cloud Service expert skill for the Asset Manager API (com.day.cq.dam.api.AssetManager). Covers two migration paths — Path A (create/upload, replacing createAssetForBinary/getAssetForBinary/client-facing createAsset with Direct Binary Access via @adobe/aem-upload) and Path B (delete, replacing removeAssetForBinary with in-JVM resolver.delete() + commit or external HTTP Assets API with IMS bearer tokens). Covers IMS authentication, service-user setup with crx delete permissions, asset processing pipeline, common pitfalls (hardcoded credentials, AEM calling its own HTTP API), and composition with replication/event-migration skills.
日本語の概要は準備中です。原文の説明を表示しています。