スキルを探す

Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research <topic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review.

日本語の概要は準備中です。原文の説明を表示しています。

Используй только внутри активного Codex Project Autopilot-проекта, когда data-layer уже относится к плану автопилота.

日本語の概要は準備中です。原文の説明を表示しています。

Run automatic SPICE simulations on subcircuits detected from KiCad schematic analysis — validates filter frequencies, divider ratios, opamp gains, LC resonance, and crystal load capacitance. Supports ngspice, LTspice, and Xyce (auto-detected). Generates testbenches, runs batch mode, produces structured pass/warn/fail report. Use when the user asks to simulate, verify, or validate any analog subcircuit — RC filters, LC filters, voltage dividers, opamp circuits, crystal oscillators. Also for "simulate my circuit", "run spice", "verify with simulation", "check my filter cutoff", "does this divider give the right voltage", "what's the bandwidth of this opamp stage". Consider suggesting simulation during design reviews when the schematic analyzer reports simulatable subcircuits and a SPICE simulator is available.

日本語の概要は準備中です。原文の説明を表示しています。

Используй только внутри активного Codex Project Autopilot-проекта, когда уже выбрана проектная фаза и нужен design direction по плану автопилота.

日本語の概要は準備中です。原文の説明を表示しています。

JLCPCB PCB fabrication and assembly — BOM/CPL generation, basic vs extended parts, assembly constraints, design rules, ordering workflow. Use with KiCad for JLCPCB manufacturing. Use this skill when the user mentions JLCPCB, wants to order PCBs or assembled boards, needs prototype bare PCBs and stencils, wants to know JLCPCB design rules and capabilities, or is asking about PCB manufacturing costs or turnaround times. For gerber/CPL export, stencil ordering, and BOM management, see the `bom` skill.

日本語の概要は準備中です。原文の説明を表示しています。

PCBWay PCB fabrication and assembly — turnkey/consigned assembly, design rules, ordering workflow. Alternative to JLCPCB for manufacturing. Use with KiCad. Use this skill when the user mentions PCBWay, needs turnkey assembly (PCBWay sources parts by MPN), has parts not available on LCSC, needs assembled boards with non-LCSC components, wants to compare PCBWay vs JLCPCB, or needs assembly with parts sourced globally rather than from LCSC only. For gerber/CPL export, stencil ordering, and BOM management, see the `bom` skill.

日本語の概要は準備中です。原文の説明を表示しています。

Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system. Output is live-ready — no review pass, no placeholder content, no prototype styling. Implements hub pages, section listings, article pages, and cross-linking for Blog, Guides, Learn, and Comparisons sections.

日本語の概要は準備中です。原文の説明を表示しています。

Anti-slop skill for PRODUCT UI - dashboards, data tables, forms, multi-step flows, settings, list/detail, app shells. The agent reads the surface, budgets the frame first, and ships dense interfaces that are correct at every edge case (overflow, long labels, empty/error/loading states, i18n expansion, keyboard/a11y). House-system-first; maps to Carbon/Polaris/Atlaskit/Fluent/Primer/Material3/Radix-shadcn/Ant. The counterpart to taste-skill, which owns landing/portfolio/marketing.

日本語の概要は準備中です。原文の説明を表示しています。

Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).

日本語の概要は準備中です。原文の説明を表示しています。

Use when defending the research design of an American Educational Research Journal (AERJ) manuscript — quantitative (multilevel, IRT, quasi-experimental, RCT), qualitative (case study, ethnography, interview), or mixed methods. AERJ judges each tradition on its own terms against the AERA reporting standards. Strengthens the design; it does not write code.

日本語の概要は準備中です。原文の説明を表示しています。

Use when defending the research design of an American Anthropologist (AA) manuscript — fieldwork and participant observation, interview and archival design for ethnographic/qualitative work, material/contextual analysis for archaeology, and appropriate lab/quantitative design for biological anthropology. AA judges each mode on its own terms with reflexivity. Strengthens the design; it does not write code or run fieldwork.

日本語の概要は準備中です。原文の説明を表示しています。

Use when building exhibits for an American Anthropologist (AA) manuscript — photographs, maps, site plans, artifact images, kinship diagrams, transcripts, evidence tables, and multimodal media — so they are self-contained, accessible (alt text), ethically cleared (consent, permissions), and count toward the word budget. Designs exhibits; it does not run analysis or clear permissions for you.

日本語の概要は準備中です。原文の説明を表示しています。

Use when building figures and tables for an Agricultural Systems (AgSy) manuscript so exhibits communicate interactions, dynamics, trade-offs, and model performance clearly. AgSy is a systems journal, so the best exhibits show trade-off frontiers, observed-vs-simulated fit, resource flows, and conceptual system diagrams — not just a bar chart of one treatment. Designs exhibits; it does not run the analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Use when building or trimming the exhibits of an American Economic Review: Insights (AER: Insights) short-format manuscript to the hard five-exhibit budget, one page each, no significance asterisks. Designs the minimum exhibit set; it does not run the analysis behind them.

日本語の概要は準備中です。原文の説明を表示しています。

Use when deciding which robustness checks belong in the few in-text words of an American Economic Review: Insights (AER: Insights) short-format manuscript versus the online Supplemental Appendix. Triages checks against the length cap; it does not design the identification (see aeri-identification).

日本語の概要は準備中です。原文の説明を表示しています。

Use when articulating why an Agricultural Systems (AgSy) result matters — its relevance for farm design, management, decision support, or policy. AgSy values systems analysis that informs a decision, so this is what separates an AgSy paper from a methods demo. It frames implications honestly within the model's scope; it does not over-claim or invent impact.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an AEJ: Economic Policy decision letter (R&R or reject-and-resubmit) has arrived and a response-letter strategy and revision plan are needed. Structures the response to referees and editor with policy-relevance front and center; it does not run new estimation or redesign identification from scratch.

日本語の概要は準備中です。原文の説明を表示しています。

Use when building or revising exhibits for an AEJ: Economic Policy manuscript so they meet AEA house style and carry the policy message — no significance asterisks, a self-contained headline exhibit, and figures that show the policy effect with uncertainty. Designs exhibits; it does not run the estimation or write the surrounding prose.

日本語の概要は準備中です。原文の説明を表示しています。

Use when drafting or revising the prose of an AEJ: Economic Policy manuscript — especially the abstract and introduction — to translate causal estimates into a clear policy takeaway without overclaiming. Shapes the policy-first narrative and house style; it does not design identification or build the welfare model.

日本語の概要は準備中です。原文の説明を表示しています。

Use when judging whether a research idea fits Administrative Science Quarterly (ASQ) and has the *surprising* theoretical insight ASQ demands. Sharpens the puzzle and the contribution claim; it does not design the study or write theory sections.

日本語の概要は準備中です。原文の説明を表示しています。

Use when revising the prose, abstract, and introduction of an American Economic Journal: Applied Economics (AEJ: Applied) manuscript so the design and headline estimate land in the first paragraph in AEA house style. Polishes exposition; it does not change the result (aeja-identification / aeja-robustness) or the exhibits.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an American Economic Journal: Applied Economics (AEJ: Applied) manuscript needs a model to interpret, discipline, or structure its empirical estimates — not to lead the paper. Calibrates how much theory belongs in an empirical-first journal and where it goes; it does not design the identification (aeja-identification) or build a standalone structural estimation.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an AEJ: Economic Policy manuscript's headline policy estimate needs to be shown stable and credible against specification, sample, inference, and identification threats. Organizes the robustness program by threat-to-the-policy-conclusion; it does not design the primary identification or write exhibits.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an Advanced Materials result is sound but its central advance and significance are not yet sharp, or when a Communication's opening paragraph must double as its abstract. Structures the one-advance narrative; does not run characterization or design figures.

日本語の概要は準備中です。原文の説明を表示しています。