「architecture」の検索結果

Autonomous Reforge-guided refactor workflow for the Humans repository. Use when the user wants Codex to target a section such as Shifts, Users, Teams, Tickets, Camps, or Store, create a dedicated worktree/branch from origin/main, run iterative architecture-focused improvements, score each stage with Reforge, gate commits through a score-blind read-only architecture review, append score and verdict details to commit messages after review acceptance, push progress, and open a PR when the loop reaches stasis.

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

Autonomous themed tech-debt cleanup. Reads docs/architecture/debt-ledger.yml, rotates to the least-recently-served debt theme, works it for a time budget (default 2h) or until drained, opens one PR, and asks judgment questions inline at the end. Use for daily debt burndown without Peter pointing at a target: grandfathered analyzer rules, architecture-test baselines, obsolete-field reads, cross-section stitching.

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

アーキテクチャ決定会議。技術選定・設計方針・構成変更を多角的に検討し、ADR(Architecture Decision Record)として出力する。「アーキ会議」「技術選定して」「設計会議」「どっちの構成がいい」「ADR書いて」などのリクエストで使用。

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.

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

Generate Mermaid diagrams from code, architecture, or concepts. Use when you need to visualize code flow, system architecture, data relationships, state machines, sequences, class structures, or any other diagrammable concept.

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

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

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

Validate process decomposition and architecture design quality before execution begins. Load when the setup-evaluator agent fires (automatic for agent-chain tasks), or when user says "evaluate this setup", "check the decomposition", "validate the architecture", "is this plan sound", "review the agent design". Catches structural errors, missing knowledge, unrealistic step ordering, and topology mismatches. Does NOT modify — only evaluates.

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

Design state-of-the-art multi-agent systems, orchestration patterns, and wiring from scratch. Load when the user asks to build an agent system from scratch, design agent orchestration patterns, choose between sequential/parallel/hierarchical workflows, or define how multiple agents should collaborate. Also triggers on "agent architecture", "multi-agent wiring", "agent orchestration pattern", "how to connect these agents", "design the communication structure". Called by agent-builder for complex topologies (>4 agents or hierarchical). For process-driven agent design, use agent-builder instead.

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

Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.

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

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

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

Frontend stack decisions, Cloudflare deployment patterns, component systems, and internal tools architecture. Use for framework selection, deployment strategy, design system bridging, shadcn setup. Activate on "frontend architecture", "tech stack", "Cloudflare Pages", "component library", "internal tools", "shadcn setup". NOT for writing CSS (use frontend-developer), design critique (use design-critic), or backend APIs.

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

Master of text-based visual communication using ASCII art, Unicode box-drawing, and structured diagram notation. Creates clear, maintainable diagrams for systems, processes, hierarchies, relationships, and psychological structures. Proactively generates diagrams to enhance understanding. Activate on visualization needs, system architecture, process flows, psychological mapping, or when complex concepts would benefit from visual representation. NOT for photo editing, vector graphics, or GUI-based design tools.

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

Treat tokens as a coding swarm's cost-of-goods-sold and legibility engine while accounting for finite subscription allowance when per-call price is unknown. Covers provider windows, remaining-usage evidence, burn forecasts, preemptive checkpoint/model switching, per-agent budgets, compaction, shared digests, context degradation, and spend metering. Activate on: "token budget", "context budget", "compaction strategy", "briefing as compression", "context rot", "summarization collapse", "COGS for agents", "subscription usage remaining", "five-hour or weekly limit", "burn forecast", "model switch before limit", or "/context-economics-for-agent-swarms". NOT for: memory architecture (use always-on-agent-architecture), single-prompt wording (use prompt-engineer), mechanism-design proofs (use nisan-et-al-2007-algorithmic-game-theory), physical containment (use sandboxed-adversarial-test-harness), or production rebodiment and fencing (use agent-resurrection-and-body-continuity).

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

Architecture-level decisions for putting a CDN in front of a web app's static assets, API responses, and file/media delivery: provider selection (hyperscaler vs. specialist $/GB), signed-URL / tokenized access for gating private content at the edge, cache invalidation strategy (versioned URLs vs. purge APIs), origin shield / tiered caching for high-miss-rate content, and CDN-layer geo-restriction. Use when deciding which CDN to put in front of a new or growing service, when private/paywalled files need edge delivery without an origin round-trip per request, or when purge/invalidation behavior is being designed rather than debugged. NOT for HTTP cache-control header syntax, Vary, stale-while-revalidate, or surrogate-key purge mechanics (see `cdn-cache-control-headers`); NOT for Cloudflare-specific product configuration once Cloudflare is already chosen (see `cloudflare`); NOT for video-specific transcoding, adaptive bitrate ladders, or streaming-protocol packaging (see `managed-video-streaming-pipeline`).

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

Apply Conway's homomorphism principle to multi-agent system design, recognizing that agent coordination structure predetermines system architecture and capability.

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

Expert API designer for REST, GraphQL, gRPC architectures. Activate on: API design, REST API, GraphQL schema, gRPC service, OpenAPI, Swagger, API versioning, endpoint design, rate limiting, OAuth flow. NOT for: database schema (use data-pipeline-engineer), frontend consumption (use web-design-expert), deployment (use devops-automator).

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

How to design contextual inputs for an always-on AI agent with episodic memory. Covers what data to feed the agent, how to structure observations and triggers, ambient context capture (screen, audio, calendar), context window budgeting, and retrieval strategies that keep the agent grounded in what's actually happening. Activate on: "what should the agent observe", "context inputs for agent", "ambient context capture", "agent triggers", "agent input design", "screenpipe integration", "context window budget", "what data to feed my agent", "/always-on-agent-inputs". NOT for: memory architecture and storage (use always-on-agent-architecture), application ideas (use always-on-agent-applications), safety concerns (use always-on-agent-safety).

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

Design bounded applications and workflows for an always-on AI agent with episodic memory. Covers product ideas, persistence-dependent workflows, and constructed examples that make delegation, interruption, evidence, and opt-out explicit. Activate on: "what can an always-on agent do", "persistent agent use cases", "agent applications", "proactive agent ideas", "what to build with episodic memory", "always-on agent product", "personal AI assistant ideas", "/always-on-agent-applications". NOT for: building the architecture (use always-on-agent-architecture), designing inputs (use always-on-agent-inputs), safety and privacy (use always-on-agent-safety).

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

Declare an agentic application's interaction disclosure, state, context, capabilities, and effect-control boundaries. Use for a reviewable design specification and static consistency audit before implementation. NOT for proving that controls are deployed or enforced, exposing private chain-of-thought, selecting a model/router, or designing a multi-agent protocol.

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

Safety-case design for always-on agents with episodic memory. Covers data hygiene, privacy and security risk surfaces, cost controls, scope, user dependency concerns, retention, incident containment, and responsible deployment evidence. It identifies hazards and asks for named controls, tests, owners, and residual uncertainty; it does not provide legal, clinical, youth-safety, or jurisdictional determinations. Activate on: "agent safety", "always-on agent privacy", "agent cost control", "persistent agent risks", "AI companion safety", "agent data hygiene", "runaway agent costs", "parasocial AI risk", "/always-on-agent-safety". NOT for: architecture design (use always-on-agent-architecture), input design (use always-on-agent-inputs), application brainstorming (use always-on-agent-applications), healthcare compliance specifically (use hipaa-compliance).

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

SERP-based semantic topic clustering for content architecture planning. Groups keywords by actual Google SERP overlap (not text similarity), designs hub-and-spoke content clusters with internal link matrices, and generates interactive visualizations. Optionally executes content creation if claude-blog is installed. Use when user says "topic cluster", "content cluster", "semantic clustering", "pillar page", "hub and spoke", "content architecture", "keyword grouping", or "cluster plan".

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

Retired pointer for Next.js SSR doctrine. Use when something references nextjs-ssr-architecture; read the ssr-zero-layout-shift skill instead.

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

Guide the user through starting a new web application project — elicit requirements (MoSCoW scoping), create architecture and requirements documents, break work into tasks, and register them as a GitHub Project kanban board. Use when the user says "新しいWebアプリを作りたい", "Webアプリの立ち上げを手伝って", "start a new web app project", "プロジェクトの要件を整理したい", or "GitHub Projectにタスクを登録したい".

This skill should be used when the user asks to "プロジェクトを解析して", "コードベースを調べてドキュメント化して", "移行作業の準備をして", "新機能実装の前にプロジェクトを整理して", "analyze this codebase", "document the project structure", "既存プロジェクトのCLAUDE.mdを作って", or wants to prepare CLAUDE.md and architecture docs before a migration, feature development, or onboarding.