Skip to main content
Manusで任意のスキルを実行
ワンクリックで
mawildoer
GitHub クリエイタープロフィール

mawildoer

1 件の GitHub リポジトリにある 8 件の収集済み skills をリポジトリ単位で表示します。

収集済み skills
8
リポジトリ
1
更新
2026-06-25
リポジトリマップ

skills がある場所

収集済み skill 数が多いリポジトリを、このクリエイターカタログ内の比率と職業範囲とともに表示します。

リポジトリエクスプローラー

リポジトリと代表的な skills

ato-language
電子エンジニア(コンピュータ除く)

Use when writing, reading, or reviewing .ato files. Triggers on "what interface for X", "how to connect Y", choosing between interface types, parameter constraints, tolerance syntax, or atopile design patterns.

2026-06-25
board-design
電子エンジニア(コンピュータ除く)

Use when designing a new board or modifying board-level architecture in atopile. Triggers on new board creation, connector wiring, power rail routing, MCU peripheral assignment, or composing packages into a board.

2026-06-25
build-and-test
電子エンジニア(コンピュータ除く)

Use when building, validating, or debugging atopile projects. Triggers on build errors, "ato build", solver failures, "no parts found", package management, creating parts from JLCPCB, or debugging connectivity issues.

2026-06-25
creating-packages
電子エンジニア(コンピュータ除く)

Use when adding a new IC, component, or subcircuit to an atopile project. Triggers on creating atopile packages, sourcing parts, vendoring an existing package, or deciding whether to make a shared package vs. inline in a board. Also use when you see ato create part or are about to write a new .ato driver module.

2026-06-25
design-review
電子エンジニア(コンピュータ除く)

Use when reviewing or completing an atopile package or board design. Triggers on design review, pre-commit check, "is this ready", quality audit, finishing a package implementation, or verifying a design before build.

2026-06-25
layout-relinking
ソフトウェア開発者

Use when renaming or refactoring components in .ato files that have existing PCB layout placements. Triggers on "layout broken", "components at origin", "lost placement after rename", "relink layout", or any .ato refactor that changes component names or module structure.

2026-06-25
lsp
ソフトウェア開発者

Use when working with .ato files and you need semantic code intelligence — hover info, diagnostics, go-to-definition, find-references, or symbol inspection. Triggers on questions like "what type is this", "what members does X have", "where is X defined", "what uses Y", checking for parse errors, or understanding atopile module/interface signatures.

2026-06-25
trade-study
電気エンジニア

Use when a design decision has multiple viable options with non-obvious trade-offs. Triggers on "should we use X or Y", connector/topology/IC selection dilemmas, architecture choices that constrain downstream work, or any hard-to-reverse decision where the best option depends on weighing competing priorities. Also use when asked to write, review, or update a trade study.

2026-06-25
1 件中 1 件のリポジトリを表示
すべてのリポジトリを表示しました