'adr' 검색 결과

Simulate concentration changes over time from biochemical models in SBML or Antimony, and compare fixed parameter conditions. Checks model units and exports CSV results plus COMBINE archives containing models and experiment settings, then replays them to compare results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Calculate concentration changes in reaction networks
• Compare baseline and altered kinetic parameters
• Inspect model units and consistency warnings

Review system architecture and major design changes for scalability, resilience, and maintainability. Identify risks, compare design tradeoffs, and document recommendations and next steps across services, APIs, data storage, security, and deployment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing microservice boundaries
• Assessing a move to event-driven architecture
• Comparing serverless and container deployment

Find opportunities to simplify a codebase by hiding complex behavior behind smaller interfaces. Compare candidates in a visual HTML report, then explore the chosen option through questions about constraints, dependencies, and testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding structural improvements in frequently changed code
• Comparing refactoring candidates visually
• Exploring constraints and testing for a chosen candidate

Draft a pull request description from existing project records and verification results. Present the change with a compact visual, before-and-after evidence, rollback details, and its wider impact so reviewers can assess the work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting a pull request description
• Explaining a refactor with a compact diagram
• Presenting existing before-and-after check results

Turn game design and architecture documents into epics, bounded groups of development work for individual modules. Produce scope documents and an index, showing which requirements have recorded design decisions and where guidance is missing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning game designs into module-level development scope
• Planning epics for a specific development layer
• Finding requirements without architecture decisions

Turn existing game code or prototypes into missing design, architecture, or concept documents. Extract implemented rules, formulas, and technical choices, ask about their intended purpose, and clearly separate observed behavior from unconfirmed interpretations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting a feature built without a design document
• Understanding an inherited codebase with missing documentation
• Turning a gameplay prototype into a concept document

Improve MNN's Vulkan backend by separating CPU scheduling bottlenecks from GPU computation costs. It guides operator and shader changes, new feature integration with compatibility fallbacks, and device testing to verify both correctness and end-to-end performance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding CPU or GPU bottlenecks in Vulkan inference
• Optimizing a specific operator or shader
• Integrating cooperative matrix or subgroup features

Turn a development phase into an actionable PLAN.md through research, planning, and verification. The skill can incorporate requirements or recorded design decisions, then check and revise the plan before presenting the results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning the next development phase
• Building a plan from requirements or design decisions
• Researching a phase before planning

Design or review Apache Hudi tables through questions about data volume, updates, and usage. Get architecture recommendations, a decision record explaining tradeoffs, and configuration artifacts for supported processing paths.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing a new Hudi table
• Reviewing an existing table design
• Planning a small prototype

Review a codebase for design friction and compare refactoring candidates in an HTML report with before-and-after diagrams. Then explore a chosen candidate through questions about constraints, module design, and testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find design problems in frequently changed code
• Compare refactoring candidates with diagrams
• Explore constraints and tests for a chosen improvement

Set up the repository settings that engineering skills read: where work is tracked, which triage labels to use, and where domain documents belong. Review existing files and confirm drafts before writing configuration documents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a repository before using engineering skills
• Configure GitHub, GitLab, or local Markdown issue tracking
• Match triage labels to an existing workflow

Review whether a proposal, specification, or design decision addresses the right problem and follows from its goals and constraints. Receive prioritized findings with supporting evidence, confidence, and concrete alternatives or questions that would resolve each concern.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether a proposal addresses the real problem
• Testing a specification against its goals and constraints
• Comparing alternatives and long-term maintenance costs

Coordinate 15 agents implementing claude-flow v3 across security, core systems, integration, testing, performance, and release work. Provides role assignments, task dependencies, GitHub tracking examples, and a four-phase schedule spanning 14 weeks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assign claude-flow v3 work across 15 agents
• Run tasks in parallel while respecting dependencies
• Track milestones and progress through GitHub issues

Plan and implement a unified AgentDB memory backend for agents. Migrate SQLite and Markdown data, add HNSW indexing for similarity search, and support shared memory and SONA learning patterns while preserving compatibility with existing systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Consolidating separate agent memory systems
• Migrating SQLite and Markdown data to AgentDB
• Finding stored information with similar meaning

SUPERSEDED by /claudex-loop (formerly /crucible; its docs-aware mode covers this variant) — prefer that skill unless you explicitly want this one. Two-act plan hardening with living documentation. ACT 1 (you ↔ Claude) — Claude interviews you relentlessly about a plan, one question at a time, challenging it against your project's existing domain model and glossary (CONTEXT.md), sharpening fuzzy terms, stress-testing with concrete scenarios, cross-referencing code, and updating CONTEXT.md + ADRs inline as decisions crystallise. ACT 2 (Claude ↔ Codex) — Claude writes the locked plan to PLAN.md and OpenAI Codex adversarially reviews it in a read-only sandbox (VERDICT:APPROVED/REVISE), Claude revises and re-submits to the SAME Codex session until APPROVED or a MAX_ROUNDS cap, then you sign off before any code. Use when the user says "/grill-with-docs-codex", "grill me against the docs then have codex review", "stress-test this against our domain model then get a second model on it", or is about to build something high-stakes in a project with established terminology/ADRs and wants alignment, documentation, AND a cross-model sanity check. Builds on Matt Pocock's grill-with-docs (MIT). NOT for reviewing already-written code (use /codex:review) and NOT for trivial changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

First-time Archcore setup. Wires the host (MCP config, hooks, CLAUDE.md/AGENTS.md managed block), measures the authored context the repo already holds, then composes a first-day seed — stack rule, run guide, data-model, integrations, config, entry points, public surface, a linked architecture overview, and specs for the top hotspot modules — shown in ONE preview and created on a single confirm. Modes, named as the first word: init import converts the repo's authored context — CLAUDE.md, AGENTS.md, .cursor/rules and other agent instructions, ADR and RFC folders, contributor docs, internal pages of a published docs site, recoverable git history — into native typed documents with no import marks, staged by a plan when the volume is large; init refresh adds facts that appeared since, or drills into one domain with init refresh <domain>. Use on a fresh clone, empty `.archcore/`, 'set up archcore', 'migrate our CLAUDE.md to archcore', 'import our docs and ADRs', or to wire host configs. Not for individual docs or planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build RoadRunner HD Map entities in MATLAB — lanes, boundaries, markings, junctions, signs, signals, barriers, parking. Use when creating driving scenes from scratch, authoring road networks for simulation and testing automated driving systems, or assembling RRHD maps from Lanelet2 or other HD map sources.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert guidance for simulating RoadRunner scenarios via the MATLAB programmatic API and Simulink co-simulation. Use when the user wants to run a simulation, step through a simulation, control actors during co-simulation, add observers, attach sensors, retrieve simulation logs, or read/write scenario variables. Covers simulateScenario, createSimulation, ScenarioSimulation set/get, ActorSimulation getAttribute/setAttribute, addObserver, SensorSimulation, Simulink co-sim blocks, and publishActorBehavior. NOT for project setup, scene building, scenario authoring, or trajectory export.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

System architecture design and review. Use when designing architecture, evaluating microservices vs monolith, writing ADRs, choosing a database, planning for scalability, reviewing system design, or generating architecture diagrams.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Unify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design the idiomatic Elixir architecture for a rewrite: set the compatibility bar (ADR-000), consult phx specialists on open questions, then build contexts, ledger and ADRs. Use after /rewrite:analyze.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Unify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.