「system」の検索結果

Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.

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

25 real-world system design case studies condensed from Alex Xu's System Design Interview Vol 1 and 2 - requirements, architecture, deep dive insights, key takeaways

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

Advanced architecture stress analysis methodology for designing systems that survive unknown stresses. Load when --residuality flag is used or when designing high-uncertainty, mission-critical systems.

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

Designs system architecture with C4 diagrams and technology selection. Routes to the right architect based on design scope (system, domain, application, or full stack). Two interaction modes: guide (collaborative Q&A) or propose (architect presents options with trade-offs).

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

Defines measurable architecture drivers and constraints before system design; edits architecture docs only.

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

Designs target system boundaries, contracts and tradeoffs from requirements; does not plan tasks or implement.

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

Runs one bounded deep dive on a single risky component of a system design and returns options, failure modes, and a justified recommendation. Use during a design session when a component needs expert depth beyond the main thread's budget.

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

Enforce Design Language System adherence in Flutter. Use when implementing design tokens, preventing hardcoded colors/spacing, or building a DLS.

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

Research a codebase and create architectural documentation describing how features or systems work. Use when the user asks to: (1) Document how a feature works, (2) Create an architecture overview, (3) Explain code structure for onboarding or knowledge transfer, (4) Research and describe a system's design. Produces markdown documents with Mermaid diagrams and stable code references suitable for humans and AI agents.

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

Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.

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

Dynamic model selection based on task complexity scoring. Replaces static model mappings with a weighted signal system that picks Opus, Sonnet, or Haiku-class speed per task. Works with agent-assignment-matrix.md.

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

Self-healing codebase system. Monitors runtime errors, test failures, and build breaks. Automatically diagnoses root cause, generates fix, validates fix, and applies if safe. Zero human intervention for routine failures.

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

Store a learning, pattern, or decision in the memory system for future recall.

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

Self-evolving skill system. Skills are scored after execution (0-100) on 5 dimensions. Score 90+ over 5 runs = crystallized (locked). Score below 30 = auto-repair attempted. Skills improve themselves through usage feedback.

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

Query the memory system for relevant learnings from past sessions using semantic search.

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

Agent reputation scoring, performance tier system, trust calibration, and task affinity matching

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

Persistent planning system with 3 markdown files (PLAN.md, PROGRESS.md, CONTEXT.md). Use when starting large features, multi-session work, or complex refactoring. Auto-tracks commits in PROGRESS.md.

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

System health check (MOT) for skills, agents, hooks, and memory

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

Use this skill when visual quality and design identity matter for a PDF. CREATE (generate from scratch): "make a PDF", "generate a report", "write a proposal", "create a resume", "beautiful PDF", "professional document", "cover page", "polished PDF", "client-ready document". FILL (complete form fields): "fill in the form", "fill out this PDF", "complete the form fields", "write values into PDF", "what fields does this PDF have". REFORMAT (apply design to an existing doc): "reformat this document", "apply our style", "convert this Markdown/text to PDF", "make this doc look good", "re-style this PDF". This skill uses a token-based design system: color, typography, and spacing are derived from the document type and flow through every page. The output is print-ready. Prefer this skill when appearance matters, not just when any PDF output is needed.

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

Use this skill when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks. Provides a durable notepad that survives compaction and lets any agent pick up exactly where the previous context left off.

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

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

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

Email delivery infrastructure - DNS authentication (SPF/DKIM/DMARC), subdomain isolation, provider abstraction, template systems, bounce handling, warmup strategy, and deliverability monitoring.

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

Design system token management, component API design, Storybook, and visual regression testing patterns

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

Use this skill when making any factual claim about the codebase — existence, absence, or behavior. Converts the claim-verification rule into a systematic action protocol that prevents false assertions from grep-only results.

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