'development' 검색 결과

Create realistic sample data for testing, development, and demos. Specify fields, record counts, value ranges, and business rules, then receive CSV, JSON, SQL INSERT statements, or a Python generator script with validation and usage instructions.

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

• Creating test data that follows business rules
• Preparing realistic sample data for demos
• Populating a test database

Turn game design and architecture documents into epics, bounded groups of development work for individual modules. Produce scope documents and an index, showing which requirements have recorded design decisions and where guidance is missing.

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

• Turning game designs into module-level development scope
• Planning epics for a specific development layer
• Finding requirements without architecture decisions

Assess a game project's development stage by examining design documents, code, tests, and planning files. Identify gaps appropriate to its workflow, compare findings with the configured stage, and recommend next steps for different team roles.

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

• Understanding the state of an inherited game project
• Getting oriented when joining a development team
• Checking gaps before a milestone

Implement a planned game development task by gathering its specifications and design decisions, then assigning the right programming specialist. Coordinate source changes, tests where required, visual evidence, and session state for subsequent review and closure.

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

• Implementing a ready game development story
• Assigning implementation to the right programming specialist
• Collecting required tests and visual evidence

Set up and run Happy components locally, including its CLI, server, mobile app, and desktop app. The guide covers building, testing, checking logs, and separating development data using pnpm, the project's package management tool.

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

• Setting up a local Happy development environment
• Rebuilding the CLI and checking its daemon
• Running the server and app locally

Develop and fix OpenShell’s keyboard-driven terminal interface using guidance on screen structure, background data fetching, themes, and navigation. Follow existing implementation patterns to add features that fit the interface’s established behavior.

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

• Adding a screen to the OpenShell terminal interface
• Fixing log following and scrolling behavior
• Implementing background data updates

Configure OAuth, the authorization flow used for provider sign-in, with portless development URLs. It guides callback registration and authentication library settings, helping diagnose rejected domains, redirect URL mismatches, and callbacks that point to the wrong address.

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

• Setting up provider sign-in with portless development URLs
• Diagnosing redirect URL mismatch errors
• Using an owned domain when .localhost is rejected

Guide development from problem definition and planning through testing, debugging, review, and final verification. It uses test-driven development, writing a failing test before implementation, and requires evidence before reporting work as complete.

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

• Define a development goal and acceptance checks
• Implement a change starting with a failing test
• Investigate a reproducible bug through small experiments

Guides Java SDK development in Apache Beam, from finding relevant modules to building code, running focused tests, and trying examples. Also explains how to publish modified modules locally and build SDK containers.

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

• Finding the Java SDK module to modify
• Running a specific test class or method
• Checking setup with the WordCount example

Develop and verify changes to Apache Beam's Python SDK. Set up a virtual environment, run tests, build installable packages or containers, and run data processing pipelines with the modified SDK.

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

• Set up an Apache Beam Python SDK development environment
• Run unit and integration tests for SDK changes
• Build SDK packages and container images

Turn site requirements or existing content into a SITE.md project guide for the Stitch Build Loop. It records the site's purpose, visual direction, navigation, file structure, and prioritized tasks to guide successive development rounds.

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

• Organize a site brief before development
• Record site purpose and visual direction
• List completed and planned pages

Guides feature development and bug fixes through test-driven development: write a test, confirm the expected failure, then add the minimum code to pass. It also covers refactoring and checking the full test suite.

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

• Define expected behavior before building a feature
• Reproduce a bug with a failing test
• Refactor code while keeping tests passing

Guide a development team from an assigned user outcome through implementation, testing, and handoff. It covers reproducing defects, checking behavior against requirements, involving design when needed, and reporting the exact changes, verification results, and remaining uncertainty.

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

• Start implementation from the assigned user outcome
• Reproduce a defect and verify its repair
• Review delivered behavior against requirements

Guide an approved defect fix from reproduction on current main through testing and independent validation. Record evidence for each operator workflow, track change size and rollback scope, and apply review records when receipt-driven development is enabled.

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

• Reproducing approved defects before implementation
• Recording runtime evidence for CLI and lifecycle flows
• Splitting fixes by cause and rollback scope

Review smart contract projects against Trail of Bits development guidelines. Examines architecture, upgrade mechanisms, implementation, dependencies, and tests, then provides system documentation, identifies gaps, and recommends improvements in priority order with code references.

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

• Review smart contract architecture
• Check upgrade and proxy designs
• Identify gaps in specifications and documentation

Translate user needs into concise stories that explain who benefits, what they want, and why. Add Gherkin acceptance criteria—preconditions, an action, and an expected result—to support development discussions and testable definitions of success.

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

• Turning requirements into user stories
• Defining testable acceptance criteria before development
• Preparing stories for backlog refinement and sprint planning

Set up an iPolloWork development environment in a Daytona cloud sandbox and access the real Electron app through a browser. Follow procedures for connection URLs, logs, restarts, code updates, and common startup problems.

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

• Launch a cloud development environment for iPolloWork
• Operate the Electron app through a browser
• Check logs and troubleshoot startup problems

Start and monitor an Ouroboros development loop that revises project concepts and acceptance criteria, the conditions for judging completion. Run and evaluate successive generations, focus revisions on failed criteria, inspect progress, or rewind to an earlier generation.

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

• Refining a project through repeated execution and evaluation
• Inspecting progress across generations
• Rewinding a development loop to an earlier generation

Inspect a project's code, history, tests, and documentation, then ask three focused questions to recommend an AI-assisted development approach. Receive one combination of methods, reasons for the choice, and practical first steps tailored to the project.

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

• Choosing an AI-assisted workflow for a new project
• Reviewing development methods for an existing service
• Aligning specifications and tests across services

Develop and fix Nexent features by connecting written specifications, acceptance criteria, implementation, and verification evidence. Plan unit tests and appropriate staged checks, maintain their links to requirements, and fill confirmed test gaps after development.

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

• Planning and implementing features from acceptance criteria
• Fixing bugs using existing specifications and tests
• Refactoring while preserving required behavior

Sub-skill of microsoft-365-agents-toolkit. Routed expert system with 100+ micro-expert files for migrating Slack bots to Teams, cross-platform bridging, and dual-platform bot development. USE FOR: migrating Slack bot to Teams, adding Teams support to Slack bot, building dual-platform bots, converting Block Kit to Adaptive Cards, identity/OAuth bridging, deploying bots to Azure or AWS, configuring AI model providers. DO NOT USE FOR: general web development, non-bot projects, standalone Teams development without Slack (use parent skill instead).

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

Establish a repeatable local Attio development loop with sanitized fixtures, a non-production workspace, explicit mutation switches, and cleanup receipts. Use when iterating on Attio mappings or API behavior. Trigger with "Attio local development", "Attio dev loop", or "test Attio locally".

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

Create a fast local development loop for Algolia record transforms and search behavior without contaminating shared indices. Use when iterating on search code, fixtures, or client wrappers. Trigger with "Algolia local development", "mock Algolia", or "test search locally".

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

Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.

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