'technology' 검색 결과

기존 코드의 일부를 감사하고 설계 결정 기록, 구현 관행, 누락 기능, 기술 선택의 네 관점에서 문제를 정리합니다. 계획부터 테스트, 수정, 재감사까지 진행합니다.

• 인수한 코드를 검토할 때
• 개발 도중 ECC 절차를 도입할 때
• 기능 추가 전에 모듈을 재검토할 때

시장 규모 추정, 경쟁사 비교, 투자자와 기술 조사를 출처와 함께 정리합니다. 사실과 추론을 구분하고 반대 근거와 위험을 포함해 사업 판단에 필요한 제안을 만듭니다.

• 시장 진입 전 규모 추정
• 경쟁사의 특징과 시장 위치 비교
• 접촉 전 투자자 조사

시스템 구조와 기술 선택을 검토하고 구성도, 데이터 흐름, 설계 판단의 근거를 문서로 정리합니다. 성능, 보안, 향후 확장을 고려해 설계안을 비교할 수 있습니다.

• 새 시스템의 구조를 설계합니다
• 기술 후보의 장단점을 비교합니다
• 구성 요소의 관계와 데이터 흐름을 정리합니다

명세와 처리 절차를 바탕으로 시스템 구성 요소와 연결 방식을 설계합니다. 기술 선정, 데이터와 API 설계, 장애 대비 및 확장 계획을 구성도와 설계 문서로 정리합니다.

• 명세를 바탕으로 시스템 구조 설계
• 구성 요소의 책임과 API 정리
• 접속 증가와 장애에 대비한 설계

Turn product requirements and user experience plans into technical architecture with Winston, a system architect persona. Discuss technology choices and their trade-offs, with an emphasis on established tools, developer productivity, and designs that can be implemented.

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

• Turning product requirements into a technical design
• Discussing trade-offs between technology choices
• Reviewing architecture with developer productivity in mind

Analyze an existing project's folders and produce a guide explaining directory purposes, naming conventions, and file placement. Choose a tree, list, or table, and optionally include templates for adding features consistently with the project's observed structure.

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

• Creating a folder guide for new team members
• Documenting naming and file placement conventions
• Preparing folder templates for new features

Compare two versions of a project and turn migration patterns into instructions for GitHub Copilot. Document API replacements, new conventions, obsolete patterns, and validation steps so future code changes follow the same approach.

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

• Documenting framework version upgrades
• Creating rules for replacing a technology
• Preserving conventions after architectural refactoring

Set up GitHub Copilot for a new project with instructions, reusable skills, and specialized agents tailored to its technology stack. Add a coding agent environment workflow when GitHub Actions is used, plus setup and customization guidance.

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

• Configure Copilot when starting a new project
• Define shared coding, testing, and review standards
• Create reusable development skills and specialized agents

Plan X content, improve opening lines and threads, and review account performance using post data. With a focus on AI and technology, the skill supports content reviews, weekly growth plans, and HTML diagnostic reports.

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

• Finding topics for AI and technology posts
• Comparing opening lines and planning threads
• Reviewing posts and profile text

Research recommended practices for a chosen technology using official documentation and maintainer sources. Get a cited recommendation that explains version context, local project constraints, uncertainties, and the next steps for planning or implementation.

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

• Check official guidance for a chosen technology
• Research version-specific migration advice
• Gather evidence before implementation planning

Turn a Zoom integration idea into a recommended architecture and implementation path. The skill identifies the task, selects the appropriate Zoom technology, and routes requests to focused skills for authentication, meetings, bots, AI workflows, or debugging.

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

• Choosing Zoom technology for a new integration
• Planning how to embed a Zoom meeting
• Finding the implementation path for a meeting bot

Evaluate a technology adoption question, a document, or proposed approaches against project evidence and constraints. Receive a supported position with tradeoffs and uncertainty, with an optional panel that consults other models and reconciles their views.

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

• Assessing whether to adopt an external technology
• Getting an overall assessment of a document
• Comparing a supplied set of approaches

Write or refine Chinese spoken video scripts about AI technology, interview questions, and current topics. New scripts follow research and outline approval, while revisions provide specific wording changes and reasons for the edits.

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

• Writing a spoken script explaining AI technology
• Turning technical interview questions into video scripts
• Preparing a script about a current AI topic

Read current headlines from designated news websites across seven categories, including politics, business, technology, and sports. The skill extracts dates and key points, then organizes a brief digest with sources and optional links.

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

• Get a quick overview of today's news
• Read a digest focused on technology or business
• Review headlines across several news categories

Create pop-up book illustrations for educational, technology, and brand materials. The skill builds image prompts around layered paper textures, an open book, and warm colors, with optional digital effects, then checks the generated image against those visual requirements.

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

• Illustrating technology products with paper textures
• Showing learning paths as pop-up book scenes
• Presenting a brand story or product

Plan the early stages of a browser game by choosing suitable technology and coordinating gameplay, interface, assets, and playtesting. It defaults to Phaser for 2D games and routes more specific work to the relevant specialist skills.

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

• Choosing technology for a browser-game prototype
• Planning gameplay loops, failure states, and progression
• Coordinating interfaces and 2D or 3D assets

Design and review how a system is divided into modules, cohesive parts with clear responsibilities. Evaluate data ownership, communication rules, dependencies, and failure handling, and decide when to split or merge parts without assuming a particular technology.

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

• Define responsibilities and boundaries for a new module
• Review dependencies between system modules
• Clarify data ownership and communication rules

Design interfaces that combine magazine-style composition with precise technology product details. Use asymmetrical columns, expressive headlines, wide image bands, fine dividers, and restrained accent colors to shape a consistent layout, navigation, and motion style.

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

• Combining editorial composition with a technology product interface
• Arranging large headlines and wide image bands
• Unifying navigation, labels, and information modules

Build or extend an isometric action RPG, viewed from an angled overhead perspective, using web technology. Develop a playable loop covering movement, combat, rewards, progression, and saves, with staged implementation and release checks.

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

• Building a first playable action RPG loop
• Adding combat, enemies, and rewards in stages
• Organizing equipment, quests, and zone data

Select technologies for AI and machine learning features in .NET 8+ applications. Get task-specific plans or implementation guidance for structured predictions, text generation, document retrieval, tool-using agents, and running pretrained models locally or in production.

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

• Choosing libraries for classification or prediction in .NET
• Adding text generation or summarization to an application
• Designing document retrieval with source-backed AI answers

Guide web application and API security testing from technology identification and path discovery through vulnerability checks. Examine authentication, input handling, and business logic, then produce a test report and proof-of-concept scripts that demonstrate the findings.

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

• Identifying a web app's technology stack and exposed paths
• Checking authentication and session management
• Testing input handling and file uploads

Turn a feature specification into a technical implementation plan. Organizes technology choices, research decisions, data models, and interface agreements into project files, while checking that the design follows the project's documented principles.

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

• Create a technical plan from a feature specification
• Resolve open questions about technology choices
• Document data models and external interfaces

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.

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

Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business consequences that need stating in business terms. Also use to judge whether a technical plan is sound before it is committed to.

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