「architect」の検索結果

Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them. Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets. The field is fragm

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

Build custom AI agents in Claude Code from a user's problem statement. This skill analyzes the user's use case, asks smart clarifying questions, researches the internet for similar agents (GitHub repos, blogs, Claude Code community patterns), and then architects and builds production-ready Claude Code agents — including subagents, skills, hooks, slash commands, MCP integrations, and CLAUDE.md configuration. Use this skill whenever the user wants to create an agent, build an automation workflow, set up a Claude Code subagent, design a multi-agent system, or says things like 'build me an agent for...', 'automate this with Claude Code', 'I want a subagent that...', 'help me create a workflow', 'set up an agent pipeline', or any variation of wanting Claude Code to do something specialized. Also trigger when the user mentions agent architecture, agent SDK, agentic workflows, or task delegation in Claude Code — even if they don't use the word 'agent' explicitly.

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

Digital Garden & Visual Architect. Use this agent to manage the Obsidian Knowledge Base, create visual logic maps via JSON Canvas, and maintain the automated development journal. It bridges the gap between abstract ideas and structured documentation. When the host supports them, use the Obsidian-focused skills and integrations for CLI, Bases, Markdown, Canvas, and defuddling workflows. When the host supports them, use the Obsidian-focused skills and integrations for CLI, Bases, Markdown, Canvas, and defuddling workflows.

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

Use when legacy prompts or older framework flows reference `super-architect` and you need the modern runtime to resolve that capability cleanly.

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

Use when legacy prompts or older framework flows reference `architect` and you need the modern runtime to resolve that capability cleanly.

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

Use when the work needs analytics architecture, event planning, KPI design, attribution boundaries, or instrumentation review across product and growth.

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

Create colorful infographic PNGs from a conversation, topic, file, skill, or workflow. Use when: インフォグラフィック, 図解, 挿絵, 章扉, X投稿用画像, OGP, HTML→PNG, visualize session, poster image. Produces 2-3 self-contained HTML patterns, renders static PNGs, and verifies every image visually before reporting. Not for animated GIFs, architecture/sequence/flow diagrams (editable .drawio or interactive HTML), or HTML slide decks.

Design, review, and debug agent workflows, and decide when a request should use a prompt, instruction, skill, agent, or hook before escalating to multi-agent design. Use for .agent.md / .instructions.md / .prompt.md / AGENTS.md work, workflow architecture, orchestration planning, scheduled automation model allocation, or when agent workflows may be overkill. Triggers on 'agent workflow', 'create agent', 'automation models', 'ワークフロー設計', 'orchestrator'.

Generate draw.io editable diagrams (.drawio, .drawio.svg) from text, images, or Excel. Orchestrates 3-agent workflow (Analysis → Manifest → SVG generation) with quality gates. Use when creating architecture diagrams, flowcharts, sequence diagrams, or converting existing images to editable format. Supports Azure/AWS cloud icons. Triggers on draw.io, drawio, ダイアグラム, アーキ図, フローチャート, シーケンス図.

Create, read, edit, and open draw.io (.drawio) files. Supports architecture diagrams, ER diagrams, flowcharts, domain model diagrams, and more. Use when requests include "create a diagram", "make a flowchart", "draw an architecture diagram", "create an ER diagram", "open a .drawio file", "what's in this diagram?", etc. Do NOT use for Mermaid or PlantUML generation.

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

Super Base Context — project doc loader & synchronizer. Triggers even without explicit "load docs"/"sync docs." READ MODE — load architecture/modules/coding/decision docs when work references project state: code work (write/modify/remove); design (features/APIs/schemas/architecture); review (modules, past solutions); tech selection; ADR research; migration/refactor planning; performance/security analysis; tests; code reviews; any spec/plan/design/ADR referencing project. WRITE MODE — NET DELTA vs. last doc sync: additions/modifications/REMOVALS/deprecations of previously-synced code or decisions (docs revert: delete BCU file/ADR), AND rollbacks. User signals: sync docs/done/ready to commit/pre-commit/record decision. Auto-fires before final task-completion reply. WRITE MODE does NOT fire on: brainstorming, generic/read-only Q&A, in-session try-and-undo with no net change, already-synced.

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

Create and maintain Architecture Decision Records (ADRs) for significant technical choices—frameworks, data stores, API shapes, ML platform decisions. Use when documenting a decision, onboarding, or superseding a prior approach.

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

Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

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

Design component architecture, REST API contracts, and data models (Pydantic schemas) before implementation. Use when planning how to build a feature, defining endpoints, or modeling data. Trigger on "design the architecture", "design the API", "data model", "how should I structure this feature".

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

Map existing business processes using BPMN 2.0 notation or simplified swimlane diagrams. Identify waste, handoffs, decision points, and improvement opportunities using Lean principles (8 Wastes). Use when documenting workflows for SOP creation, automation assessment, or process improvement. Do not use for software architecture diagrams — use architecture tools instead.

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

React Native mobile development patterns - New Architecture (Fabric, TurboModules, JSI), component architecture, React Navigation 7+, FlashList v2 optimization, gestures with Reanimated 4, platform-specific code, React 19 features

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

Generate architecture diagrams as .excalidraw files from codebase analysis. Use when the user asks to create architecture diagrams, system diagrams, visualize codebase structure, or generate excalidraw files.

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

Clean/hexagonal architecture: dependency rules, ports and adapters, layering, and testable boundaries. Use when structuring applications for maintainability and testability.

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

Architect persistent, searchable memory for agents — episodic, semantic, and procedural stores with retrieval, consolidation, and forgetting policies. Use when designing how an agent remembers across sessions.

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

Architect autonomous agent systems — perception/action loops, tool design, planning strategies, memory, and multi-agent orchestration patterns. Use when designing an agent from scratch or scaling a prototype to production.

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

Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.

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

Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.

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

Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.

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

Unity UI/UX pattern design-to-code translation. Screen flow architecture, View/ViewModel separation, HUD architecture, feedback & juice systems, dynamic list/grid views, transition & animation contracts. UI Toolkit only. DESIGN INTENT format: INTENT/WRONG/RIGHT/SCAFFOLD/DESIGN HOOK. Based on Unity 6.3 LTS.

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