本文へ移動
cccskills
無料GitHub で公開

dev-architecture-playbook

Route full software-development architecture work from product intent through design, implementation, testing, release, and operations. Use when the user asks for a complete development architecture, wants to know which Spellbook skills to combine, needs an execution path across PRD/spec/API/data/security/performance/release/SRE, or asks to turn an idea or repo into a production-ready engineering plan.

majiayu000/spellbook
インストール方法を見る

含まれるファイル（2）

  • SKILL.md3.3 KB
  • agents/openai.yaml239 B

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Dev Architecture Playbook

Purpose

Use this as the lifecycle router before starting broad product or architecture work. It chooses the minimum useful skill chain, defines gates, and prevents starting implementation before the required contracts exist.

Route

Classify the request first:

RequestPrimary SkillsOutput
Idea, product direction, or market/user problemproduct-discovery, prd-masterProduct brief, user stories, success metrics
Architecture or module boundariesarchitecture-foundation, technical-spec, elegant-architectureArchitecture spec, boundaries, rejected alternatives
API, auth, data, or schema contractapi-design, auth-security, database-patterns, data-contract-migrationsVersioned contracts and migration plan
UI/product surfacefrontend-design, ui-ux-pro-max, ui-design-system, playwright-automationUX flow, component plan, visual checks
Implementation workflowflowguard, threads, systematic-debugging, comprehensive-testingBounded execution, ownership, root-cause debugging, and verification
Quality and regression riskcomprehensive-testing, codebase-audit, vibeguard, project-health-auditorTest matrix and risk list
Release and operationsrelease-engineering, config-secrets-environments, performance-capacity, incident-slo-runbook, observability-sre, devops-excellenceRollout, config, capacity, SLO, runbook

Required Gates

Do not treat the architecture as complete until these gates are explicit:

  1. Goal and non-goals.
  2. Domain model and ownership boundaries.
  3. External API, data, and config contracts.
  4. Security and permission model.
  5. Test strategy with command-level verification.
  6. Release, rollback, and migration gates.
  7. Observability, SLO, and incident response.

If a gate is irrelevant, state why. Do not silently skip data, security, or rollback gates for production systems.

Execution Pattern

Use this sequence for greenfield or major refactors:

  1. Product: write the product brief or PRD.
  2. Architecture: define modules, runtime boundaries, and tradeoffs.
  3. Contracts: define API, data, config, and security contracts.
  4. Plan: split work into independently verifiable steps.
  5. Implement: use one workflow skill per step, not every skill at once.
  6. Verify: run build, typecheck, tests, and focused behavioral checks.
  7. Release: define rollout, migration, rollback, monitoring, and support owner.

For existing repos, start with repo-agent-context-audit or codebase-audit before proposing new structure.

Output Shape

Return a compact plan:

goal:
context:
selected_skill_chain:
architecture_gates:
implementation_steps:
verification_commands:
release_and_ops_gates:
open_risks:

Prefer the smallest chain that covers the risk. Too many skills at once usually means the scope needs to be split.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

agentsmd-optimize

無料

Audit and organize AI coding-agent instructions, including AGENTS.md, CLAUDE.md, skills, and agent definitions. Use when the user asks to diagnose conflicting instructions, excessive approval pauses, broad skill triggers, duplicate guidance, or broken instruction references, or to clean up that instruction set. Ordinary code review, Markdown editing, or application debugging alone does not trigger this workflow. Inspection stays read-only; apply changes when authorized.

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

majiayu000/spellbook2872026年10月8日 更新

agentsmd-scaffold

無料

Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.

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

majiayu000/spellbook2872026年10月8日 更新

api-design

無料

REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.

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

majiayu000/spellbook2872026年10月8日 更新

app-ui-design

無料

Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.

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

majiayu000/spellbook2872026年10月8日 更新

app-user-story-qa

無料

End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.

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

majiayu000/spellbook2872026年10月8日 更新

architecture-foundation

無料

Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.

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

majiayu000/spellbook2872026年10月8日 更新

majiayu000 のスキルをすべて見る

このスキルの問題を報告する