'java' 검색 결과

Inspect suspicious PDFs without opening them in a reader. Use PDFiD, pdf-parser, and peepdf to examine internal objects, extract scripts, embedded files, and URLs, and document how the suspected attack works.

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

• Triage suspicious PDF email attachments
• Investigate embedded JavaScript and automatic actions
• Extract embedded files and external URLs

Helps build JavaScript and TypeScript projects with Bun, covering setup, package management, testing, and bundling code for distribution. It also guides migration from Node.js and use of Bun’s built-in APIs.

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

• Start a JavaScript or TypeScript project with Bun
• Migrate an existing Node.js project to Bun
• Set up tests and production builds

Apply consistent coding practices across TypeScript, JavaScript, React, and Node.js projects. Get guidance on naming, types, error handling, API design, file organization, and tests to make code easier to read and maintain.

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

• Aligning coding conventions across a team
• Refactoring long functions and deeply nested code
• Reviewing React components and state updates

Extract code and resources from installed Electron apps to inspect how they are built. Restore original files when source maps contain them, or format compressed JavaScript for easier reading. Supports app discovery on macOS and Windows.

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

• Inspecting code bundled in an Electron app
• Restoring source files from source maps
• Formatting compressed JavaScript for reading

Build custom calculation and parsing tools that an n8n AI Agent can call. This skill covers JavaScript or Python inputs, structured arguments, string results, tool descriptions, and fixes for invocation and output errors.

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

• Adding a calculation tool to an AI Agent
• Defining typed inputs for multiple arguments
• Fixing tool output type errors

Apply Apache ShardingSphere’s written coding standards during implementation or review, covering naming, Java constructs, tests, and Maven dependencies. Also audit a specified scope without editing files, combining automated checks with manual inspection of applicable rules.

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

• Check changed code against written repository standards
• Review Java naming and declaration conventions
• Verify changed Maven dependency declarations

Automate browser tasks such as reading JavaScript-rendered pages, filling forms, clicking through workflows, and taking screenshots. Maintain login sessions, manage separate browsers, and capture network responses, with approval checks for sensitive actions.

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

• Extracting content from pages that use JavaScript
• Automating form entry and page navigation
• Checking page appearance with screenshots

Create a coordinated set of video covers in 3:4, 16:9, and 4:3 formats from AI or Java scripts. Choose illustrations featuring a consistent presenter character or text-only layouts with white titles and yellow keywords.

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

• Creating matching vertical and horizontal video covers
• Making text-only covers with white and yellow lettering
• Keeping the same presenter character across covers

Inspect website responses with curl, using browser-like request headers and checking file size, content, and format. Identify placeholder pages and choose a browser-based or direct API approach when the expected content is missing.

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

• Investigating downloads that contain no page content
• Checking whether a response is HTML, JSON, or PDF
• Fetching pages that vary by browser identification

Build custom calculation and parsing tools that an n8n AI Agent can call. This skill covers JavaScript or Python inputs, structured arguments, string results, tool descriptions, and fixes for invocation and output errors.

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

• Adding a calculation tool to an AI Agent
• Defining typed inputs for multiple arguments
• Fixing tool output type errors

Analyze TypeScript and JavaScript code for reusable design structures known as GoF patterns. Get detection reports, quality scores, and prioritized refactoring suggestions that account for the frameworks and libraries already used in the project.

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

• Find existing design patterns in a codebase
• Plan refactoring for complex conditionals
• Evaluate the quality of a pattern implementation

Diagnose and improve slow web interfaces by measuring loading, rendering, interactions, and animations. The skill addresses images, JavaScript bundles, page layout, and network requests, then compares before-and-after results to verify improvements across devices and connection speeds.

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

• Reducing slow initial page loads
• Improving sluggish scrolling and animations
• Reducing image and JavaScript download sizes

Review regular expressions used to detect errors in agent engines. Check for empty matches, test patterns against real logs, and add safeguards against repeated matches that can cause JavaScript loops to hang.

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

• Review new error detection patterns
• Test patterns against empty strings
• Check detection using real error logs

Investigate cross-site scripting, where untrusted input executes as JavaScript in a web page. Check reflected, stored, and browser-side cases, distinguish escaped output from executable content, and validate reproducible behavior and user impact before reporting.

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

• Checking how search terms and URL parameters appear in pages
• Testing stored content in wikis and profile fields
• Reviewing JavaScript paths that insert input into pages

Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns. Triggers: "CosmosClient java", "CosmosAsyncClient", "cosmos database java", "cosmosdb java", "document database java".

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

Azure Monitor OpenTelemetry Exporter for Java. Export OpenTelemetry traces, metrics, and logs to Azure Monitor/Application Insights. Triggers: "AzureMonitorExporter java", "opentelemetry azure java", "application insights java otel", "azure monitor tracing java". Note: This package is DEPRECATED. Migrate to azure-monitor-opentelemetry-autoconfigure.

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

Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Triggers: "PersistentAgentsClient", "persistent agents java", "agent threads java", "agent runs java", "streaming agents java".

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

Guide for upgrading Java projects between major versions (8→11→17→21→25). Use when user says "upgrade Java", "migrate to Java 25", "update Java version", or when modernizing legacy projects.

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

Use when you need to generate or improve Java project documentation — including README.md files, package-info.java files, and Javadoc enhancements — through a modular, step-based interactive process that adapts to your specific documentation needs. This should trigger for requests such as Improve the code with documentation; Apply documentation; Refactor the code with documentation; Generate README or developer documentation for a Java project; Document Java APIs architecture or project workflows. Part of Plinth Toolkit

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

Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast principles, handling thread interruption correctly, documenting exceptions with @throws, enforcing logging policy, translating exceptions at API boundaries, managing retries and idempotency, enforcing timeouts, attaching suppressed exceptions, and propagating failures in async/reactive code. This should trigger for requests such as Exception handling; Use try-with-resources in Java code; Create exception chaining in Java code; Apply fail-fast validation in Java code; Review Java exception taxonomy and propagation. Part of Plinth Toolkit

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

Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory; Inventory Java cursor rule skills; List available Java system prompt skills. Part of Plinth Toolkit

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

Use when you need to refactor Java code for high performance — including memory/allocation reduction, CPU hot-path optimization, and syntax/API/control-flow improvements. This should trigger for requests such as Review Java code for high performance; Optimize Java hot path; Reduce Java allocations; Improve Java latency/throughput. Part of Plinth Toolkit

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

Use when you need to review, improve, or refactor Java code for type design quality — including establishing clear type hierarchies, applying consistent naming conventions, eliminating primitive obsession with domain-specific value objects, leveraging generic type parameters, creating type-safe wrappers, designing fluent interfaces, ensuring precision-appropriate numeric types (BigDecimal for financial calculations), and improving type contrast through interfaces and method signature alignment. This should trigger for requests such as Review Java code for type design; Improve type design in Java code; Fix primitive obsession in Java code; Create value objects in Java code. Part of Plinth Toolkit

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

Use when reviewing, improving, or refactoring Java object-oriented design, including applying SOLID, DRY, or YAGNI; improving classes and interfaces; correcting encapsulation, inheritance, or polymorphism; resolving God Class, Feature Envy, or Data Clumps; and improving object creation, methods, or exception contracts. Triggers include review Java OOD, refactor Java OOD, improve Java OOD, fix OOP misuse, and identify Java code smells. Part of Plinth Toolkit

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