'pty' 검색 결과

Format gh-aw terminal output using Go struct tags, annotations attached to data fields. Set labels and section titles, format numbers and dollar amounts, omit empty fields, and render lists of records as tables.

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

• Display workflow details as aligned fields
• Show job lists as terminal tables
• Format token counts and estimated costs

Read before a js eval cell that installs a package, spawns a server or PTY, or starts a long run, and before any bun -e, script, server, CLI, test, bundle, or package-management work: this session's eval js kernel runs Bun 1.4+ (this skill is present only when it does). Bun 1.4 ships builtins that replace 15+ npm deps — check here BEFORE installing sharp, puppeteer/playwright (scraping), marked, node-cron, node-pty, concurrently, serve-static, tar, json5, fast-xml-parser, string-width. Triggers: eval js, bun, Bun.serve, bun test, bun build, bun install, bun run, image resize, headless browser, markdown render, cron, PTY.

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

Use when designing or implementing empty, first-run, no-result, offline, error, or waiting states in Apple-platform apps — every empty state explains what is missing, why it matters, and what to do next.

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

Loading, empty, and error states with AdwStatusPage and AdwSpinner — placeholder icons, titles, action buttons. Use when an app view can be empty, loading, or failed.

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

Standardizes UX states for data fetching flows (loading, error, empty, success) and complex multi-view UI patterns. Provides state machine approach recommendations, loading skeletons, error boundaries, and empty state components. Use when implementing "loading states", "error handling", "empty states", or "state machines".

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

Hermes에서 Actual Computer로 자신의 기기에 AI 모델을 실행하도록 연결을 설정합니다. 중계 서비스와 로컬 연결, 모델 선택, 응답 확인 및 오류 점검을 다룹니다.

• Actual 키로 Hermes를 연결합니다
• 자신의 기기에서 모델을 실행합니다
• 로컬 모델을 찾아 내려받고 불러옵니다

기존 디자인 체계에 따라 스마트폰부터 큰 화면까지 대응하는 UI를 구현합니다. 컴포넌트 구조와 상태 관리, 키보드 조작, 로딩 중·빈 데이터·오류 표시를 정리합니다.

• 새 페이지와 UI 컴포넌트를 만듭니다
• 스마트폰과 컴퓨터 화면을 조정합니다
• 키보드와 화면 읽기 지원을 개선합니다

빈방 상태와 재실자의 활동을 기록해 해당 방에 맞는 감지 모델을 학습합니다. 학습 후에는 사람의 유무, 자세, 호흡을 실시간으로 확인하는 과정까지 다룹니다.

• 특정 방에 맞는 감지 모델 학습
• 빈방 상태와 재실자 활동 기록
• 학습 후 사람 유무와 자세 및 호흡 확인

Check that HTML declares the correct page language and marks sections written in other languages. Find missing, empty, or invalid language tags and suggest corrections that support screen reader pronunciation, browser translation, and spell checking.

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

• Checking the language declared for a page
• Marking language changes in multilingual content
• Reviewing language settings for screen reader pronunciation

Audit or write a page’s main H1 heading. Find missing, repeated, empty, or brand-only headings, then suggest topic-specific text that naturally includes relevant keywords and stays consistent with the page title and content.

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

• Auditing page headings
• Writing H1 headings for landing pages or blog posts
• Checking CMS template output

Review iframe and frame titles so screen reader users can identify embedded content before entering it. Find missing or empty title attributes, add meaningful descriptions, and verify the changes with browser accessibility tools or assistive technology.

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

• Checking titles on embedded advertisements and social media widgets
• Reviewing missing or empty iframe title attributes
• Verifying frame identification with a screen reader

Improve the experience after signup so new users reach a useful result sooner. Review setup steps, checklists, empty screens, and email triggers, then produce a prioritized audit or a redesigned flow with a measurement plan.

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

• Investigate drop-off during initial setup
• Design a first-session checklist
• Write guidance for screens with no data

Create a specialized Claude Code subagent with Hindsight long-term memory. Start with an empty agent or import prepared documents, then equip it with knowledge pages and memory search to reuse information across sessions.

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

• Create a specialized agent that remembers across sessions
• Build an agent from prepared reference documents
• Start an empty agent and add knowledge over time

Plan a simple daily attendance register covering check-in, check-out, hours, absences, and correction requests. When requested, generate empty templates in CSV, SQL, JSON Schema, or Notion mappings to prepare records for payroll input.

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

• Designing a daily check-in and check-out register
• Clarifying late arrival and half-day recording rules
• Creating empty attendance templates for payroll input

Plan a practical equipment register for tracking serial numbers, assignees, locations, purchase values, warranties, and returns. On request, create empty CSV templates, SQL table definitions, JSON Schema, or Notion mappings from a shared field list.

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

• Setting up a laptop and equipment register
• Planning equipment returns when employees leave
• Reviewing fields needed for an asset audit

Analyzes one .NET project to plan integration tests for an Oracle-to-PostgreSQL migration. Identifies database access methods, prioritizes migration risks, and documents test cases, seed data, and coverage, including empty strings, NULL values, and timezone behavior.

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

• Identifying database access methods that need integration tests
• Prioritizing tests for Oracle-specific behavior
• Planning checks for empty strings, NULL values, and timezones

Update Pester test assertions, checks of expected results, from classic v5 syntax to v6 Should-* commands. Identify behavior changes involving booleans, empty values, and collections, then verify the suite and report conversions needing human judgment.

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

• Convert assertions in PowerShell test files
• Adopt Should-* syntax one file at a time
• Review boolean, empty-value, and collection checks

Write integration tests for core error processors by simulating API failures with a mock model. Check retry attempts, changes to conversation messages, and streamed responses, with guidance on test setup and diagnosing empty output.

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

• Check retries and message changes after API errors
• Diagnose empty output in streaming tests
• Verify unrelated errors pass through unchanged

Improve the experience after signup by identifying where new users drop off and helping them reach their first useful result. Develop setup flows, checklists, guidance, email triggers, and prioritized experiments based on activation metrics.

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

• Find where new users drop off after signup
• Design setup checklists and empty-state guidance
• Coordinate onboarding emails with in-app actions

Create and run tests for interactive command-line tools and terminal interfaces using @microsoft/tui-test. Simulate keyboard input, check visible text, and compare screen snapshots in a separate terminal environment for each test.

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

• Testing selection prompts with arrow keys and Enter
• Checking terminal screen snapshots
• Automating text entry and keyboard navigation

Update visible interfaces in Lite and but.dev using @gitbutler/ui-react. It guides component reuse, relevant design references, concise screen text, and visual checks in light and dark themes for forms, dialogs, notifications, and other surfaces.

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

• Add forms or confirmation dialogs
• Improve empty states and notifications
• Rewrite labels and hints

Build and update Kortix web screens with established interface components and reference layouts. Guides component selection for forms, lists, modals, loading states, and notifications, including replacements for deprecated components and consistent responsive page structure.

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

• Build a settings screen with existing components
• Replace deprecated interface components
• Standardize loading, empty, and error states

Test Omnigent’s Cursor SDK integration against a live local server. Build test agents, run real conversations, and check authentication, model selection, and tool connections while investigating empty responses or bridge processes left after shutdown.

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

• Test Cursor authentication and real responses
• Verify file operations and sub-agent delegation
• Investigate invalid models and empty output

Create a temporary workbench for one existing component, using realistic mock data and a grouped state switcher. View loading, empty, error, access, and other implemented states individually, with a link to each state.

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

• Comparing loading, empty, and error states in a table
• Checking displays for different roles and plans
• Inspecting layouts with realistic amounts of sample data