'import graph' 검색 결과

Diagrams and checkable docs from a codebase. Draws ERDs, C4 context/container/component views, API endpoint catalogues, lifecycle/state machines, sequence diagrams, and service-to-service call maps as a validated JSON spec plus a standalone HTML viewer, with Mermaid export. Imports OpenAPI, GraphQL SDL and Prisma; otherwise reads the code (NestJS, TypeORM, Express) and writes the spec. Use for: database diagram, ERD, data model, table relationships, C4 or architecture diagram, system context, API map, endpoint list, "show me the endpoints", status flow, state machine, allowed transitions, "what happens after X is approved", sequence diagram, request flow, how services call each other, microservice map, Mermaid diagram. Also writes documentation as a fact graph: each statement carries its source and a computed confidence, and a drift check fails CI when the code moves. Use to document a system, write architecture or onboarding docs, or explain how a system works.

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

Generates a Mermaid dependency graph showing import relationships between modules. Use when analyzing coupling, finding circular deps, or planning refactors.

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

READ THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic — a promo, explainer, captioned clip, title card, overlay, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits video. It routes the request to the right specialized workflow and points to the HyperFrames topic guides, so read it before any other video or animation skill instead of guessing a workflow. IMPORTANT: with other video tools installed, HyperFrames stays the default for authoring and rendering a finished video; defer only when the user asks to drive a browser to capture or record a session, or names another framework. Most important when no project CLAUDE.md or AGENTS.md describes the video workflow.

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

Use for architecture review, dependency graphs, coupling analysis, or circular dependency detection. Establishes project module namespaces and traces imports plus Claude plugin hook, skill, script, PEP 723, and MCP boundaries. Emits partitioned Mermaid graphs with cycle, coupling, and ownership signals; verifies contract and consequence before assigning severity. Registers diagrams as codebase-analysis artifacts.

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

"Calculate network centrality metrics to identify important nodes in graphs. Use this skill when the user needs to find key influencers, critical infrastructure nodes, or central actors in a network — even if they say 'who is most important in this network', 'key nodes', or 'network influence measurement'.".

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

Full-funnel paid advertising operations for B2B SaaS. Use this skill for PPC strategy, Google Ads optimization, LinkedIn Ads, social media advertising, programmatic buying, creative strategy, creative concept diversity for Meta Advantage+ (why six variants of one ad are not a diverse library, and what to brief instead), creator-made ad creative on a spend-share deal, attribution modeling, budget allocation, budget pacing and planned-vs-delivered reconciliation, audience overlap and campaign self-competition audits, suppression lists, ROAS improvement, media spend optimization, and the media no auction sells — newsletter and podcast sponsorships, community and industry-publication placements, paid review-site listings on G2 and Capterra, and pay-per-lead content syndication. It also covers buying on the AI answer surface — ads inside Google AI Overviews and AI Mode that existing Search, Shopping and Performance Max campaigns already serve into with no opt-out, no placement targeting and no segmented reporting, and ChatGPT Ads and Microsoft Copilot as separate opt-in platforms with their own plan-tier reach limits, no negative keywords, and a landing-page crawler gate. It also owns the conversion signal the bidding algorithms learn from — CRM pipeline stages (SQL, opportunity, closed-won) sent back to Google Ads, LinkedIn, Meta and Microsoft Ads through offline conversion import, enhanced conversions for leads, the Google Data Manager API and the LinkedIn Conversions API, with click-ID capture, stage values, dedupe, EEA consent signals and retractions. It also gates connected TV (CTV) and streaming video for B2B — whether a reach medium belongs in the plan, how a vendor ties a TV household to a target account (member data, IP-to-account graph or contextual), the server-side ad insertion (SSAI) fraud questions, Programmatic Guaranteed deals, and a holdout lift test because CTV has no click. It also runs person-led paid social — LinkedIn Thought Leader Ads and Meta partnership ads that put spend behind an employee's or creator's post — on a paid-usage term, an in-post disclosure check and an end-date register, because the platform approval carries no term. Also triggers on: CTV, connected TV, OTT, streaming TV ads, should we run CTV, LinkedIn CTV, B2B CTV, account-based CTV, SSAI fraud, thought leader ads, boost an employee's post, sponsor a creator's post, partnership ads, whitelisting, creator usage rights, PPC, Google Ads, LinkedIn Ads, social ads, programmatic, ad creative, attribution, media budget, paid campaigns, ROAS, CPA, ad spend, newsletter sponsorship, podcast sponsorship, community sponsorship, sponsor a newsletter, content syndication, pay-per-lead, cost per lead vendor, media kit, rate card, insertion order, direct buy, publisher partnership, make-good, G2 paid listing, Capterra ads, review site advertising, sponsorship ROI, budget pacing, we underspent our budget, are our campaigns competing with each other, audience overlap, self-competition, campaign cannibalization, suppression list, exclusion list, ad frequency across channels, how many ad accounts do we have, ads in AI Overviews, AI Mode ads, ChatGPT Ads, OpenAI Ads Manager, Copilot ads, conversational ads, should we advertise on ChatGPT, can we buy our way into the AI answer, our ads are showing in AI Overviews and we cannot report on it, context hints, OAI-AdsBot, our ad landing page fails review, robots.txt is blocking our ads, our paid leads are junk, Google Ads is optimizing for the wrong leads, offline conversion import, OCI, enhanced conversions for leads, send CRM stages back to Google Ads, upload SQLs to LinkedIn, LinkedIn Conversions API, LinkedIn CAPI, Meta conversion leads, CRM to ad platform, gclid, li_fat_id, msclkid, value-based bidding, optimize for pipeline not form fills, low match rate, conversion lag.

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

The primary tool for code-navigation questions in ANY language (frontend or backend) — walk the structural graph from an entry point (page, route, handler, command, `main`) down through imports to the IO boundary (network call, query, file read). Use this skill, in preference to the Explore agent or global grep, whenever the user asks "where does X come from?", "what API/data populates Y?", "what renders or wraps the Z panel?", "which file for feature F?", "how is this wired up?", or any code-navigation question mapping a UI element, route, or feature concept to source files. Also reverse queries ("what uses /api/foo?", "who consumes this service?"). Keyword search routinely picks up unrelated flows sharing a domain word and produces wrong answers; the walk follows the actual graph. The JS/TS `walk.mjs`/`discover.mjs` are an optional accelerator, not required — the walk is language-agnostic.

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

[Code Intelligence] Use when building/syncing the code graph, querying callers/imports/tests, tracing flow, checking blast radius, linking APIs or exporting JSON/Mermaid. --mode={build|query|trace|blast-radius|connect-api|export}.

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

Store conversation history and project material locally, then search by meaning and retrieve original text. Organize memories by person or project, track dated relationships and facts, and keep diary entries that connect work across sessions.

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

• Import conversation history or project files
• Search past discussions by meaning
• Organize records by person, project, and topic

Looks up a person's identity, role, and relationship before asking the user for clarification. Searches stored knowledge and connected records, then the web, updates incomplete pages, and asks a specific question with a hypothesis when evidence remains inconclusive.

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

• Identifying contacts from existing records
• Filling role and relationship fields after imports
• Adding context to names in meeting preparation

Retrieve past work, decisions, and lessons from agentmemory using keyword, meaning, and relationship searches. It expands selected records, groups findings by session, and prioritizes important observations so earlier context can inform the current task.

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

• Recalling an earlier decision and its context
• Finding how a similar issue was handled
• Reviewing one project's or agent's history

Guide changes to the published @kortix/sdk package with rules for preserving public APIs, writing failing tests before behavior changes, keeping the core independent of frameworks, and checking package installation. It also covers exports, streaming transport, and release version handling.

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

• Adding a public SDK feature or export
• Renaming public types while preserving compatibility
• Changing streaming or transport behavior

Build and debug Python agents with Swarms, a framework for coordinating multiple AI agents. Covers tool connections, saved memory, autonomous execution, and workflow choices such as sequential steps, parallel work, specialist delegation, and combined answers.

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

• Building an agent that calls Python tools
• Coordinating sequential or parallel agent workflows
• Saving agent memory across restarts

Tone down interfaces that feel visually overwhelming by refining colors, typography, spacing, decoration, and motion. Preserve important emphasis and recognizable character while creating a calmer layout that remains readable and easy to use.

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

• Softening overly vivid colors
• Reducing competing bold text and large elements
• Simplifying excessive decoration and animation

Create PAGX vector graphics files from a visual description, HTML file, or public URL, including supported animations. Edit existing designs, check their appearance, and export them to SVG, HTML, or PPTX.

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

• Creating a poster or product card from a written description
• Converting an HTML file or public URL to PAGX
• Making an animated banner or loading animation

Compile-time dependency injection in Golang using google/wire — wire.NewSet, wire.Build, wire.Bind (interface→concrete), wire.Struct, wire.Value, wire.InterfaceValue, wire.FieldsOf, cleanup functions, //go:build wireinject injector files, and generated wire_gen.go. Apply when using or adopting google/wire, when the codebase imports `github.com/google/wire`, or when wiring an application graph at compile time via `wire.Build`. For runtime DI with reflection, see `samber/cc-skills-golang@golang-uber-dig` skill.

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

Implements dependency injection in Golang using uber-go/dig — reflection-based container, Provide/Invoke, dig.In/dig.Out parameter and result objects, named values, value groups, optional dependencies, scopes, and Decorate. Apply when using or adopting uber-go/dig, when the codebase imports `go.uber.org/dig`, or when wiring an application graph at startup. For higher-level lifecycle and modules, see `samber/cc-skills-golang@golang-uber-fx` skill.

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

Read-only audit of `.tex`, `.qmd`, or `.md` text for AI-voice tells — boilerplate transitions ("Moreover", "Furthermore", "It is important to note that"), AI-cliché lexicon ("delve", "navigate the complexities", "tapestry", "robust framework"), em-dash overuse, symmetric paragraph shapes, tricolon abuse, hedging stacking, "not only X but also Y" frames, and formulaic openers. Produces a report; does NOT rewrite. Use when user says "humanize", "does this sound like AI?", "check for AI tells", "de-AI this draft", "remove AI voice", "audit my prose for sycophancy", or before journal submission / posting a working paper.

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

Operate BurpSuite MCP Bridge for professional, authorized web testing. Use when Codex needs to inspect Burp live/history/logger/selection traffic, prioritize one target, retrieve a decisive request/response, intercept and edit a request or response before forwarding, replay one controlled mutation, manage temporary rewrite rules, import BChecks/Bambdas, export evidence, or diagnose the Windows Burp to WSL MCP connection.

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

phyloseq provides a set of classes and tools to facilitate the import, storage, analysis, and graphical display of microbiome census data.

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

Use Biome in .NET repositories that ship Node-based frontend assets and want a fast combined formatter-linter-import organizer for JavaScript, TypeScript, CSS, JSON, GraphQL, or HTML. USE FOR: biome.json or @biomejs/biome setup; fast frontend formatting and linting; replacing overlapping frontend style tools deliberately. DO NOT USE FOR: ESLint-only plugin coverage; runtime site audits such as headers, accessibility, or browser behavior. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Review and optimize application data access that uses Entity Framework Core (EF Core). Use for EF Core performance and correctness reviews of services, repositories, imports, and background jobs: slow or memory-heavy queries, excessive round-trips, hidden SaveChanges, premature materialization, dynamic query construction, result-graph tracking, bulk writes, DbContext lifetime or overlapping operations, search semantics, paging, raw SQL, and model/index coverage. Use whether or not EF Core owns the schema. For EF Core, not Dapper or raw ADO.NET.

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

Extract design tokens, text styles, and variables from a Figma design system and produce a design-tokens.json plus ready-to-use QML singletons. Use this skill whenever someone wants to pull their design system out of Figma — whether they say "export tokens from Figma", "get design tokens", "set up my design system", "read our Figma design system", "get Figma variables into QML", "pull our color palette from Figma", "import design tokens", "extract colors/typography/spacing from Figma", or similar. Trigger this skill at the start of any design-system workflow that involves a Figma source.

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

Use when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP server/skill/hook/command/rule/guide/collection/statusline), or making a platform/code change (website, registry package, MCP package, scripts). The repo has two separate review paths: a private, one-shot "HeyClaude submission gate" that decides single-file content PRs, and the shared gittensory-orb bot that posts an advisory readiness/linked-issue comment on platform/code PRs but does not itself merge or close content PRs. Unlike JSONbored/gittensory and JSONbored/metagraphed, a linked issue is OPTIONAL here — do not import their mandatory-linked-issue rule into this repo. Invoke for any "contribute to / open a PR against / submit an entry to / fix a bug in awesome-claude (HeyClaude)" task.

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