'architecture analysis' 검색 결과

Use this skill for all requirements-related work in a MATLAB MBSE project using the Requirements Toolbox (slreq). Covers creating and populating requirement sets, derivation links, test case requirements, verification coverage, reading and tracing links across requirement sets and models, checking link health, allocating requirements to components (Implement links), and building traceability reports. Trigger when the user asks about slreq API, slreqx files, slmx link files, outLinks/inLinks, traceability matrices, coverage analysis, broken links, or mapping requirements to architecture components. Use proactively for any requirements or traceability task.

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

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.

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

Technical decision-making frameworks - trade-off evaluation, reversibility analysis, and second-order thinking for better engineering choicesUse when "should we, which is better, trade-off, decision, choose between, versus, pros and cons, what if we, is it worth, evaluate options, decisions, trade-offs, architecture, adr, reversibility, strategy, planning, risk" mentioned.

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

Measure what matters. Event tracking design, attribution modeling, funnel analysis, experimentation platforms. The complete guide to understanding what your users actually do, not what you hope they do. Good analytics is invisible until you need it. Then it's the difference between guessing and knowing. Use when "analytics, tracking, events, funnel, conversion, attribution, segment, amplitude, mixpanel, posthog, ab testing, experiment, cohort, retention, measure, metrics, analytics, tracking, events, funnel, conversion, attribution, data" mentioned.

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

Threat-model a sensitive design with STRIDE on request. Read-only analysis of threats, controls, and implementation constraints.

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

Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "SEO planning", "content strategy", "keyword strategy", "content calendar", "site architecture", or "SEO roadmap".

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

Analyze card sorting results to inform information architecture and navigation structure. Use after conducting open or closed card sort studies.

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

Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for GEO), content scoring targets, measurement framework, and content differentiation through original research and first-hand experience. Use when user says "blog strategy", "content strategy", "blog positioning", "what should I blog about", "blog topics", "content pillars", "blog ideation".

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

Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts, citation capsule planning, information gain prompts, and multi-channel distribution plans. Briefs are optimized for Google rankings and AI citations (GEO/AEO). Use when user says "content brief", "blog brief", "write brief", "outline blog", "plan blog post", "blog outline", "content outline".

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

Applies the reasoning style of Geoffrey Hinton, deep learning pioneer and 2018 Turing Award winner. Use this skill whenever evaluating AI safety, existential risk, neural network architectures, cognitive science, or tech regulation. Reach for this when the user is discussing LLM capabilities (understanding vs. autocomplete), the biological vs. digital intelligence divide, AI alignment strategies, or the societal/economic impacts of automation. It is highly applicable when dealing with contrarian scientific ideas, hardware/software integration (mortal vs. immortal computing), or global cooperation on technological threats. Do not wait for the user to name Hinton; trigger this skill proactively for any deep learning or AI existential risk analysis.

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

Multi-model agent orchestration using specialized agents for planning, coding, research, math/science, visual analysis, and adversarial review. Use when tasks are complex enough to benefit from different models' strengths, when you want adversarial review to catch blind spots, or when coordinating multi-step workflows across agent roles. Triggers on complex projects, multi-step tasks, architecture decisions, or when explicitly requested.

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

Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability/security/maintainability analysis.

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

Brainstorm solutions with trade-off analysis and brutal honesty. Use for ideation, architecture decisions, technical debates, feature exploration, feasibility assessment, design discussions.

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

Write, restructure, classify, and review documentation with the Diataxis framework. Use when the user asks to create, improve, audit, or reorganize documentation of any kind: knowledge bases, help centers, onboarding guides, process docs, manuals, runbooks, product or API docs, tutorials, how-to guides, references, explanations. Also use when the user mentions Diataxis, docs taxonomy, or documentation architecture, or asks why a document feels confusing. Also use for Simplified Technical English (ASD-STE100) or controlled-language rewrites of English technical docs. Not for marketing, legal, sales, press, or fiction writing unless the user wants a Diataxis-style analysis.

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

Product analyst — metrics architecture, funnel analysis, A/B test design, retention, and growth measurement. Use when asked to "design an A/B test", "analyze the funnel", "define a north star metric", or "measure retention".

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

Systematic departures from rational choice theory and their implications for economic analysis and policy. Covers cognitive heuristics (anchoring, availability, representativeness), biases (loss aversion, status quo, overconfidence), prospect theory (reference dependence, probability weighting, diminishing sensitivity), nudge theory and choice architecture, and the integration of psychological findings into economic models. Use when analyzing decision-making under uncertainty, evaluating policy interventions that exploit behavioral patterns, or assessing where standard rational-agent models break down.

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

Autonomous feature research and gap analysis. Use when starting /add-new-feature or analyzing existing architecture documents. Explores codebase patterns, identifies ambiguities, and produces feature-context-{slug}.md for orchestrator RT-ICA phase. Does NOT make technical decisions.

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

SAM-style feature initiation workflow — discovery through codebase analysis, architecture spec, task decomposition, validation, and context manifest. Use when a user asks to add a feature, plan a feature, or convert an idea into an executable SAM plan.

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

Unified code intelligence — Skeleton Index (zero-dep, <4s) + AST knowledge graph (CodeGraph) + architecture diagrams (Mermaid) + smart context builder. Pre-indexes code structure so AI agents understand any codebase instantly. 95% token compression for onboarding. 30% fewer tokens for deep analysis.

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

Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.

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

Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches, before-and-after security architecture views, engineering tradeoff analysis, or an implementation-ready plan for a selected hardening option. Also use automatically after a Codex Security scan with reportable findings when the top-level scan workflow requests final-report hardening guidance.

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

Structures technology diligence with architecture review, code quality assessment, scalability analysis, and technical debt evaluation. Use when evaluating startup technology, assessing engineering teams, or reviewing technical infrastructure.

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

Generates MkDocs-flavored or standard GitHub-flavored Markdown documentation from codebase analysis findings including API references, architecture guides, standalone markdown files, and change summaries (converted from agent)

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

Explores codebases to find relevant files, trace execution paths, and map architecture with team communication capabilities for collaborative analysis (converted from agent)

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