개발 스킬

Handle email verification in agent signup and login flows with disposable inboxes. The skill can create an address, wait for a message, and extract an OTP code or magic link, with options for simulated mail in CI and inbox troubleshooting.

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

• Verifying a signup that sends an email
• Extracting an OTP or magic link for browser automation
• Testing email flows in CI without SMTP

Automatically simulate analog subcircuits detected from KiCad schematic analysis. Check values such as filter cutoff, divider output, op-amp gain, and resonance, then receive a structured pass, warning, or fail report with the selected simulator.

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

• Verify an RC or LC filter cutoff from a KiCad schematic
• Check a voltage divider or op-amp stage by simulation
• Review crystal load capacitance or circuit resonance

Build and query a local graph of code relationships to find connections, callers, architectural hubs, and likely change impact. It can reduce repeated repository navigation for large, tangled codebases; its benefit depends on project size and structure, and it does not replace reasoning about design or performance.

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

• Mapping an unfamiliar codebase
• Finding what connects two code areas
• Checking callers and change impact

Review pull requests or staged code changes for correctness, security, edge cases, error handling, duplication, and complexity. It reports findings above its confidence threshold and returns an APPROVE, REQUEST CHANGES, or COMMENT verdict with suggested fixes.

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

• Review a pull request before merging
• Check staged changes for security and logic issues
• Get a verdict with confidence-rated findings

Build mobile apps locally and prepare them for App Store or Google Play submission. The workflow uses fastlane for builds and releases, checks metadata and device behavior before submission, and monitors staged rollouts for crashes.

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

• Preparing an iOS app for TestFlight or App Store review
• Building a signed Android release for Google Play
• Checking app metadata and device behavior before submission

Simplifies code, plans, and systems while preserving required outcomes and constraints. For code, it measures per-function branching complexity, records changes, and adds a regression gate to the project’s normal verification path.

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

• Reducing complexity while refactoring code
• Removing dead code or guards that no longer serve a purpose
• Simplifying a roadmap or process without dropping requirements

Within an active Codex Project Autopilot project, turn discovery or approval inputs into a scoped implementation plan. Compare minimum, balanced, and expanded options, recommend one in plain language, and record deliverables, acceptance criteria, risks, and needed manual steps.

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

• Planning implementation after project discovery
• Comparing three scope and effort options
• Choosing a practical technology stack for an MVP

Start new work by classifying the request, researching and verifying an approach, then defining scope and success checks. For resumed work, validate a handoff or checkpoint manifest, compare it with the current repository, and prepare bounded context for continuing at the right phase.

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

• Scope a new feature or bug fix
• Research and verify an implementation approach
• Resume work from a checkpoint manifest

Use this skill as a practical guide when creating or maintaining a Julia package. It covers package layout, public APIs, multiple dispatch, type design, formatting, performance measurement, error handling, and documentation practices.

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

• Organize source files and a package entry point
• Design Julia APIs and types using multiple dispatch
• Format code and measure performance with Julia tools

Review a branch against the project’s `.archcore/` records by checking whether changed code matches its documents and whether changed documents match the code. It reports which side is out of date, checks related plans and closeout, and can audit documentation gaps or stale records.

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

• Reviewing a branch before merging
• Checking whether project documents match changed code
• Auditing stale records and documentation gaps

Implement backend logic and integrations within an active Codex Project Autopilot project, following its approved plan. The skill validates inputs, handles errors and logs, and records implementation progress and required environment secrets for the next handoff.

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

• Implementing backend work from an approved Autopilot plan
• Wiring an integration with clear error handling
• Validating inputs and documenting required secrets

Design the data layer for an active Codex Project Autopilot project when its plan calls for one. The skill first checks whether a database is needed, then documents entities, ownership, access controls, and a maintainable schema or migration plan.

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

• Designing a data model within an Autopilot project
• Checking whether a planned feature needs a database
• Documenting entity ownership and access rules

Builds frontend interfaces inside an active Codex Project Autopilot project, following its approved plan and design direction. It implements responsive screens, covers key UI states, checks specified widths, and records implementation handoff details.

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

• Building a planned frontend screen in an active Autopilot project
• Implementing responsive layouts and key UI states
• Recording routes, backend placeholders, and checked screen widths

Review code for five common quality concerns: input validation, edge cases, error handling, duplication, and complexity. It also checks whether automated quality gates produce trustworthy evidence, helping identify issues that need fixing before a change is ready.

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

• Review an implementation for common defects
• Check API input validation and error handling
• Find duplicated or overly complex code

Audits repository instruction files used by Claude Code and Codex, reports missing, generated, stale, or conflicting states, and can create a missing adapter from a declared source after confirmation. It preserves conflicts and records source and output provenance.

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

• Auditing CLAUDE.md and AGENTS.md status
• Generating a missing instruction adapter
• Checking for stale generated governance files

Investigate bugs by reproducing the failure, testing possible causes, and tracing the root cause before proposing a fix and regression test. For refactoring, map dependencies, coupling, risks, and affected files into a change plan.

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

• Tracing an error from its visible symptom to the root cause
• Narrowing down a flaky test or intermittent failure
• Planning a refactor by mapping dependencies and risks

Run a structured development workflow that compares approaches, implements against tests, applies adversarial quality checks, and measures outcomes. It records findings and can revise the approach when experiments reveal brittleness or unmet expectations.

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

• Comparing implementation approaches before coding
• Iterating on code with tests and quality gates
• Checking a change for edge cases and security risks

Build small, reliable automation scripts or workers within an active Codex Project Autopilot project, following its plan. The output includes execution logs and updated project state, with dry-run support for side effects and retries for external I/O when needed.

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

• Implementing an automation task in an active Autopilot project
• Adding a dry-run preview before actions with side effects
• Recording script actions and failures in an execution log

Set up Archcore for a repository by wiring supported host configuration and preparing an initial knowledge base from existing authored context and code. Import mode converts project documents, while refresh adds newly discovered facts or focuses on a domain; changes are previewed before confirmation.

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

• Setting up Archcore on a fresh clone
• Importing agent instructions, ADRs, and repository docs
• Refreshing Archcore after new project facts appear

Use this skill to assess code structure, module boundaries, dependencies, and interface stability before proposing changes. It helps keep designs aligned with existing patterns and favors small changes that reduce coupling and make future work easier to manage.

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

• Reviewing module boundaries before a change
• Reducing dependencies and coupling
• Checking whether an abstraction is premature

Manage an electronics project's bill of materials from schematic review through sourcing and order preparation. It identifies missing part data, coordinates distributor lookups, records validated details in KiCad properties, and exports tracking or fabrication files.

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

• Finding missing part numbers and sourcing details in a schematic
• Comparing distributor stock and pricing for a target quantity
• Exporting a BOM or distributor order files

Search DigiKey by keyword or manufacturer part number to review specifications, price, and stock, and download datasheets. It can also sync a local datasheet folder from a KiCad schematic or a batch MPN list, tracking downloads in a manifest.

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

• Look up a component by name or MPN
• Check product specifications, pricing, or stock
• Download a datasheet for a selected part

Audit a project or learning workflow for scope drift, conflicting plans, inconsistent names, and code quality concerns. The skill reads project files and code, then reports evidence, severity, and suggested next steps without changing files.

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

• Checking whether project work has drifted from its agreed scope
• Finding conflicting plans or inconsistent naming
• Reviewing code against project decisions without editing it

Investigate a reproducible bug, test failure, or unexpected page behavior, then make a narrowly scoped fix. The workflow calls for a regression test before changing code, verifies the fix, and reports remaining risks and evidence while avoiding unrelated refactoring or feature work.

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

• Finding the cause of a failing test
• Fixing an unexpected page or feature behavior
• Adding a regression test before a minimal code change