'roles' 검색 결과

How game development works as a process — roles, subtasks, workflows and role descriptions, especially (but not only) for Roblox. Use this skill when it's about the ORGANIZATION of game dev rather than concrete code: Which roles exist (Creative Director, Engineer, Artist, Polish/Audio, Business, QA-Tester, Game Critic)? Who does which subtask? What does a development chain (concept → backend → frontend → polish → test) look like? How do you write a Game Design Document / KONZEPT.md? How do several (AI) agents divide up a game? Also trigger on "plan a new game", "create Game Design Document", "which roles do I need for my game", "development workflow for a game", "who tests the game", "structure a game idea", "Roblox genre/monetization".

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

Reduce container attack surface by building application images on Google distroless base images that contain only the application runtime with no shell, package manager, or unnecessary OS utilities.

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

Securing AWS Lambda execution roles by implementing least-privilege IAM policies, applying permission boundaries, restricting resource-based policies, using IAM Access Analyzer to validate permissions, and enforcing role scoping through SCPs.

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

프로젝트 문서 정리 요청에 맞는 전문 스킬을 선택합니다. 요청 시 문서 역할, 로컬 링크, 설계 결정 기록 색인과 근거 참조를 파일 변경 없이 점검합니다.

• 프로젝트 문서 정리 절차 선택
• 기존 문서의 정보 출처 파악
• 로컬 링크와 설계 결정 색인 점검

가정이나 소규모 실험용 네트워크에서 라우터, 스위치, Wi-Fi 장비의 역할과 배선을 정리합니다. IP 주소, DHCP, DNS를 계획해 연결 불안정과 향후 확장에 대비합니다.

• 가정용 네트워크와 장비 역할 설계
• NAS와 서버의 주소 및 이름 고정
• Wi-Fi 불안정, 이중 NAT, DHCP 중복 점검

구상이나 기존 저장소를 바탕으로 AI 에이전트의 역할, 보고 체계, 작업 인계를 정리하고 규격에 맞는 회사 또는 팀 패키지를 만듭니다.

• 구상에서 에이전트 회사를 만듭니다
• 저장소를 팀 구성으로 정리합니다
• 역할 분담과 작업 인계를 설계합니다

Analyze Git changes before submitting or merging a pull request. Assess risk and complexity, classify changes, suggest reviewer roles, and identify files needing closer inspection using diff statistics and file-level risk analysis.

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

• Assess change risks before submitting a pull request
• Review large changes spanning multiple modules
• Identify reviewer roles suited to the changes

Review HTML list structure so screen readers can identify lists and announce item counts. Find list items without valid containers, check custom accessibility roles, and guide fixes to markup used for navigation or styling.

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

• Review list markup split across components
• Fix navigation lists with invalid nesting
• Check parent roles for custom lists

Review article bylines to check that author names, roles, and biography links are clearly visible. Inspect rendered pages and related metadata to identify specific pages or templates that need clearer author information.

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

• Checking author information on blog posts
• Adding author names, roles, and profile links
• Reviewing author information in rendered HTML

Check that ARIA roles, which describe interface elements to assistive technology, include their required attributes. Identify missing state or value information in rendered HTML and get guidance on fixes and accessibility verification.

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

• Checking required attributes on custom sliders
• Reviewing shared interface components for accessibility
• Verifying state information conveyed to screen readers

Review ARIA roles, labels that tell assistive technology what page elements do, and correct invalid values. Prefer standard HTML controls where suitable, then check keyboard behavior, focus movement, and screen reader output to verify the changes.

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

• Finding invalid or misspelled ARIA role values
• Replacing custom widgets with standard HTML controls
• Reviewing accessibility in shared UI components

Plan and review systems where several AI agents work together. Assess whether multiple agents are useful, choose roles and communication methods, and define shared files, verification, and resource limits to address conflicts, spreading errors, and uncontrolled execution.

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

• Deciding between one agent and several agents
• Designing agent roles and communication
• Reviewing shared files and context boundaries

Set up Antigravity 2.0 Agent Manager alongside Antigravity IDE to coordinate parallel development agents. Assign roles and folder boundaries, review their changes in the editor, and use Git checkpoints to manage shared work.

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

• Setting up Agent Manager alongside the IDE
• Assigning frontend, backend, and QA roles
• Separating editing scopes to avoid conflicts

Plan startup hiring from pre-seed through Series A. Organize roles, reporting lines, salaries, and equity compensation, then estimate staffing costs and hiring timelines around revenue goals, funding milestones, and budget limits.

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

• Prioritizing the next startup hires
• Budgeting staffing costs, including benefits and overhead
• Planning salary and equity ranges

Plan Claude Code agent teams by choosing team size, roles, and agent types with the tools each task needs. Preset compositions cover reviews, debugging, implementation, research, security audits, and migrations, alongside display settings for local or CI environments.

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

• Choose team size and roles for a development task
• Assign separate review areas to multiple agents
• Split bug investigation across competing hypotheses

Choose an Azure role that grants only the permissions an identity needs. The skill finds suitable built-in roles, creates custom definitions when necessary, and generates CLI commands and Bicep infrastructure code for assigning the role.

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

• Choose a role for a specific set of Azure operations
• Create a custom role when built-in roles do not fit
• Generate CLI commands for a role assignment

Configure tools and skills for sub-agents before dispatching development tasks. Role presets cover implementation, planning, reviews, testing, and verification, with defined boundaries for what each agent should do and whether it may modify files.

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

• Setting tool permissions before spawning a sub-agent
• Separating implementation, planning, and review roles
• Configuring agents for review without file changes

Analyze AWS IAM access policies with boto3 and Cloudsplaining-style checks to find permissions that could grant greater access. Produces a JSON report linking risky permissions to users or roles, with severity ratings and remediation guidance.

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

• Audit AWS IAM policies for excessive permissions
• Find permission combinations that enable privilege escalation
• Trace risky policies to affected users and roles

Build or tune a monitoring pipeline that learns normal user behavior from activity logs. Use Elasticsearch or OpenSearch to score unusual activity, compare colleagues in similar roles, and combine warning signs into insider threat alerts.

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

• Building continuous monitoring for insider threats
• Scoring unusual logins and large downloads
• Comparing behavior across similar job roles

Design employee access management across multiple systems using HR records. This skill covers account changes when people join, move roles, or leave, along with role definitions, approval workflows, periodic access reviews, and cleanup of accounts left behind.

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

• Automating account changes for hires, transfers, and departures
• Finding accounts that remain after employees leave
• Reviewing overlapping roles and unnecessary permissions

Audit Kubernetes RBAC, the rules that assign access through roles, to identify excessive permissions, risky role assignments, and paths to gaining higher privileges. Review service accounts and produce findings with recommended permission changes.

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

• Reviewing access permissions in shared Kubernetes clusters
• Finding accounts that can read secrets or gain higher privileges
• Checking service account token mounts

Improve resumes for software engineering, technical product management, data, and DevOps roles. Organize technical skills, connect achievements to business results, and highlight projects in a format suited to applicant tracking systems, software used to process job applications, and recruiters.

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

• Organize technical skills for a target role
• Rewrite experience to show technical and business impact
• Choose projects to highlight during a career change

Open the hosted context-mode Insight dashboard in your default browser to access analytics for AI-assisted engineering teams, including productive rates per engineer, retry waste, blockers, and views tailored to different roles.

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

• Opening the team's development analytics dashboard
• Reviewing productive rates and retry waste per engineer
• Checking blockers and views tailored to team roles

Maps people involved in a deal or account using CRM records, communications, or supplied files. Shows roles, engagement, and stance with evidence, identifies missing decision makers and dependence on one contact, and suggests paths to new relationships.

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

• Identify decision makers and influencers in a deal
• Check whether a deal depends on a single contact
• Find introduction paths to people you have not reached