Dev Studio

Start here — clarify what you want, then route into the right studio workflow across the full lifecycle (build → ship → accept → promote)

Show the current state of the studio's Build → Ship → Accept → Promote lifecycle — active workflow/stage, last verdict, blockers, next action

Dispatch one dev-studio role directly — /dev-studio:agent <role> <task> delegates the task to that specialist (planner|engineer|reviewer|operator|e2e-tester|marketer|coordinator), skipping the workflow gates

Run a dev-studio workflow by name — /dev-studio:workflow <name> <input> routes to deliver-service | ship-service | accept-service | promote-service (same as the /dev-studio:workflows:* commands)

Deliver a service end to end — plan, build (backend + frontend + tests) from the scaffold, then adversarial code + security review, packaged for sign-off

Turns a short service request into a service contract with binary, testable acceptance criteria, scoped to the team scaffold repo (github.com/aws300/scaffold). Use at the START of a workflow to convert a 1–4 sentence ask into the contract the engineer builds against and the reviewer grades against. Not for implementation — it scopes and defines "done" (use the engineer for the build).

Implements a service against the approved contract — proto-first ConnectRPC backend (Go/Python), SolidJS frontend, and tests — by following the scaffold repo's own scripts and CI. Use AFTER the plan is approved. It builds, then hands off to the reviewer; it does NOT self-evaluate and does NOT advance on a FAIL.

The adversarial Evaluator — its job is to FIND FAILURES, not confirm success. Use to challenge the plan before a build (APPROVE/REVISE), the build after the engineer finishes (PASS/FAIL), the release before ship (GO/NO-GO), and the promo materials for accuracy (GO/NO-GO). Verifies against the scaffold repo's own CI gates. The single most important role for output quality.

Packages a reviewed service for the team's Kubernetes cluster and wires it into the running platform — Helm release, Envoy route, IRSA, and observability against the cluster's existing Prometheus/Loki/Tempo/Grafana — following the scaffold repo's deploy scripts and CI. Use after delivery. It produces a staged deploy + rollback plan and observability config; the live deploy stays a human action.

A BLACK-BOX acceptance Evaluator. It NEVER sees source code — given only the deployed product URL, API base URL, and Grafana URL, it exercises them with a browser and HTTP/API tools and judges UI consistency, API consistency + stability, cloud-native observability coverage, and log coverage. Use to accept a DEPLOYED service. Issues a scored PASS/FAIL; FAIL loops back to the engineer (UI/API/log) or operator (observability).

个人知识库（Obsidian wiki vault）的唯一入口与控制面：记录、调研、蒸馏、摄入、查询、维护、可视化、自动化，一站式覆盖。 Use this skill whenever the user wants to interact with their wiki / knowledge base / second brain / notes in any way — 写入或读取都走这里。触发词包括但不限于："wiki", "记到 wiki", "帮我记录今日笔记/工作日志", "帮我记录会议纪要", "记一下今天做了什么", "帮我调研某个 URL / 调研一下 X", "记录一下这个客户沟通", "帮我写周报/月报", "整理成文档存到 wiki", "把最近的笔记蒸馏一下 / 提炼知识 / 整理成概念页", "ingest 这些文档/PDF/网页", "导入我的 Claude/Codex 对话历史", "我知道关于 X 的什么 / 查一下 Y", "audit/lint 我的 wiki / 找坏链孤儿页 / 健康检查", "补交叉引用 / 归一标签 / 查重合并", "wiki 状态/进度", "导出图谱 / 着色 / 建仪表盘", "初始化/重建 vault", "设置定时任务/自动维护/自动周报", "log this", "record today's work", "research this url and save it", "distill my notes", "query my wiki", "lint/audit my wiki", "ingest these docs", "set up a cron for my wiki", "请使用 skill wiki 管理/处理这个文档" (bind an attached document as the vault). 它把零散口语扩写成专业中文文档并 归档（日报/周报/月报、会议纪要、技术调研、日记），自动滚动汇总，蒸馏 journal/_raw 为知识页，并通过内置 框架手册覆盖 obsidian-wiki 的全部 AI 能力（ingest/query/lint/cross-link/dedup/export/research/history-ingest/ dashboard/rebuild 等）。vault 通过 .config/skills/wiki/wiki.json 绑定（先查 cwd，再查 ~），可关联任何本地 git 目录或 AgentX 附加的 Library 文档；每次写完自动同步（git commit & push，或 AgentX 内走 save_document）。

Acceptance-test a deployed product as a black box — drive the live UI and API, then verify observability and logs in Grafana — judging UI consistency, API consistency + stability, observability coverage, and log coverage WITHOUT seeing source. Use by the e2e-tester. Triggers on "acceptance test", "e2e test the deployed product", "is the live service correct", "black-box test".

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Build a service from the team scaffold (github.com/aws300/scaffold) — proto-first ConnectRPC backend (Go 1.26 / Python 3.13) + SolidJS frontend — by following the repo's OWN scripts and CI rather than re-explaining the stack. Use when: implementing a new service or feature, regenerating proto stubs, or running the local build/lint/test loop before review. Triggers on "build the service", "implement the backend", "scaffold", "regenerate protos", "make the frontend". Not for: deploy/Helm packaging (use deploy-pipeline) or black-box acceptance (use webapp-testing).

Produce a search-driven, multi-dimension market assessment for a shipped product — comparable products, competitive positioning, market dimensions, and recommended go-to-market directions, every claim cited. Use by the marketer. Triggers on "market assessment", "who are the competitors", "comparable products", "market positioning", "go-to-market".

5 hooks across 5 events