OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
A skill your agent uses when implementing, porting, integrating, reproducing, or debugging support for a model in PHYAI.
$ npx skills add mingti-org/phyai --skill phyai-model-implement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mingti-org/phyai phyai-model-implement --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mingti-org/phyai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/phyai-model-implement .claude/skills/phyai-model-implement && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "phyai-model-implement" agent skill from https://github.com/mingti-org/phyai/tree/main/.claude/skills/phyai-model-implement into .claude/skills/phyai-model-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phyai-model-implement", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mingti-org/phyai/tree/main/.claude/skills/phyai-model-implementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mingti-org/phyai --skill phyai-model-implement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mingti-org/phyai phyai-model-implement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mingti-org/phyai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/phyai-model-implement .agents/skills/phyai-model-implement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "phyai-model-implement" agent skill from https://github.com/mingti-org/phyai/tree/main/.claude/skills/phyai-model-implement into .agents/skills/phyai-model-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phyai-model-implement", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mingti-org/phyai --skill phyai-model-implement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mingti-org/phyai phyai-model-implement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mingti-org/phyai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/phyai-model-implement .cursor/skills/phyai-model-implement && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "phyai-model-implement" agent skill from https://github.com/mingti-org/phyai/tree/main/.claude/skills/phyai-model-implement into .cursor/skills/phyai-model-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phyai-model-implement", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mingti-org/phyai.git --path .claude/skills/phyai-model-implement--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mingti-org/phyai --skill phyai-model-implement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mingti-org/phyai phyai-model-implement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mingti-org/phyai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/phyai-model-implement .gemini/skills/phyai-model-implement && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "phyai-model-implement" agent skill from https://github.com/mingti-org/phyai/tree/main/.claude/skills/phyai-model-implement into .gemini/skills/phyai-model-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phyai-model-implement", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mingti-org/phyai phyai-model-implementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mingti-org/phyai --skill phyai-model-implement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mingti-org/phyai.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/phyai-model-implement .github/skills/phyai-model-implement && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "phyai-model-implement" agent skill from https://github.com/mingti-org/phyai/tree/main/.claude/skills/phyai-model-implement into .github/skills/phyai-model-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phyai-model-implement", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mingti-org/phyai --skill phyai-model-implement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mingti-org/phyai phyai-model-implement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mingti-org/phyai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/phyai-model-implement .opencode/skills/phyai-model-implement && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "phyai-model-implement" agent skill from https://github.com/mingti-org/phyai/tree/main/.claude/skills/phyai-model-implement into .opencode/skills/phyai-model-implement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phyai-model-implement", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
phyai-model-implementA skill your agent uses when implementing, porting, integrating, reproducing, or debugging support for a model in PHYAI.
Phyai Model Implement is an agent skill from mingti-org/phyai. Use this skill when implementing, porting, integrating, reproducing, or debugging support for a model in PHYAI. This includes translating architecture research into PHYAI code, adding model configuration, modeling modules, runners, schedulers, weight loading, layer reuse, focused tests, validation scripts, and implementation plans while respecting PHYAI model-development constraints.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Planning and Translation. The repository describes itself as: PhyAI is a high-performance framework for running Physical AI models (VLA, WAM, and beyond), supporting both cloud-based serving and on-device deployment. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 36a46bf. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Phyai Model Implement loads about 3.7k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 1,629 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from mingti-org/phyai at commit 36a46bf, republished under its MIT licence (© mingti-org). 1,629 words, ~3,743 tokens.
.claude/skills/phyai-model-implement/SKILL.md (or your agent's skills folder).First, carefully study the existing repositories and articles. If the user has not provided references, ask them for the relevant references before proceeding.
PHYAI uses a strict three-layer separation for every model:
modeling_xxx.py - Pure architecture definition: stateless, no KV cache, no runtime state
model_runner_xxx.py - Runtime state management: KV cache pool, condition cache, prefill/decode switching
scheduler_xxx.py - Orchestration loop: denoise loop, sampler, CFG, multi-step orchestration,
multi-GPU and multi-stage coordination
vae.py - Extra models or processing files, such as VAE, and auxiliary modelsNever:
Call relationship between layers:
Engine Plugin (main_xxx.py)
+-- Scheduler (scheduler_ws1_xxx.py)
+-- ModelRunner (model_runner_xxx.py)
+-- Model (modeling_xxx.py)Each layer calls only the layer immediately below it. Do not skip layers. A scheduler must not call
an nn.Module.forward directly; it must go through the runner.
phyai/src/phyai/models/<model_name>/
+-- __init__.py # Export all public symbols
+-- configuration_<model>.py # Frozen dataclass configuration
+-- modeling_<model>.py # Pure network architecture
+-- model_runner_<model>.py # Runtime state wrapper
+-- scheduler_ws1_<model>.py # Single-GPU scheduler; ws = world_size
+-- main_<model>.py # Engine plugin entry point; Entry subclass
+-- (optional) sampler_*.py # Diffusion or ODE sampler
NOTE: name it XxxSampler, not XxxScheduler,
to avoid conflict with phyai.runtime.schedule.Scheduler.Naming rules:
<model>_weight_remap."pi05" or "cosmos3_policy".Follow these steps in order.
configuration_<model>.py)@dataclass(frozen=True).config.json with load_config(path, XxxConfig).nested_sources class variable
to define the mapping.__post_init__, such as GQA divisibility and even head_dim.XxxConfig() can be constructed without
arguments in tests.modeling_<model>.py)Principles:
phyai.layers, such as Linear, RMSNorm, Attention, and
RotaryEmbedding.phyai.layers.attention.phyai.layers.rotary_embedding.RMSNorm or LayerNorm from phyai.layers.xxx_weight_remap(name) returns the checkpoint key to PHYAI key
mapping.phyai.layers rather than to the model
directory.Typical forward signature:
class XxxModel(nn.Module):
def __init__(self, config: XxxConfig, *, params_dtype=torch.bfloat16, device=None):
...
def forward(self, inputs, ...) -> output:
"""Run one forward pass without storing intermediate state."""phyai.weights.loader.load_pretrained(module, path, remap=xxx_weight_remap, strict=False).def xxx_weight_remap(name: str) -> str | None; returning None
means the weight is skipped.assert len(report.missing) == 0.model_runner_<model>.py)phyai.runtime.model_runner.ModelRunner, whose abstract methods are setup() and
forward().encode_condition once and reuse the result in later steps.use_cuda_graph flag.torch.compile, applied to submodules in setup().reset(), which clears per-request caches and is called at the start of each new request.scheduler_ws1_<model>.py)phyai.runtime.schedule.Scheduler, whose abstract methods are setup() and
step(request).runner.forward for a diffusion denoise loop or an
autoregressive decode loop.randn.@dataclass; include all inference parameters in the request.step() should behave functionally: given a request, return a result, and do not keep state
across requests.main_<model>.py)@Engine.register decorator.setup(args), step(request), and close().setup is responsible for loading the configuration, building the model, loading weights,
building the runner and scheduler, and warming up.step delegates directly to the scheduler.close releases all GPU resources.phyai-utils-tools package)BaseModelProcessor and implement build_preprocessor() and
build_postprocessor().phyai. phyai-utils-tools is an independent leaf package and must not depend
on the main library.phyai.layers or phyai.runtime unless a required
layer or system component is missing. If a change is needed, tell the user first.phyai/models/<model>/; do not
scatter it elsewhere.phyai.layers.params_dtype during construction.phyai/tests/; the suite requires CUDA and runs real kernels..cache/, because CI does not
have enough resources for them.conftest.py aborts collection on a machine without CUDA; layers construct on the engine
default device.target = "cuda".get_logger(__name__) from phyai.utils; never
logging.getLogger. Use logger.info_rank0(...) for rank-0-only lines, plain
logger.info(...) when every rank should log (the [rank R/W] label comes from the
formatter), and logger.warning_once(...) on per-request / per-layer paths. Do not pass a
logger or a level as an argument, and do not call print directly.get_*() getters.type: ignore. Fix the type instead of suppressing the warning.Validation must compare PHYAI against the original reference implementation, not only against shape checks or smoke tests. Keep the reference repository available locally when possible, run the same checkpoint and deterministic inputs through both implementations, and save enough intermediate tensors to identify the first layer that diverges.
Before judging final quality, align the basics with the reference repository:
# Same input: PHYAI forward vs. reference forward.
# Expected cosine > 0.99, allowing for bf16 accumulation error.
cosine = F.cosine_similarity(phyai_out.flatten(), ref_out.flatten(), dim=0)For a diffusion or flow model, compare the predicted velocity/noise/action for one fixed step
against the reference repository first. The final single-step output cosine similarity must be
greater than 0.99. If it is below 0.99, do not treat the port as validated; find the earliest
diverging intermediate tensor and fix the corresponding config, weight mapping, layout, precision,
or preprocessing issue.
# Determinism: same seed -> exactly identical output, cosine = 1.0.
# Convergence: after the denoise loop, output std should be far below noise std.After single-step parity passes, run the full PHYAI scheduler against the reference repository with
the same request and deterministic seed. The final end-to-end result should also reach cosine
similarity greater than 0.99 against the reference output, unless the reference uses a documented
non-deterministic kernel. If it cannot meet this threshold, document the exact source of drift and
whether it comes from precision, sampler implementation, preprocessing, or an intentional algorithmic
deviation.
report = load_pretrained(model, path, remap=remap, strict=False)
assert len(report.missing) == 0 # All weights have been loaded.Existing model implementations live under phyai/src/phyai/models/. Before implementing a new
model, read one complete existing model implementation as a reference.
Write code that remains friendly to later performance optimization, including but not limited to
torch.compile and CUDA graphs.
torch.compile Friendlyif tensor.item() > 0, because it causes graph breaks unless the algorithm truly requires it.torch._dynamo.mark_dynamic().forward and immediately call .to(device). Preallocate buffers in
__init__ or setup().[t1, t2, t3] followed by
torch.stack() is fine, but appending tensors to a list in a loop and then calling cat may
trigger a graph break.torch.nn.functional over custom Python loops. For example, use
F.scaled_dot_product_attention rather than a hand-written softmax plus matmul.forward. tensor.item(), tensor.cpu(), and
print(tensor) all break graph execution.forward. Preallocate torch.empty, torch.zeros, and
torch.randn buffers, then fill them in-place in forward.if self.use_xxx:
with a Python bool is acceptable; if tensor > 0: is not.contiguous() calls. Call it only when a kernel truly requires contiguous
memory.phyai.layers.attention; it
chooses flashinfer, flash_attn, or SDPA automatically.torch.cuda.synchronize() in forward. It serializes all streams unless needed
for debugging.© mingti-org, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/phyai-model-implement of mingti-org/phyai.
Open the folder on GitHubat commit 36a46bf
Phyai Model Implement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Phyai Model Implement this skillmingti-org/phyai | 129 | — | ~3.7k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 71k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Paseo Committeegetpaseo/paseo | 20k | 1 repos | ~496 | Automated safety check: Pass | Custom licence | |
| Improvefossasia/eventyay-interpretation | 1.6k | 10 repos | ~3.7k | Automated safety check: Warn | MIT | |
| Dsh Web Documentationzhu1090093659/dsh-web | 8.5k | — | ~479 | Automated safety check: Pass | Apache-2.0 | |
| Implementation Plan Creatortailcallhq/forgecode | 7.6k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
fossasia/eventyay-interpretation
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.
zhu1090093659/dsh-web
A skill your agent uses when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.
tailcallhq/forgecode
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
u-ichi/reviewable-html-workbench
Plan Mode の <proposedplan を出す直前に、計画の段階・依存関係・検証観点を一時HTMLで視覚確認したい時に使う agent-internal skill。Use this agent-internal skill to create a temporary HTML preview for a plan just before presenting…
mingti-org/phyai
Generate a local phyai environment report for debugging system, Python, CUDA/GPU, dependency, workspace package, git, and PHYAI configuration issues.
mingti-org/phyai
A skill your agent uses when the user provides a paper, arXiv link, technical report, model card, checkpoint name, GitHub repository, or local codebase and asks to research, explain, compare, or…
mingti-org/phyai
Triage and resolve review comments on a GitHub PR — fetch all comment surfaces (issue / inline / review), validate each suggestion against upstream source rather than trusting blindly, present…
mingti-org/phyai
Analyze a phyai .memory file or directory supplied by the user: parse what task/session it records, locate and inspect the referenced code repository when available, verify claims against local code…
Categories
A skill your agent uses when implementing, porting, integrating, reproducing, or debugging support for a model in PHYAI. Phyai Model Implement is an agent skill from mingti-org/phyai. Use this skill when implementing, porting, integrating, reproducing, or debugging support for a model in PHYAI.
Phyai Model Implement fits situations like: debugging support for a model in PHYAI; tasks that involve Planning; tasks that involve Translation.
Run `npx skills add mingti-org/phyai --skill phyai-model-implement -a claude-code`. Or copy the skill folder (.claude/skills/phyai-model-implement in mingti-org/phyai) into .claude/skills/phyai-model-implement in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mingti-org/phyai --skill phyai-model-implement -a codex`. Or copy the skill folder (.claude/skills/phyai-model-implement in mingti-org/phyai) into .agents/skills/phyai-model-implement in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mingti-org/phyai --skill phyai-model-implement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/phyai-model-implement, .gemini/skills/phyai-model-implement, .github/skills/phyai-model-implement and .opencode/skills/phyai-model-implement in your project.
SKILL.md names no scripts, command-line tools or credentials: Phyai Model Implement is instructions for the agent only. Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Phyai Model Implement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Phyai Model Implement: OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars), Paseo Committee (getpaseo/paseo, 20k stars), Improve (fossasia/eventyay-interpretation, 1.6k stars) and Dsh Web Documentation (zhu1090093659/dsh-web, 8.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
mingti-org (a GitHub organization) maintains it in mingti-org/phyai, which has 129 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: mingti-org/phyai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.