개발 스킬

Assess engineering team health with frameworks such as Core 4 and DORA, then identify workflow bottlenecks and developer friction. It also helps frame technical debt as a business investment and consider how AI tools affect team productivity.

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

• Measuring delivery speed and stability
• Finding delays between code completion and deployment
• Making a business case for technical debt work

Learn to direct AI agents through software development by choosing delegable tasks, writing specific instructions, coordinating parallel work, and reviewing generated code. The skill includes frameworks and examples for planning, debugging, and using peer reviews to catch issues before deployment.

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

• Choosing engineering tasks suitable for delegation
• Writing clear prompts and project context for agents
• Coordinating parallel development and reviewing code

Turn a product idea, written requirements, or visual mockup into an interactive prototype with AI coding tools. Use it to explore a concept, test features with users, or give engineers working reference code for implementation.

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

• Exploring a product idea with a working prototype
• Testing a feature with users before full development
• Turning a screenshot or sketch into an interactive demo

Understand how `@bradygaster/squad-cli` records its version, which project files `squad upgrade` replaces or preserves, and how to check npm for a channel’s latest release. Use this knowledge to interpret upgrades and version checks.

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

• Check what a Squad upgrade will replace or preserve
• Find how the CLI records its installed version
• Look up the latest npm release for a channel

Guide changes to the Squad CLI using its established coding conventions. Covers Node.js built-ins, standard tests, readable errors, cross-platform paths, and initialization and upgrade behavior that preserves user-owned files.

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

• Modify the Squad CLI following existing conventions
• Review initialization and upgrade file handling
• Check paths for Windows, macOS, and Linux

Use this reference to determine which Squad files are authoritative, who can read or write them, and how conflicts are resolved. It helps coordinators place state correctly, check file ownership, and handle competing changes.

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

• Resolve a conflict between Squad files
• Check who may edit a file
• Choose where a piece of state belongs

Coordinate work across independent Squad installations by discovering their capabilities and delegating tasks across repositories. It guides context sharing, acceptance criteria, and progress tracking, while distinguishing persistent Squad teams from temporary groups of agents.

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

• Finding another Squad with the capabilities a task requires
• Handing off work for features that span repositories
• Tracking delegated infrastructure or support requests

Coordinate AI teams running in separate repositories by choosing a communication method for questions, reviews, task delegation, and dependency analysis. The guide explains synchronous CLI sessions, direct metadata reading, and asynchronous requests through Git or GitHub issues.

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

• Asking another repository's Squad about its architecture
• Requesting a review of a pull request across repositories
• Delegating work that should persist beyond one session

Apply a review rejection process for agent teams. It keeps the original author from revising or advising on the rejected artifact, assigns another agent to revise it, and escalates to the user if no eligible agent remains.

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

• Assign a different agent after a review rejection
• Keep revision ownership independent from the original author
• Escalate when all eligible agents are locked out

Follow Squad’s branch and release process: start feature work from `dev`, use issue-based branch names, and target pull requests to `dev`. The guide also covers parallel work with Git worktrees, coordinated changes across repositories, and promotion to preview, insiders, and stable releases.

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

• Start an issue branch from dev
• Run several repository issues in parallel with worktrees
• Coordinate pull requests across dependent repositories

Guide agents through failures with timed retries, alternative methods, targeted fixes, and clear handoffs. It also explains when to continue with partial results, helping teams choose a recovery approach that fits the problem.

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

• Retrying temporary API and network failures
• Switching methods when a tool fails
• Diagnosing build and test errors

Share a code snippet to get a plain English explanation of its purpose, the role of each major part, and the programming concepts it uses. When appropriate, the skill also points out bugs or suggests improvements, making code easier to learn, review, or document.

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

• Understand an unfamiliar code snippet
• Learn the concepts behind a function
• Prepare a code explanation for documentation

Understand existing code through a plain-language explanation of its purpose, steps, and key programming ideas. The skill can tailor the explanation to the detected language and include a sample input or output when useful, helping with learning and onboarding.

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

• Understanding an unfamiliar function
• Learning how an algorithm processes input
• Getting a walkthrough of a code snippet

Apply safe operating rules to KiCAD tasks by routing design changes through Konnect MCP tools and using exported data for analysis. The skill explains tool discovery, verification, and the limits of schematic, PCB, and library editing methods.

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

• Changing a schematic or PCB design safely
• Checking connections or exported BOM data
• Discovering available KiCAD toolsets

Prepare KiCAD projects for board fabrication by recording the fabricator’s order requirements, checking DRC evidence, and exporting Gerber, drill, BOM, and placement files. It guides artifact review and assembly previews; its rough cost estimate is only for coarse comparison.

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

• Preparing Gerber and drill files for a board order
• Exporting BOM and pick-and-place files for assembly
• Reviewing a fabrication package before upload

Use this skill to build a KiCAD PCB layout, from board outline and component placement to trace routing, copper pours, and design rule checks (DRC). It guides the workflow and helps verify changes against the live board and project rules.

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

• Placing components on a new board
• Routing signal traces and differential pairs
• Adding copper zones after routing

Build and edit KiCAD schematics through MCP tools by placing components, wiring pins, and adding net labels or power symbols. The workflow also checks connections, runs ERC, and inspects a rendered schematic for layout issues.

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

• Creating a schematic from a circuit description
• Adding components and connecting named signals
• Building common circuits such as dividers or LED drivers

Review KiCAD schematics and PCB layouts with rule checks, connectivity evidence, and design audits through MCP tools. The skill groups findings by severity, suggests fixes, and reports when incomplete checks prevent a readiness verdict.

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

• Checking schematic ERC and PCB DRC findings
• Reviewing a board before manufacturing
• Finding shorts, missing connections, or power issues

Search KiCAD libraries for symbols and footprints, then create or register custom parts when needed. The workflow checks pin and pad numbering against the exact part datasheet, helping you build reusable project libraries and verify edits before using components in a design.

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

• Finding an existing symbol or footprint
• Creating a custom component from a datasheet
• Registering a project-specific library

Use this skill when adding or changing commands in a Typer-based CLI. It provides templates for single commands, command groups, and destructive actions, plus registration steps and conventions for arguments, output, confirmations, and exit codes.

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

• Adding a single command to a Typer CLI
• Creating a group of related subcommands
• Implementing a delete command with confirmation

Review Typer CLI command implementations against a focused checklist. Check command structure, argument and option syntax, error handling, exit codes, output conventions, destructive action safeguards, and help text, then summarize findings and suggested fixes.

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

• Reviewing a Typer command implementation
• Checking error handling and exit codes
• Finding missing safeguards on delete commands

Set up a machine-level connection between Codex and the Bindry MCP server. This one-time configuration enables compiled Bindry skills to use live content, with an API key and the Bindry API base URL.

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

• Enable live mode for Bindry skills
• Connect Codex to the Bindry MCP server
• Prepare a machine for live Binder syncs

Compile skills from a Bindry Binder into a project’s Codex skills folder. Choose a pinned snapshot or live mode, and use a Binder ID, export URL, or saved export file as the source.

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

• Install skills from a Bindry Binder
• Refresh previously compiled skills
• Compile a specific published Library version

Check compiled Bindry skills against their source Binder and report which are current, stale, live, or unverifiable. This read-only check makes no edits or updates; use the sync skill separately to refresh stale skills.

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

• Check whether compiled skills are out of date
• Review version differences with a Binder
• Identify live skills that stay current