'stack' 검색 결과

Create and maintain project documents in conductor/ covering the product, technology stack, development workflow, and work units. Extract context from existing code, check document consistency before implementation, and update documentation as the project evolves.

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

• Set up context documents for a new project
• Document an existing codebase for onboarding
• Check project documents before implementation

Migrate Vue applications from Table v8 to v9 by checking table creation, rendering, and reactive state updates. Combine Vue-specific changes with the shared core migration checklist, then verify types and affected feature behavior.

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

• Upgrading Vue tables from v8 to v9
• Reviewing table creation and rendering changes
• Fixing reactive state updates after migration

Connect Table v9 state to Alpine bindings and manage pagination from application code. Explains reactive reads, getter and callback setup, shared state atoms, and why some captured values fail to follow later updates.

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

• Control pagination from Alpine state
• Display current table state in Alpine bindings
• Investigate stale values after state replacement

Manage Table v9 state in Svelte 5, including pagination controlled by application code. Guides reactive reads that update the interface, getter and callback wiring, and the distinction between tracked values and one-time snapshots.

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

• Control pagination from application state
• Show table state in a Svelte interface
• Investigate values that stop updating

Migrate Svelte tables from Table v8 to v9 by reviewing table creation, rendering, state handling, and shared hooks. The checklist also guides type checking and verification of data updates and enabled table features.

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

• Migrating Svelte tables from Table v8 to v9
• Replacing writable-store setup with runes and getters
• Reviewing rendering and state handling after migration

Manage Table v9 state in Ember so table changes reach the screen. Covers tracked properties, external atoms that hold state, controlled updates, and where values must be read for Glimmer to track changes.

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

• Fixing page numbers that do not update on screen
• Managing pagination through tracked properties
• Sharing table state through external atoms

Implement reactive state reads and external control for Table v9 in Solid. Learn where to track changes, how to manage pagination state, and how to handle updater functions or shared state correctly.

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

• Control pagination with Solid signals
• Investigate table updates that do not appear on screen
• Share table state through external atoms

Read and control Table v9 state in Preact, including pagination. Guides state subscriptions, which keep the interface updated, and externally managed state so table changes and controls stay synchronized while rerenders can be scoped to relevant values.

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

• Control pagination from Preact state
• Fix table values that fail to update on screen
• Limit rerenders to selected state

Build and review JetBrains plugin interfaces using Swing and IntelliJ Platform components. Follow concrete rules for layouts, theme colors, fonts, spacing, dialogs, and tool windows while keeping shared style values consistent.

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

• Building tool windows and settings screens
• Reviewing theme colors, fonts, and spacing
• Choosing components for dialogs and notifications

Investigate software errors, version conflicts, and API questions across official documentation, GitHub, technical Q&A, and Chinese developer communities. Results distinguish matching errors, source authority, and reported environments, giving you documented leads and next checks for debugging.

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

• Find existing reports of the same error
• Investigate package and runtime version conflicts
• Look up API usage in documentation and Q&A

Prepare and launch Autoware with CARLA on UE 5.8 through its native ROS 2 interface. Check communication topics and sensors, generate required maps, and configure either the classical stack or camera-only VAD model.

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

• Check whether a CARLA build supports Autoware
• Inspect topics exchanged between CARLA and Autoware
• Generate lanelet2 and point-cloud maps for a town

Build web application features across the interface, API, and database, with authentication, input checks, and safe data handling. The skill guides technical design, implementation, error handling, and component testing in one workflow.

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

• Building data entry and editing forms with matching APIs
• Adding authenticated profile pages
• Designing data flows from database to interface

Format long articles for blogs and newsletters with a magazine-style layout inspired by Substack and Medium. A centered text column, contrasting headings, styled quotations, and labeled code blocks give readers clear visual cues throughout the page.

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

• Formatting a long blog article
• Preparing an essay or newsletter for publication
• Laying out articles with quotations and code examples

Search GitHub, Stack Overflow, Hacker News, and HuggingFace for code examples, projects, technical answers, discussions, models, datasets, and Spaces. Filter supported searches and receive structured JSON results containing titles, links, and snippets.

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

• Find code examples and open-source projects
• Search technical answers and GitHub Issues
• Explore developer news and discussions

Add CSS animations to web interfaces using ready-made patterns for menus, modals, loading states, text changes, and more. It selects a suitable pattern, connects markup and any required JavaScript, and preserves reduced-motion support.

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

• Adding opening and closing animations to menus and modals
• Animating loading placeholders and loaded content
• Adding transitions for changing text and numbers

Investigate cloud configuration weaknesses across AWS, GCP, and Azure, including public storage, exposed services, and leaked credentials. Find candidates in public information and JavaScript, then verify data access and permissions to establish practical impact.

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

• Checking public access to S3, GCS, and Azure Blob storage
• Reviewing exposed serverless and managed services
• Assessing CloudWatch RUM guest role permissions

Add a deployable service by following a structured guide for application code, infrastructure, configuration, and related integrations. It tracks applicable steps, reports local verification results, and leaves deployment and secret creation as explicit follow-up work.

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

• Adding a Rust service or Kafka consumer
• Creating a Cloudflare Worker
• Adding a Pulumi infrastructure stack

dstack is an open-source control plane for GPU provisioning and orchestration across GPU clouds, Kubernetes, and on-prem clusters.

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

Octane bindings for TanStack DB. useLiveQuery hook with dependency arrays (8 overloads: query function, config object, pre-created collection, disabled state via returning undefined/null). useLiveSuspenseQuery for Octane Suspense with Error Boundaries (data always defined). useLiveInfiniteQuery for cursor-based pagination (pageSize, fetchNextPage, hasNextPage, isFetchingNextPage). usePacedMutations for debounced Octane state updates. Return shape: data, state, collection, status, isLoading, isReady, isError. Import from @octanejs/tanstack-db (re-exports all of @tanstack/db).

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

Build SwiftUI layouts using stacks, grids, lists, scroll views, forms, and controls. Covers VStack/HStack/ZStack, LazyVGrid/LazyHGrid, List with sections and swipe actions, ScrollView with ScrollPosition and scroll-driven reveal surfaces, Form with validation, Toggle/Picker/Slider, .searchable, and overlay patterns. Use when building data-driven layouts, collection views, paged detail reveals, settings screens, search interfaces, or transient overlay UI.

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

This skill should be used when the user asks to "dev-init", "技術スタックを選定", "新規プロジェクト初期化", "initialize tech stack", "プロジェクトをセットアップ", "setup project", "scaffold project", "プロジェクト作成", "tech stackを決める". インタラクティブなヒアリングでプロジェクトの技術スタックを決定し、dev-context互換のコンテキストファイルを生成する。承認制でプロジェクトスキャフォールディングも実行可能。

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

Fullstack development toolkit with project scaffolding for Next.js/FastAPI/MERN/Django stacks and code quality analysis. Use when scaffolding new projects, analyzing codebase quality, or implementing fullstack architecture patterns.

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

Audit a project's infrastructure and SaaS stack, then produce a cost report showing what the user currently pays and what they would save by consolidating onto Temps (self-hosted or Temps Cloud). Detects hosting platforms (Vercel, Netlify, Railway, Render, Heroku, Fly.io), analytics (PostHog, Plausible, Mixpanel, Amplitude, Fathom), error tracking (Sentry, Bugsnag, Rollbar, Honeybadger), session replay (LogRocket, FullStory, Hotjar, Highlight), uptime monitoring (Pingdom, UptimeRobot, Better Stack, Checkly), managed databases (Supabase, Neon, PlanetScale, MongoDB Atlas, Upstash, RDS), and transactional email (SendGrid, Postmark, Resend, Mailgun) from dependencies, config files, and env var names. Use when the user wants to: (1) Know how much they would save by switching to Temps, (2) Audit their SaaS/infrastructure spend, (3) Compare their current stack's cost against self-hosting, (4) Decide whether Temps is worth it, (5) Build a business case for consolidating tools. Triggers: "how much would I save", "temps savings", "cost comparison", "audit my stack", "am I overpaying", "saas spend", "calculate savings", "is temps cheaper".

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

The epistack package main objective is the visualizations of stacks of genomic tracks (such as, but not restricted to, ChIP-seq, ATAC-seq, DNA methyation or genomic conservation data) centered at genomic regions of interest. epistack needs three different inputs: 1) a genomic score objects, such as ChIP-seq coverage or DNA methylation values, provided as a `GRanges` (easily obtained from `bigwig` or `bam` files). 2) a list of feature of interest, such as peaks or transcription start sites, provi

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