'code graph' 검색 결과

Read frontend source code to document colors, typography, spacing, components, and layout rules in DESIGN.md. Use it to understand an existing interface or prepare design guidance for Stitch without building or running the app.

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

• Document an existing app's design system
• Review styling when the app cannot run
• Prepare an existing visual identity for Stitch

Run Python through the shell when a code sandbox fails to start or connect. Uses a heredoc, a way to pass multiline code, with examples for generating charts, Word documents, and processed JSON files.

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

• Continue Python work when the code sandbox is unavailable
• Create a graph image from Excel data
• Generate a Word document with headings and a table

Generates cryptographic test vectors, inputs with expected outcomes, by deliberately changing implementation code and finding changes existing tests miss. Verifies new vectors across independent implementations and compares detection rates before and after adding them.

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

• Finding coverage gaps in cryptographic test vectors
• Creating invalid inputs that exercise validation checks
• Building test vectors shared across independent implementations

Analyze code structure with Trailmark to identify complex functions, trace input flow, assess impact across connected code, and locate privilege boundaries. The resulting JSON provides detailed evidence for deciding where to focus a code audit.

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

• Prioritizing code audit targets
• Tracing input flow and assessing impact
• Inspecting unresolved calls and type references

Turn cryptographic code or specifications into sequence diagrams showing who sends each message, which cryptographic operations occur, and where failures stop the exchange. Outputs include Mermaid source, a plain text diagram, and a protocol summary.

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

• Visualizing handshake and key exchange steps
• Extracting message flows from RFCs and papers
• Diagramming ProVerif or Tamarin models

Inspects compiled instructions and bytecode to identify timing risks in cryptographic code. Helps trace flagged operations back to secret data, distinguish false positives, and review fixes across compiler settings and target architectures.

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

• Reviewing signing and encryption routines
• Checking division involving secret values
• Inspecting authentication tag comparisons

Build or update a Figma design system from existing code. Organize shared colors, spacing, and typography, create reusable components with states and theme bindings, document their use, and check differences between the implementation and Figma.

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

• Building a Figma component library from existing code
• Organizing shared settings for light and dark themes
• Creating a button with variants and variable bindings

Find API patterns and examples for coding agents with ADK, the Agent Development Kit. Covers tools, state, callbacks, multi-agent coordination, and graph workflows, with Python and Go references plus guidance on studying existing implementations.

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

• Adding tools and callbacks to an ADK agent
• Implementing state management and agent coordination
• Designing branching and parallel graph workflows

Build forms with Formik and yup, a library for defining input validation rules. Apply field errors, submission feedback, edit detection, and step-specific validation to login screens, editing forms, and forms split across multiple steps.

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

• Building login and registration forms
• Adding conditional input validation
• Editing existing records with change detection

Guide a bug bounty investigation from scope checks and asset discovery to vulnerability testing, impact validation, and report writing. Covers web applications, source code, and AI features, with an emphasis on reproducible evidence of real harm.

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

• Planning an investigation for a new bug bounty target
• Reviewing source code for risky implementation patterns
• Testing web and AI features for security flaws

Analyze relationships between people, objects, or papers as networks in Python. Use NetworkX to find shortest paths, identify important nodes and communities, visualize connections, exchange graph data, and generate sample networks for testing.

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

• Visualizing social relationships or paper citation networks
• Finding shortest paths through a network
• Identifying important nodes and closely connected groups

Use whenever the agent needs to add, create, hand-author, patch, or place Motion Graphic JSX assets in a OpenChatCut project. This is the direct-authoring path: use create_motion_graphic_from_code / edit_asset / edit_item, not motion-graphic-gen or submit_motion_graphic. Covers project/timeline intake, project visual language, editable properties, asset binding, inline JSX authoring, existing asset updates, timeline placement, and verification.

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

Query the local code graph (functions, classes, calls, imports) through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what's the architecture / which subsystems exist?", "what's the impact of changing this?". The graph is an AST-derived map of the repo, queried as files (no build needed — it rebuilds automatically).

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

Query the local code graph (functions, classes, calls, imports) through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what is the architecture / which subsystems exist?". The graph is an AST-derived map of the repo, queried as files (no build needed — it rebuilds automatically).

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

将 CodeGraph 作为默认内置 MCP-backed 代码图谱能力接入，用于 brownfield 符号搜索、 调用链、影响面和上下文查询。输出必须回落到 `/team-*` 主链和 artifacts。

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

PROACTIVELY query the code graph database to understand relationships and impact of changes. Use this skill WHEN READING any file to understand context, when searching for files, when exploring the codebase, or when you need to understand what depends on a component. This is your primary tool for understanding code structure and avoiding breaking changes.

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

Decision protocol for building, debugging, and operating LangGraph-based agent systems. Activates when a coder agent is asked to design a stateful LLM workflow, add human-in-the-loop, choose a multi-agent pattern (supervisor / swarm / hierarchical), pick a checkpoint backend, or migrate a fragile chain into a durable graph. LangGraph is positioned by its maintainers as a "low-level orchestration framework for building, managing, and deploying long-running, stateful agents" — this skill encodes the *when* and *why*, not the API.

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

Query patent bibliographic (catalog) information from the Nexscope patent database by patent ID or publication number. Triggered when users mention patent bibliographic info queries, patent catalog information, patent applicant queries, patent inventor queries, patent classification codes, patent abstract retrieval, patent citation analysis, patent priority claims, patent application citations, patent examiner information, patent bibliographic data, inventor lookup, applicant lookup, patent classification, patent metadata, Nexscope, or patent citations. Even if the user does not explicitly mention "bibliographic info," this skill should be triggered whenever their need involves querying detailed metadata for a specific patent by patent ID or publication number.

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

Audit existing typography in a codebase — find inconsistencies, hardcoded sizes, and hierarchy gaps. Use when asked to "audit our typography", "find hardcoded font sizes", or "our type is inconsistent".

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

Deterministic Software Graph analysis via Ontoly CLI and MCP. Use when: (1) Codebase architecture, dependency, route, service, module, configuration, or impact questions need graph evidence, (2) A repository should be analyzed before source search, (3) You need a persistent SoftwareGraph.json for validation, MCP, or agent workflows. Triggers: "build software graph", "trace route", "impact analysis", "architecture summary", "dependency graph", "what uses this", "Ontoly".

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

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

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

Use when needing global or relational understanding of codebases or knowledge corpora. Keywords: GraphRAG, knowledge graph, entity extraction, community summarization, graph traversal, Microsoft GraphRAG.

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

Generate proper ENCODE citations for publications, grants, and presentations. Use when the user needs to cite ENCODE data, create bibliography entries, write acknowledgment sections, or ensure compliance with ENCODE data use policy.

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

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

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