「developer-experience」の検索結果

JP's signature red-team pass — "how would I break this?" Argue against your own approach before proceeding. Trigger on any high-stakes decision, architecture choice, or before marking work complete.

日本語の概要は準備中です。原文の説明を表示しています。

Architecture decisions, trade-off analysis, and ADR authoring. Trigger when a significant technical decision needs to be made, documented, and owned — not when an implementation detail needs a choice.

日本語の概要は準備中です。原文の説明を表示しています。

Review gate for correctness, reuse, and simplification. Produces a structured verdict with actionable findings. Trigger on any PR before merge, or on any agent-generated code before it is committed.

日本語の概要は準備中です。原文の説明を表示しています。

Measure, root-cause, fix, verify and record performance contention on a developer machine: cloud-sync daemons (iCloud Drive, OneDrive, Dropbox, Google Drive), file indexers, AI-tool MCP server fleets, and automation browsers left behind by tests and browser skills. Trigger when the machine is slow, apps freeze, browser or MCP tool calls time out, load exceeds the core count, or before and after any UI/UX/performance test run. Includes the L0–L4 optimisation scale and the test-hygiene contract.

日本語の概要は準備中です。原文の説明を表示しています。

Force plan, HLD, ADRs, and constraints to exist BEFORE any code is generated. Trigger when starting a new feature, epic, or significant change.

日本語の概要は準備中です。原文の説明を表示しています。

Go / no-go gate before any deployment. Checks failure modes, rollback plan, cost, production bar, and definition of done. Trigger before releasing to any environment that carries real consequences.

日本語の概要は準備中です。原文の説明を表示しています。

Govern the SemVer release process — versioning discipline, tag-based GitHub releases, changelog hygiene, and the ADR that confirms the release strategy is agreed. Trigger when setting up a release process, before a first public release, or when release practice has become inconsistent. Owned by delivery-orchestrator.

日本語の概要は準備中です。原文の説明を表示しています。

Pursue an agreed goal to a working outcome without waiting: decompose it, re-prioritise as evidence arrives, branch, gate, get an independent review (a different model or a fresh reviewer subagent — the writer never approves), merge, prune, and bank the operator's decisions in STATUS.md instead of blocking on them. Trigger on "get it done", "don't wait for me", "proceed autonomously", or when an epic or roadmap objective is handed over. Not a close-out: this work set is expected to grow.

日本語の概要は準備中です。原文の説明を表示しています。

Govern discovery, eligibility, and submission of a plugin or skill to official directories, registries, marketplaces, and curated GitHub lists. Use when preparing or sending plugin listings, marketplace forms, directory PRs, or repository recommendations; require current policy evidence and a final human confirmation before every external submission.

日本語の概要は準備中です。原文の説明を表示しています。

GStack developer-experience plan review for setup, local commands, docs, test loops, onboarding friction, and maintainability before implementation.

日本語の概要は準備中です。原文の説明を表示しています。

GStack developer-experience review for implemented repositories and workflows, focused on setup friction, command reliability, docs gaps, and maintainability.

日本語の概要は準備中です。原文の説明を表示しています。

GStack autoplan method for running a broad CEO, design, engineering, and developer-experience review before opening implementation windows.

日本語の概要は準備中です。原文の説明を表示しています。

Expert en platform engineering (developer experience, IDP, golden paths, self-service, métriques)

日本語の概要は準備中です。原文の説明を表示しています。

API business builder — Developer experience, rate limits, docs, billing, usage analytics

日本語の概要は準備中です。原文の説明を表示しています。

Expert en playgrounds d'agents IA (tests interactifs, mode debug, exécution pas-à-pas, logging)

日本語の概要は準備中です。原文の説明を表示しています。

Expert en documentation d'agents IA (README, API docs, exemples d'usage, troubleshooting, changelog)

日本語の概要は準備中です。原文の説明を表示しています。

Chooses and designs developer surfaces for an agentic product: SDK, CLI, MCP, GUI, API, webhooks, and pd tube-style listener/sender workflows. Use when deciding why a user belongs in an SDK versus CLI/MCP/GUI, planning Python SDK parity, or making agent invocation easy across languages. NOT for implementing the full SDK, generic API docs, or UI visual design.

日本語の概要は準備中です。原文の説明を表示しています。